The Scaling Readiness Assessment
Sixteen weighted questions that tell you which phase is actually blocking your growth, and which one you are wasting money on instead.
- PHASE 01DiagnoseKnow what is actually true
- PHASE 02DesignDecide how it works at the next size
- PHASE 03DeployMake the design real on Tuesday
- PHASE 04SustainHold it after attention moves
You are probably solving the wrong phase
Growth is not the hard part. Most companies can sell their way into a bigger number. What breaks is everything underneath it, and it breaks in a specific order.
Scaling is a change-leadership problem, which means it runs through four phases: Diagnose, Design, Deploy, Sustain. Skip one and the work downstream does not hold. Spend money in the wrong one and you get motion without movement.
The pattern is consistent. Companies feel pain, jump straight to Deploy, and buy something. A recruiter. An HR platform. A leadership offsite. The pain returns in eighteen months wearing different clothes, because the problem was never in Deploy.
The earliest weak phase is the only one that matters.
The phases are sequential, not parallel. A weak Sustain score does not mean you have a Sustain problem. If Diagnose is also weak, Diagnose is your constraint, because you cannot sustain a design you built on guesses.
This assessment scores all four, then names the earliest one that falls short. That is where the work starts. Everything after it is premature.
Diagnose
Do you know what is actually true right now, or are you working from impressions? Founders are systematically the last to hear bad news.
Design
Have you decided how this company works at the next size, or are you letting structure emerge and calling it culture?
Deploy
Can the organization actually run what you designed? A design nobody can execute is a document.
Sustain
Will any of it hold once your attention moves on? This is the phase almost everyone skips, and the reason the same problems return.
Symptoms lie about which phase they live in
Almost every scaling symptom presents as a Deploy problem, which is why almost every scaling budget gets spent there. Here is what the same five symptoms usually turn out to be.
| What it looks like | What most companies buy | What it usually is |
|---|---|---|
| Good people keep leaving | A compensation review | Design. There is no career architecture, so there is nothing to stay for. Paying more buys a delay, not a decision. |
| Nothing gets decided | Another recurring meeting | Design. Decision rights were never assigned. A meeting is where the ambiguity gets discussed, not where it gets resolved. |
| The founder is drowning | An executive assistant | Sustain. Everything still escalates to one person. You have made the bottleneck faster, not narrower. |
| New hires take forever to contribute | More senior hires | Deploy. Onboarding is improvised. Seniority does not compensate for having to guess at how things work here. |
| We tried this before and it did not stick | The same initiative, harder | Sustain. Nothing reinforced it after launch. The second attempt fails the same way unless the reinforcement changes. |
The score tells you the risk. The constraint tells you the work.
85 and above, ready to scale. Structure is ahead of headcount. Close what is open and proceed.
65 to 84, scale with guardrails. The foundation holds at current size and will strain at the next one. Fix the constraint phase in parallel with growth, not after it.
40 to 64, strained. Expansion will amplify what is already weak. Slow the hiring plan by a quarter and close the constraint phase first. This is the cheaper decision even though it will not feel like it.
Below 40, fragile. The business is running on individual effort rather than structure. Growth from here does not scale the company, it scales the fragility.
Do not start with your lowest score.
Start with the earliest phase that falls short. If Diagnose and Sustain are both weak, Sustain is a symptom. You cannot reinforce a design you built without facts, and you cannot fix reinforcement while the underlying design is still a guess.
The panel names your constraint automatically. Work it until it clears, then re-run this. The answers move faster than you expect once the right phase gets attention.
Turn the constraint into a plan
A Leadership OS Assessment is a structured working session with your leadership team. We pressure test the phase your result flagged, identify what has to be built before the next growth jump, and leave you with a sequenced plan rather than a list of concerns.
Schedule a Leadership OS Assessment