Enterprise Services · Capacity-Aligned Execution Pilot · Twelve Weeks · One Primary Team · One Bounded Work Route
Change the conditions. Measure what moves.
You already suspect execution drag is slowing this team. What you do not have is proof that fixing the work path, not the people, will move it. The Pilot tests that around one primary team and the bounded work route affecting its result. The primary team supplies the measurement unit. The people controlling relevant decisions, approvals, and handoffs participate in the redesign. We change one or two conditions and measure whether the operating result improves. Where baseline shift, load signature, and shared conditions also point to a capacity effect, we test whether that improves too.
Every Pilot tests the operating result. When a capacity hypothesis is present, it also tests reversibility. The week-12 readout shows what moved. The 30-day durability check confirms whether connected expansion is justified, backed by evidence from your own route, not a vendor's case study.
Executive Summary A measured operating test, not a rollout on faith.+
The Pilot takes a finding worth acting on and tests it inside your organization. We choose one primary team, bound the work route affecting its result, change one or two conditions, establish the baseline, and measure the same operating result at the other end. The primary team supplies the measurement unit. A small route group includes the people who control the decisions, approvals, and handoffs the intervention must change.
What gets measured: primary proof comes from an operating metric agreed with the sponsor, such as approval wait, decision cycle time, reversals, rework hours, queue age, milestone completion, manager after-hours work, or strategic work completed. We also look at privacy-protected aggregate capacity patterns, app engagement, and employee sentiment. Those help explain what happened. They do not substitute for an operating result.
How it runs: three phases over twelve weeks. Baseline (weeks 1 to 2), implementation (weeks 3 to 10), and findings and executive readout (weeks 11 to 12). One 30-day post-Pilot durability check follows the final readout. About 30 minutes per week of employee time beyond normal work. About 2 to 3 hours per week for the manager.
What you receive: a documented before-and-after findings report, the intervention record, an implementation playbook, an executive deck you own, and one 30-day durability check. That gives your leadership a defensible basis for the next call: keep going, change course, or stop, without guessing. A publishable case study is developed only when the measured results, client approval, and confidentiality requirements support one. The Manager Capacity Cohort runs concurrently so the pilot manager leaves with practices for sustaining the change. The week-12 endpoint shows what held during the Pilot. The durability check tests whether the result persists as active Pilot support decreases.
Investment: pilots typically scope between $120K and $180K. Design Partners run between $100K and $150K, with 15% of Audit fees credited against Pilot cost when both are contracted together. Three Design Partner slots are planned for 2026, subject to availability at scoping.
The Pilot changes the conditions and measures the result.
Queues, approvals, handoffs, too much work in progress, unclear decision rights, and rework can slow execution even when capacity is intact. The same conditions can also reduce access to judgment, focus, communication, and creativity. Capacity is variable access to existing skill under the conditions of the moment, not a fixed trait and not a substitute for work-path evidence. Most organizations guess which one they are dealing with. Guess wrong, and you either replace people who were never the problem or leave a broken work path in place. The Pilot replaces the guess with evidence.
The Pilot changes one or two supported conditions and measures the operating result. Where the prior evidence supports a capacity hypothesis, the Pilot also tests whether the associated capacity pattern moves without replacing the people. A weak or null capacity result does not erase a structural improvement, and it does not point to another cause on its own. The evidence determines the claim.
The wrong pilot team
Most organizations want to choose the team under the most visible strain. That is usually the wrong place to run a measured intervention. A team in active crisis needs relief, not a twelve-week experiment. Once the Pilot becomes a rescue operation, the evidence gets muddy.
The right team has visible execution drag, a stable enough operating window to measure, and one business outcome the sponsor is prepared to own. The manager must actively work the redesign, not merely permit it. The executive sponsor must protect the intervention from competing priorities, including their own.
One team can be the primary measurement unit without being the whole route. If the targeted condition is controlled by another function, the relevant decision makers, approvers, or handoff owners must join the route group or formally commit to the test. A Pilot cannot test a redesigned approval route while the person controlling that approval remains outside the intervention.
If the team you have in mind is barely keeping its head above water, say so in the scoping call. We may recommend immediate load relief, a different team for the Pilot, or a different intervention entirely. The goal is not to force every problem into the Pilot format. It is to run a test whose result can be trusted.
What the pilot does
Twelve weeks. Three phases. Then one 30-day durability check to see what holds as active Pilot support decreases.
Weeks 1 to 2. Baseline.
We agree the primary operating metric and reconstruct the current path before changing anything. Depending on the case, the baseline may include approval wait, decision cycle time, queue age, work in progress, reversals, rework hours, milestone movement, manager after-hours work, or strategic work completed. Where capacity evidence is useful, it is collected privately and reported only in privacy-protected aggregate. No manager receives individual app activity, individual Zone history, or live individual-state monitoring.
We also map the route the change itself must take. The plan names the primary measurement team, the people who control relevant decisions, approvals, and handoffs, what each role must do differently, what existing activity must stop, and which bypasses or leadership overrides could restore the old route.
Weeks 3 to 10. Change the conditions.
We implement one or two targeted changes drawn from the supported findings. That may mean limiting work in progress, clarifying decision rights, removing an approval, redesigning a handoff, or restoring enough operating margin for the new design to hold. The specific change depends on what the evidence points to. The intervention is specific enough to test, not a broad operating overhaul.
When the change replaces an approval, meeting, report, or handoff, the old requirement is retired or explicitly suspended for the test. The Pilot does not add a new procedure while quietly leaving the old one in place unless a controlled comparison requires both.
Concurrently, the pilot manager runs the Manager Capacity Cohort. Five practices over six weeks. Practicum work draws directly from the team's operating conditions. Managers learn to route from declared capacity, observable load, and task consequence, including whether the work is complex, reversible, or safe to defer. They do not infer or monitor private individual states.
Individuals have private access to the Emergent Skills app and the relevant curriculum for the duration. The app helps identify the state already present, route to the appropriate intervention, and route the next work to what that state can safely support. It supports Reset → Build → Thrive, including restoring or routing around reduced access and deploying Green capacity deliberately through Think Better, Communicate Better, Fix the Pattern, Create Better, and Prepare Better. No manager visibility. No employer surveillance.
The intervention record identifies which work-path, manager, and individual components were used. Sometimes several things change together. When that happens, we can tell you whether the package worked. We cannot honestly claim which individual piece caused how much of the result.
Weeks 11 to 12. Measure and report.
We re-measure against the baseline and report the result whichever way it lands. What moved, what did not, whether the intervention was implemented as designed, what the capacity evidence supports, and what the organization should do next. You receive a findings report your leadership co-authors and a deck your sponsor can present without us in the room.
Thirty days after the final readout. Durability check.
We check whether the primary operating result held as active Pilot support decreased, whether the old approval, meeting, escalation, or handoff returned, whether people created a route around the change, and whether demand moved somewhere else. The check confirms whether connected expansion is justified, whether the design needs another adjustment, or whether the improvement depends on support that must remain explicit.
What gets measured
Operating outcomes first. Capacity evidence second.
One primary operating metric, agreed before the intervention begins. Examples include approval wait, decision cycle time, reversals, rework hours, queue age, milestone completion, manager after-hours work, or strategic work completed.
The work-path measures tied to the change. Work in progress, handoff count, escalation distance, approval steps, waiting time, restart frequency, or whatever directly shows whether the targeted condition changed.
Implementation fidelity and reversion. Whether the agreed change actually happened, which roles adopted or bypassed it, what pulled the work back toward the old route, whether the old requirement was actually removed, whether demand shifted elsewhere, and whether the change lasted long enough to test fairly.
Capacity and participation signals. Privacy-protected aggregate patterns, app and curriculum engagement, and brief employee sentiment can help interpret the result. They are supporting measures, not a manager dashboard and not the primary proof of value.
The endpoint decision. Scale, adapt, stop, or run a better test. We decide what success means before the Pilot starts, then measure against it. The week-12 readout gives the operating result. The 30-day durability check confirms whether connected expansion is justified or whether continuing support remains part of the intervention. If other changes happened during the twelve weeks that could have affected the result, we document them. A null or inconclusive result is reported as such, without converting participation or sentiment into a success claim.
The internal case record is useful because it is built from your team, your path, your metric, and your intervention. The question at the end is narrower: did this work here, well enough to justify doing more of it?
Who The Pilot Is For
A team with visible execution drag, a measurable outcome, and a sponsor who can protect the test.
Emergent Skills serves mid-to-large organizations with departments doing demanding knowledge work, where judgment and decisions materially shape the result rather than routine execution. A Pilot usually centers on one primary team or bounded business unit and includes the people outside it who control the relevant route. Product, engineering, legal, finance, R&D, clinical operations, deal teams, professional services, and strategy are examples, not a closed sector list.
Who runs it
A senior practitioner leads the engagement and stays with it from scoping through the 30-day durability check. You are not handed off mid-engagement, and the same practitioner is available for follow-on work if the evidence supports scaling.
For Design Partner pilots, the founder joins methodology shaping at kickoff, baseline review in week 2, a mid-engagement review in week 6, and final deliverable review in week 11, and remains available for executive escalation. On the first Design Partner pilot, the founder co-delivers alongside the senior practitioner. This phase is deliberately used to sharpen delivery against real enterprise conditions. Outcomes are measured, not presumed.
Investment
Pilots typically scope between $120K and $180K.
The Audit identifies the supported work-path pattern, assesses the capacity evidence, and builds the cost and intervention case. The Pilot acts on that case: twelve weeks centered on one primary team and the bounded route affecting its result, changing one or two work-path conditions, developing the manager's demand and consequence routing practices, introducing private app and curriculum support, measuring the result, and completing one 30-day durability check. That delivery and measurement scope is the difference in price. What you are paying for is a defensible answer, not a bet. The Pilot makes sense when the priority, delay, or operating problem at stake is materially more expensive than the cost of finding out whether the proposed fix works.
Up to three Design Partner slots are planned for 2026. Design Partner pilots currently scope between $100K and $150K (approximately 15% below standard), plus founder co-delivery on the first Pilot and anchor case-study consideration when the measured results and permissions support publication.
15% of Audit fees credit against Pilot cost when both are contracted together. Final pricing depends on primary-team size, route-group scope, the operating metric, baseline depth, intervention complexity, and delivery format. Confirm current Design Partner availability and pricing in the scoping call.
2026 Design Partner Cohort · Up to Three Planned Slots
Early adopters help sharpen the delivery model.
Design Partner pilots trade a lower fee for closer founder involvement, practical input into delivery, and case-study work when the measured results and permissions support it. The current offer includes:
- Founder co-delivery on the first Pilot, and founder involvement at the named touchpoints on the others while the firm remains in this phase.
- Methodology input from your operating conditions, used to sharpen how the intervention and measurement model works at enterprise scale.
- Anchor case-study consideration, only when measured results, client approval, confidentiality requirements, and separately agreed attribution terms support publication, plus approximately 15% off the engagement.
Questions
What does my team have to do?
Each person in the primary team commits about 30 minutes a week beyond normal work for brief measurement, private app and curriculum use, and the small amount of input needed to implement the agreed change. The manager's time is 2 to 3 hours a week. Route-group participants outside the primary team join only the working sessions and decisions needed to change the approval, handoff, or decision they control. The executive sponsor commits to four review meetings across the twelve weeks and protects the test from competing priorities. Individual app activity and Zone history are never shared with the manager or employer.
What if the pilot does not produce clear results?
We report that. Sometimes the result is unclear. Maybe we were wrong about the cause. Maybe the change was not large enough, or the metric was not sensitive enough to catch it. Maybe something else shifted during the twelve weeks. Maybe implementation did not hold long enough to test it fairly. The findings document what happened, what remains uncertain, and whether to adapt, stop, or run a better test. We do not retrofit participation or sentiment into a success story.
Who owns the findings and any case study?
You own the internal findings report, intervention record, implementation playbook, and executive deck. Any external case study, whether named or anonymized, requires a separate written agreement covering outcomes, confidentiality, attribution, and final approval.
Test the change before you scale it.
Twelve weeks from now, you could know whether fixing the work path moves the number that matters. Thirty days later, you could know whether the result began to hold as active Pilot support decreased. Tell us the execution pattern, the Audit finding if one exists, the primary team you are considering, the other roles controlling its route, and the operating metric that matters. We will tell you whether the conditions are stable enough for a Pilot, what a credible intervention could test, what it would cost, and what result would justify the next step. If a Pilot is not the right move, we will say so. Current Design Partner availability is confirmed during scoping.