The Change Nightmare That Felt Like a Proverbial Crime Scene

Here’s a moment of truth—be honest: Six months after your organization made a major change, if you asked your team today how it was handled—and what the experience really felt like—what would they say?

It’s a deceptively simple question, but one that reveals more than most organizations are prepared to face. In my experience, the answers rarely lie in project plans, Monday/Trello dashboards, or executive summaries. Instead, they’re whispered in the quiet conversations people have when the meetings end; they lurk in the sighs behind muted microphones; and they’re evident in the gradual shift from engagement, to fatigue, to outright anger, that metrics often fail to capture in time.

To explore this more fully, let me tell you a story.

Investigating the Crime Scene

Consider one organization I worked with a couple of years ago. Let’s call it Acme Corporation. The name is fictitious for obvious reasons; but the events I’m about to describe are not fictional at all. And, while certain details have been adapted, they’re uncomfortably—and painfully—familiar.

Acme set out to do what many organizations aspire to do: modernize its operations by implementing a new enterprise-wide software system. The initiative was positioned as a strategic investment in the company’s future, promising increased efficiency, improved integration across functions, and a more seamless experience for both employees and customers. The business case was well-articulated, the funding secured, and the timeline—although ambitious—seemed achievable, at least on the surface.

From a distance, the change appeared well-conceived. Up close, however, a different picture began to emerge. The first sign that something was amiss wasn’t in the form of a dramatic failure, but rather in the absence of something more subtle and arguably more important: clarity. Unfortunately, communication about the change project was sporadic, fragmented, and siloed. Messages were released, but they lacked cohesion.

Updates were shared but not only did they not tell a consistent story, they weren’t always shared with everyone who needed to be informed. Employees received just enough information to know that something significant was happening, but not enough to understand what it meant for them or how they were expected to respond. In the absence of a clear and continuous narrative, people did what people have always done in uncertain environments: they filled in the gaps themselves. Informal networks became the primary source of information, speculation began to replace understanding, and a sense of unease quietly took hold.

When the new software system eventually went live, the transition was abrupt and chaotic to say the least. Rather than a carefully staged rollout that allowed individuals and teams to adapt incrementally, the change steamrolled in with the grace of a bull in an antiques store, which left little room for preparation and adjustment. Employees were expected to begin using the new system with minimal training, while at the same time navigating a series of technical issues that were still being addressed by the third-party software vendor.

What might have been manageable challenges in isolation quickly compounded, layering one on top of another. In some parts of the organization, the new system was operational; in others, legacy systems remained in place. This created a fragmented environment in which employees were forced to navigate between old and new ways of working, often without clear guidance on which system to use in a given situation. The result was not simply inconvenience, but a fundamental disruption to the flow of daily work as well as sheer confusion and frustration.

Managers, who might ordinarily serve as a beacon of stability during periods of change, found themselves in a particularly difficult position. Expected to provide direction and reassurance, they were instead grappling with the same uncertainties as their teams. Lacking access to complete and consistent information, they were unable to answer questions with confidence or to offer the level of support their teams needed. The very individuals who should have been enabling the transition were, through no fault of their own, rendered ineffective.

At the leadership level, a different set of challenges was unfolding. Information from the software provider was incomplete and often delivered in silos, limiting leaders’ ability to fully understand the scope and nature of the issues being experienced on the front lines of the change. Decisions were often based on partial visibility, therefore creating a disconnect between leadership perception and employee reality. Over time, this gap widened, eroding trust not only in the change itself but in the leadership guiding it.

As weeks turned into months, the human cost of the change became increasingly apparent. Employees were not simply frustrated; they were exhausted—and, in many cases, deeply resentful. The constant effort required to navigate an unstable system, combined with the cognitive load of working in an environment characterized by uncertainty, began to take its toll. Morale declined, engagement was a distant memory, and a sense of helplessness—even resignation—began to replace the initial willingness to adapt.

By the six-month mark, Acme had achieved what could be described, from a purely technical perspective, as “implementation.” The system was in place. The old ways of working had, for the most part, been replaced. And yet, when viewed through the lens of human experience, the outcome was far less successful. They even lost a few good employees along the way. While it’s difficult to quantify the direct impact, it would be naive to assume that an experience of this magnitude didn’t contribute to some degree.

What remained was a workforce that had endured the change rather than embraced it, and an organization that had, perhaps inadvertently, compromised a few of its most valuable assets: trust, culture, cohesion, and engagement. This is the point where the phrase “crime scene” begins to feel less hyperbolic and more like an accurate description. The question, then, is not whether something went wrong, but…why.

Understanding the Breakdown: Where Process Meets Experience

To answer the question of why things went wrong at Acme, we need to move beyond the visible symptoms and examine the underlying processes—or, more precisely, the absence or breakdown of those processes—that shape how change is experienced.

The ACMP Standard for Change Management provides a useful lens through which to view this situation. It describes change management not as a set of isolated activities, but as a structured, iterative process designed to guide individuals and organizations from a current state to a desired future state. Crucially, it emphasizes that stakeholders require information, leadership support, training, coaching, reinforcement, and time in order to decide whether and how to engage with change. In the case of Acme, several of these elements were either insufficiently addressed or misaligned, creating the conditions for the experience we have just examined.

A critical starting point in any change effort is the evaluation of impact and organizational readiness. This involves not only understanding what is changing, but also assessing who will be affected, how their work will be altered, and whether the organization possesses the cultural and operational capacity to absorb the change. In the absence of a thorough and ongoing assessment, organizations risk underestimating the complexity of the transition and overestimating their readiness to execute it successfully.

Equally important is the role of leadership. Effective change requires sponsors who are not only visible and supportive but also informed and aligned. When leaders operate with incomplete information or inconsistent messaging, they are unable to fulfill their role as credible advocates for the change. This aligns with John P. Kotter’s assertion that strong leadership and a clearly communicated vision are essential to successful transformation efforts. Without them, even well-designed initiatives can falter.

Communication, too, plays a central role, but not in the limited sense of announcements or updates. The ACMP Standard frames communication as a strategic function that must be tailored to the needs of different stakeholder groups, delivered through appropriate channels, and supported by mechanisms for feedback and dialogue. When communication is fragmented or one-directional, it fails to provide the clarity and reassurance that individuals need in order to navigate change effectively.

Another area of breakdown at Acme was the development of capability. Change often requires individuals to adopt new behaviors, learn new skills, and operate within new systems. Without a deliberate and well-executed approach to learning and development, employees are left to bridge the gap between expectation and ability on their own. The result is not empowerment, but frustration and diminished performance.

Finally, the absence of effective feedback mechanisms and reinforcement strategies meant that Acme lacked the ability to monitor progress, respond to emerging challenges, and sustain the desired changes over time. As Weiner (2009) demonstrates, organizational readiness—particularly shared commitment to the change and confidence in the ability to execute it—is a critical factor influencing whether change efforts are effectively implemented.

People Make Change Adoption Happen

What becomes evident through this analysis is that the failure at Acme was not solely rooted in technology, nor in the strategic intent behind the change. It was rooted in a failure to adequately address the human dimensions of change. Prosci’s well-known phrase, “the people side of change,” captures this idea succinctly, but its implications are often underestimated.

Every change, regardless of its technical or operational focus, ultimately requires individuals to alter how they think, behave, and perform their work. This is not a trivial undertaking. It involves not only cognitive adjustment, but also emotional response. “Transformation is a process, not an event… people are often afraid of change, and they resist it when they do not understand what is happening or why” (Kotter, 1995). When organizations fail to recognize and address these dynamics, they create environments in which resistance is not an obstacle to be managed, but an inevitable outcome of the conditions they have established.

Returning to the Question

Which brings me back, once again, to the question I began with. “Six months after your organization made a major change, if you asked your team today how it was handled—and what the experience really felt like—what would they say?” The answer to that question is not merely a reflection of a single initiative. It is an indicator of how organizations approach change more broadly—whether they view change as a technical exercise to be executed or as a human experience to be guided with intention and care.

Closing the Acme Case—and Moving Forward

If there is a lesson to be drawn from the story of Acme, it’s not simply that change can go wrong, but that the factors contributing to that outcome are both identifiable and, importantly, addressable. As the situation at Acme unfolded, another pattern began to emerge—one that is both common and, in many cases, entirely avoidable. In an effort to move quickly and address multiple priorities at once, the organization effectively attempted to advance the change on too many fronts simultaneously. What may have been intended as momentum instead created fragmentation, leaving employees to navigate a shifting landscape without a clear sense of direction or progress.

John Kotter speaks directly to this risk in The Heart of Change, noting that when organizations attempt to manage too many initiatives at once, they often end up slowing themselves down rather than accelerating progress. As he explains, “with so much going on at once, you run the danger of getting nothing finished very fast… This creates problems. It leads to frustration. People wonder where you’re leading them—and whether or not you’re taking the right approach” (Kotter & Cohen, 2002).

That sense of frustration and uncertainty was not theoretical at Acme—it was lived. Employees were not resisting the change in principle; they were reacting to an environment in which priorities were unclear, progress was uneven, and the path forward felt increasingly difficult to trust.

A structured approach to change management, such as that outlined in the ACMP Standard or other established change management frameworks, doesn’t necessarily guarantee success. However, it significantly increases the likelihood that change will be experienced in a way that supports, rather than undermines, the people responsible for bringing it to life.

Organizations that invest in understanding impact and readiness, equipping leaders, communicating effectively, building capability, and reinforcing desired behaviors are not simply more effective at implementing change. They are more effective at sustaining trust, engagement, and performance in the face of ongoing transformation. Ultimately, we know that change is constant; and the entire world is currently experiencing change at a pace that’s more rapid than what most people are accustomed to. Being intentional and proactive with how we approach and prepare for it is probably the most important thing we can do.