When a foundation or nonprofit updates its software system, the purchase typically requires years of research and a financial investment that can run well into six figures. So, it’s important to make the most of that purchase. The most effective way to do that is to use system upgrades as an opportunity to reexamine internal processes
That kind of self-reflection allows the organization to get the best return on their investment, while following best practices for a software purchase. In fact, in a recent Innovation Process Design survey, 100% of participants said process design is essential when adding new software. By maximizing internal processes, organizations can get employees out of the back office and back to serving their communities.
“It’s important to have a high-level outlook of what outcomes drive the process and not be married to current processes in order to achieve the same result in a more efficient manner,” wrote one respondent.
“I can’t imagine how you can put in new software without reimaging the process,” wrote another.
In all, 24 philanthropic and nonprofit organizations completed the survey. Approximately half of respondents were financial leaders. The other half were grantmakers and technology leaders. Most respondents — 80% — had recent experience implementing sizable new software projects.
Exactly what reimaging should look like depends on the type of project in question. If your software installation is small or low risk, following vendor best practices or holding internal discussions may be enough. Larger or more involved projects may require an outside coach to lead the process or provide redesign training.
Wondering where to start? Here are a few key questions to answer before you complete your next software purchase:
1. How should you redesign? About half of survey respondents said they typically manage process redesign internally. Another 41% said engaging an outside coach is an important part of the process. A coach’s process improvement expertise can be a powerful tool when employees are hesitant to make changes, too busy to fully focus on the task, or inexperienced in process design.
2. When should you redesign? Reimaging before selecting a new software system gives nonprofits a clear picture of how they can work more efficiently and may even help them realize they don’t yet need new software. Redesigning after a system has been selected but before it’s installed, on the other hand, allows foundations to build new processes with the new system’s capabilities in mind. Building processes after the system is in place is another viable option, but respondents said it often feels like “trying to build a plane while it’s in the air.” Half of respondents to the Innovation Process Design survey said the best time to redesign is after selecting the new system and before installation. Meanwhile, another 37% say redesigning before selecting a new system is the way to go, and the final 12% say redesign should be done after the new system is in place.
3. Should you go big? The answer to this question may depend on the size of your software purchase or the needs of your processes, but 60% of survey respondents said they received more benefit from major process redesign than from minimal or no redesign. For some, going big led to better outcomes, faster implementation, and more significant return on a major systems investment, while giving team members the confidence to ask and resolve questions. In addition, 58% of participants combined process improvement training with redesign. These organizations said they received significant value from process training and this approach.
Understanding the goals of work is the first level of process redesign. It creates a framework that organizations can use as they proceed to the second level, which includes process work — identifying the structure of who does what, and when they do it. The third level is process detail — identifying the screens, fields, reports, and steps used to complete the work. However, all organizations should incorporate level three – process detail – when implementing a new software system.
Once an organization has a clear picture of its needs and the scope of the software project at hand, the team can identify the steps needed for reaching its goal — whether that involves a major design or a few simple process tweaks. This thinking is summarized in a matrix you can use to identify the specific process redesign steps to help your team be successful. See the matrix and survey summary report here: Summary of Reimage Processes for New Software Survey
Changing the way things have always been done is intimidating, and there are inherent risks. But applying time-tested resources in a way that best meets your nonprofit’s needs will make it easier to successfully manage the twists and turns of process transformation.