<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=657107854491317&amp;ev=PageView&amp;noscript=1">
bad-software-selection-hero

Oscar's Terrible, Horrible, No Good, Very Bad Software Selection Process

If you're like me, you probably belong to several nonprofit-oriented social media groups, discussion forums, and listservs. These communities provide a much-needed space for conversations and advice about the many things that pop up regularly in the life of a nonprofit accidental techie:

  • Email display issues
  • Social media posting issues
  • Digital engagement strategy
  • Website challenges
  • Campaign victory stories
  • Google Ad Grants and Google Ads struggles
  • A staffer who just quit and no one else has the passwords
  • House file cleanup support

There's one type of post, though, that I see multiple times a day in every one of these groups that just drives me bonkers. Not surprisingly, it has to do with nonprofit software — CRMs, email marketing programs, event management systems, and the like. For our purposes here, let's just call the prospective software "Platform Banana."

Has Anyone Ever Used Platform Banana?

It's an innocent enough question. An accidental techie who is searching for new software wants to hear the good, the bad, and the benign. This is all part of doing due diligence when you're evaluating nonprofit software, right?

Sort of.

Here are the typical responses I see when someone posts that question:

  • Love it.
  • Hate it.
  • Have you considered Platform Pumpkin?
  • Bad customer service.
  • Great customer service.
  • I work for Platform Banana and would love to speak with you.
  • Too big and too expensive.
  • Too small and too expensive.
  • Have you considered Platform Raspberry? It's free!
  • I work for Platform Pumpkin and would love to speak with you.

Not so helpful. Perhaps even harmful. Just ask Oscar.

drawing of small people interacting with a large signpost with arrows 1 and 3 pointing left and arrows 2 and 4 pointing right

A Cautionary Tale

Oscar and I have worked together on and off for years. He is the development and events manager at a national cause and cure organization. And he's pretty darn savvy about data and technology. In 2017, his team needed to find a replacement for their legacy online fundraising and email marketing system. The software they were using was no longer being supported by the vendor, and the product was rapidly becoming outdated and buggy.

Being a well-connected professional, his first step was to ask his peers. These were people he knew and whose opinions he trusted. Oscar asked them what platform their organizations used for fundraising and email marketing. He asked them how they liked using it. He also asked about cost and customer service. He contacted the vendor whose product was mentioned in glowing terms, and after seeing a product demo, Oscar signed a three-year contract.

And Then It All Blew Up

The implementation went well … for the first three weeks. At the four-week mark, Oscar was starting to feel nervous. There was a running list of functionality requirements that were either problematic, out of scope, or just plain impossible. Some of them were critical to hitting his annual fundraising goals. Here are the things that showed up on Oscar's list:

  • Limited ability to style new donation forms with the organization's brand
  • Manual file import/export was the only way to integrate with the existing CRM
  • No ability for supporters to log in and manage their demographic or gift info
  • Email tool didn't support targeting by zip code
  • Lack of native social media integration

As his list of issues grew longer, Oscar frequently thought about the peers who had told him they were so happy with this same system. Why wasn't he as happy as they were? Was there something wrong with him or his team?

While he secretly wanted to blame the software vendor, Oscar knew that most of this was on his shoulders. He hadn't told the vendor about his detailed needs — the requirements were uncovered over the course of the implementation project.

Opinion Without Context Is Dangerous

Easy access to user opinions and ratings can be great. Going out to dinner and looking for a new restaurant? Don't make reservations until you've checked the reviews.

But investing time and money in a piece of software is very different from buying dinner. If your entrée is a dud, you're out $30, and you can try another restaurant tomorrow. If you pick the wrong system, it's a really big deal.

When Oscar circled back to his buddies to share his experience and compare notes, he realized something he hadn't known before — the troublesome requirements on his list weren't universal!

His peers didn't need targeting by zip code, and they were satisfied with the level of branding they could put on donation forms. While some of his colleagues had similar needs, most were very different.

The Right Time for Opinions

I've heard stories just like Oscar's time after time. Many of my clients work with me because they've picked their technology just like he did — with the best of intentions and a poor process. They are delighted to learn there's a better way to approach technology selection that minimizes the risk of picking the wrong platform.

There are five discrete stages in a decent software evaluation process.

Stage One: Identify the Problems

Make a list of everything that's painful or broken or can't be done in the current software. Ask yourself: Would a new system fix these things? If the solutions you need are different (example — we need more training) don't look around for a replacement product just yet. Invest your time and money in the right places.

Stage Two: Document Your Requirements

If you made it past Stage One and you know it's time to move into something new, your job is to write down everything you need a new system to do. Decide which functionality is a priority (example — we need donors to log in and update their info). Oscar skipped this step, and it really tripped him up — he didn't understand enough about his requirements to make sure new platforms were able to meet them.

Stage Three: Manage the Demo Cycle

It's time for some test drives. Check out some software vendor websites and measure their systems against your requirements. Share your pain points, requirements, and budget with three or four vendors. Watch their system demos. If there's something you don't understand, ask questions. Not sure what to ask? Read this post for tips!

Stage Four: Gather Data About the Finalists

You know what you need, and you've seen the software in action. You've narrowed the field to one or two systems — and it's finally time to ask folks about their experiences. Now you can go forth and solicit opinions from peers, contacts, and random strangers on the Internet. The vendor should give you three or four references to contact. Please contact them. You may also want a second demo of each system.

Stage Five: Purchase the Software and Prepare for Implementation

You've used a solid process to get here. Now you've made the decision and are going to sign the paperwork. Read through that contract before you sign it. Make sure you know what you are buying. Assemble your internal project team and work with the implementation partner to put together a manageable plan for system setup, launch, and training.

Get References at the Right Time

Yes, Oscar had skipped the most important part of the selection process  — defining his functionality and integration requirements — and had gone straight to gathering references. Once his new system was set up, he had to limp along for two years in a platform that wasn't a great fit for his needs. And that's not all. He needed to sell his leadership team on making the financial investment for a move to another system. Because he picked the wrong one. Yuck.

That's why when people post the question "Has anyone used Platform Banana?" in nonprofit forums, I cry a little. Because it's a sure sign that they probably haven't gone through a decent software evaluation and selection process. And they are going to be unhappy with the outcome.

The moral of the story? Don't be like Oscar. Spend the time upfront to define your needs and save the opinion gathering for another day.

This post is republished with permission from Maureen Wallbeoff's blog. Maureen is a nonprofit digital strategist and technology coach. In addition to her work with clients, she has authored two guides on nonprofit engagement software, blogs at her website, and answers questions live every Friday afternoon on her Facebook page. A regular contributor to nonprofit industry media channels, Maureen has led workshops all over the U.S. and Canada and is one of Idealware's expert trainers.

BROWSE FUNDRAISING SOLUTIONS

Additional Resources: Software Selection