The Valley of Despair: Why Digitalization Hurts Before It Works
Every company transitioning from spreadsheets and emails to specialized software will go through the Valley of Despair. Learn what it is, why it's normal, and how to get through it without giving up.
- Written by
- Mihai Gheorghe
- Published on
- March 23, 2026
The Valley of Despair: Why Digitalization Hurts Before It Works
You've made the decision. Your company is moving from spreadsheets and emails to a new system - an ERP, a CRM, project management software, whatever it may be. The team is enthusiastic. Everyone agrees: "It's about time."
Two weeks pass. Things aren't getting better. They're getting worse. Reports that used to take an hour now take two. People can't find what they're looking for. Someone sends the wrong order because they couldn't find the right button. Your operations manager walks in and says: "Maybe we should go back to how things were."
Congratulations. You've arrived in the Valley of Despair.
And here's the good news: this is completely normal.
What Is the Valley of Despair?
The Valley of Despair is a concept from change management that describes a predictable phenomenon: when an organization implements a major change - whether it's new software, a new process, or a reorganization - performance temporarily drops before rising above the previous level.
The model traces its roots to psychiatrist Elisabeth Kübler-Ross's work on the stages of adapting to change and has been adapted by change management specialists like John Fisher for organizational contexts.
The Valley of Despair isn't a sign that you chose the wrong solution. It's a natural stage that every organization goes through when adopting something new.
The curve looks something like this:
The 5 Stages of the Curve
1. Certainty (Current State) Everything works "acceptably." Yes, there are inefficiencies, but everyone knows how things work. The spreadsheet is slow, but everyone knows it. It's a comfort zone - even if it's not efficient.
2. Chaos (Valley of Despair) The new system is implemented. Nobody knows exactly where things are anymore. Old processes no longer work, new ones aren't yet understood. Productivity drops. Frustration rises. This is where the temptation to quit appears.
3. Caution The team starts understanding the new processes. Things aren't chaotic anymore, but they're not smooth either. People are careful, double-checking, moving slowly but surely.
4. Confidence New processes become natural. The team sees the first real benefits: faster reports, fewer errors, information just a click away. Resistance transforms into acceptance.
5. Competence (Future State) The new way of working is "the normal." Performance exceeds the previous level. People wonder how they ever managed without the new tools.
Why This Matters for Your Business
Problem #1: Companies Give Up in the Valley
The most dangerous moment in a digitalization project isn't the beginning - it's weeks 3 through 6 after implementation. Exactly when chaos is at its peak and benefits aren't yet visible.
What typically happens:
- A manager says: "This software doesn't work"
- The team starts using spreadsheets again "temporarily"
- Someone proposes: "Let's wait, it's not the right time"
- The project gets abandoned or "postponed" (which is the same thing)
The result? You've spent money, time, and energy, and you're back exactly where you started - except now you also have a team that's more skeptical of any future change.
Most digitalization projects don't fail because of technology. They fail because the organization gives up in the Valley of Despair.
Problem #2: Nobody Warns You
Most software vendors and IT consultants sell you a linear vision: "We implement, train the team, everything gets better." Nobody tells you there will be a period where things get worse than before.
But if you know the Valley of Despair is coming, you can manage it. If you don't know - you interpret it as failure.
What the Valley of Despair Looks Like in Practice
Let's take a concrete example: an installation company with 40 employees transitioning from Excel and WhatsApp to an integrated project management system.
Before Implementation (Certainty)
| Process | How it worked |
|---|---|
| Material orders | Excel sent via email to manager |
| Project tracking | Shared Excel file on Google Drive |
| Reporting | Manual, every Friday, 3 hours |
| Documents | PDFs via email, folders on local drives |
| Team communication | WhatsApp, phone calls |
Everything "works." Slow, error-prone, with lost information - but it works.
Weeks 1-2 (Entering the Valley)
- New system is installed, team receives training
- First orders are entered incorrectly - they don't know the required fields
- The project manager can't find the dashboard they were shown in the demo
- Two technicians refuse to use the mobile app: "I don't have time for this nonsense"
- The director receives an incomplete report and gets frustrated
Weeks 3-5 (The Bottom of the Valley)
- Half the team has gone back to Excel "temporarily"
- Data is partial - some in the system, some in spreadsheets
- The situation is worse than before because now you have two systems
- Someone says in a meeting: "I told you this wouldn't work"
Weeks 3-5
The critical moment: this is where the project lives or dies
Weeks 6-8 (The Climb)
- Those who persevered start seeing benefits
- A report that used to take 3 hours is now generated in 5 minutes
- The manager discovers they can see all project statuses from a single screen
- The team starts requesting new features: "Can we also add..?"
- Excel becomes the "backup," then gradually disappears
Month 3+ (Competence)
- Nobody thinks about "how things used to be"
- Data is in one place, accessible to everyone
- Decisions are made faster, based on real data
- The director says: "Why didn't we do this sooner?"
7 Strategies to Get Through the Valley Successfully
1. Prepare the Team Before Implementation
Don't launch the software without explaining what's coming. Show them the change curve. Tell them: "There will be a 3-4 week period where things will be harder. It's normal. It's temporary."
When people know that difficulty is expected and temporary, they tolerate it much better than when they think something is wrong.
2. Appoint Internal "Champions"
Identify 2-3 people in the team who are more open to change. Give them early access to the system, additional training, and the explicit role of helping colleagues. Colleagues listen better to an internal "champion" than to an external consultant.
3. Eliminate the Possibility of Retreat
This is controversial but effective: at some point, you need to cut off access to the old systems. As long as the spreadsheet remains an option, people will go back to it at the first sign of difficulty.
Run systems in parallel for 1-2 weeks for safety, then switch definitively. Don't let the "backup" become the excuse to not adopt the new system.
4. Celebrate Small Wins
The first report generated automatically. The first order processed without errors. The first month without manual reconciliation. Make these moments visible - send a message to the team, mention them in meetings. Small wins build the momentum to keep going.
5. Accept the Temporary Productivity Drop
Plan the implementation during a quieter period, not peak season. Budget for a 20-30% productivity decrease in the first 2-3 weeks. With this buffer, the pressure to "go back to the old way" drops dramatically.
6. Provide Continuous Support
Not one training session and then "figure it out." Instead:
- Short weekly Q&A sessions (30 minutes)
- A dedicated support channel (WhatsApp or internal chat)
- Quick guides for the most common operations
- Someone available to help during the first few weeks
7. Measure and Communicate Progress
Define clear metrics before implementation:
- Processing time for an order
- Number of errors per week
- Report generation time
- Team satisfaction (a simple 3-question survey)
Communicate these metrics weekly. When the team sees that numbers are improving - even slowly - motivation grows.
Why This Model Works
The Valley of Despair isn't just a nice metaphor. It's a documented and predictable pattern. And that's precisely why it's useful: what's predictable can be managed.
The difference between a successful digitalization and a failed one isn't software quality. It isn't the budget. It isn't even the team's technical readiness. The difference is realistic expectations about what's coming and the commitment to traverse the Valley together.
Every company that has successfully gone through a digitalization has also gone through the Valley of Despair. The difference is they didn't stop halfway.
How to Make the Valley Shallower and Shorter
You can't eliminate the Valley of Despair - it's a natural part of the change process. But you can influence two things: how deep it is and how long it lasts.
| Factor | Makes the Valley deeper | Makes the Valley shorter |
|---|---|---|
| Communication | Lack of information about what's coming | Full transparency, regular updates |
| Training | One session, then "figure it out" | Continuous support, weekly Q&A |
| Leadership | Management that hesitates or criticizes the new system | Visibly committed leadership |
| Implementation | Big-bang: everything at once | Iterative: one process at a time |
| Feedback | Ignoring team complaints | Active feedback collection and adjustment |
Next Steps
If you're at the beginning of a digitalization project - or in the middle of one that "isn't working" - consider these questions:
-
Does your team know about the Valley of Despair? If not, show them this article or the curve image. This awareness alone dramatically changes perception.
-
Do you have internal champions? If not, identify 2-3 people who can become change ambassadors.
-
Do you have clear metrics? If not, define 3-4 indicators to track before, during, and after implementation.
-
Do you have dedicated support? If your team is navigating the change alone, consider a partner who's been through this before.
At [Conresti](https://conresti.com), when we implement automation solutions for clients, we explicitly budget for and manage the Valley of Despair - with 30 days of hypercare and dedicated support during the critical period. Because we've learned that technical success without change management isn't success at all.
Related Articles:
Weekly newsletter
No spam. Just the latest releases and tips, interesting articles, and exclusive interviews in your inbox every week.