Over the years, I have noticed that every major transformation seems to follow the same emotional timeline. It does not matter whether it is an ERP implementation, an acquisition, or another large organizational change. The project usually begins with optimism. People are excited about what is being built, the timeline feels achievable, and every challenge seems manageable because there is still plenty of time to solve it. The kickoff meetings are full of energy, people volunteer ideas, and someone inevitably says, “We’ve got this.”
Then, somewhere along the way, the calendar quietly changes everything. The funny part is that the project itself often has not changed very much. The issues everyone is talking about during the final weeks were usually there a month earlier. The defects are not necessarily bigger, the team has not suddenly become less capable, and the plan has not mysteriously fallen apart overnight. What has changed is that go-live no longer feels like a distant milestone sitting comfortably on the horizon. It has become next week, and suddenly every unresolved issue feels as though it has the potential to stop the business.
After participating in enough implementations, I have almost come to expect this moment. In fact, if nobody is asking difficult questions during the final weeks, I become a little suspicious. Healthy organizations should become more curious as reality gets closer. What fascinates me, however, is how quickly the conversation changes. A month earlier people are talking about configuration, testing, and project plans. The closer go-live gets, the less anyone talks about the project itself. Instead, they begin imagining Monday morning.
- Will orders still process?
- Will customers notice anything different?
- How long will it take to complete tasks that everyone can do almost without thinking today?
- Will the reports still make sense?
- Will the business slow down?
I have always believed that these questions are less about technology than they are about confidence.
For years, people have learned how to navigate the systems they use every day. They know where to click, who to call, which shortcuts save time, and which workarounds quietly keep everything moving. Most of that knowledge has been built over hundreds or thousands of small experiences that eventually become second nature. Then go-live arrives and, almost overnight, people are asked to let go of that familiarity and trust something they have not yet had the opportunity to master.
When you think about it that way, the anxiety starts to make perfect sense. None of us enjoys feeling like beginners again.
I remember learning to drive with a standard transmission. Eventually, changing gears became automatic. I stopped thinking about the clutch, the timing, or the sound of the engine because my brain had built enough experience that driving became almost effortless. If someone handed me a car tomorrow with the gear pattern completely rearranged, I would probably look like I had never driven before. It would not be because I had forgotten how to drive. It would be because something that had become instinctive suddenly required conscious thought again.
Organizations experience something remarkably similar before go-live. The fear is rarely about one specific issue sitting on the project tracker. More often, it is the uncertainty of not knowing how long familiar tasks will take once the old routines disappear. Processing times feel uncertain. Established habits no longer apply. People worry that the business they know so well may suddenly become unfamiliar, even if only for a short period of time. It is not really a fear of the system. It is a fear of temporarily losing confidence in the way they work. The more I have reflected on this, the more I have realized that acquisitions behave in much the same way.
Early in the transaction, conversations revolve around opportunity. Teams discuss strategic fit, synergies, growth, and value creation. There is plenty of time to debate assumptions because closing still feels comfortably distant. As Day One approaches, however, the questions become noticeably different. Executives begin asking harder questions. Leaders challenge assumptions they were comfortable with only weeks earlier. Suddenly everyone is thinking less about the acquisition itself and more about what Monday morning will actually look like.
That shift is completely understandable because uncertainty always feels larger when the deadline is no longer theoretical.
One of the advantages of having lived through enough transformations is that you begin to recognize this pattern. You stop interpreting every difficult conversation as evidence that the project is failing. Instead, you recognize that people are finally experiencing the weight of what they are about to do. In many ways, that is a healthy sign. It means the organization has stopped thinking about the project and started thinking about the business.
That does not mean every concern should be dismissed. Some of the most important risks emerge during the final weeks precisely because people are now looking at the future through the eyes of those who will have to live with the outcome. The challenge is learning how to distinguish between a genuine operational risk and the perfectly normal anxiety that accompanies significant change.
The organizations that navigate this period well are not necessarily the ones with the shortest issue logs or the fewest defects. They are the ones whose leaders continue making thoughtful decisions while everyone else feels the pressure of the calendar. They acknowledge uncertainty without allowing uncertainty to drive every decision. They create enough confidence that people remain focused on solving today’s problems instead of imagining tomorrow’s disasters.
Perhaps that is why I have stopped worrying when projects become uncomfortable just before go-live. It usually means reality has arrived. The project is no longer an interesting initiative being discussed in meeting rooms. It is about to become the way people work every single day. And maybe that is the real lesson.
Projects do not suddenly become more difficult the weeks before go-live; they simply stop being projects and start becoming someone else’s Monday morning.
