Making the Leap - Transitioning to New Software Platforms
April 6, 2017
Anyone who works with technology long enough knows the feeling of dread that accompanies an end-of-life announcement for a dependable software solution. Immediately following the dread, or perhaps running parallel to it, come the inevitable questions associated with transitioning to new software platforms:
- How am I going to identify replacement solutions?
- What criteria should drive the final selection?
- How will this impact the people who rely on the old technology?
- Is this going to necessitate larger changes?
- How can we make the leap without causing disruption?
For those responsible for ensuring a smooth transition to new software platforms, the list of questions is much longer.
Last week I had an opportunity to speak with a senior systems analyst at one of our customers who went through this experience. What struck me as interesting was his initial priority that the new system – and I quote – “not suck worse” than the out-of-life platform he was replacing.
This priority confirms the adage that change is scary. But it’s also inevitable. Especially when technology is involved. They key is to embrace change with a plan to make the most from the opportunity to upgrade. But disruption, a concept heralded in best-selling business books, t, often prohibits the adoption of new technologies in real life.
At the end of the conversation, I realized the importance of striking a balance between new technology, disruption and user adoption. In fact, from our conversation, I saw how the approach our customer took represents the Holy Grail for those facing an end-of-life or out-of-support technology scenario.
If you’d like to learn more about how our customer made the necessary leap to a new platform and the results it achieved, you’ll find the entire customer journey in this case study.
Submitted by Glenn Seaberg
Director of Marketing