Insights
/
Transformation
Transformation that works looks different from transformation that gets presented. The difference is who is doing the work — and where they are doing it from.
The consulting model and its limitations
The conventional consulting model for transformation follows a familiar sequence. An external team is engaged to diagnose a problem, develop recommendations, and — if the engagement extends to implementation — provide oversight and advisory support as the client organisation attempts to execute against those recommendations.
This model has produced genuine value in many organisations. It also has a structural limitation that is well understood by clients who have been through the experience: the distance between the consultant's recommendations and the organisation's operational reality is often larger than it appears at the time the engagement is designed.
A team that diagnoses a problem from the outside, working primarily through interviews, data reviews, and process mapping, will develop a picture of the organisation that is accurate at a high level but that inevitably misses the texture and complexity that only becomes visible through sustained, close engagement. The recommendations that emerge are shaped by that picture. When they encounter the full complexity of implementation, the gaps in the model become the gaps in the plan.
What embedded transformation looks like
Embedded transformation is a different approach. Rather than providing diagnosis and recommendations from outside the organisation, an embedded team works inside it — joining the operations they are helping to improve, participating directly in the management rhythms that will sustain the change, and doing the hands-on work of implementation rather than advising those who do it.
This distinction is not merely structural. It changes the quality of the insight available, the speed with which problems can be identified and addressed, and the degree to which the changes made are genuinely embedded in how the organisation functions rather than documented in plans that may or may not translate into operating practice.
An embedded operator who sits in the daily operational meetings of a business function understands that function differently from one who reviews its performance data and interviews its leaders. They see the informal dynamics that determine how decisions are actually made. They observe where the process that exists on paper diverges from the process that is actually followed. They hear what is not said in formal settings but is discussed with consistency in the corridor. That understanding is not achievable from a distance, and it meaningfully improves the quality of the transformation work that follows.
The credibility of doing
Transformation that is led by people who are doing the work, rather than advising those who do it, generates a different kind of credibility within the organisation.
The teams inside an organisation undergoing transformation are acutely aware of whether the people leading the change have genuine operational credibility — whether they understand the realities of running the function they are proposing to change. An embedded operator who has worked at senior levels in comparable environments, who can speak to their own experience of having solved similar problems, and who is visibly committed to working through the implementation details rather than delegating them, earns trust in a way that a more advisory relationship cannot replicate.
That trust is not incidental. It is one of the primary determinants of whether the change programme achieves genuine adoption or merely compliance. Teams that trust the people leading a change are more likely to engage with it honestly — to surface the real barriers to implementation rather than managing the perception of progress, to raise the problems that need addressing rather than finding workarounds, and to sustain new practices after the change programme has formally concluded.
Diagnosis that stays alive
One of the features of embedded transformation that is often underappreciated is the ongoing quality of the diagnostic work. In a conventional consulting engagement, diagnosis happens at the beginning and informs the programme design. Once implementation begins, the diagnostic phase is formally concluded and the organisation is working from a fixed picture of what needs to change and why.
Embedded transformation allows the diagnosis to remain alive throughout implementation. An operator who is consistently present in the organisation continues to receive and interpret information about performance, about emerging problems, and about the ways in which the change programme is or is not producing the intended effects. When reality diverges from the model — as it inevitably does — the embedded team is positioned to recognise that divergence early and adapt the programme accordingly.
This adaptability is one of the most significant advantages of the embedded approach. Transformation programmes that are designed and then executed against a fixed plan, without meaningful feedback loops, tend to deliver the plan rather than the outcome. The plan and the outcome were aligned at the point of design. As implementation proceeds, that alignment degrades. The organisations that respond most effectively to this divergence are those with someone close enough to the work to see it and the authority to act on what they see.
Building internal capability
A further advantage of embedded transformation is its effect on internal capability development. When external support works alongside the internal team rather than in parallel to it, the knowledge transfer is continuous and practical — it happens through the shared experience of solving actual problems rather than through formal training that may or may not connect to the daily work.
Internal leaders who have worked closely with experienced operators through a significant transformation develop capabilities that cannot be acquired any other way. They have seen how a particular type of problem is diagnosed and approached. They have observed the judgement calls made under time pressure and uncertainty. They have had the experience of their own instincts being tested against a more experienced reference point in real time, and of learning from those moments in a way that is considerably more durable than instruction alone.
This is the difference between an engagement that improves performance for the duration of the external support and one that improves the organisation's capacity to continue improving after that support has concluded. The organisations with the most durable transformations are typically those that invested in building real capability rather than importing temporary expertise.
The honest question of proximity
Embedded transformation requires a willingness on both sides to accept a different kind of working relationship — one that involves genuine proximity to the organisation's operational reality and a degree of candour that is harder to sustain at arm's length.
For organisations that are accustomed to managing external advisors at a distance — providing curated access to information, managing the relationship at the senior level — this requires a shift in approach. The value of embedded transformation depends on honest access: to the real performance data, to the genuine constraints, to the people who understand where the problems actually sit. Without that access, the embedded model produces the same quality of insight as any other advisory relationship, at greater cost and inconvenience.
When that access is provided in good faith, the quality of the transformation work that results is of a different order. It is grounded in an accurate understanding of the organisation as it actually is, delivered by people who are genuinely accountable for the outcomes they are working toward, and designed to leave the organisation in a better position to manage its own performance once the external engagement concludes.
Let's chat.
We love solving complex problems.
Let's discuss yours.

Morgan
Simplify • Transform • Deliver



