Somewhere in the early weeks of a startup's life - before there is an org chart, or job descriptions, and before anyone has thought about governance - its shape begins to form.
Not planned, but as an emergent pattern.
Work moves. Decisions get made. Someone answers the customer. Someone else handles the build. And whoever handles what, this week, is likely to handle the same thing next week. None of this was decided. It happened because it was convenient and it worked. And because repetition is the path of least resistance.
This is how organisational shape begins: not through design, but through flow.
The structure nobody builds
Founders think of organisational structure as something that arrives later; after the product is established, the team has grown, and there is something substantial enough to organise around.
They are right that formal structure arrives later. They are not right that the organisation is shapeless until this point.
Work flowing through an organisation creates channels. Channels become paths. Paths become expected routes. By the time a startup is thinking about its first formal hires, it already has default decision-makers, established priorities, and implicit rules about how things get done. Implicit and undocumented.
Speed and its consequences
The primary driver of early flow decisions is urgency.
There is no time to think carefully about where a decision should sit. There is a customer waiting, a feature breaking, a deadline approaching. Someone picks it up. The person who picks it up tends to be whoever has the most context, the most availability, or the most willingness to act.
This produces organisations that function. It does not produce organisations that are aligned.
If a startup's strategy - even an implicit one - is to build a product that a particular kind of user loves, then the shape of the organisation should, ideally, reflect that. Who has authority over product decisions. How quickly feedback moves from users to builders. Where trade-offs get resolved.
Early flow decisions do not consider any of this. They consider what needs to happen right now.
How patterns become structures
The transition from emergent pattern to structure happens gradually, through accumulation.
The engineer who fixed the first three infrastructure problems becomes the person others defer to on infrastructure questions, even after the team has grown and others might be more qualified. The founder who handled the first difficult client conversation becomes the person difficult clients ask for, regardless of whether that is the best use of their time at scale.
What begins as a practical arrangement becomes an expectation. What becomes an expectation becomes, in effect, a rule. The organisation has acquired a shape - a set of default flows, embedded ownerships, and implicit authorities - that will influence how everything subsequently works.
The window that closes
There is a period, in the early life of any startup, when this emerging shape is still malleable.
Roles exist, but have not calcified. Patterns have formed, but can be disrupted without significant cost. The person who has defaulted into a particular kind of decision-making can be redirected, the flow of a particular kind of work can be reoriented, without unravelling the organisation to do it.
At this stage, it is still possible - without restructuring or significant disruption - to ask: “Does the way work currently flows reflect where we are trying to go? Are the right decisions sitting with the right people? Are the patterns that are forming ones we would choose?”
The window in which these questions are cheap to act on is narrow. A few weeks. A few months, at most.
In no time, that window of opportunity has closed, and probably went unnoticed.
What hardening looks like
After the window closes, the costs of changing shape increase significantly.
Systems have been built around the existing flows. New people have been hired and have learned how things are done here; not from documentation, but from observation and imitation. Expectations have formed around roles and responsibilities. Relationships have developed around established coordination paths.
To change any of this requires working against accumulated momentum. The decision-making pattern that would have shifted with a conversation in month two requires a reorganisation in month eighteen. The coordination path that could have been redrawn with an afternoon's thought now requires new processes, new accountabilities, and a communication programme.
Shape, once embedded, resists change, simply because everything else has grown around it.
Scale as a diagnostic
Growth exposes the shape that early decisions built.
At small scale, informal structures work because everyone has full context. The default decision-maker knows enough to make most decisions well. The informal coordination path works because the people on it can communicate without process.
At larger scale, these conditions no longer hold. The decision-maker cannot have full context across a larger organisation. The informal coordination path, stretched across more people and more complexity, becomes slow and unreliable.
The symptoms that follow - slowing delivery, unclear ownership, recurring bottlenecks - are not failures of the people involved. They are the stress patterns of a shape that was formed for a smaller, simpler organisation, now carrying a larger load.
What the startup shape becomes
The informal patterns of an early startup do not disappear as the organisation matures. They become formalised.
Default decision-makers are given titles. Informal coordination paths become governance processes. The implicit escalation thresholds become policy.
The shape that emerged from early, practical, speed-driven flow decisions is now the operating architecture of the organisation. Its origins are largely invisible or forgotten.
And strategy must travel through it.
The late arrival of strategy
Most startups formalise their strategy after their shape is already established.
A new strategy enters an organisation that already has embedded flows, concentrated authorities, established patterns. The strategy may call for distributed decision-making; the organisation has centralised it. It may require cross-functional collaboration; the informal structure has created silos. It may depend on rapid delivery; the embedded coordination paths add friction at every step.
The misalignment is the result of strategy arriving into a system it was not designed to fit, and inheriting constraints created by decisions made long before anyone was thinking strategically.
Awareness before design
Early-stage startups do not need formal organisational design. They need to move.
But there is something they can do that costs very little and matters a great deal:
- Noticing how work currently flows
- Observing where decisions are landing
- Recognising which patterns are repeating and whether they reflect what the organisation is trying to become.
This is not a matter of (re)design. It is a matter of noticing and maintaining the option to adjust the shape before it hardens.
The formal governance questions - decision rights, escalation structures, accountability frameworks - come later. But the informal patterns that will become those structures are forming now.
The shape that is inherited
The organisational shape of a startup doesn’t wait to be designed. It forms immediately, through the first practical decisions about how work moves.
It forms quickly, through the repetition that turns convenience into convention.
It hardens gradually, as systems and expectations accumulate around it.
And by the time the organisation’s scale makes it visible, it is already expensive to change.
The brief window during which the shape is still forming, and alignment is still possible, passes largely unnoticed.
Ady Coles works with leadership teams to help strategy survive contact with reality. His focus is on strategy management and agile strategy delivery - designing the translation between intent and execution so that direction remains coherent as organisations move, grow, and adapt. He works as a fractional and advisory partner where clarity, judgement, and sustained alignment matter more than plans on paper.