# 3.3 The middle 80 percent: the worker plans and executes (/ai-worker-paradigm/the-10-80-10-operating-rhythm/middle-80-percent)

---
type: Document
title: "3.3 The middle 80 percent: the worker plans and executes"
description: "What the worker does in the middle 80 percent, the small job the human keeps there, and when to interrupt."
status: stable
order: 103.3
ksor:
  owner: team:panaversity
  audience: [ public ]
  approval:
    by: process:panaversity
    at: 2026-10-08T21:51:33Z
chapter: "03"
part: I
expert_status: required
concepts: [ "3.3" ]
last_verified: 2026-10-04
generated:
  at: 2026-10-08T21:51:33Z
  by: process:panaversity
trust_tier: unverified
build_id: sha256:2f1e14f2a0f11dbc37eb5856ca9b7d35b4ce4894da74c3328cf61a3c17c03861
dirty: true
ksor_version: 0.0.60
---

**In everyday life.** A friend is cooking dinner for you. If you stand over the stove and keep changing the heat, you end up cooking it yourself, only slower. You stay nearby in case they ask where the salt is. With the cook, changing the heat is steering, and the salt is the one question you stay nearby to answer.

In the middle 80 percent the worker owns the steps. It reads the inputs, decides the order of work and chooses its tools. It checks its own intermediate results and gathers the evidence the review contract asked for. On a delegated task this happens on the worker's own machine, often while you are away (Chapter 1).

> [!TIP]
> **Your job in the middle**
>
> This job is small and specific.
>
> - **Stay reachable.** A good brief makes the worker stop and ask when a stop rule applies. Answer quickly, and answer the question asked.
> - **Approve what the authority level requires, and only that.** If the brief says the worker drafts, there is nothing to approve until the final 10. If a product asks you to confirm a step, read it. Do not click through it without thinking.
> - **Watch if you like, but do not steer.** A progress view is for noticing that something is badly wrong, such as the wrong files or the wrong month. It is not for redirecting each step.

Interrupt when a stop condition appears. There are four: you learn something that changes the intent, you see the wrong inputs, the worker acts beyond its authority, or its behavior looks suspicious. For a change of intent, stop the run, fix the first 10 percent and start again. For example, you learn during the run that the brief had the wrong month. Changing the brief mid-run, one message at a time, leaves no clear record of what the worker was asked to do.

Why hold back? **Because every interruption moves work from the worker back to you, and that work is the reason you delegated.** Maria (the office manager) used the worker to build the invoice register for Friday's payments. She did not trust the worker to work on its own. So she approved each step and fed the worker one invoice at a time. She did the planning herself and paid for the worker as well. The register took her 90 minutes, and doing it by hand takes about 75.

Holding back is also what makes parallel work possible. You cannot steer three tasks at once, but you can brief three well and check three sets of evidence.

Trust in the middle is earned per kind of task, not given once. A new task type, or a task that touches money, may run with the worker asking before each important step. A task with a clean record can run with less. Chapter 7 turns that judgment into the autonomy ladder.