M54GrowStrategy & Growth· Module 4
Scaling Operations
What worked at 20 people fails at 70. Errors and complaints grow faster than revenue.
- Scale
- Grow
- Stabilise
- Operations
- People
- ~5 min · Checklist
The business problem
Informal ways of working succeed when the founder can see everything. As the business adds people, branches or volume, those methods break: new staff learn different ways, quality varies and managers spend their time firefighting.
Why it matters
Scaling requires the business to become repeatable: standard work, clear measures and a review rhythm that work without the founder present. Without them, growth multiplies problems.
What you will learn
- Recognise the signs that operations are not scaling
- Identify which processes must be standardised first
- Build replicable standards for a new site or team
- Put the management rhythm in place before expanding
Core questions
- What breaks first as volume increases?
- Could a new branch or team run from our written standards?
- What does the founder check personally that must become a system?
- Are we ready for the next step?
Work through the module
CaseWhat is happening?
Restaurant, second branch · Illustrative teaching case
A successful restaurant opens a second location. Recipes and portions differ, stock losses rise and cash is handled differently at each site. The first branch's system was the founder's presence. Before any further expansion, the business writes standard recipes, a stock and cash routine and a branch manager scorecard.
Full teaching case: Growth Broke the Business · The Second Branch
DecisionWhat does the leader need to decide?
Open a third branch now, or first make the model repeatable?
FrameworkHow should they think about the problem?
Standard work and the replicable operating model
Documented processes, clear measures and a daily review rhythm make work consistent. A replicable model packages them — standards, controls, roles and reviews — so a new site can run without the founder on site.
ToolWhat can they use?
Scaling readiness checkChecklist
- Core processes documented as SOPs
- Measures and targets for each site or team
- Controls for cash and stock
- Manager scorecard and review rhythm
- Training plan for new staff
ApplicationHow does it apply to their business?
Apply it to your own business:
- List what the founder checks personally each day
- Turn each check into a written standard
- Decide who reviews it when the founder isn't there
ImplementationWhat changes?
What should change in the business:
- Complete the checklist before the next expansion
- Pilot the standards in the existing operation
- Train managers to run the rhythm
ReviewDid it work?
How to tell whether the change worked:
- Are sites performing to the same standard?
- Have error and complaint rates stabilised as volume grows?
- Can a site run for a week without the founder?
After this module you should be able to decide
Open a third branch now, or first make the model repeatable?
And leave with: A scaling-readiness check and the standards needed before the next step.
Sequence · Strategy & Growth
Related modules
Part of these learning paths