The Designed Structure
The org chart. Tidy, hierarchical, largely theoretical. It tells you who reports to whom. It was designed for an industrial age that no longer exists.
The Method
Your organisation has two structures. One was designed. The other evolved — and it's the one that actually runs the place.
The org chart. Tidy, hierarchical, largely theoretical. It tells you who reports to whom. It was designed for an industrial age that no longer exists.
The informal network. Who actually gets consulted before a decision lands. Whose opinion quietly shapes outcomes three levels up. None of that appears on a reporting line.
ONA maps the second one. It analyses the real patterns of communication, collaboration, and influence across your workforce. The methodology is grounded in decades of network science. The output is something most senior leaders have never had: a map of how their organisation actually functions, not how they were told it does.
The Data
Your organisation is already generating the data. It has been for years.
Every email thread, every meeting invitation, every message on your collaboration platforms leaves a structural trace — not the content, never the content, but the pattern. Who initiates. Who responds. Who is consistently left off the thread.
ONA reads those patterns at scale and turns them into a map of your working relationships as they actually exist.
Where the metadata doesn't tell the full story, we ask. Short, targeted surveys — not another engagement questionnaire — that put specific questions to specific people: who do you go to when you're stuck, whose judgement do you trust, who in this organisation is genuinely difficult to reach?
The answers fill in what the data can't see.
No other diagnostic gets this close to operational reality.
The Findings
What the data surfaces tends to unsettle people. Not because it reveals dysfunction — though it often does — but because it shows how much has been happening outside the view of the people responsible for managing it.
They probably don't have a title that reflects it. They may not even realise it themselves. But remove them — through burnout, resignation, or a poorly timed restructure — and you'll feel it for months. ONA finds them before that happens.
Someone in your organisation is the single point of failure for too many decisions. Their manager thinks they're thriving. Their colleagues know better. ONA shows you the structural overload your HR data will never catch.
Not because of conflict. Because the organisation drifted and nobody noticed. Two functions that need each other are operating on parallel tracks, duplicating work, missing opportunities, occasionally making contradictory decisions. The org chart suggests they're connected. The network data says otherwise.
Beneath the structure, your people self-organise into clusters built on trust, shared language, and proximity of work. These informal communities are where culture actually lives — where new ideas spread or get killed, where change lands or doesn't. Most culture programmes never find them. ONA maps them.
There are connections that should exist and don't. Between a function with deep expertise and a team that desperately needs it. Between the people running the transformation and the people it's supposed to transform. These aren't relationship problems. They're design failures — and they're visible once you know where to look.
Most organisations find out how important someone was after they've gone. Attrition modelling lets you run that scenario before it happens — mapping whose departure would fragment a team, break a bridge between two communities, or leave a function functionally isolated. It changes how you think about retention, and who you're retaining for.
The candidate with the strongest track record and the weakest network position will struggle in a senior role that depends on informal influence. ONA doesn't replace your talent assessment framework. It adds the dimension that most frameworks are blind to: whether this person is actually woven into the fabric of the organisation they'd be leading.
DEI programmes stall when they're built on sentiment. ONA doesn't ask people how included they feel. It shows you whether they are.
An employee on the periphery of the network — present on the org chart, absent from the flows of information, opportunity, and trust — is not a culture statistic. They are a resignation waiting to happen.
The Outcome
Transformation programmes don't fail because the strategy is wrong. They fail because the people designing the strategy can't see the organisation they're designing it for.
They're working from the map, not the territory. They don't know which leader has the informal credibility to carry a change initiative and which one — despite the title — will quietly undermine it. They don't know which teams are already stretched to breaking point, or which relationships are one bad quarter away from collapse.
ONA doesn't make leadership easier. It makes the hard decisions harder to avoid.
When you can see where influence actually sits, you stop guessing which interventions will stick. When you know which people are structurally overexposed, you protect them before they leave rather than diagnose what went wrong after. When the network gaps are visible, you can close them deliberately rather than hoping the next reorganisation accidentally fixes them.
Most senior leaders make organisational decisions with less information than they'd accept in any other domain. That's not a personal failing. It's a data problem.
Stop managing the map. Start leading the network.
ONA solves it. A single engagement reveals what years of org charts and engagement surveys have missed.
Register Interest