critical-chain

Critical Chain & Buffer Management

When to Apply

• Managing Goal execution pace and timeline
• Buffer zone changes (GREEN/YELLOW/RED)
• Detecting and resolving bottlenecks
• Prioritizing which Actions to execute next
• When the founder asks "are we on track?"

Core Framework

TOC 5 Focusing Steps

Applied to the KPI tree. The Crux Driver (highest importance x tractability) is the constraint:

1. IDENTIFY: The Crux Driver is the constraint — most important AND most solvable bottleneck
2. EXPLOIT: Maximize that Driver's throughput. Execute its Actions first, eliminate waste, remove blockers. Never let constraint Actions wait.
3. SUBORDINATE: All other Drivers serve the constraint. Non-constraint Actions only execute when they don't compete for resources with constraint Actions.
4. ELEVATE: If Exploit is insufficient, propose additional investment (new Action types, budget, tools) for the constraint.
5. REPEAT: When the constraint moves (metric improves, another Driver becomes bottleneck), re-identify and restart.

Buffer Management (3-Zone Traffic Light)

Buffer sizing: Project Buffer = 50% of estimated time to achieve Goal.

Feeding buffers: Each non-constraint Driver has a small feeding buffer protecting the constraint. If a non-constraint Action delays, the feeding buffer absorbs it.

Zone	Buffer Consumed	Agent Behavior
GREEN (0-33%)	On track	Normal execution. Continue planned Actions. Light monitoring.
YELLOW (33-67%)	Falling behind	Investigate root cause. Generate recovery Actions. Notify user. Increase scan frequency.
RED (67-100%)	Significantly behind	Auto-propose high-impact recovery. Escalate to user. Deprioritize low-impact Drivers. Consider scope adjustment.

Buffer consumed: 45%  [========----------]
Goal progress:   34%  [======------------]
Status: YELLOW — buffer consumption outpacing progress

Buffer as early warning: Unlike milestone tracking (detects problems after deadline miss), buffer management provides continuous visibility. YELLOW at 20% progress gives weeks of lead time.