Nonprofit Technology Project Management Tips for a Smooth Ride

It’s quite a trip to go down the road of getting a new website, CRM, or other system. All too often, nonprofit technology projects are like taking a cross-country road trip riding in an Indy 500 race car: driving into curves so fast the wheels come off the ground and screeching into turns as your body is rocked from one side of your seat to the other. While that might be thrilling, it’s not really the kind of trip you would want for a technology project. However, if you have the right implementation partner in the driver’s seat they will take you to your destination safely, without the daredevil stunts. There are also some things you can do to help keep your next nonprofit technology trip smooth. Here are 4 nonprofit technology project management tips.

Put someone in the passenger’s seat

First things first: It’s critical to have at least one person inside your nonprofit who can be the primary navigator, holding the project, timelines, and information gathered from others. So, assign an internal Project Manager to be in the passenger’s seat where they can see what’s coming up while your consultant is in the Driver’s seat. If it’s too much for one person to dedicate that kind of time, assign two and they can switch off as needed.

Allow time for test driving

Going through a big technology project impacts staff in many different ways. Hold back on other large initiatives where you can. Make sure the team is given time to take test spins, provide feedback, check to see if the system is designed in a way that works for them, and to get the training needed to build confidence in the new technology. After all, they will be the drivers once the initial trip is completed. This critical piece will keep your staff from feeling like they are in a race car too.

Plan to learn new things

New technology always comes with learning curves. Sometimes they are hairpin turns, but even gradual shifts require adaptation. Either way, new information will need to be learned. Your driver (partner!) is there to help you. A good driver will be specific about their plans, and each little piece of information will serve the greater purpose of having a brand new system that works the way you need it to. The Project Manager at your org must keep and store the information they’ve been taught in order to drive off into the sunset with a clean and well maintained system for years to come.

Communicate with your driver

While you’re riding along, enjoy the scenery, but make sure you are paying attention so you can advise the driver. Your driver knows where you want to go and can get you there, but there are multiple routes to take. Input via email and conference calls are required to make sure you get to the destination you intended. The Project Manager needs the capacity to have these valuable and defining conversations. This is especially important for getting to your destination on time. A quick response keeps the project moving.

Follow these guidelines for nonprofit technology project management and your next project will be more like cruising down a country road, enjoying the scenery, in a sporty car with the top down. It will still be exciting and thrilling with some unexpected turns, but it won’t be death defying.

For more great tips on how to have a successful, smooth, nonprofit technology project, download our Guide.