Growth Stage: Organize It

STAGE: Growth Stage
ORIENTATION: Roughly $10M-$50M / Typically 20-100 employees
NAME OF THE GAME: Organize It
MASTERY TARGET: Organizational Capability
FOUNDER ROLE: Orchestrator, standard-setter, leadership-team builder
DOCTRINE: Know which game you are playing before you decide what advice to follow.

Growth Changes the Management Problem

A Growth Stage company can be healthier on paper and harder to run at the same time. Revenue is up. The team is larger. There are managers, specialists and systems that did not exist a few years ago. Yet the founder can feel more necessary because more work crosses functional boundaries and more exceptions reach the person with the broadest context.

The instinct is often to add more people, more software, more meetings or a stronger executive. Those moves can help. They can also add another layer of coordination to a management system that was never designed.

The Organize It game begins with a different question: what capability does the organization itself need so added complexity does not automatically become added founder involvement? Revenue is the scoreboard. Capability is the win condition.

ASK ATHENA WHAT GROWTH REQUIRES FROM YOUR COMPANY

Describe where complexity is creating the most friction. Athena will help you look across Revenue, Operations and Leadership before recommending a direction.

What Winning This Game Means

Organizational Capability is becoming dependable when the company can create, sell, deliver, manage, decide and learn through managers, standards, systems and shared judgment under ordinary pressure.

A document, meeting rhythm, org chart or software platform counts only if the behavior it was meant to create is visible.

What Management Must Accomplish at This Stage

Turn founder judgment into standards, decision criteria, role expectations and leadership capability.
Design managerial roles around outputs, complexity, time horizon, authority and interfaces rather than titles alone.
Build functional leaders who own significant outcomes and develop capability beneath them.
Make recurring cross-functional work explicit enough that it does not require founder arbitration.
Build operating and financial visibility that warns management before margin, working capital or capacity become emergencies.
Concentrate the founder on a deliberately narrow reserved-decision set rather than ordinary complexity.

Problems and Stall Signals That Often Show Up Here

The sales playbook exists, but only the founder can make it work.
Pricing exceptions multiply faster than the pricing logic can explain them.
Process documents exist, but exceptions still return because judgment rules are missing.
Function leaders own numbers but lack authority to affect them.
Leadership meetings report upward and wait for founder direction.
New management layers add communication delay but little distinct managerial value.
Revenue grows while cash emergencies, working-capital surprises or capacity problems repeat.
The founder is in fewer meetings but remains the hidden approval system.
Founder absence creates a backlog of ordinary decisions.
Strategy and leadership development keep losing time to current operating exceptions.

Founder Experiences That Often Show Up Here

The Growth Stage is dense with recognizable founder experiences because increasing complexity exposes the difference between personal capability and organizational capability.

Revenue Grows Without Corresponding Health: growth can hide weak economics or fragile capability.
Paper Profit, Real Cash Pressure: revenue and accounting profit do not eliminate working-capital risk.
Informality Becomes Expensive: shared context no longer scales across functions and layers.
Capable Functions Still Require Founder Integration: good departments still need one person to make the company act like one company.
Decisions Return to the Founder and Delegated Responsibility Migrates Back: the organization executes work but ambiguity travels upward.
Senior Leadership Cannot Remove Founder Dependency: hiring an executive does not change the system if capability or authority is unclear.
The Founder May Be Part of the Constraint and Earlier Strength Becomes a Ceiling: the same speed, judgment and intervention that built growth can become an upstream constraint.

Problem Finder

Which of these sounds most familiar?

Select a problem to read its canonical description. These are characteristic stage problems, not claims of statistical prevalence.

Strategies and Tactics That Fit Now

Founder-led selling by exception

Use founder participation for strategic deals, unusual relationships or situations where founder involvement has defined value. Ordinary pipeline should belong to revenue leadership. The evidence is that deal progression and pricing remain dependable when the founder is absent.

Critical-path standard work

Standardize processes where variation damages quality, margin, safety, retention or cash. Preserve discretion where expert judgment creates value. The goal is not documenting every task. It is making the critical path dependable.

Managerial Role Charters and Role-Horizon Audits

Define the outputs, work complexity, horizon, decision authority, interfaces, team accountability and measures before selecting the person. Then ask whether each leader is spending enough time at the horizon their role exists to own.

Decision architecture

Use explicit decision records for consequential, recurring, cross-functional or repeatedly delayed decisions. Name the owner, required input, boundary, escalation trigger and review point. Not every small decision needs a map. The decisions that repeatedly create delay or founder escalation do.

Weekly operating review, monthly strategic/financial review and quarterly priorities

Weekly forums should close decisions, commitments and constraints. Monthly reviews should examine forecast assumptions, working capital, margin, capacity and strategic exceptions. Quarterly priorities should force tradeoffs, name one owner and define evidence of completion.

Leading scorecard

Track a small set of leading measures tied to management questions and action thresholds. More metrics do not create more management. Visibility without action becomes reporting overhead.

Founder Approval Log and Founder Rescue Review

For two weeks, record approvals and alignment requests that reach the founder. Classify why they came upward: missing capability, unclear authority, missing information, habit or founder reinsertion. Review recent rescues the same way. Look for categories, not isolated incidents.

Two-week founder absence stress test

Predeclare the few decisions that truly require the founder, let ordinary operating decisions move and review what waited, what moved and what was reopened. Use the result as diagnostic evidence, not as a performance stunt.

Wrong-Game Advice to Reject

Decentralizing consequential authority before managers, standards and financial visibility are dependable.
Hiring a COO and expecting one person to substitute for missing organizational capability.
Adding layers because the company feels busy without defining the distinct managerial value of each layer.
Installing elaborate enterprise metrics while basic ownership and decision rules remain weak.
Calling the founder the bottleneck while continuing to preserve preference-based vetoes and answer questions other leaders should own.

How You Know You Are Winning

Ordinary new business is created and advanced through a team and method rather than founder reputation alone.
Ordinary pricing stays inside explicit guardrails without founder approval.
Critical work maintains acceptable quality through founder or key-person absence.
Function leaders own significant outcomes and decisions inside defined authority.
The leadership team resolves ordinary cross-functional issues without founder arbitration.
Management layers add distinct context, integration or judgment instead of acting as approval relays.
Management can forecast working-capital, margin and capacity consequences before they become emergencies.
The founder owns a small reserved-decision set and a two-week absence does not create a backlog of ordinary decisions.

What Opens Next

When Organizational Capability is dependable, the next problem is no longer whether managers and systems can perform. The next problem is whether consequential authority can move through capable leaders and units without routine founder approval.

That is the Early Scale Stage. The next game is Decentralize It. The next mastery target is Distributed Authority.

Ask Athena About This Stage

Go Deeper

Use the Founder’s Map to locate the game and identify uneven development. Explore the Growth Stage Playbook for the full management field guide. Read The Founder’s Gauntlet for the Five Games map and The Founder’s Trap when founder dependency is the binding mechanism.

THE FOUNDER’S GAUNTLET

Know the game, the gate ahead and the organizational capability required to earn the next game.

GET THE DIGITAL BOOK FOR $1

Founder's Map Stage Field Guide The Founder's Gauntlet