Embedding is a project in its own right

Every organisation has a change plan. Almost none of them have an embedding plan. And that is exactly where the investment walks out the door. The announcement gets made. The consultants pack up. The new structure goes live. And then everyone assumes the hard work is done. It is not.

Here is what I see in organisation after organisation. The project gets a business case. It gets a sponsor, a timeline, a budget, and a steering committee. It gets reported on at every ELT meeting until go-live. And then? The embedding phase gets a vague intention and a hope that leaders will figure it out. No formal plan. No defined outcomes. No one tracking whether the benefits are actually landing. No executive accountability for what happens after the announcement. This is not a resourcing problem. It is a priority problem.

The hard work is what comes next - the Tuesday mornings, the conversations nobody is having, the leaders who are still waiting to see if anyone notices whether they have actually changed or not. I have worked inside enough transformations to know that the messy middle - the part no one plans for - that's where organisations are either won or lost.

And the capability I bring to that work is not just technical. It is the willingness to stay present in the complexity, to keep asking what the human experience is, and to build the capability of the leaders around me so that when I leave, they can hold it themselves. That last part matters. Because sustainable transformation is not dependent. It is built.

Embedding is not a phase. It is a discipline. And it deserves the same formal treatment as the project that preceded it - a written plan, defined outcomes, tracked benefits, and executive sign-off. Organisations treat embedding as the tail end of the project. It should be treated as a project in its own right. Same rigour. Same governance. Same expectation of results.

The change was expensive to design. Protect that investment by being just as deliberate about making it stick. Without that, you are not embedding change.

You are hoping it sticks.

Join the conversation on this piece over on LinkedIn  ·  Back to Insights