Investing in new technology for your nonprofit opens up a wealth of possibilities. With the right tools, you can go from spending hours tracking down the right data to accessing it in minutes. Or, you can level up from confusing, disorganized fundraising events to streamlined auctions that excite and engage your guests.
But whether you’ve decided to invest in auction software or a new constituent relationship management (CRM) system, implementing new technology can be a challenge. That’s why it’s crucial to create a detailed implementation plan that will keep you on track and ensure the process goes smoothly. To do so, follow these steps:
We’ll cover each step in detail so you can make all the right preparations to embark on your technology journey with confidence. Let’s get started.
Start by thinking about why you chose this technology to begin with. Ask yourself these key questions:
Use the answers to these questions to define your vision for your new technology. Outline what the software will do for you, which teams will benefit from using it, and what results you’d like to achieve in the long run. This will help your team and any external parties understand the reasoning behind the switch and your implementation’s key focus areas.
For example, say that you sought out marketing automation software because your team was spending too much time writing and sending emails that didn’t convert. You might decide that your goals for the new software are to reduce team time spent on email by 50% and improve your email marketing conversion rate by 10%. With these goals in mind, your implementation team prioritizes the software’s email automation features and spends less time on social media automation.
Once you’ve outlined your goals, determine who will take the lead on implementing your new technology and who else should be involved in the process. Depending on the scale of the implementation, you may need a large team or only a few key players.
At a minimum, your implementation team will likely include:
For larger organizations, consider including one staff member from each team that will be using the software, such as your fundraising and marketing teams. Make sure to outline specific roles and responsibilities for each team member, and take into account how much time each person will be able to commit to the implementation.
When hiring outside consultants, be sure to evaluate your existing resources and budget beforehand. Do research to discover which consultant would be the best fit, and consider seeking out technology grants for nonprofits that can cover software and implementation costs if needed.
Next, estimate how long each aspect of your software implementation will take. Keep in mind that this is an important step regardless of your project’s scale—even if the software you’re implementing is more basic, you’ll still want to schedule time to add your data, fix any issues, and train your team before moving forward.
Break up your timeline into stages, and outline an estimated length of time for each stage. For example, Redpath’s Salesforce for Nonprofits implementation guide breaks up a Salesforce implementation into these five phases:
Adjust your timeline based on the complexity of your software, any existing deadlines, and team member availability. For example, if you’re hosting a major fundraising event in December and will need to use your new software to send out event communications, plan your timeline so that every stage will be completed by November.
Try to set more generalized time periods rather than specific dates when possible. That way, you leave enough room to handle any unexpected hurdles that come up.
Finally, plan how you’ll document your implementation process and communicate details to the rest of your team. Keeping accurate records of the implementation’s progress, issues, and training process will help you update and train anyone who gets added to the project later. You can also use these notes to guide future technology implementations.
To outline a communication plan, decide who will need to be informed about the technology and when. This might look like:
It also helps keep everyone on the same page if you outline how team members working on the implementation will communicate with each other. For instance, they might communicate via email on a daily basis and meet to discuss the project once a week.
Your implementation plan should provide a solid structure for your team to keep everyone on track, but it doesn’t have to be set in stone. Adjust the plan as you go along if you find that a certain stage is taking longer than anticipated or you run into bumps in the road. No matter what, you’ll have a solid foundation to guide you.