Scale — The Organism Grows
When progress is no longer confined to a single team, new challenges emerge. Multiple teams improving simultaneously create overlaps, resource conflicts, and strategic drift. Unlike Team, which runs a full PDCA cycle, Scale operates as a Check-Act amplifier — it takes the Check output from each Team layer, processes it at organizational scale, and feeds back into the next Team cycle.
Pains
Scaling improvement across teams introduces a distinct set of dysfunctions. Obeyaka Scale identifies three and provides a specific moment to counteract each one.
Misalignment — Teams pursue different or conflicting objectives. Each team optimizes for its own goals, but the sum of local improvements does not add up to organizational progress. Strategy exists on paper but does not reach execution. Teams deliver results that are technically correct but strategically irrelevant.
Untapped Value — High-impact opportunities are not identified or prioritized effectively. Resources are spread evenly instead of concentrated where they matter most. Good ideas compete with great ones for the same attention, and the organization captures a fraction of the value it could.
Overlapping — Work is duplicated or conflicting across teams. One team's improvement breaks another team's process. Dependencies are invisible until they cause rework. Teams improve in parallel without awareness of each other's changes, creating friction instead of flow.
Moments
Obeyaka Scale addresses these pains through three coordination moments:
Align — Counteracts: Misalignment. Always ask for pertinence with vision. Improvements must be checked against the organization's strategy. A perfectly executed improvement that serves an obsolete objective is waste. Alignment ensures every transformation connects to the long-term direction.
Rank — Counteracts: Untapped Value. Don't assign resources equally. Aligned improvements compete for limited resources (people, budget, equipment). Ranking ensures the highest-impact improvements receive attention first and high-value opportunities are not left on the table.
Sync — Counteracts: Overlapping. Don't improve all, all the time. Multiple teams generate multiple improvements in parallel. Synchronization is critical to avoid redundant work and ensure a sustainable improvement rhythm across processes.
| Moment | Description | Role | Event | Artefact |
|---|---|---|---|---|
| Align | Unite teams around shared strategy and vision | Planning Leader | Summit | Roadmap |
| Rank | Concentrate resources on highest-impact opportunities | Project Leader | Office | Funnel |
| Sync | Eliminate overlap and synchronize across processes | Progress Leader | Network | Workflow |
Flow
| Step | Layer | PDCA | Event | Description |
|---|---|---|---|---|
| S1.1 | Strategic | Check | Summit | Team Owners review objectives and transformation initiatives across the organization |
| S1.2 | Strategic | Act | Summit | Team Owners adjust the innovation portfolio and define upper-level objectives for the next cycle |
| S2.1 | Tactical | Check | Office | All improvement opportunities with value-capture potential are collected and tracked across teams |
| S2.2 | Tactical | Act | Office | Highest-impact improvements are prioritized and the transformation portfolio is adjusted |
| S3.1 | Operational | Check | Network | All improvements are collected by process and reviewed for overlaps and dependencies |
| S3.2 | Operational | Act | Network | Improvements are synchronized to avoid rework and optimize resources |
PDCA Cycle
Role
Routine
Board
Connections to Team
- Review to Summit (T1.3 → S1.1) — Team-level results feed the Summit review
- Summit to Planning (S1.2 → T1.1) — Adjusted portfolio becomes input for next Planning cycle
- Debriefing to Office (T2.3 → S2.1) — Debriefing opportunities feed the Office
- Office to Debriefing (S2.2 → T2.4) — Prioritized improvements return to teams
- Circle to Network (T3.3 → S3.1) — Circle results feed the Network
- Network to Circle (S3.2 → T3.4) — Synchronized improvements return to Circles
Anti-patterns
The Coordination Layer Without Execution
The organization invests in Scale events — Summit, Office, Network — but the teams underneath are not running their cycles. There is nothing to coordinate. The amplifier is on, but there is no signal.
How to detect: Scale events produce decisions and priorities, but teams do not change their behavior. Upper-level objectives are defined in the Summit but never appear in team Matrices. Prioritized improvements from the Office are not reflected on team Boards.
How to recover: Scale cannot exist without Team. If teams are not running their PDCA cycles, Scale events have no inputs and their outputs have nowhere to land. The fix is not to improve the Scale events — it is to establish functional teams first.
The Central Planning Trap
Scale events gradually absorb decision-making that should happen in Team. The Office starts assigning tasks to teams. The Network starts defining improvement priorities for individual Circles. The Summit starts setting tactical targets. The amplifier becomes the engine.
How to detect: Team Leaders wait for Scale decisions before acting in their Briefings. Circle improvements require Office approval before starting. The boundary between "coordination" and "control" has blurred.
How to recover: Scale events are Check-Act only — they review and adjust, they do not plan or execute. If a Scale event is making decisions that belong in a Team event, that decision must be pushed back down. The rule is simple: if the decision affects only one team, it belongs in Team.