Why does Improvising Change Communication Stop Working?
Early in your career, you could wing change communication. Leadership would announce something, you'd handle the fallout, answer questions as they came up, adjust on the fly.
It worked because you were operating at small scale. One team. One project. Limited complexity.
Then something changed. Your scope expanded. You're coordinating across departments now. Managing initiatives that affect dozens or hundreds of people. Dealing with dependencies you didn't have before.
And suddenly, winging it doesn't work anymore.
Intuition doesn't scale
When you're coordinating a single team, you can rely on intuition. You know your people. You can read the room. You can course-correct in real time based on feedback.
But when you're coordinating across multiple teams, functions, or locations, your intuition doesn't reach. You can't be in every conversation. You can't read every room. You can't course-correct what you can't see.
What worked through informal adjustment and good instincts starts breaking down. Messages fragment across teams. Different managers emphasize different things. Gaps emerge that you don't discover until they've caused problems.
Memory fails under volume
When you're managing one or two changes at a time, you can keep track of what you've communicated to who. You remember what questions came up. You know what follow-up you owe.
When you're managing five concurrent initiatives, each affecting different populations, each in different phases, your memory becomes a liability.
You forget to address something in one rollout that you handled well in another. You repeat the same explanation to the same person because you've lost track of who you've already briefed. You miss follow-up commitments because they're not written down anywhere systematic.
This is cognitive overload. You're trying to coordinate complexity without infrastructure to support it.
Improvisation creates inconsistency
When you wing it, each communication is a fresh effort. You're thinking through the message in the moment. Addressing what feels most urgent. Responding to whoever is in front of you.
That creates variation. You explain the same change three different ways depending on who asks. You provide different levels of detail based on how much time you have. You emphasize different aspects because you're responding to different contexts.
None of those variations feel problematic in isolation. But people compare notes. They notice the inconsistencies. They wonder why they're getting different information.
Suddenly your credibility is questioned.
The shift from responder to architect
When work was simple, your job was to respond well. Handle what comes up. Answer questions. Adjust as needed.
As complexity increases, that approach becomes insufficient. You need to anticipate, not just respond. You need to prevent problems, not just solve them. You need to create structure that makes coordination reliable, not just hope your instincts are good.
This is the shift from responder to architect. From handling communication to designing communication systems.
What a system provides that intuition can't
A systematic approach to change communication doesn't replace your judgment. It structures your judgment so it's applied consistently.
It gives you a framework for deciding what to communicate when. It provides language for talking about phases and breakdowns. It creates repeatability so you're not reinventing your approach every time.
It lets you coordinate across scale and complexity without relying on memory, presence, or informal correction. It makes your work reproducible. Which means it becomes organizational capability, not just personal competence.
The resistance to systems
Most people resist systematizing their work because it feels constraining. Like it will make them less responsive. Less human. Less able to adjust to context.
But that's not what good systems do. They don't eliminate flexibility. They eliminate the coordination failures that happen when you rely entirely on improvisation.
You still exercise judgment. You still adapt to context. You're just doing it within a structure that prevents predictable failures.
When to make the shift
You need a system when improvisation starts creating problems you can't solve through better responsiveness.
When messages fragment across teams despite your efforts to communicate clearly. When you're repeating yourself but people still seem confused. When initiatives that should work keep hitting unexpected resistance.
Create repeatable success
The fact that winging it stops working is evidence that the work has scaled beyond what informal coordination can handle.
Some people recognize this and build systems. Other people keep trying harder with approaches that don't scale, wondering why they're working harder for worse results.
Learn the systematic approach. There's a structured method for change communication that scales across complexity; one that turns your good instincts into repeatable capability instead of hoping you remember to apply them every time.
References & Related Reading:
1) Sweller, "Cognitive Load During Problem Solving" (Cognitive Science, 1988): https://onlinelibrary.wiley.com/doi/10.1207/s15516709cog1202_4
2) Levitt and March, "Organizational Learning" (Annual Review of Sociology, 1988): https://www.annualreviews.org/content/journals/10.1146/annurev.so.14.080188.001535
If you're running a rollout and want a plan for each stage, The DANCE System gives you 29 tools across five phases, from defining the change to keeping it in place after launch.
Related Blog Posts:
Why do people stop believing announcements?
When does change communication need a system?
