You sign up for an ERP transformation because of the view from the other side: cleaner data, faster closes, one version of the truth, processes that scale past the few people who currently hold them in their heads. Those gains are real, and they are worth the trip.
But the gains are not the first thing you feel. The first thing you feel is the drop.
What most consultants don't say out loud at the kickoff: it gets worse before it gets better. On go-live day, productivity does not jump. It dips. Every daily routine you had quietly automated in your own head gets disrupted, some on day 1, some midmonth, and some in your first close. And for a while you are slower, clumsier, and more frustrated than you were the month before. That dip has a shape — and the shape is the same on every project.
Every project has the same curve
I have never seen a software go-live that skipped the valley. You cannot flip the switch on a new system and a new set of routines without first taking a hit to productivity. It isn't a question of talent or effort. It's a question of grooves.
The people who run your finance operation today have deep grooves worn into their brains — processes they have learned over years and run hundreds of times without thinking. That fluency is exactly what makes them good. It is also exactly what a transformation disrupts. We come in and re-cut the grooves, and for a while the old muscle memory fights the new way of doing things. There is a lot of reverb in those old grooves, and it takes reps to quiet it down.
There's a strange consolation in this. The newest people on a team often have the easiest go-live, precisely because their grooves aren't deep yet. Less to unlearn, less reverb.
The dip is not a sign that something went wrong. It is a sign that something is actually changing.
Why we call it the Valley of Despair
The valley was never the problem. The problem is that many implementers get a client “live,” declare victory, and move on to the next engagement as the client slides down the descending curve. The client gets left at the bottom of the valley, and that is what leads to despair.
The valley is unavoidable. Your choice of implementation partner will determine if you are accompanied in it or abandoned. Your power lies in this choice.
The valley is inevitable. Its dimensions are not.
You have to go through it. There is no path around the valley, the same way there is no way to learn any new skill without being bad at it first. But not all valleys are alike.
A good one is shallow and narrow — a sunny walk through a gentle dip in the terrain. You notice you're lower for a cycle, and then you're climbing again. A bad one is a canyon, where the bottom drops out and you can't see the far wall. Same valley on the map. Wildly different experience crossing it.
Our entire job at go-live is to make the trough as shallow and as narrow as possible. That work happens on three fronts.
- Design. The less there is to relearn, and the fewer ways there are to fall, the shallower the valley. Good design pushes everything down a small number of clean paths and clears out the spiderwebs of one-off processes that accumulate in every legacy system. When there is one obvious way to do a thing instead of nine inherited ones, people find their footing faster.
- Training. A go-live should be a performance, not a first rehearsal. Before the curtain goes up, you let people fight through the real steps by hand, in a sandbox, where nothing is at stake — no live customers, no real dollars, nobody's job on the line. Reps before go-live build the muscle memory so you aren’t rattled when you are under pressure in Production. Repetition and clear instructions are most of what turns a canyon back into a gentle dip.
- Enablement. This is the front the old playbook skipped entirely. It means not leaving at launch. It means staying in the valley with the team to capture every this-doesn't-work-the-way-we-expected — and, critically, sorting those into two piles: painful because it's unfamiliar, and painful because we built it wrong. The first kind gets better on its own with reps. The second kind is a bug, and we fix it. Telling them apart is critical.
Straddling worlds
There is a particular flavor of valley depth that comes from straddling two worlds at once, and it's worth naming because it catches people off guard.
You rarely flip an entire operation over in a single night. The clean break applies to new work; the work already in flight usually runs its course on the old model. So for a stretch — often months — you are running in parallel. Old projects finish the old way. New projects start the new way. And every person in the middle is straddling the new and the old.
The good news: this particular discomfort is temporary by design. The last old project closes, the old world fades, and you get to focus on the new.
"You're angry at me" is not a bad sign
So here is the expectation we set with every client, plainly: for a little while, your job is going to feel harder, and you may be a little angry at the people who did this to you. That feeling is not evidence of a mistake. It is the cost of admission, and far more often than not it means real change is underway — not that it's failing.
To help with this, lower the stakes in your own head. A go-live is not a moon mission. Nobody is being launched into outer space, no lives are at risk, and you will still be able to breathe no matter what breaks on day one. It is okay if something doesn't work, or if you do it wrong, or if you can't figure it out yet. That is normal. That is what the early days are for.
Final thoughts
The valley is the toll you pay for the view. You don't get to skip it, and you shouldn't trust anyone who promises you can. What you do get to choose is its dimensions and how you cross it — and who is standing next to you at the bottom.
A golive is a finish line of a sort, but it is not the finish line. There is always a room or two where the paint is still drying. The measure of a good partner isn't whether they got you live. It's whether they are still there in the valley with you, helping you up the other side. Because with the right plan, preparation, and partner, it can just be a valley - hold the despair.
