Individual Layer · Professional Skills Curriculum + App
Build the skills.
Reset access. Deploy Green capacity.
Ten Professional Skills Pillars. Reset → Build → Thrive. State-sized tools and five Green deployment paths. The curriculum and App are not a default fix. They are used inside an ES intervention only when a focused operational investigation shows that individual capacity support belongs in the response.
Before you fund the fix, find the right problem. ES first checks the business result, prerequisites, necessary work and ownership, the work path, conditions around execution, and competing explanations. The curriculum develops capability over time. The App supports the moment. Neither substitutes for fixing the work itself when that is where the evidence points.
Built for the floor, scaled to the ceiling. Private to the professional.
The Individual-Side Hypothesis
Skill can stay intact while usable access narrows.
The ES hypothesis: accumulated demand makes it harder for a capable professional to use the judgment, focus, and communication they already have. The skill did not leave. Access to it changed.
The design failure is the Green Zone Trap: building every instruction for full attention, working memory, and follow-through. A person may need a tool precisely when a multi-step tool is hardest to start.
State-sized design lowers the entry cost. But not every performance problem is a capacity problem. Queues, approvals, handoffs, and rework can slow the work all by themselves. So can missing ownership, unclear priorities, skill gaps, external dependencies, or other conditions. ES tests the competing explanations against the work and the evidence before deciding whether the individual-capacity layer belongs in the response.
Build for the constrained case.
A curb cut removes a barrier for wheelchair users and also helps people moving strollers, carts, or luggage. The product principle is similar: design the smallest genuinely usable entry point first, then scale upward.
In ES language: build for the floor, scale to the ceiling. Make the tool usable when attention, working memory, or effort are limited, then offer more when more capacity is available.
One pillar. Twelve weeks. Three phases.
Each of the ten pillars currently follows a 12-week Reset → Build → Thrive structure, designed for roughly ten minutes of daily practice. Printable materials can be read, marked up, and used offline. A participant works through one pillar at a time.
Weeks 1-4
Reset: body-first
Participants test grounding, breath, movement, and anchoring to find out what actually helps under real conditions. At Week 4, they look at what worked, what did not, and what they can realistically use when capacity is low. If something is not helping, they change it. Completion is not proof.
Weeks 5-8
Build: cognitive
The next phase adds cognitive tools: noticing the pattern earlier, testing assumptions, interrupting unhelpful responses, and choosing a better next move.
Weeks 9-12
Thrive: strategic
The participant plans around real capacity, protects higher-access windows, and routes valuable work toward them. At Week 12, the participant compares where they are with where they started and asks a simple question: did any of this make a difference in the work?
Four state-sized versions of every tool.
A tool that is usable in Green may demand too much attention or follow-through in Red. Every tool therefore has four entry points sized to the state already present, not the state the training wishes were present.
The table shows one illustrative body-first tool. The same state-sizing rule applies across the curriculum.
| Zone | Version | Duration | Illustrative action |
|---|---|---|---|
| 🟢 Green | Full | 3-5 min | Six-step grounding sequence using breath, pressure, and awareness |
| 🟡 Yellow | Smaller | 1-2 min | Three steps: press, squeeze, breathe |
| 🔴 Red | Tiny | 30 sec | Press feet. Feel floor. One breath. |
| ⚫ Can't-Even | Five-second floor | 5 sec | Press heels. Feel ground. |
Same job. Smaller entry point.
Design guardrail: the floor version has to be genuinely usable at the floor, not merely a shorter Green tool.
Ten Professional Skills Pillars.
Each pillar uses the same Reset → Build → Thrive arc and the same state-sized design.
- Composure & Performance Under Pressure
- Stress Load & Sustained Output
- Execution & Delivery
- Focus & Attention Control
- Communication & Connection
- Emotional Regulation & Recovery
- Resilience & Change
- Confidence & Standing
- Motivation & Drive
- Rest & Recovery
Entry is selected from the actual work demand and the professional capability most relevant to it. A professional preparing for high-stakes meetings may begin with Composure & Performance Under Pressure. A team under sustained demand may use Stress Load & Sustained Output. A group losing usable attention to interruptions may use Focus & Attention Control. After one pillar, the next step is chosen from observed need and the deployment scope, not from a fixed ladder.
The Live Operating Layer
The curriculum develops capability. The App supports the moment.
The App has two jobs: help when access is low, and help people make better use of Green when it is available. It does not decide someone's state. The professional identifies where they are, uses a tool that fits, and decides what kind of work makes sense next.
🟡 Yellow · 🔴 Red · ⚫ Can't-Even
Reset access, or route around the state.
A state-matched intervention is designed to help interrupt carryover from a meeting, decision, conflict, or stretch of context switching. The next move may be to recover, reduce the demand, simplify the task, pair on the work, defer it, or move it.
The goal is not to force Green. When usable capacity does not return, consequential work waits, pairs, simplifies, or moves. Sometimes the right instruction is: do not make this decision now.
🟢 Green
Deploy access while it is available.
Green is the ES working state: more judgment, range, creativity, communication, and pattern recognition are available than usual. The operating question is where to spend it.
Protect the window. Use Green on work that benefits from the best available thinking, not low-value coordination that can be handled later or elsewhere.
Reset protects value. Deploy Green creates it. The point is not only to lose less capacity. It is to use the capacity you have on work worth doing.
Private by design. Managers do not receive individual App activity, individual Zone history, live individual-state information, or drill-down data. They act only on capacity the employee chooses to declare, observable load, and task consequence.
Deploy Capacity
Five Green paths. One question: where should this capacity go?
When a professional identifies usable capacity, the App helps route that window toward work that benefits from it. Green is not the absence of a problem. It is a scarce opportunity for higher-value judgment and execution.
Think Better
Decisions, priorities, plans, and tradeoffs. Use available range before pressure narrows what the professional can see and rework risk rises.
Communicate Better
Messages, feedback, and hard conversations. Use Green for clarity, nuance, and the sentence that may prevent avoidable cleanup.
Fix the Pattern
Meetings, handoffs, rework, and bottlenecks. Use available capacity to surface the system around the problem instead of defaulting to blame.
Create Better
Ideas, positioning, product thinking, and strategic connections. Protect enough range for original work to become usable output.
Prepare Better
Preparation before predictable pressure. Move the decision, message, or plan upstream instead of leaving it for a lower-access moment.
Inside the Connected ES System
Start with the execution drag, not an App rollout.
The curriculum and App are one layer of Performance Infrastructure for Demanding Knowledge Work. ES first investigates the business result, the conditions needed to produce it, necessary work and ownership, the work path, conditions around execution, and competing explanations. When the evidence supports an individual-capacity component, the Pilot can introduce the appropriate curriculum and App support alongside any changes to the work.
Evidence boundary. A stalled work path can be demonstrated from the work itself. A capacity claim requires separate evidence. That is what the Four Tests and a measured change are for. If the capacity hypothesis does not hold up, we say so. Any supported finding about the work still stands, and another explanation may fit better.
Inside the Pilot
The Pilot establishes baseline operating metrics, changes one or two supported work-path conditions, trains managers in demand and consequence routing, and introduces the relevant curriculum and App. Examples of primary proof measures include approval wait, decision cycle time, reversals, rework, queue age, milestone completion, manager after-hours work, and strategic work completed. App engagement and sentiment are supporting measures.
After proof, inside the License
A successful Pilot can earn a recurring License. Depending on scope, the License can include App access, the ten-pillar curriculum, manager cohorts, privacy-protected aggregate operating-demand patterns, operating-outcome reporting, quarterly reviews, and ongoing support. It does not create manager access to individual App activity or private Zone history.
Printable PDFs, workbook pages, and the curriculum compass support use away from the screen. The App is the live operating layer. Outcomes are measured, not assumed.
Bring one priority that should have moved.
The Stalled Priority Snapshot is a focused operational investigation of one priority. The 90 minutes is the working session, not the whole investigation. Written input and available records are reviewed around it. The readout states what the evidence supports, what remains uncertain, the costs we can establish, and the next justified step. A 14-day test is proposed only where the evidence supports one.
The Snapshot examines competing explanations locally. The Diagnostic tests whether a pattern recurs across a broader set of work. A Pilot tests an evidence-supported change, including reversibility when a capacity-effect hypothesis is actually in scope.
Capacity Intelligence™ · The Zones Framework™
Performance Infrastructure for Demanding Knowledge Work. Not therapy. Not wellness. Not employee monitoring.
