Scary Stories of Nonprofit Technology Projects

Do you have scary stories of nonprofit technology projects from the past? Does it make the hair on your neck stand up every time you think about using a particular system? Are you terrified at the very idea of adding a new tech tool at your organization?

How many nonprofits could sit around a campfire and tell stories of implementations gone wrong? Look at the cobwebs gathering on the brand new database that no one is actually using, the zombie employees endlessly reconciling data between disconnected systems, and the vampires draining away your day with endless manual processes. These stories make our skin crawl because we all know that these challenges lead to wasted time and donor dollars. We’ve noticed a common ghastly theme among nonprofit organizations who experience these terrors; they prioritized speed in their decision-making and implementation process.

It’s understandable to want your CRM or website to be up and running ASAP. Sometimes we wish we could cast a spell to make it happen faster, but there are three really important reasons to slow it down and take more time.

The Past Can Haunt You

When you’re choosing to implement a new system, or revamp one that’s already in place, it can be tempting to try and replicate all of your current processes and workflows… including ones that aren’t actually serving you any longer. It’s natural for your processes to be somewhat dictated by the tools you use, over time, but it’s important to take a step back and notice where that’s happened. That gives you the chance to rethink and revise, rather than just sticking with “the way you’ve always done it.” This takes time! But it’s the only way to break free from old habits and ensure you’ll actually get the most value out of your new technology.

The Devil’s in the Details

We have had many clients who come to us just a year or two after implementing a new system, already needing to make a significant change. Most of the time it’s because they missed some essential details the first time around, and quickly discovered the new tool wasn’t actually supporting their needs. Maybe it lacked certain critical features or reporting capabilities, or maybe they didn’t take enough time at the beginning to clean their data or conceptualize permission sets. To ensure your organization gets a long-lasting solution, it’s imperative to think through the details and start from a solid foundation.

There’s Safety In Numbers

It’s easy to focus solely on a set of features and functionality, and not the actual process of adopting a new system. All too often, technology systems sit around gathering dust because key people at the organization were left out of the loop when the change was made. Yes, it takes time to schedule group training sessions and get feedback from a wider swath of users, but these steps can make all the difference when it comes to the ultimate success of the project.

We find that clients who really engage the whole organization in the implementation process have much greater adoption rates. It doesn’t happen overnight, but a collaborative approach gets better results, every time.

Your story doesn’t have to be a scary one!

Taking the time to question your assumptions, think through the details, and make implementation a group endeavor are the keys to avoiding scary stories about technology. Don’t create technology nightmares that will come back and haunt you for years by rushing through your next technology implementation.
Want to get a jump on thinking ahead? Download our free Nonprofit Guide to Preparing for Successful Technology Changes with 6 steps for a smooth and easy start to finding your next technology solution.