Implementation: Don’t Lose Sight of the Why
Implementation: Don’t Lose Sight of the Why
If you’ve ever breathed a sigh of relief at the end of a long software implementation, you’re not alone. That moment of “phew, we made it” often comes with a quiet forgetting of all the promises made at the start, all the dazzling demo moments, and all the bold claims about how this new solution would “revolutionise your business”.
I’ve been on both sides of the implementation fence—supplier and purchaser—and I’ve seen it happen time and time again. Long projects wear everyone down, and by the time go-live finally arrives, people are just happy it’s done. But what about the why? What were your original requirements? What pain points was this shiny new software meant to solve? And—here’s the hard question—has it delivered?
Keep Your Eye on the Prize
It’s surprisingly easy to lose track of those original goals. That’s why I always keep a clear, simple list of:
What was demoed
What problems we expected the software to solve
What features or capabilities were crucial to us
It sounds obvious, but during the chaos of an implementation, it’s easy to let that slip. Everyone’s trying to meet deadlines, keep momentum, and manage frustrations. You get tunnel vision and start making compromises just to push the project over the line.
The Feature Fade
How many features were “lost” along the way? Things you once saw as essential get quietly shelved because they were too complex, too time-consuming, or just too much hassle. And let’s face it—you’re still running your travel business while all this is happening. Implementation isn’t your day job.
I’ve been there. When I led the global Salesforce implementation for a travel business, I was the client—not the supplier. But I came armed. I had documented every feature, every promise, saved every email and demo recording. I didn’t leave anything to memory. I also documented every single scope change, postponement, and cost implication. If something was postponed, I sent a quick email to the supplier to confirm: this is postponed, not cancelled, and here’s the financial impact.
Why? Because what feels like a quick verbal agreement in the moment can easily turn into, “Oh, I thought we dropped that,” months later. That’s a costly misunderstanding.
Block Time for Documentation
I know what you’re thinking: “I don’t have time to send follow-up emails after every meeting.” But you have to make time. Block 15 minutes before and after every implementation meeting in your calendar. It’s a habit that will save you hours—and heartache—later.
Need Help?
If you’re gearing up for an implementation or already in the thick of one, I offer an implementation support service designed to help businesses like yours stay on track. From documenting scope and managing supplier expectations to keeping your original goals front and centre, I can help ensure your project delivers what it promised.
Interested? Let’s talk. Reach out via the contact form Sygnifiq.com and let’s make sure your implementation is one you’ll be proud of—not just relieved to finish.
