Service / Growth infrastructure
Build the operating foundations growth will ask for next.
Growth infrastructure helps a team decide which operating habits, roles, and decision systems need to mature before more complexity turns into recurring friction.
Discuss this workBest fit
Who it is for
Founder-led teams approaching a new stage of complexity: more people, more customers, more parallel work, or a leadership group that needs more than informal coordination to stay aligned.
Working aim
A focused, proportionate operating foundation that supports growth without importing bureaucracy ahead of need.
Signals to investigate
The friction is usually visible before it is named.
- New hires need repeated oral context to understand priorities, decisions, and how work moves.
- A small number of leaders still act as the route through most cross-functional questions.
- The company has added tools and meetings faster than it has clarified the operating rules behind them.
- Teams solve similar coordination problems repeatedly because the learning never becomes a shared practice.
Method
Build around the work people actually need to do.
Identify the near-term growth pressures and the operating assumptions that are unlikely to hold as complexity increases.
Prioritise a small number of foundations across ownership, decisions, cadence, and delivery instead of pursuing an abstract maturity model.
Turn the priorities into usable practices, introduce them in context, and leave room to adapt as the organisation learns.
Practical outputs
Useful artefacts, not a deck that needs translating.
- A view of the operating pressures most relevant to the next stage
- A prioritised foundation plan with clear choices and dependencies
- Role, decision, and working-practice notes for the selected areas
- Simple templates or rituals that support adoption in live work
- A practical review point for deciding what to strengthen next
How the work moves
Flexible phases, paced by the problem and the team.
The sequence below is a guide rather than a fixed-duration programme. The depth of each phase changes with the scope, availability, and what emerges in the work.
- 01
Frame the next stage
Make the coming growth pressures and current operating constraints explicit enough to choose where to focus.
- 02
Choose the foundations
Select the few practices worth strengthening now, with attention to the order in which they can realistically be adopted.
- 03
Embed and revisit
Introduce the practices through real work and establish how the team will revisit them as its needs change.
Operating-system map
The service strengthens one part of a connected system.
The parts reinforce one another: priorities guide decisions, decisions shape the working rhythm, and delivery and learning keep the system useful when conditions change.
What to look for
Observable examples of a clearer way of working.
- A leadership team can explain which decisions should remain close to the work and which need a wider forum.
- New team members can find the current priorities, their operating context, and the route for resolving common questions.
- A recurring review distinguishes an operating problem that needs a new practice from a one-off issue that needs a local decision.
- The team has a visible shortlist of operating foundations to improve, rather than a broad and unowned transformation agenda.
Boundaries
What this work does not replace.
- It is not a substitute for a company strategy, a hiring plan, or functional expertise where those are the underlying need.
- It does not assume that every growing team needs the same structure, toolset, or management layers.
- It does not remove the need to revisit choices as the company, its market, and its people change.
Questions
FAQs
How do we avoid adding bureaucracy too early?
The work starts with a concrete operating pressure and favours the smallest practice that addresses it. If a rule, forum, or artefact does not help people make or execute a decision, it should be questioned.
Does this require an organisational redesign?
Not necessarily. The scope may include clearer roles or decision rights, but it is designed around the foundations most useful at the current stage rather than a predetermined reorganisation.
Can we start before the next growth milestone is certain?
Yes. The aim is not to predict every future condition. It is to strengthen the practices that reduce today’s recurring friction and give the team a better way to adapt when conditions change.
Start with the friction