The Observation That Led to Organisation Insights

Over forty M&A engagements at Element taught me one thing more clearly than any other: the decisions that cost most are the ones made without an accurate picture of the current state.

Not because organisations are careless. Because current-state analysis is the work that gets cut when timelines are tight and the pressure to show momentum is real. Because the picture it produces leads with constraints rather than possibilities — which makes it a difficult document to table when an investment has already been approved. Because most organisations have never needed to produce it in a form that is structured enough to be tested, verified, and usable across a programme.

What I kept seeing in M&A appeared in different forms elsewhere.

• A transformation programme that had designed a target state against an assumed current state — and discovered mid-execution that the path between them did not exist in the way the roadmap required.

• An enterprise software implementation that hit a structural problem nobody had been asked to investigate before go-live.

• A strategy document that was coherent at the level it was written and incoherent at the level it needed to be executed — because nobody had mapped it against what the organisation could actually do.

The gap was consistent. The context varied. The cost of encountering it mid-programme was, in each case, significantly higher than the cost of surfacing it at the start.

Organisation Insights was built around that observation. The work is structured current-state analysis — a methodology that covers four interconnected areas: the technology estate, the people and their positions, the business processes, and the strategic context. Each produces its own picture. Together they produce a model of the organisation that can be used to test assumptions, sequence change, identify constraints, and ground decisions in what is actually there rather than what is assumed to be there.

The organisations we work with are preparing for acquisitions, planning transformation programmes, selecting and implementing technology, or trying to understand what they have before committing to a direction. What they have in common is a recognition that the analysis preceding the decision determines the quality of the decision — and that doing it properly requires a structured approach rather than a documentation review.

The work is not glamorous. It surfaces things that are uncomfortable. It takes longer than producing a target-state document. And it consistently changes what gets planned, how long things realistically take, and where the actual risks sit — before they become the kind of discoveries that programme reviews are written to explain.