A private read for the person. A shared rule for the work.
The Zones Framework™
Four states. One rule for deciding what happens to the work next. Individuals use Zones privately to decide what they can take on next. Managers use them to change the demand around the work. Private app data stays private.
A bad work path can stall a capable team on its own. But sometimes the same conditions slowing the work are wearing down the people carrying it too. Zones are for that second problem.
🟢 Green · 🟡 Yellow · 🔴 Red · ⚫ Can't-Even
Executive SummaryFour states, one routing protocol, and a firm line around private data.+
You do not have equal access to everything you know how to do all day long. Someone can make a hard decision easily at 9 a.m. and struggle with the same decision after four meetings and a pile of unresolved work. Their ability did not disappear. Their access to it changed.
Green is where you want the hard thinking. Yellow can still get plenty done, but complicated work starts costing more. In Red, ask what truly cannot wait. At Can't-Even, almost everything can wait.
One line matters here. Individuals use Zones for themselves. Managers never use them to classify employees. Managers work from three things instead: what the employee chooses to tell them, what they can already see about the workload, and how consequential the work is.
Zones do not explain why every project is late. A bad approval path can stall good people all by itself. Trace the work first. If the path explains the stall, fix it. If something more appears to be happening to the people carrying it, test that separately.
The research supports the underlying idea: access changes. It does not prove our four Zones are the right model. That is ours to prove in the Pilot.
The Same Person Is Not the Same All Day
Capacity is the share of what you already know how to do that you can reliably reach right now. Four meetings, three unresolved decisions, an interruption every ten minutes, and a bad night can change that by afternoon. Zones give people a simple way to say "this is what I have available right now." The organization can then decide what happens next.
Green can carry complex decisions, strategy, creative work, and high-stakes communication. Yellow calls for clearer work and fewer decisions. Red and Can't-Even call for lower consequence, a reset, or work that gets paired, simplified, delayed, or moved. The goal is not to force Green. It is to make a safer next decision.
Individuals work with their own state. Managers work on demand and consequence. Private state stays private.
Simple operating rule: work enters a path. Trace what happened to it first. If the path caused the problem, fix the path. If those same conditions also appear to be reducing judgment, focus, or communication, test that separately. Zones help decide what happens next.
An Illustrative Workday: Same Skill, Different Access
Tap any point on the chart to see event details
This is an illustration, not a score. The same person can have very different access to the same abilities across a day, and not all of that shift comes from work. The operating question is whether what is being asked of them fits what they have available right now.
Established research is consistent with the premise that cognitive precision varies 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 our Zones, the 0-9 illustration, or state-aware routing.
We are not asking managers to become clinicians or to guess at private states. Managers use what they are told, what they can see, and what the task costs if it goes wrong. The Pilot tests whether routing and demand changes move 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 say something about capacity. Managers route from what they are told and what they can already see. Treating every condition like Green (Green Zone Trap) is one avoidable source of execution cost. It is not the only one. Queues, approvals, handoffs, work in progress, and rework stall capable people on their own.
🟢 Green Zone (7-9)
Route the highest-value work here.
This is where the hard thinking belongs: strategy, creative problem-solving, complex collaboration, consequential decisions, and the conversations that are difficult to have well. Green is finite. Protect it for work that creates value rather than filling it with coordination that could have happened anywhere.
Routing response: when capacity is available, protect it, deploy consequential work into it, and do not spend the margin merely because it exists.
🟡 Yellow Zone (4-6)
Route defined execution and reduce decision load.
Yellow still gets plenty done. Deadlines get met. What shrinks is the room for complexity, nuance, and multi-step judgment, so the same work carries more effort and more risk of a second pass. Simplify it, lighten it, or move it. Do not diagnose the person.
Routing response: clarify the work, cut decision density, redistribute load, and allow a reset before the carryover spreads.
🔴 Red Zone (1-3)
Route only what cannot wait.
By Red there is very little usable margin. Thinking narrows, communication gets more reactive, and consequential decisions carry more risk than they would have that morning. Pause it, pair it, or move it.
Routing response: stop adding avoidable demand, hold strategic and high-stakes conversations, cut communication volume, and protect the next recovery window.
⚫ Can't-Even Zone™ (0)
Route the smallest possible demand.
The person is telling you there is no usable margin for complex work right now. Do not read that as disengagement or poor motivation. The only useful question is what the smallest safe demand is, and what can wait until it is not.
Routing response: minimal instructions, no avoidable decisions, and a recovery path. Consequential work waits.
Important distinction: Zones are not a manager dashboard. Individuals use them on themselves. Managers never receive individual app activity, Zone history, or live state monitoring.
The Routing Protocol
Managers use three things: what the employee chooses to tell them, what they can already see about the workload, and how consequential the work is. The output is a decision about the work rather than a judgment about the person. Proceed, wait, pair, simplify, move, or reset.
Some avoidable management failures are routing failures. Strategy work gets scheduled after a morning of back-to-backs. Performance feedback happens in the hour after an escalation. A leadership offsite lands in a quarter already carrying more change than it can absorb. But routing is not the whole diagnosis. The work may simply be stuck in a queue, an approval, a handoff, or a rework loop. We trace the path first and test 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, cut decision volume, redistribute load, and reset before carryover spreads. |
| 🔴 Red | Only what cannot wait. | Anything reversible, strategic, nuanced, or high-stakes. | Stop adding avoidable demand, cut 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. |
That is the practical value of the framework: a shared way to match work to the capacity that exists, without turning anyone's private state into management data.
Most Work Systems Are Built for Green
Training programs, meeting cadences, feedback processes, and deadlines are usually designed as though people have constant access to the skills the work requires.
When that assumption is wrong, you get slower decisions, uneven quality, more conflict, and more rework. Zones make the mismatch discussable. We still check whether the work path is creating drag on its own.
Yellow
is where execution risk can hide
Not failed. Not checked out. Still functioning, but at reduced margin.
People in Yellow still show up, answer messages, attend meetings, and ship the 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. It is not a performance label.
External research uses several overlapping constructs, including state-dependent performance, stress, and recovery, but none of them is identical to a Zone. Yellow is operating language, not wellness language and not a diagnosis. It is not a manager-visible status either.
Managers Cannot Control Capacity. They Can Control Demand.
Capacity Intelligence™ is the discipline of changing demand and task consequence without monitoring anyone's internal state. You read the work system, use what people choose to tell you, protect the work that matters most if it goes wrong, and build some margin into the rhythm.
1. Read the work path
Start with the work. Where is it waiting? What keeps coming back? Who has become the unofficial approval queue? You can find a surprising amount of execution drag without asking a single question about motivation.
2. Route from three signals
Use those three signals to decide what happens to the work next. None of them requires knowing anything private.
3. Change the conditions
Cut decision density, remove approvals nobody needs, redistribute load, and protect the periods when capacity is high. These change the conditions around the work rather than the person's state.
4. Review the path, then test the capacity effect
When a decision fails, conflict escalates, or work comes back for another pass, ask where it waited, looped, or overloaded before you ask anything about the people. Then test whether reduced access also contributed. One incident proves nothing.
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 get the next thing done anyway. 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 an intervention sized to it, and route the next work to what that state can safely carry. Sometimes the correct instruction is: do not make this decision now.
1. Identify the state already present
A private self-check, with no result that becomes a performance label or a manager-visible 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 task should happen now at all.
3. Deploy Green deliberately
When Green capacity is available, the app points it at Think Better, Communicate Better, Fix the Pattern, Create Better, or Prepare Better.
The app experience is private. The Pilot tests whether combining work-path redesign, manager practice, and private individual support moves agreed operating metrics. Reset protects value. Deploy Green creates it.
Research Basis
Zones are a practical operating layer informed by established work on state-dependent performance, cognitive load, stress and recovery, decision quality under pressure, and work design. That evidence supports the premise that access varies. It does not validate our four categories as psychometric instruments or prove any routing outcome.
Research contextEstablished evidence supports variable access. Our routing model remains to be tested.
Those traditions are well established, and they support one 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, collected 9,248 time points and found that within-person upswings in cognitive precision preceded and predicted same-day self-reported goal setting and achievement across academic and nonacademic domains. A one-standard-deviation change in cognitive precision carried an effect the authors describe as statistically equivalent to about 40 minutes of work. Trait-level self-control and conscientiousness did not moderate the association. The student sample limits direct workplace generalization, and the study did not test Zones or manager routing.
Two questions remain open, and they are ours to answer. Can individuals read their own state reliably enough to pick a useful intervention? Does state-aware routing, combined with work redesign, move operating metrics that were agreed in advance? We have to prove that ourselves.
How Organizations Use the Zones
Monday demand check: Managers review queues, stacked decisions, calendar load, recovery limits, and the high-value work most at risk this week. They use what people have chosen to tell them. No private data is required.
Pre-decision check: Before a high-stakes decision, the facilitator checks decision load, reversibility, and timing, then leaves room for anyone to say what they have available. If the conditions do not support the work, the meeting changes shape or the decision waits, pairs, or moves.
Green-capacity deployment: When protected capacity exists, point it at strategy, preparation, or the difficult conversation you keep deferring. Do not let it fill up with 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 settles nothing.
Where Zones Fit in the ES System
Zones are the private state language and the shared routing logic for the capacity side of this work. They do not explain every delay, and they 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.
Capacity Taxes
Overlapping cost lenses showing where supported execution-drag cost lands. They are not the causes, and they are not additive buckets.
Start with the work, not the people. If the path explains the stall, fix the path. If the same conditions also appear to be reducing access to judgment, focus, or communication, test that separately.
The Snapshot traces one path. The Diagnostic looks for the pattern elsewhere. The Audit prices what the evidence supports. The Pilot changes the condition and sees whether the number moves.
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 produces a local routing hypothesis and estimates a visible drag floor from directly traceable extra labor. The Diagnostic examines whether the same pattern shows up elsewhere and screens the capacity effect.