More insights.
Subscribe to our newsletter.
Deep dives into design thinking, creative process, and the intersection of business and aesthetics.
The return of the spreadsheet
The software implementation was supposed to change everything. The business invested significant time and money into the project, employees attended training sessions, and leadership communicated the benefits. Launch day arrived; everyone was optimistic, and the future looked more organized than ever.
Three months later, employees quietly returned to their spreadsheets.
If you’ve ever witnessed this happen, you’re not alone. Many software implementations struggle not because the technology is bad, but because implementation involves much more than simply turning on a new system.
Technology is the easy part
Software vendors often focus heavily on features, functionality, and technical capabilities. Those things matter, but they’re rarely the biggest obstacle. The real challenge is helping people change the way they work. Employees develop habits over time, teams create routines, and processes become familiar. Introducing a new platform often means asking people to learn different workflows while continuing to perform their existing responsibilities.
That’s a significant adjustment, particularly when employees don’t fully understand why the change is happening in the first place. Even the best software can struggle if the people expected to use it don’t feel invested in the outcome.
No clear definition of success
One reason implementations fail is that businesses aren’t entirely sure what success looks like. The objective becomes “implement the software” rather than “improve efficiency,” “reduce delays,” or “create better visibility.” Installing the system becomes the goal instead of the business outcome the system is meant to support.
Without clear objectives, it’s difficult to measure progress or evaluate whether the implementation is actually delivering value. Teams become frustrated because expectations are unclear, and leadership struggles to determine whether the investment was worthwhile.
Trying to change everything at once
Another common mistake is attempting too much too quickly. Businesses introduce new software, redesign workflows, create new reporting structures, and change employee responsibilities simultaneously. While the ambition is understandable, the result is often confusion and resistance.
Successful implementations typically focus on gradual adoption. Employees need time to learn, adapt, and build confidence. Small wins create momentum, and momentum encourages long-term success. Change is much easier to manage when people aren’t overwhelmed by it.
Software doesn’t change businesses
Technology can support change, but it doesn’t create change on its own. People create change. Processes create change. Leadership creates change. Software simply provides a platform that enables those efforts.
The most successful implementations recognize this reality. They focus on communication, training, adoption, and process improvement alongside the technology itself. Because at the end of the day, a great system that nobody uses effectively is still a failed implementation.
The return of the spreadsheet
The software implementation was supposed to change everything. The business invested significant time and money into the project, employees attended training sessions, and leadership communicated the benefits. Launch day arrived; everyone was optimistic, and the future looked more organized than ever.
Three months later, employees quietly returned to their spreadsheets.
If you’ve ever witnessed this happen, you’re not alone. Many software implementations struggle not because the technology is bad, but because implementation involves much more than simply turning on a new system.
Technology is the easy part
Software vendors often focus heavily on features, functionality, and technical capabilities. Those things matter, but they’re rarely the biggest obstacle. The real challenge is helping people change the way they work. Employees develop habits over time, teams create routines, and processes become familiar. Introducing a new platform often means asking people to learn different workflows while continuing to perform their existing responsibilities.
That’s a significant adjustment, particularly when employees don’t fully understand why the change is happening in the first place. Even the best software can struggle if the people expected to use it don’t feel invested in the outcome.
No clear definition of success
One reason implementations fail is that businesses aren’t entirely sure what success looks like. The objective becomes “implement the software” rather than “improve efficiency,” “reduce delays,” or “create better visibility.” Installing the system becomes the goal instead of the business outcome the system is meant to support.
Without clear objectives, it’s difficult to measure progress or evaluate whether the implementation is actually delivering value. Teams become frustrated because expectations are unclear, and leadership struggles to determine whether the investment was worthwhile.
Trying to change everything at once
Another common mistake is attempting too much too quickly. Businesses introduce new software, redesign workflows, create new reporting structures, and change employee responsibilities simultaneously. While the ambition is understandable, the result is often confusion and resistance.
Successful implementations typically focus on gradual adoption. Employees need time to learn, adapt, and build confidence. Small wins create momentum, and momentum encourages long-term success. Change is much easier to manage when people aren’t overwhelmed by it.
Software doesn’t change businesses
Technology can support change, but it doesn’t create change on its own. People create change. Processes create change. Leadership creates change. Software simply provides a platform that enables those efforts.
The most successful implementations recognize this reality. They focus on communication, training, adoption, and process improvement alongside the technology itself. Because at the end of the day, a great system that nobody uses effectively is still a failed implementation.