The Practical Side of Organizational Change
I've spent more years than I care to count watching well-intentioned change initiatives stumble over the same predictable rocks. Dean Anderson's approach to Change Management Dean Anderson caught my attention early on because it wasn't another academic framework built for conference slides. It was grounded in the actual messiness of getting people to move when they didn't want to move. His work with The Anderson Corporation centered on a simple truth that most organizations ignore until it's too late: change isn't a process you run, it's a conversation you have with people who are genuinely scared about losing something familiar. That sounds obvious in a meeting room. It sounds completely different when you're standing in front of forty people who've just been told their roles are changing and your calendar is packed with three more of these across the week.
Dean Anderson's Core Approach
Anderson emphasized narrative and storytelling as the primary vehicles for change, not because narratives are soft or optional, but because they are the only mechanism through which people actually make sense of disruption. Facts get filed away. Stories get carried into the next day. His framework broke down into practical components: understanding the existing narrative, creating space for a new one, and doing it slowly enough that people don't feel ambushed. The speed part is the one that gets ignored. Every organization I've worked with wants to compress the timeline. They always regret it later.
What Actually Happens in Practice
Here's the thing nobody puts in the training manual. When you apply Anderson's approach, you run into the "silent resistance" problem. This isn't the kind of pushback you can address with a memo or a town hall. It's the phenomenon where people show up to every meeting, nod at everything, and then go back to their desks and do exactly what they were doing before. Not actively resisting. Just... neutrally persisting in the old way. I encountered this specifically with a mid-sized logistics company trying to migrate from a legacy dispatch system. The leadership had bought into the new platform, the vendor had done their demo, and everyone was checking the "change adoption" boxes. But the dispatchers, who were the actual users, had already formed an informal network for handling exceptions that the new system couldn't replicate. Within six weeks, they were using the new tool for routine cases and falling back to paper notepads and text messages for anything complicated. Productivity dipped. Morale dipped harder. The workaround wasn't more training. It was mapping the exception-handling process with the dispatchers themselves and rebuilding the system configuration around their actual workflows, not the idealized version. That took three weeks of walking the floor and sitting with people during their shifts. It also required admitting that the vendor's implementation playbook was built for companies with half the edge-case density we dealt with.
Get the Full Details
Counter-Intuitive Lessons
One insight that took me years to internalize: the people most resistant to a change initiative are often the ones who understand it best. The employees who ask the hardest questions, who push back on the rollout schedule, who seem like obstacles to speed usually have the clearest picture of what could go wrong. Dismissing them as blockers is a mistake that compounds. Engaging them as stress-testers usually surfaces problems you'd otherwise discover during the worst possible moment. Another thing beginners miss: Anderson's emphasis on narrative doesn't mean you spend all your time telling stories. It means you pay attention to the existing story people are already living. If the current organizational narrative is "we survive by improvising," no amount of change messaging will override that until the people actually experience something different. You have to create conditions where the new behavior produces a better outcome, consistently, before the narrative shifts. That's why quick wins matter more than strategic alignment in the early phases.
Where This Approach Breaks Down
Let me be blunt about the limitations. The narrative-driven approach works poorly in environments where leadership isn't willing to be transparent about the reasons for change. If the real reason is cost-cutting and you dress it up as "evolving our competitive positioning," people will sense the gap between the story and the substance. The framework assumes a baseline of trust that simply doesn't exist in every organization. It also doesn't scale well to large-scale restructuring. When you're laying off twenty percent of a workforce while trying to maintain morale among the survivors, storytelling becomes almost offensive if it's not backed by concrete decisions. In those scenarios, clear and direct communication about what's happening and why, combined with genuine support for affected employees, matters far more than narrative cohesion. There's also a time cost. A properly executed Anderson-style change intervention, with the floor-walking and the exception-mapping and the narrative work, takes considerably longer than a standard rollout. In my experience, you're looking at two to three times the timeline of a traditional approach for comparable scope. Some organizations can't absorb that delay. That doesn't make them wrong, it just makes them a poor fit for this method.
A Practical Starting Point
If you're working with Change Management Dean Anderson principles and you want a concrete place to begin, start by identifying the people who are most likely to silently persist in the old way. Not the vocal opponents, not the eager adopters. The quiet ones. Spend time with them before the formal rollout begins. Understand what they're actually doing, not what they should be doing. The gaps between those two descriptions are where your change initiative will live or die. There's no download link for this, and that's the point. It's not a tool you install. It's a practice you develop through repeated exposure to the failure modes I described. The frameworks are available through The Anderson Corporation's publications and workshops, but the value is in how you apply them to your specific organizational context, not in the frameworks themselves. I've found that the most effective change practitioners I know keep a running list of the assumptions they made that turned out to be wrong. That list is more valuable than any methodology guide because it captures the actual learning, not the theoretical one.
