Service / Growth infrastructure
More people should not mean more decisions waiting on you.
As the team grows, habits that once worked can start getting in the way. Find which roles, decisions, and routines need to change first.
Discuss this workBest fit
Who it is for
Founder-led teams adding people, customers, or parallel projects, where a quick conversation no longer keeps everyone up to date.
The aim
Working habits the team can use as it grows, with only the process it needs.
Common problems
Does any of this sound familiar?
- New hires need someone to explain the same priorities, decisions, and working habits each time.
- 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.
Look at what is growing and which current habits are already struggling to keep up.
Choose a few changes to responsibilities, decisions, meetings, or delivery that would help now.
Try those changes in daily work. Write down what people need and revise it as you learn.
What the work can include
Documents and tools the team can use.
These are examples. The scope determines what we agree to deliver.
- A list of the working habits most likely to struggle as the team grows
- An ordered plan of changes and what each one depends on
- Written responsibilities, decision owners, and working instructions
- Templates and routines to use on current work
- A practical review point for deciding what to strengthen next
How the work moves
Start small, then adjust.
The steps below are a guide. Timing depends on the scope, who is available, and what we find.
- 01
Look at what is growing
Identify what more people, customers, or projects will ask of the team, and where it already struggles.
- 02
Choose what to change first
Select the few practices worth strengthening now, with attention to the order in which they can realistically be adopted.
- 03
Try it and review it
Introduce the practices through real work and establish how the team will revisit them as its needs change.
Operating-system map
How priorities become finished work.
Priorities guide decisions. Reviews show what is moving and what is stuck. What you learn changes the next plan.
What to look for
What a useful change could look like.
- 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 short list of changes to make, with someone responsible for each one.
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?
Start with a problem people are already having. If a rule, meeting, or document does not help them decide or act, question whether it needs to exist.
Does this require an organisational redesign?
Not necessarily. Clearer responsibilities or decision owners may be enough. The scope depends on what the team needs now.
Can we start before the next growth milestone is certain?
Yes. Start with recurring problems you already have. Review the changes as the company grows and the needs become clearer.
Start with the problem