Process Scaling Framework

Purpose

This recipe produces a Process Formalization Roadmap that tells a startup exactly which processes to document, automate, or eliminate at each headcount milestone (10, 25, 50, 100) and a Process Audit Checklist assessing the current state. The core tension in scaling is that too little process causes chaos while too much process kills speed. This framework specifies the minimum viable process at each phase. [src1]

Prerequisites

• Team size known — current headcount and 12-month target determines which phase to plan for
• Scaling readiness assessed — Scaling Readiness Assessment
• Hiring plan exists — Hiring Scale-Up Playbook
• List of recurring tasks — identify all repeatable work currently done by the team
• Knowledge of current pain points — where things are breaking, being dropped, or inconsistent

Constraints

• Never formalize a process that has not been executed manually at least 5 times. Premature formalization encodes wrong assumptions. [src3]
• Process documentation must be owned by the executor, not a manager. People who design processes without executing them create bureaucracy. [src6]
• At under 15 people, avoid approval workflows or formal sign-offs. The coordination overhead exceeds the cost of errors they prevent.
• Every process must have a single owner and a review date. Unowned processes become zombie bureaucracy. [src2]
• Process overhead should not exceed 15-20% of any employee's time. [src5]

Tool Selection Decision

Which path?
├── Currently 1-10 people → growing to 15-25
│   └── PATH A: Minimal Docs — shared docs + verbal handoffs, document only what breaks
├── Currently 10-25 people → growing to 30-50
│   └── PATH B: Core Playbooks — Notion/Confluence playbooks + lightweight automation
├── Currently 25-50 people → growing to 50-100
│   └── PATH C: Process Library — full process library + workflow automation + metrics
└── Currently 50+ → growing to 100+
    └── PATH D: Process Operations — dedicated ops function + process governance

Execution Flow

Step 1: Audit Current Processes and Pain Points

Duration: 1-2 hours · Tool: Spreadsheet

Create a Process Audit Matrix for every recurring activity. Categorize into five functional areas: Product/Engineering, Sales/Revenue, Customer Success, People/HR, Finance/Admin. Score each on breakage frequency (1-5) and breakage impact (1-5). Processes scoring 15+ are critical. [src1]

Verify: All recurring processes listed, scored, and ranked. · If failed: If the team cannot list processes, spend 1 week tracking all work done, then audit.

Step 2: Apply the Phase-Appropriate Process Level

Duration: 1-2 hours · Tool: Document

Map each priority process to the appropriate formalization level: [src2] [src4]

Phase 1 (1-10 people): Document only what breaks — deployment, customer onboarding checklist, incident response. Simple checklists, max 1 page.

Phase 2 (10-25 people): Core playbooks — add hiring process, employee onboarding, sales process, support triage, sprint cadence. Notion/Confluence playbooks with owners and review dates.

Phase 3 (25-50 people): Process library + automation — add expense approval, performance reviews, cross-team handoffs, reporting, security policies. Centralized library with workflow automation.

Phase 4 (50-100 people): Process governance — add change management, compliance frameworks, vendor policies, data governance. Process ops function with quarterly governance reviews.

Verify: Each priority process mapped to appropriate level. · If failed: Default to one level below what you think you need. Under-formalizing is easier to fix than over-formalizing.

Step 3: Build the Process Documentation

Duration: 2-4 hours · Tool: Notion, Confluence, or Google Docs

For each process being formalized, create a Process Card: Name, Owner, Trigger, Steps (numbered single actions), Decisions (if/then branches), Output, Handoff, Review date, Sunset criteria. Max 1 page per process. Write for the new hire who starts Monday. [src6]

Verify: Top 5-10 processes documented, owners assigned, review dates set. · If failed: Start with top 3 only. Ship imperfect docs rather than waiting for perfect ones.

Step 4: Identify and Implement Automation Opportunities

Duration: 1-2 hours · Tool: Zapier, Make, or n8n

Evaluate three automation levels: Manual + checklist (< 10 people), Semi-automated with triggers and notifications (10-50 people), Fully automated with exception-based review (50+ people). Priority targets: notifications/routing, data transfers, reporting, onboarding sequences. [src5]

Verify: Top 3-5 automation opportunities identified, at least 1 implemented. · If failed: Start with simple Slack/email notifications.

Step 5: Set Up Process Health Monitoring

Duration: 30-60 minutes · Tool: Spreadsheet or dashboard

Track quarterly: compliance rate, completion time, error rate, satisfaction score. Rules: if compliance < 60%, redesign the process; if completion time increased > 50%, simplify; if satisfaction below 3/5, remove unnecessary steps; if unused for 30 days, sunset. [src1] [src3]

Verify: Process health dashboard created, first review date scheduled. · If failed: Use a simple spreadsheet reviewed quarterly.

Output Schema

{
  "output_type": "process_formalization_roadmap",
  "format": "MD + XLSX",
  "sections": [
    {"name": "process_audit", "type": "array", "description": "All recurring processes scored and ranked", "required": true},
    {"name": "phase_mapping", "type": "object", "description": "Which processes to formalize at current and next phase", "required": true},
    {"name": "process_cards", "type": "array", "description": "Documentation for top priority processes", "required": true},
    {"name": "automation_plan", "type": "array", "description": "Automation opportunities ranked by ROI", "required": true},
    {"name": "health_dashboard", "type": "object", "description": "Metrics and review schedule for process health", "required": true}
  ]
}

Quality Benchmarks

If below minimum: Without at least the top 10 processes audited, formalization will address the wrong processes. Start with the audit.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Formalizing everything at 10 people

Creating a 50-page operations manual, requiring approval workflows for expenses, and mandating weekly written status reports when the team is 8 people. The team spends 30% of time on compliance and zero time saved. [src3]

Correct: Document only what breaks

At 10 people, formalize only the 3-5 processes where mistakes have actually happened. Everything else stays as verbal agreements. Add process only when pain exceeds the overhead.

Wrong: Copying big company processes

Implementing full OKR frameworks, quarterly business reviews, and three-stage approval chains because large companies use them. These assume hundreds of employees and dedicated ops teams. [src4]

Correct: Scale-appropriate process

Use the simplest version that solves the actual problem. At 25 people, OKRs can be a spreadsheet reviewed monthly. Hiring approval is a Slack message. Upgrade only when the simple version stops working.

Wrong: Processes designed by non-executors

Having a consultant or manager document processes they do not personally execute. The documentation describes an idealized workflow that does not match reality.

Correct: Executor-authored documentation

The person who does the work documents the process. The manager provides the template and review, but the content comes from the executor. [src6]

When This Matters

Use this recipe when the startup is experiencing scaling pain — things falling through cracks, inconsistent quality, slow onboarding, or too many meetings — and needs to determine which processes to formalize without killing speed. Most critical at the 15-25 person transition (where tribal knowledge stops working) and again at 40-60 people (where cross-functional coordination breaks down).