Change that sticks. Because people, not slides, deliver outcomes.

Most transformation programmes know what they want to change. Fewer get the people-side right. We design from both sides, and we don't leave until the new way of working is the only way of working.

Three reasons. In roughly this order.

Reason 01

The case is technical, not human

The deck explains the new operating model. Nobody explains why anyone in the building should care.

Reason 02

Sponsorship is too weak

The change owner reports into a manager who can't say no to the executives whose teams are most affected.

Reason 03

Adoption is treated as the last phase

By the time anyone is thinking about it, the new tool/process/structure has already been built. For the wrong context.

Six engagement types we take on.

Business / IT transformation

Operating model changes, ERP and platform migrations, ways-of-working shifts.

Post-merger integration

The people-and-process side. Identity, security, ERP, network, harmonising governance under one roof.

Bi-modal IT rollouts

Agile and traditional delivery coexisting without civil war.

Agile/DevOps adoption beyond IT

Into facilities, finance, HR, ops. Where the discipline genuinely fits.

Cybersecurity programme change

The part most security work skips and pays for later.

Compliance as change programme

NIS2, CMMC, GDPR. Compliance is mostly behaviour, not technology.

Four phases. Honest sponsorship test up front.

Phase 01 · Weeks 1–3

The case for change

Two paragraphs anyone in the company would understand. If we can't write it, the transformation isn't ready and we'll say so.

Phase 02 · Weeks 4–6

Stakeholder & resistance plan

Who wins, who loses, who's neutral but loud. Where the resistance is. How we're going to address it directly.

Phase 03 · ongoing

Run the programme

Operational target, milestones, training, ritual changes, leadership behaviours. ADKAR, Kotter, Bridges. Used where they help, ignored where they're theatre.

Phase 04 · last 90 days

Make the new way the only way

Sunset the old process, retire the old tool, change the rituals. If the team can still do it the old way, you'll never finish.

Four things buyers ask.

Do you do change communications and training delivery?

We design and steer. We don't run a content shop or training delivery operation. That's where you bring in your in-house team or a specialist partner.

What if the executive sponsor isn't strong enough?

Then the transformation will fail and we'll tell you so before we start. The most useful thing we sometimes do is recommend you delay the programme by 90 days while you fix the sponsorship.

Can you join an in-flight transformation?

Yes. Often the most useful intervention. 4-week diagnostic on what's working, what isn't, and what the realistic recovery path looks like. About 30% of the time: "stop, restart with different sponsorship".

How long does a typical transformation take?

9 to 24 months for the structural part. 24 to 36 for the cultural part to be irreversible. Anyone promising you 3 months is selling you a re-org with a new logo.

Where to from here

Got a transformation that's in trouble?

Bring it. We'll tell you what's actually wrong, even if the answer is "stop the programme".