An investment-funded technology business asked HumanDynamics to identify what was blocking growth and assess whether the organisation could deliver its plan. Three structural problems emerged — none visible from the org chart, each a material constraint on the business's ability to scale.
The business had investment, a product in market, and a growth plan. What it lacked was confidence that the organisation was structured to deliver that plan. Growth was slower than it should have been, execution felt harder than team size suggested, and the CEO sensed something structural was blocking progress — without being able to identify what.
HumanDynamics mapped the actual collaboration structure of the business: how decisions were being made, where information was flowing, which functions were connected to which, and where the structural constraints on growth actually sat.
Three distinct findings emerged. Each was independent. Together they explained why a business with the right ingredients was not producing the outcomes its plan required.
"The plan described what the business needed to do. The network showed why it was structurally incapable of doing it."
HumanDynamics structural analysis findingThe network showed the CEO as a single point through whom the majority of collaboration, decision-making, and information flow was routed. Attempts to delegate had been made but had not translated into structural change. Those with nominally delegated authority remained peripheral to the flows they were supposed to be managing.
Some founder centrality in a business of this size is expected. What the network revealed was centrality at a level that had become a structural constraint. The CEO was not just involved in key decisions — they were the routing point for decisions that should have been made independently. Information that needed to move across the organisation was moving through the CEO rather than between the functions that needed it.
Delegation had been attempted but structural analysis explained why it had not worked: those given delegated authority had not acquired the network connections needed to exercise it. Formal authority and structural influence were misaligned. The CEO remained the de facto centre even where they were not intended to be.
A business structured this way has a hard ceiling on its growth rate: the bandwidth of the CEO. Every additional hire, new market, or increase in operational complexity adds load to a single structural node. The organisation could not scale faster than one person could process — regardless of the capital behind it or the quality of the plan.
The standard response to founder bottleneck is to hire a leadership team and formally assign authority. This is necessary but insufficient: formal delegation changes the org chart, not the network. If people continue routing decisions and information through the founder — by habit or necessity — the structural bottleneck persists regardless of what reporting lines say.
Structural delegation requires the network to reorganise around new authority, not just new titles. That reorganisation can be designed and accelerated — but only once the current structural state is visible.
Founder dependency is among the most common structural risks in growth-stage acquisitions — and among the most underestimated. Structural analysis distinguishes between businesses where delegation has genuinely taken hold and businesses where it exists on paper only. That distinction is not visible from the org chart or management interviews. It is visible from the network.
The operational core — teams managing delivery and product — were densely connected and central. Sales and business development were structurally peripheral: poorly connected to the core, with limited access to the information and relationships needed to operate effectively, and largely absent from the flows that determined organisational priorities and resource allocation.
The business had been built around making a product work. In the early stages that was correct, and the network had organised around it — operations and product central, commercial activity secondary. The problem was that the network had not reorganised as strategic priorities shifted to growth. The structural priority was still delivery, even as the commercial imperative had become urgent.
Commercial functions were operating with structural disadvantages unrelated to their capability. They lacked access to product knowledge needed to sell effectively, were absent from priority-setting conversations, and their resource requests were structurally less visible than those of the delivery teams at the network's centre.
The growth plan assumed commercial execution at a level the structural conditions did not support. Sales targets had been set and investor commitments made against an implicit assumption that the organisation was oriented toward commercial outcomes. The network showed it was not. The plan and the structure were in conflict — and the structure was winning.
Closing the gap required structural change: integrating commercial functions into the flows where priorities were set and decisions were made. Not additional headcount — a different network.
This pattern — a business built for delivery that has not reorganised for commercial scale — is one of the most consistent findings in growth-stage technology businesses at the point of acquisition. Commercial acceleration programmes stall when the organisation is not structurally oriented toward the outcomes they require. Identifying this before the VCP is designed prevents the most common and most expensive version of that failure.
Beyond the misalignment in Finding 02, the network revealed deeper fragmentation. Engineering and Business Development — critical to both delivery and growth — were structurally isolated, not just from each other but from the core. The UK operation had limited structural integration with the rest of the business, functioning as a partial silo rather than a connected part of a coherent whole.
For a technology business, Engineering is a core value driver. Its structural position determines how quickly product decisions are made, how well commercial requirements translate into delivery, and how effectively technical capability compounds. The network showed Engineering insufficiently integrated with the commercial, operational, and leadership functions whose decisions determined what it was asked to build and when — leaving it reactive rather than strategically embedded.
The UK operation had not been deliberately isolated — the disconnection had emerged over time. Information flow between the UK and the core was thin, collaborative relationships sparse, and priorities misaligned with the broader organisation. The consequences were being absorbed as friction rather than recognised as a structural problem with a structural solution.
Structural fragmentation does not stay static. An Engineering team peripheral to commercial decisions becomes progressively less able to anticipate commercial needs. A geography that is poorly integrated develops its own priorities and culture, making subsequent integration progressively more difficult. The structural conditions present at the time of analysis were the beginning of a trajectory, not a stable state.
Identifying fragmentation before it becomes entrenched is the point at which it is cheapest to address. The network provided the evidence needed to design integration grounded in actual collaboration patterns — not org chart assumptions about what should already be connected.
Functional and geographic isolation is systematically underweighted in pre-acquisition diligence, which assesses capability within functions rather than connectivity between them. A strong Engineering team and a capable regional operation can both appear adequate in isolation while being structurally fragmented in ways that directly constrain execution. Integration plans built on an assumption of organisational coherence — when the underlying structure is fragmented — consistently underdeliver on synergy targets and timelines.
Three findings. Each identified a constraint the growth plan had not accounted for — and each required a different set of decisions to address.
| Decision area | Without structural analysis | With HD structural analysis |
|---|---|---|
| Finding 01 — CEO bottleneck & delegation failure | ||
| Leadership design | Delegation assumed to be working based on org chart. Gaps attributed to individual capability rather than structural failure. | CEO structural centrality quantified. Delegation failure identified as a network problem — requiring structural intervention, not personnel change. |
| Scaling strategy | Growth targets set without accounting for structural constraint on execution speed. Capital deployed against a plan the organisation was not built to deliver. | Hard ceiling on growth rate identified before further capital was deployed. Structural delegation programme designed to redistribute network centrality, not just formal authority. |
| Finding 02 — Commercial activity structurally peripheral | ||
| Commercial execution | Revenue underperformance attributed to commercial team capability or market conditions. Structural misalignment not identified as a cause. | Peripheral position of commercial functions identified as the primary constraint. Redesign focused on structural integration of sales and BD into the core — not additional headcount. |
| Resource allocation | Operational teams continued to command structural priority. Commercial requests remained less visible and less influential than delivery demands. | Organisation structurally reoriented toward commercial outcomes — changing which conversations commercial teams were part of, not just their size. |
| Finding 03 — Functional and geographic isolation | ||
| Engineering integration | Engineering assessed as capable in isolation. Peripheral structural position not identified. Misalignment with commercial and product functions attributed to process failure. | Engineering's structural isolation identified and corrected in the redesign — integrating technical capacity into the decision flows where it was needed. |
| UK operation | UK treated as operationally adequate. Structural disconnection invisible. Integration risk not factored into the growth plan. | UK isolation quantified. Integration programme designed around actual collaboration gaps — before the disconnection compounded further. |
The structural evidence changes the decisions. The conversation starts here.
Request a Consultation