The Work That Succeeds by Shrinking (Part 3 of 3)

Every professional’s instinct is calibrated to throughput. Handle more. Process more. Be indispensable by volume. The measure of a good week is a full queue efficiently cleared.

That instinct was built over careers where it was the right instinct. It is the wrong instinct for the co-pilot stage — and most organizations never change the framework to say so.

The co-pilot role, designed correctly (as Part 2 established), is not an executor role. Its purpose is to map where the AI’s reliable territory ends — and to do that mapping so precisely that the map transfers to the system itself. The co-pilot isn’t clearing cases. They’re defining the boundary. Every accurately documented edge case is boundary data. Every precisely reasoned intervention is training signal. Every week where fewer cases needed a human is a week where the work landed.

The executor’s success metric is volume maintained. The co-pilot’s success metric is volume declining.

Those are not the same job. But most organizations deploy the co-pilot role and leave the executor metric in place. The job description doesn’t change. The performance review criteria don’t change. The implicit signal in the culture — do more, handle more — doesn’t change. And so the person in the role optimizes for the metric they have, which is the wrong one.

The results are predictable. Exception rates plateau. Progression stalls. Stage 1 continues indefinitely because the people running it are calibrated — unconsciously, reasonably — to keep it running. Gartner’s prediction that 40%+ of agentic AI projects will be abandoned by end of 2027 is regularly attributed to technology failure or unclear ROI. One underexamined explanation is the metric: organizations that never redesigned the co-pilot role plateau at Stage 1 and conclude that the technology didn’t deliver. The technology delivered. The job design didn’t.

What the job looks like when redesigned is not abstract. Here are three industries where the transition is in progress and the change is concrete.

Legal. The executor version: review 150–200 contracts per week, flag issues, pass to senior associates. The success metric is throughput — contracts cleared, turnaround time maintained.

The redesigned version: the job is to build the AI’s exception taxonomy. Not to review contracts en masse, but to identify the specific clause patterns the AI consistently misclassifies — the indemnity formulations it reads as standard when they aren’t, the liability caps it approves that fall outside acceptable range for this client type — and to document the reasoning behind each correct answer precisely enough that the pattern can be encoded. The output is a taxonomy, not a review count. The ABA’s 2025 task force declared that “AI has moved from experiment to infrastructure for the legal profession”; the firms that progress past Stage 1 are the ones where the co-pilot is building that taxonomy, not just clearing the queue.

The success metric: intervention rate declining week over week. The proportion of AI-flagged items requiring human correction should be shrinking. When it does, the boundary is moving.

Accounting. The executor version: test 400–500 journal entries per week, run reconciliations, perform vouching procedures. Throughput is the measure. This is the routine work that trained junior CPAs through sheer volume — and that the AI has largely absorbed.

The redesigned version: the job is to map the AI’s exception patterns. The AI will flag anomalies — not all of them are errors. Some are legitimate business events that look unusual to a pattern-recognition system but are valid in context. The redesigned co-pilot identifies which anomaly categories are genuine errors, which are legitimate events the AI hasn’t learned to recognize, and builds the decision logic that distinguishes them. The output is a decision framework. The AICPA’s Profession Ready Initiative, launched in February 2026, is the profession’s acknowledgment that the job is changing and the job description hasn’t caught up.

The success metric: the proportion of AI-flagged anomalies requiring human review should decline as the framework matures.

Software engineering. The executor version: review pull requests, fix bugs, implement features. Commit count, PR throughput, story points closed.

The redesigned version: agent supervisor. The job is to identify the architectural decisions AI coding agents consistently get wrong — where agent-generated code is syntactically correct but architecturally misaligned, where it introduces technical debt that won’t surface until a later integration — and to document those failure modes precisely enough to inform system-level constraints. Anthropic’s 2026 Agentic Coding Trends Report found agents now complete an average of 20 autonomous actions before requiring human input. What the engineer supervising those agents is actually doing is defining the boundary of those 20 actions — which decisions the agent can own, which it must escalate, and what the failure modes look like when it gets that wrong.

The success metric: not commits. Architectural decision quality. Reduction in integration failures across agent-generated work.

In all three cases, the new success metric runs in the same direction: intervention rate declining, the boundary sharpening. The work that looks like doing less is exactly the work the role was designed to do.

Here is what nobody says out loud in most co-pilot deployments: the better you do this job, the less the job needs doing.

Not the less valuable you are. The less this specific function requires a person. Those are different things, and the failure to distinguish them is where the woman in the opening went wrong — and where most organizations fail to help people go right.

Every professional instinct built over a career points toward indispensability through volume. Be needed for more, not less. The co-pilot role inverts that at the task level. Your most successful days are the ones where the AI needed you less than it did last week, because that means the boundary you’ve been mapping is holding.

This creates a specific and largely unacknowledged psychological challenge. Most co-pilots don’t consciously resist the new metric. But they unconsciously optimize for the old one. They handle cases the AI could probably manage, because handling things feels like working. They document edge cases less precisely than they could, because the intervention is the visible work and the documentation is invisible. They don’t push the AI as hard as they should, because pushing harder means fewer interventions, which reads — through the old metric — as being needed less.

The effect is subtle. No individual decision looks like resistance. The aggregate is a stalled exception rate and a Stage 1 that never progresses. Not because the technology failed, and not because the people are disengaged. Because the metric was wrong and the job was never redesigned to say so.

This is the fixable part. But only if it’s named.

The success paradox only holds if you’re looking at the wrong window.

William Stanley Jevons observed in 1865 that when steam engines became more efficient, Britain didn’t use less coal — it used more. The efficiency gain reduced cost per unit. Lower cost per unit expanded demand. Expanded demand consumed more total resource than inefficient engines ever had. Jevons’ Paradox has held across energy economics for 160 years. It applies here.

When AI makes knowledge work output cheaper per unit — cheaper contract reviews, cheaper audit samples, cheaper code checks — volume doesn’t stay flat. Cost drops trigger demand expansion. The PE firm that could afford one due diligence report now commissions three. The mid-market company that couldn’t justify a legal review for routine contracts now orders one on everything significant. An accounting firm that once managed 80 client engagements can handle 400. Output multiplies because the unit cost fell.

Every additional unit of AI output is an additional demand on human judgment. Someone has to evaluate it, direct it, decide what to do with the result, and own the outcome. As output volume grows, that demand grows with it. The co-pilot who maps the AI’s boundary and exits Stage 1 doesn’t graduate into a world with less need for judgment. They graduate into a world where the demand for judgment — the work that can’t be automated — is expanding faster than it was before automation started.

BCG’s April 2026 analysis of approximately 165 million U.S. jobs found that 50–55% will be reshaped over the next two to three years, with only 10–15% fully displaced over a longer horizon. 68% of companies expect to maintain workforce size. And accounting offers the most precise version of Jevons already in motion: Client Advisory Services — the judgment-intensive work — grew at a median 17% rate compared to 9.1% for overall firm revenue. Net CAS fees per professional reached $156,250, up 29% since 2022. Practices project 99% growth over the next three years. The compliance work is automating. The advisory work is accelerating. Those are not two separate trends. They are the same dynamic: unit cost falling, total demand rising.

The co-pilot’s success is not self-elimination. It is the prerequisite for stepping into the work Jevons guarantees is expanding.

The redistribution thesis is often left at the level of “advisory roles” and “higher-value work” — accurate but not useful to someone trying to understand what their Monday morning looks like in eighteen months. Here is what the endpoint jobs actually look like in the industries where Stage 1 is progressing.

The former document reviewer (legal).

The Stage 3 job is not “senior reviewer.” It is strategic associate: managing 5–8 active matters simultaneously, synthesizing AI analysis into the 2–3% of issues that require attorney judgment, briefing the partner on exactly which decision points need their attention. The client relationship that needs a person on the phone. The novel argument on an unsettled legal question where there’s no good training data. The SDNY ruling in February 2026 confirmed the accountability floor: an attorney’s judgment, signature, and professional standing cannot be delegated to a system. That floor is the Stage 3 job description. Success is no longer measured in contracts reviewed. It’s measured in matters resolved, client relationships held, issues caught before they became problems.

The former transaction tester (accounting).

The Stage 3 job is Client Advisory: combining the AI’s financial pattern detection with the business context the AI doesn’t have, identifying the strategic implication of what the numbers show, advising on decisions the analysis informs. The PCAOB’s AS 1000 standards hold the accountability floor in audit; everything the AI handles below it frees the practitioner for the work above it. The CPA who can tell a client what a pattern in their financials means for their next capital allocation decision is doing work that requires the AI’s output, professional judgment to interpret it, and enough client context to make it actionable. Success is measured in advisory revenue and decisions informed — not tests run.

The former code reviewer (engineering).

The Stage 3 job is engineering lead for a system that includes AI agents as team members. The work is architectural: defining the constraints the agents operate within, handling the integration failures that cross agent boundaries, making the system-level calls that no agent can make because they require a view of the whole. Where Stage 1 was catching the AI’s edge cases in individual pull requests, Stage 3 is designing the systems that determine what edge cases the agents will encounter. Anthropic’s labor market study shows no systematic increase in unemployment for AI-exposed workers, but a clear hiring slowdown for 22–25-year-olds in highly exposed occupations. The front of the pipeline is thinning; the work at the top is not contracting.

In each case, the path from executor to judgment role runs through the co-pilot stage. Not around it, not despite it — through it. The boundary-mapping work of Stage 1 creates the taxonomy that defines Stage 2. The judgment-call inventory of Stage 2 defines the permanent floor that Stage 3 works within. The stages are not just organizational milestones. They are how the individual develops the judgment the Stage 3 job requires.

The manager’s job in the co-pilot transition is not primarily to manage anxiety. It is to redesign the job explicitly, install the new metric from day one, and name the endpoint in advance.

Anxiety is downstream of metric confusion. The woman who updated her resume wasn’t irrational — she applied a reasonable inference to the information available to her. The fix is not better reassurance. It is a job description that makes a declining queue recognizable as success.

At the start.

Not: “your role is to review AI outputs for quality.” That is the executor description. The redesign conversation sounds like this: “Your job is to define what right looks like in situations the AI hasn’t encountered yet. The more precisely you document the reasoning behind each judgment call — not just the outcome, but why that’s the right answer in this context — the faster the system learns. We’re going to track your intervention rate together. Over time, that number should decline. When it does, it means what you’re doing is working.”

That framing gives the person a way to measure their own success that is consistent with the stage ending. The redeployment is not a surprise if the co-pilot understood the stage from the beginning. Prosci’s research is consistent: 58% of employees want to hear about personal impacts from their direct supervisor — not from a town hall, not from corporate communications. The conversation has to happen at the manager level to land.

During.

Show the curve. The intervention rate data belongs on the co-pilot’s screen, not just the management dashboard. A declining line is motivating in a way that abstract progress updates are not — it shows that the boundary they were asked to move is moving. Gallup’s April 2026 research found that employees who strongly agree their manager actively champions AI use are more than twice as likely to use it frequently. Showing the curve is the simplest possible version of that.

At the end.

The advancement conversation requires specificity. Not: “your role is evolving.” Not: “we’re moving to the next phase.” Those statements communicate that something is ending without saying what comes next.

Specific looks like: “The class of cases you were handling is now handled. The intervention rate has held below threshold for six weeks. That means Stage 1 is done. Here’s the taxonomy you built — this is what Stage 2 works from. And here’s where we’re pointing you next, and why.”

The co-pilot built something. Tell them what it was.

This series gave you the map (Part 1), the mechanics (Part 2), and now the personal transition.

The hardest thing to hold, for anyone in a co-pilot role, is this: I am doing the job right when I am needed less for this specific task. That inverts every professional instinct built over a career. The instinct isn’t wrong — it’s calibrated to the wrong window.

Zoom out, and the picture changes. WEF’s Future of Jobs Report 2025 projects 78 million net new jobs globally by 2030, with 170 million created against 92 million displaced. BCG’s 2026 analysis found 68% of companies expect to maintain workforce size. And Jevons tells you why: AI output volume is expanding, and every unit of AI output is an additional demand on the human judgment that evaluates, directs, and owns it.

The work that succeeds by shrinking is building toward work that doesn’t. The judgment jobs are on the other side of Stage 1 being completed, not abandoned.

The junior analyst from the opening would have stayed if someone had given her a new metric to measure herself against. Most people would. The technology automates the work. The job redesign automates the fear.

Both matter. Only one of them requires a manager who understood what Stage 1 was actually for.