Operational Payoff · Operations Consulting · Capacity-Aligned Execution Pilot
Test the proposed fix. Measure the business result.
A project is falling short or a recurring problem keeps returning. An operational investigation has identified a change worth testing. The Pilot does not start by guessing at the cause. It puts that evidence-supported change into practice around one primary team and a defined part of the work affecting its result. We agree what should improve, involve the people who control the change, and measure what happens.
Before you fund the fix, find the right problem. The Pilot comes after that investigation, when the remaining question is whether the proposed change actually improves the business result.
You receive the findings, what remains unresolved, and the next decision the evidence supports. Twelve weeks is a planning assumption, with a follow-up check initially planned for 30 days after the final readout. Duration and follow-up timing are agreed around the work cycle and evidence needed.
For operations managers, project managers, division leaders, and others accountable for the business result. A Pilot needs a defined scope, a measurable question, and authority to make the proposed change.
Executive Summary Does the proposed change improve the result?+
The Pilot starts with a finding from an operational investigation that warrants a measured test. We define one primary team, the work affecting its result, and the people inside and outside that team who control the necessary decisions, approvals, and handoffs. We establish a baseline, implement one or two supported changes, and measure the agreed result.
What gets measured: one primary operating metric tied to the business result, such as approval wait, decision cycle time, rework hours, or milestone completion. We also check whether the change was implemented and whether it moved work or delay elsewhere. When evidence suggests that interruptions, switching, or competing decisions contribute to errors, we test that explanation separately.
How it runs: baseline, implementation, and findings, followed by a check on whether any improvement holds as active support decreases. The twelve-week plan below illustrates the sequence. The work cycle determines the agreed duration and review points.
What you receive: a before-and-after findings report, intervention record, implementation playbook, executive deck, and follow-up durability check. You own these internal deliverables. The recommendation may be to continue, adapt, stop, or gather specific missing evidence. Each further engagement is a separate decision.
Investment: the planning range is $120K to $180K. The Design Partner planning range is $100K to $150K, with up to three slots planned for 2026. Availability, final scope, fees, and any Audit credit are confirmed during scoping.
Test the explanation behind the proposed fix.
The investigation comes first. ES checks whether the expected outcome is still valid, whether it remains a chosen priority, whether the required capability, information, authority, and funding exist, and whether an external dependency controls progress. We then check whether the work needed to produce the result was identified and assigned. These checks come before the two routes below.
Necessary work and ownership. A rollout can finish while nobody owns making it work with real data and exceptions, agreeing the handoffs, or switching off the old process. If assigning that work is a straightforward correction, the recommendation may be to make it. A Pilot is justified only when there is a material question to test.
Route 1: work gets stuck. The evidence may point to a queue, repeated approval, unclear decision right, or handoff that sends work back. The Pilot tests whether changing that part of the work path improves the agreed result.
Route 2: work demands disrupt execution. Interruptions, constant switching, and competing decisions may contribute to errors, rework, or missed handoffs even when people have the skills. The Pilot can test whether changing those demands reduces the observed failures. Both routes can occur together.
The two execution routes are part of the investigation, not the whole investigation. Other explanations remain open, including skill, staffing, tools, incentives, strategy, external dependencies, or a known standard that is not being followed. The proposed change must follow the evidence. Findings may also point to a management decision, more investigation, or a different specialist.
When a Pilot is worth doing
A Pilot needs an important unanswered question, a usable baseline, and a change whose effect can be measured. The sponsor owns the business result. The plan names who owns the intervention, the metric and target, the prediction being tested, and the evidence that would count against it.
The manager must be able to implement the agreed change. If another function controls an approval, decision, or handoff, that owner must participate or formally commit to the test. One team can supply the measurements while several teams help make the change.
The operating window must be stable enough to interpret the result. A team in active crisis may need immediate relief first. A clear local correction may need an owner and a decision. Neither situation automatically calls for a Pilot. When the proposed change crosses teams, the sponsor also needs clear authority and a measurement record that can stand apart from competing internal explanations.
If the cause has not been investigated, the Stalled Priority Snapshot can be a starting point. It is a focused operational investigation of one result; the 90 minutes is the working session, not the whole investigation. A Capacity Audit may be appropriate when deeper measurement is needed. Existing client evidence can also inform scoping. The question is what evidence and authority are needed to run a useful test.
How the Pilot runs
The example below uses twelve weeks, followed by a durability check 30 days after the final readout. We agree the actual duration and follow-up timing around how often the work repeats and how long an effect would take to observe.
Weeks 1 to 2. Establish the baseline.
We agree the expected result and primary operating metric, review existing evidence, and reconstruct the current work. The plan records the baseline, target, accountable owner, change to be tested, and review point. Where the available baseline is too thin, we identify the additional evidence needed before drawing a conclusion.
We also map what implementation requires: which roles must act differently, what necessary work still needs an owner, what authority and resources are needed, what existing activity must stop, and where a bypass or leadership override could restore the old process.
Weeks 3 to 10. Make the agreed change.
We implement one or two changes supported by the investigation. That may mean assigning necessary work, limiting work in progress, clarifying decision rights, removing an approval, redesigning a handoff, or reducing interruptions around consequential work. The change is specific enough to test against the agreed prediction.
When a change replaces an approval, meeting, report, or handoff, the old requirement is retired or explicitly suspended for the test. Any reason to retain both is recorded, along with the extra work this creates.
Where manager practice belongs in the intervention, the Manager Capacity Cohort can run alongside the test. Its five practices over six weeks use the team's actual work. Decisions about what should proceed, wait, simplify, or move use observable workload, the consequences of the task, and capacity an employee chooses to declare.
Where private individual support is relevant, the agreed scope can include the Emergent Skills app and curriculum. Individuals use these to consider their current capacity and the work ahead. Managers and employers never receive private app activity, individual Zone history, or live individual-state data.
The intervention record identifies every component used. If work-path changes, manager practices, and individual support are introduced together, we assess the combined intervention. The record limits what can be attributed to any one component.
Weeks 11 to 12. Measure and report.
We compare the agreed metric with the baseline, check how the change was implemented, and document other events that could explain the result. The report states what improved, what did not, what remains uncertain, and the next decision. If a causal question remains unresolved, it names the next evidence step or management decision, its owner, and the review point.
Follow-up. Check whether the improvement holds.
Initially planned for 30 days after the final readout, this check examines what happens as active Pilot support decreases. Did the operating result hold? Did the old approval, meeting, or handoff return? Did demand move elsewhere? The findings inform whether to extend the change, adjust it, stop, or retain specific support. One follow-up observation provides limited evidence about longer-term durability.
What gets measured
The business result determines the measure.
One primary operating metric. We agree how it relates to the result the sponsor needs. Depending on the case, it may be approval wait, decision cycle time, rework hours, queue age, or milestone completion. A faster process can still leave the intended business result unresolved; the readout makes that distinction clear.
Whether the targeted condition changed. Measures may include work in progress, handoff count, approval steps, waiting time, or restart frequency. We check whether necessary work was assigned and completed, whether people adopted or bypassed the change, and whether delay or extra work shifted elsewhere.
A separate capacity question, when warranted. Where baseline shift, a load signature, and shared conditions support the hypothesis that demands are reducing access to existing skill, the Pilot tests reversibility. That requires evidence from changed conditions: improvement in the agreed operating metric and the associated capacity pattern without replacing the people. Faster flow alone does not establish that effect. The result may support, weaken, or leave the hypothesis unresolved.
Supporting evidence. Where relevant and agreed, privacy-protected aggregate patterns and participant feedback can help interpret the result. Reporting thresholds and confidentiality rules are set during scoping. Participation, app use, and sentiment cannot establish an operating improvement by themselves.
The next decision. We agree the target and decision rule before the intervention. The final readout and follow-up inform whether to continue, adapt, stop, or run a better test. An inconclusive result includes the specific evidence still needed. Improvement in one team supports a decision about the next test; it does not establish that the same change will work everywhere.
Who The Pilot Is For
Leaders who need evidence before extending a change.
Emergent Skills serves operations managers, project managers, division leaders, COOs, Chiefs of Staff, and others accountable for business results in organizations of any size. Pilot fit depends on the value at stake, the work being tested, access to evidence, and authority to act. It can center on one team or a defined business unit, with participation from the other roles that control the relevant work.
The method focuses on work where judgment, analysis, decisions, communication, and complex problem-solving materially affect the result. The industry matters less than whether there is a useful, measurable question and a proportionate test.
Who runs it
A senior practitioner leads the engagement from scoping through the agreed follow-up. The delivery lead and responsibilities are confirmed during scoping.
Jim Wilde built the ES methodology through decades of enterprise systems work, including nine years working on mta.info and related Metropolitan Transportation Authority systems. That experience shapes the approach: investigate the work, test competing explanations, and connect the next action to the result it is meant to produce.
Design Partner engagements include closer founder involvement at kickoff, baseline review, a review during implementation, and final deliverable review. Founder co-delivery is planned for the first Design Partner Pilot. The roles and touchpoints are agreed in the scope.
Investment
Pilot planning range: $120K to $180K.
The Pilot covers the agreed baseline, implementation, measurement, findings, and follow-up around one primary team and the work affecting its result. Manager practice and private individual support are included where they belong in the agreed intervention. Final fees, duration, deliverables, and participation are confirmed during scoping.
A Pilot should be proportionate to the operating problem and the decision at stake. If an internal correction, a smaller test, or further evidence would answer the question, that should be the recommendation.
The Design Partner planning range is $100K to $150K, approximately 15% below the standard range. Up to three Design Partner slots are planned for 2026. Confirm availability and the final fee during scoping.
15% of Audit fees credit against Pilot cost when both are contracted together, subject to the agreed scope and terms. Pricing depends on team size, participation across functions, baseline depth, intervention complexity, and delivery format.
2026 Design Partner Cohort · Up to Three Planned Slots
Help refine the Pilot in real operating conditions.
Design Partners receive a lower fee and closer founder involvement while contributing practical input on delivery. Results are reported whichever way they land. The planned offer includes:
- Founder involvement at agreed touchpoints, with co-delivery planned for the first Design Partner Pilot.
- Practical input into the method, based on what implementation and measurement require in your organization.
- Case-study consideration, only when measured results, client approval, confidentiality requirements, and separately agreed attribution terms support publication.
Questions
Do we need a Pilot for every finding?
No. A finding may call for a management decision, a straightforward correction, more evidence, or stopping or redirecting the work. A Pilot needs a material question, a measurable baseline, an accountable owner, and an intervention whose prediction can be tested. There is no obligation to proceed to a License or another engagement.
What does my team have to do?
The illustrative twelve-week plan allows about 30 minutes per person each week beyond normal work for measurement and agreed supporting activities. Manager time is estimated at 2 to 3 hours per week through week 10 and 3 to 4 in the final two weeks. The sponsor plans for four reviews and protects the agreed test from competing priorities. Other decision makers and handoff owners participate where their work must change. We confirm the actual implementation effort and participation before starting.
Private individual tools are used only as part of the agreed scope. Managers and employers never receive private app activity, individual Zone history, or live individual-state data.
What if the Pilot does not produce clear results?
We report that. The explanation may be wrong, implementation may not have held, the work may not have repeated enough, or another change may have affected the result. The findings distinguish these possibilities where the evidence allows. They state whether to adapt, stop, or obtain specific additional evidence, with an owner and review point for the next step.
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.
Bring the finding and the change you want to test.
Tell us which business result is falling short, what the operational investigation found, and who controls the proposed change. Bring any Snapshot readout, Diagnostic summary, Audit findings, or existing operating evidence. The scoping call determines whether a Pilot would answer a useful question, what it would require, and what it would cost.
If a smaller correction, more evidence, or a different intervention is the right next step, we will say so.
