Design the Smallest Useful Change

Why this matters

Grand redesigns usually die. They touch every step, upset every owner, take months, and get judged by the one metric someone liked on the slide. Small, testable changes that remove real friction survive. The change that stays in place is the one whose success is obvious to the people doing the work — not the one that looked impressive at the kickoff.

What you will be able to decide after this

Where the first intervention should go — the friction that matters most, not the one easiest to automate.
What to leave alone, including steps that are merely strange.
How to write a change that can be measured and rolled back.

Core lesson

From the map and the human-checkpoint decisions, identify the smallest change that would measurably improve the workflow.

Prefer changes that:

Reduce waits or handoffs — the Module 1 map usually shows a queue that explains the cycle time. Removing one handoff beats automating three steps.
Remove low-value rework — the loops where the same work gets redone because an earlier step produced something unusable.
Place AI only where verification cost is acceptable — the Core Judgment filter applies at workflow scale. If verifying the AI's step costs more than doing the step, it is not a candidate, no matter how well the demo looked.
Keep ownership clear — every step still has one accountable person. A change that blurs that is not an improvement.

Write the change as a concrete design, not a vision. A vision is a paragraph about efficiency. A design names the step, the person, the constraint, the measurement, and the rollback.

The one-page brief has six sections, and every one must be fillable:

What exactly changes — one or two steps, named, from the map. Not "the process."
What stays the same — the steps that are strange but stable, or out of scope because the owners are not ready. State them.
Where AI is used (if at all) and how it is constrained — which step, which input, what it may not do, what the human sees before the work proceeds.
Where the human checkpoints sit — carried over from Module 2, unmodified.
How you will measure whether it worked — the numbers from the Module 1 baseline, named for after.
How you will roll it back if it fails — the reverse switch. If there is no rollback, the change is not small.

Worked example

The renewal workflow from Module 2 has a 14-hour specialist wait: draft renewals sit in the specialist's inbox until the specialist batches them once a day. The smallest useful change is not a new system and not an AI that writes renewals. It is: the eligibility check runs at submission time (the data is already recorded), the system drafts the low-risk renewal using the eligibility output, and the specialist reviews the drafts twice a day against the pricing criteria — explicit accept, revise, or reject, no silent auto-advance. What stays: the pricing step, the confirmation step, and the named owner of each. Measurement: specialist wait in hours, first-pass acceptance rate, rework rate, against the Module 1 baseline. Rollback: the draft step turns off with a single flag; eligibility-at-submission is a configuration change in the existing system, reversible in minutes. The change is small enough that "did it work" is answerable in two weeks.

Practice

From your Module 1 map, list the three largest waits or rework loops. For each, write the smallest possible intervention in one sentence. Mark which one you would bet on, and why.

Apply — produce the artifact

Produce the one-page redesign brief for the smallest useful change to your workflow. Fill all six sections: what exactly changes, what stays the same, where AI is used and how it is constrained, where the human checkpoints sit, how you will measure whether it worked, and how you will roll it back if it fails.

Verify

Walk the brief with someone who does the work and someone who owns the outcome. If either cannot explain how they would know the change succeeded or failed, tighten the measurement section.

Sources

This module is original practice guidance based on the authoring standard and does not depend on a specific external factual claim. Editorial review is still required.