Change Management: The Backbone No One Designs in Time
- Parmonia

- Aug 7
- 3 min read
Change management is not a bolt-on solution, and it isn't synonymous with communication. It's part of the transformation strategy's architecture from day one: who the stakeholders are, who the subject-matter experts are, who is directly impacted, how that map shifts as the process moves, which moments are critical, who owns communication at each of them, and what to do when something unplanned happens, in either direction. Treated any other way, as the last mile, the communication rollout that begins after every decision is made, it's the reason adoption numbers, measured almost immediately after launch, so rarely hit target.
The pattern holds regardless of company size, though the shape of the mistake shifts with scale. In one mid-sized company we worked with, the owner cascaded the change directly: a single video call laying out what needed to happen, by when, and how, no room for questions. The follow-up showed stagnation, not progress. Each team had understood something different, hadn't cross-checked with the others, and several weren't clear on what was expected of them. In a large enterprise, the CEO took the opposite structure: an in-person briefing with three key people, then everything else pushed down through email. The result was more uncertainty than clarity; no one was confident about direction, or whether their role was even secure. Centralised or distributed, the failure was the same: design the change first, plan for the people second.
What changes when people are part of the design.
Designing change management as continuous rather than staged allows it to adapt mid-course. There's still tension along the way, and that's expected. But when the people affected are part of the design from the outset, not just the people who own the vision, commitment and performance behave differently, at both the individual and organisational level. People aren't just receiving the change. They co-designed it. They know their input is still in it.
In that same mid-sized company, once the design process opened up to more functions and feedback was genuinely solicited, something surfaced that the initial analysis had missed entirely: the process originally slated for a third phase was, in fact, the company's core process, the one that defined it to its customers and its community. No one had seen it earlier because no one had asked earlier. Complete information isn't a precondition to start; markets, solutions, and the information itself keep shifting regardless, but asking the right people early is. That company lost a year to a transformation with no concrete results, until it did.
The variable everyone forgets: language.
One part of change management is rarely named directly: language. This isn't about standardising the message. It's about building it with cultural intelligence, adapting form without losing substance, and carrying that same sensitivity into intercultural communication when teams span geographies or languages. Telling every team "we're on track" or "we're in chaos" builds nothing; it's empty language. What builds connection, and therefore the kind of impact that shows up in tangible results, financial or operational, is language calibrated to each group, at each moment. This is a capability any member of an organisation can build, not a function reserved for whoever owns internal comms.

How do you know it's working?
Three concrete signals:
Adoption holds beyond the initial measurement window; months, even years later. One client, facing a shift in business strategy, adapted to a changing market without losing its core purpose, in order to keep delivering value to existing and prospective customers and to its wider community. The team was involved from day one: what was happening, what the first solutions looked like, what feedback came back, what alternatives people proposed, through design, results, and iteration.
Feedback channels stay open after formal launch. People are still asking questions openly, without hesitation, still offering and seeking feedback, proposing solutions, co-implementing, pushing back respectfully, still looking to improve.
The message keeps adapting to each group, with intercultural communication and cultural intelligence functioning as the foundation of change management, and as part of the organisation's cultural DNA, internally and externally.
When that's true, change management has stopped being a phase. It's become part of the system.
The two organisations this piece opened with were facing different versions of the same question: What do you understand change management to mean? And how do you centralise its design while executing it in a decentralised way?



Comments