Private state language. Shared routing logic for demanding work.
The Zones Framework™
Four operating states. One shared protocol. Individuals use Zones privately to identify the state already present, choose the right intervention, and route the next work. Managers use the same logic to redesign demand and route work from declared capacity, observable load, and task consequence—not private app data.
Execution drag has two interacting sources: friction in the work path and reduced access to skill in the people carrying it. Work can wait, loop, pile up, or stall in a queue even when capacity is intact. The same conditions can also reduce access to judgment, focus, communication, and creativity. Zones address that capacity side without replacing the work-path diagnosis.
🟢 Green · 🟡 Yellow · 🔴 Red · ⚫ Can't-Even
Performance infrastructure. Not wellness. Not therapy. Fix the path. Protect the capacity. Route the next work.
A Practical Routing Signal for Changing Conditions
Capacity is variable access to existing skill in the moment. Demand, recovery, control, interruptions, and unresolved work can change that access without changing the person's underlying ability. The Zones Framework gives the individual a private language for the state already present and gives the organization shared logic for deciding what work should proceed, wait, pair, simplify, or move.
The point is not to label people or assign them a state. Green can support complex decisions, strategy, creative work, and high-stakes communication. Yellow may need clearer work, fewer decisions, and less load. Red and Can't-Even call for lower consequence, a reset, or work being paired, simplified, delayed, or moved. The goal is not to force Green. It is to make a safer next decision.
Individuals identify and work with their own state. Managers manage demand and consequence. Managers never receive individual app activity, Zone history, or live state monitoring.
Simple operating rule: work enters a path. Friction can slow it directly and can also reduce access in the people carrying it. Flow evidence establishes path drag; the Four Tests govern the additional capacity claim. Zones help route the response when capacity is relevant, and the Five Capacity Taxes show where supported cost lands.
An Illustrative Workday: Same Skill, Different Access
Tap any point on the chart to see event details
This is an illustration, not a psychometric score and not a manager dashboard. It shows how one person's privately assessed capacity could move under changing conditions. Same person. Same skill. Different access. Some variation comes from outside work; ES does not try to eliminate it. The operating task is to avoid placing high-consequence work on the lowest-access moments when the person declares reduced capacity or observable load supports caution.
Established research is consistent with the premise that cognitive precision can vary within the same person. A 12-week longitudinal study published in Science Advances linked within-person changes in cognitive precision with same-day self-reported goal setting and achievement. That supports the logic of variable access; it does not validate the ES Zones, the 0-9 illustration, or state-aware routing.
The Zones Framework does not ask managers to become clinicians or infer private states. Managers use declared capacity, observable load, and task consequence. The Pilot tests whether routing and demand changes improve agreed operating metrics.
The Four Routing States
Zones describe the state already present; they do not diagnose personality, motivation, or capability. The individual may use them privately and may choose to declare capacity. Managers route from that declaration, observable workload, and task consequence. Treating every condition like Green (Green Zone Trap) is one avoidable source of execution cost; queues, approvals, handoffs, work in progress, and rework can create drag even when capacity is intact.
🟢 Green Zone (7-9)
Route the highest-value work here.
Strategy, creative problem-solving, complex collaboration, high-quality decisions, and high-stakes communication are best placed when usable capacity is available. Green is finite; protect it for work that creates value rather than filling it with low-value coordination.
Routing response: when capacity is available or declared, protect it, deploy consequential work, and do not consume the margin merely because it exists.
🟡 Yellow Zone (4-6)
Route defined execution and reduce decision load.
Yellow means functioning with reduced margin. The person may still execute and meet deadlines, but complex judgment, nuance, and multi-step decisions may carry more effort or risk. The right move is to simplify, reduce load, or move the work—not diagnose the person.
Routing response: when reduced capacity is declared or load is visibly high, clarify the work, reduce decision density, redistribute load, and allow a reset.
🔴 Red Zone (1-3)
Route only what cannot wait.
Red indicates very limited usable margin. Thinking may narrow, communication can become more reactive, and consequential decisions carry more risk. The correct response may be to pause, pair, simplify, or move the work.
Routing response: stop adding avoidable demand, hold strategic or emotionally loaded work, reduce communication volume, and protect the next recovery window.
⚫ Can't-Even Zone™ (0)
Route the smallest possible demand.
The individual is signaling that there is no usable margin for complex work right now. Do not infer disengagement or poor motivation. The operating question is: what is the smallest safe demand, and what can wait?
Routing response: minimal instructions, no avoidable decisions, and a recovery path. Consequential work waits, pairs, simplifies, or moves.
Important distinction: Zones are not a manager dashboard. Individuals use Zones privately to identify the state already present, choose an intervention, and route the next work. Managers act only on capacity the employee chooses to declare, observable workload and calendar conditions, and task consequence. They never receive individual app activity, Zone history, or live state monitoring.
The Routing Protocol
Declared capacity, observable load, and task consequence are the inputs. The routing decision is the output: proceed, wait, pair, simplify, move, or reset. The protocol reduces guessing without asking managers to classify people.
Some avoidable management failures are routing failures. Strategy work gets scheduled after a morning of back-to-backs. Performance feedback happens after an escalation. A leadership offsite lands in a quarter already overloaded with change. But routing is not the whole execution diagnosis: work may also be stuck in queues, approvals, handoffs, or rework. ES checks the path first and tests the capacity effect separately.
| When the state is privately identified or voluntarily declared... | Route this kind of work | Hold this kind of work | Run this response |
|---|---|---|---|
| 🟢 Green | Strategy, complex decisions, creative work, high-stakes communication. | Administrivia that wastes the state. | Protect the conditions and deploy the work that creates value. |
| 🟡 Yellow | Tactical execution, familiar work, defined deliverables. | New strategy, high-stakes negotiation, performance conversations, avoidable approvals. | Clarify, reduce decision volume, redistribute load, and reset before carryover spreads. |
| 🔴 Red | Only what cannot wait. | Anything reversible, strategic, nuanced, or emotionally loaded. | Stop adding avoidable demand, reduce communication volume, and protect the next recovery window. |
| ⚫ Can't-Even | Only the smallest safe demand. | Everything that can wait. | Minimize demand, avoid consequential decisions, and create a recovery path. |
This is the practical value of the framework: a shared protocol for matching work to declared capacity and task consequence without turning private state into management data.
Work Systems Often Assume Green
Training programs, meeting cadences, feedback processes, and deadlines are often designed as if people have constant access to the skills the work requires.
When that assumption is wrong, slower decisions, lower quality, more conflict, and more rework can follow. The Zones Framework makes the capacity mismatch discussable. ES still checks whether the work path itself is creating direct drag.
Yellow
is where execution risk can hide
Not failed. Not checked out. Still functioning, but at reduced margin.
People in Yellow may still show up, answer messages, attend meetings, and ship urgent work. Visible output can continue while the margin for judgment, creativity, pattern recognition, and recovery shrinks. That is why Yellow calls for lighter routing or a reset—not a performance label.
External research uses several overlapping constructs, including state-dependent performance, stress, recovery, and presenteeism, but none is identical to an ES Zone. ES uses Yellow as practical, non-clinical operating language. It is not a validated diagnosis or a manager-visible status.
What Managers Learn to Change
Capacity Intelligence is the managerial discipline of changing demand and task consequence without monitoring private individual states. Managers read work-system evidence, use declared capacity when it is offered, protect high-consequence work, and build operating margin into the rhythm.
1. Read the work path
Managers learn to notice queues, approval waits, rework loops, stalled handoffs, too much work in progress, stacked decisions, and calendar load. These patterns can create execution drag directly.
2. Route from three inputs
Use capacity the employee chooses to declare, observable load, and task consequence to decide whether work should proceed, wait, pair, simplify, or move.
3. Change the conditions
Reduce decision density, clarify work, remove avoidable approvals, redistribute load, protect Green-capacity periods, and create reset points. The aim is not to force a state; it is to improve the conditions around the work.
4. Review the path, then test the capacity effect
When a decision fails, conflict escalates, or work returns for another pass, ask where the work waited, looped, or overloaded first. Then test whether reduced access also contributed. One incident does not prove the capacity claim.
Why the app matters
The app helps people reset access, build capability, and deploy Green capacity.
The worker-facing app has two live jobs: reset access or route around a reduced state, and deploy available Green capacity toward valuable work. It also develops ten Professional Skills Pillars through Reset → Build → Thrive.
The app does not route a person into a Zone. It helps the professional identify the state already present, choose a state-sized intervention, and route the next work to what that state can safely support. Sometimes the correct instruction is: do not make this decision now.
1. Identify the state already present
The professional uses a private self-check without turning the result into a performance label or manager status.
2. Reset access or route around it
In Yellow, Red, and Can't-Even, the app offers smaller, tiny, or five-second versions and helps decide whether the next work should wait, pair, simplify, or move.
3. Deploy Green deliberately
When Green capacity is available, the app routes it into Think Better, Communicate Better, Fix the Pattern, Create Better, or Prepare Better.
The app experience is private. Managers do not see individual use, Zone history, or live state. The Pilot tests whether combining work-path redesign, manager practice, and private individual support improves agreed operating metrics. Reset protects value. Deploy Green creates it.
Research Basis
The Zones Framework is a practical operating layer informed by established work on state-dependent performance, cognitive load, stress and recovery, decision quality under pressure, and organizational work design. That evidence supports the premise that access can vary; it does not validate the ES Zones as psychometric categories or prove routing outcomes.
Research contextEstablished evidence supports variable access. The ES routing model remains to be tested.
The framework draws on research traditions including cognitive load, stress and executive function, recovery, state-dependent performance, and work design. These traditions support a testable premise: the same person can have different access to the same skill under different conditions.
A 12-week longitudinal study of 184 university students, published in Science Advances, found that within-person changes in cognitive precision were associated with same-day self-reported goal setting and achievement across academic and nonacademic domains. Stable traits such as self-control and conscientiousness did not eliminate the day-to-day association. The student sample limits direct workplace generalization, and the study did not test ES Zones or manager routing.
The ES hypotheses remain testable: can individuals use Zones reliably enough to choose appropriate interventions, and do state-aware routing plus work redesign improve agreed operating metrics? Measured ES outcomes must come from Pilots against pre-agreed operating metrics.
How Organizations Use the Zones
Monday demand check: Managers review queues, stacked decisions, calendar load, recovery limits, and Green-level work at risk. They use declared capacity when it is offered; no private Zone data is required.
Pre-decision check: Before a high-stakes decision, the facilitator checks decision load, reversibility, and timing, then invites any voluntary capacity declaration. If the conditions or declarations do not support the work, the meeting changes shape or the decision waits, pairs, or moves.
Green-capacity deployment: When protected capacity is available and voluntarily declared, direct it toward strategy, preparation, difficult communication, pattern repair, or creation rather than filling it with low-value coordination.
Post-incident review: Trace the work path first: where did it wait, loop, restart, or overload? Then ask whether reduced access may also have contributed. A single incident does not establish a capacity diagnosis.
Where Zones Fit in the ES System
Zones are the private state language and shared routing logic for the capacity side of ES. They do not explain every delay and do not replace work-path evidence.
Work Demand and Flow
What enters, how much stays open, where work waits, who it routes through, how often it loops, and how much recovery and operating margin the system allows.
Zones
The private individual language and shared routing logic used to identify the state already present, choose an intervention, and decide what work can safely proceed. It never becomes a manager dashboard of individual state.
Capacity Taxes
Overlapping cost lenses showing where supported execution-drag cost lands. They are not the causes and are not additive buckets.
The Snapshot traces one local path and creates a credible routing hypothesis worth testing. The Diagnostic maps recurring friction and screens the capacity effect. The Audit prices supported loss with overlap controls. The Pilot tests whether changing the path, manager practice, and private individual support improves operating metrics.
Bring One Priority That Should Be Moving Faster
The Stalled Priority Snapshot traces where the work waits, loops, restarts, or routes through an overloaded decision point. It creates a credible local routing hypothesis and estimates a visible drag floor from directly traceable extra labor. The Diagnostic examines whether the pattern is shared and screens the capacity effect.