How We Work C&T 101
Plain English

C&T
101.

What change and transformation actually is. Why most of it fails. Why your organisation probably needs it. No jargon. No consulting waffle.

What it actually is

Change & transformation is the work of moving an organisation from how it operates today to how it needs to operate tomorrow.

That sounds obvious. But it is not the same as a project. A project builds something — a new system, a new building, a new product. Change and transformation is what happens to the people, the processes, the structures and the culture when the project lands. It is the work of making the new way stick.

Most organisations are very good at the project. They are significantly less good at the change. The system goes live. The new process is documented. The announcement is made. And then — slowly, invisibly, for entirely understandable human reasons — the organisation drifts back to the old way.

That drift is not a failure of will. It is a failure of design. The change was not designed to hold.

Why it fails

Not for the reasons you might think.

📋
It was designed for the boardroom
The communications plan. The town hall. The all-staff email. These reach people formally. They do not change what people say to each other in the corridor. That is where the decision about whether to adopt the change actually gets made.
👤
Managers were briefed, not enabled
A manager briefing tells people what is changing. Manager enablement prepares them to handle the specific conversations their team will have — the objections, the worries, the "will my job change?" question at 4pm on a Friday. Most change programmes do the former and skip the latter.
🏁
Go-live was treated as the finish line
The programme demobs. The governance stands down. The change champions are thanked. And the organisation — told the change has been delivered — is no longer structured to sustain it. Go-live is a milestone, not the finish line. The finish line is month 12.
What a proper change programme contains

Not a communications plan. A programme.

Discovery
Understanding the organisation as it actually is — including the informal politics, the corridor dynamics and the resistance that will materialise before the first workshop.
Stakeholder management
Mapping who matters, what they think, and what it will take to move them. Identifying the informal leaders whose views shape the group — and designing specifically for them.
Manager enablement
Not a briefing. A programme. Managers equipped to handle the specific conversations their teams will have, in the corridor, before and after every formal communication.
Readiness assessment
An honest assessment of whether the organisation is ready to go live — before it does. Go-live earned, not assumed. A programme that is not ready is a programme that will revert.
Embedding & hypercare
The period immediately after go-live is when most change is most vulnerable. The programme continues. Reversion is identified and addressed before it becomes the norm.
Benefits verification
At month 12, returning to verify that the change held and the benefits are being realised against the baseline established before the programme started. This is the finish line.
When you need it

If any of these are true, you need a change programme.

▸You are implementing a new system and assuming people will use it because they have been told to.
▸You are redesigning your operating model and the communications plan is three slides at the end of the deck.
▸You have tried this before and it did not stick.
▸Your managers are supportive in workshops and quiet in corridors.
▸You are 3 months post go-live and adoption is lower than projected.
▸Your benefits case has not been verified since the programme was approved.

Sound familiar?

Tell us what you are dealing with. The first conversation is free of agenda.

Start a conversation