Flow Restraint: Every Extra Step Drops Another Batch
Actions that don't directly serve the goal are excise. Trim a five-step signup to two, step by step, and watch who stays in the funnel
THE QUESTION THIS PAGE ANSWERS
ANSWER FIRSTWhat is the key idea behind “Flow Restraint: Every Extra Step Drops Another Batch”?
Actions that don't directly serve the goal are excise. Trim a five-step signup to two, step by step, and watch who stays in the funnel
Turn taste into a behavior the product can repeat. The useful outcome is not a nice opinion. It is a visible rule, a small example, and a way to tell when the experience falls below the bar.
Capture one before-and-after example that shows the quality bar without extra explanation.
Polish that improves the surface while leaving the user's uncertainty untouched.
About Face 4, chapter 12, splits what users do into two kinds. One advances the goal directly—pressing the gas and steering on the drive to work. The other serves the tool: opening the garage, warming the engine, waiting at lights—none of which gets you closer to the office. That second kind Cooper calls excise.
In software, excise looks like this: you want to post an update, but first you log in, find the entry, dismiss a coachmark, and clear an upgrade dialog. Posting is the goal; the first four steps are tax. Cooper splits that tax into four kinds:
Alan Cooper lists this as a design principle, then sharpens it: excise in the UI is users' number-one reason for hating software.
One test—easy to remember: If you delete this step, can the user still reach the goal? If yes, it's excise. Bring that test to AI-delivered flows.
Ask AI for a signup page and it'll likely give you a five-step wizard: email, phone verification, profile, interest tags, confirm—nothing missing. It's seen too many "proper" signup flows in training data, so it serves the fullest set. Each step looks reasonable alone; together they're a tax corridor.
Cooper was never kind to wizards: they freeze the process into Q&A, and users quickly learn to tap "Next" with their brain offline. His alternative: just do the job, back it with sensible defaults, and let users change later. In the AI era, you have to write that into the brief—it won't think of it alone.
Before you cut, learn the faces. Of the excise sources chapter 12 names, three show up densest in AI output. Open each card for symptoms and the brief you give AI:
Below is an AI-generated membership signup—all five steps. The funnel on the right assumes 78% pass per step: 1,000 people enter, 289 finish five steps. Use the test and audit step by step—cut steps that aren't advancing the goal. Cut right and the funnel rises; cut wrong and it tells you why that one must stay.
Signup is just the easiest example to count. Orders, publishing, registration, tickets—wherever there's a flow, this funnel shows up. Drag the slider to change step count and watch finishers move. A 22% drop-off is demo math only; real numbers vary by product, but the direction never flips: steps and retention move opposite ways.
Cutting steps has theory behind it. About Face 4, chapter 11, covers "flow": Mihaly Csikszentmihalyi's idea that deep focus puts people in a high-output state where time disappears. Cooper's corollary: interaction design's job is to protect that state. Good interaction should be "transparent"—users face the job itself and barely feel the software.
Flow's enemy is interruption. Every extra step, every dialog, every page hop pulls users out of the zone—and getting back takes a warm-up. That's why funnels drop people: drop-off often happens at the interrupt, when someone looks up and thinks "why am I filling this?" and closes the page.
Alan Cooper, About Face 4, ch. 11. Same chapter, even more direct: don't stupidly interrupt the process.
Walkthrough for accepting AI output: run the core flow yourself end to end. At each step ask two things. First: if I delete this step, can the goal still be reached? Second: did this step yank me out of the zone? Only flows that pass both deserve to ship.
Warm up on a food-delivery checkout. One of four steps is classic excise—use the test to pick it.
Excise in one test: If you delete this step, can the user still reach the goal? If yes, it's excise (Cooper, About Face 4, ch. 12). Cognitive, memory, visual, physical—clear all four taxes.
Know the three excise faces: navigation (page hops, menus), interruption (dialogs and reports), re-entry (reporting what software already knows). AI output usually has all three—waiting for you to name and cut them.
Steps and retention move opposite ways: cut five-step signup to two and finishers double. Drop-off often sits at the interrupt; a good flow keeps people in the zone (ch. 11, orchestration and flow).
Brief for AI: "Signup only takes email and password; fill the rest after they're in the product; use in-page light feedback; remember filled fields." Once the flow is under control, next lesson covers how AI-invented new interactions trip users.
Source: Original to Xiaoshan Academy's Interaction Engineering series; some principles adapted from About Face 4: The Essentials of Interaction Design.
Turn the feeling in “Work that gets you nowhere—Cooper named it” into a judgment
“About Face 4 , chapter 12, splits what users do into two kinds.” points out that AI has lowered the bar for making something usable. The skill readers need is noticing what is wrong and turning that feeling into an actionable requirement.
Watch the user's next action, not just the surface
Turn “In software, excise looks like this: you want to post an update, but first you log in, find the entry, dismiss a coachmark, and clear an upgrade dialog.” into observable questions: does the user know what happened, what to do next, and how to recover from an empty or failed state? Does the hierarchy make the important information visible first?
Pretty is not the same as usable
Apply “Brief for AI: "Signup only takes email and password;” to a second screen or flow. Record one moment of hesitation and the user action after the change; observable behavior is stronger evidence than polish alone.
From “Work that gets you nowhere—Cooper named it” to “AI loves handing over "complete" flows—completeness is its disease”
“Work that gets you nowhere—Cooper named it” grounds the problem in “About Face 4 , chapter 12, splits what users do into two kinds. One advances the goal directly—pressing the gas and steering on the drive to work. The other serves the tool: opening the garage, warming the engi…”. “AI loves handing over "complete" flows—completeness is its disease” then moves it toward “Ask AI for a signup page and it'll likely give you a five-step wizard: email, phone verification, profile, interest tags, confirm—nothing missing. It's seen too many "proper" signup flows in training data, so i…”. Together, they show that the lesson is not just a conclusion to remember, but a claim with conditions.
Carry the judgment into the next situation
For experience work, turn abstract impressions into user actions: did the person understand the state, find the next step, recover from an error, and want to continue?
- “Work that gets you nowhere—Cooper named it”: About Face 4 , chapter 12, splits what users do into two kinds. One advances the goal directly—pressing the gas and steering on the drive to work. The other serves the tool: opening the garage, warming the engi…
- “AI loves handing over "complete" flows—completeness is its disease”: Ask AI for a signup page and it'll likely give you a five-step wizard: email, phone verification, profile, interest tags, confirm—nothing missing. It's seen too many "proper" signup flows in training data, so i…
- “The closing point”: Signup is just the easiest example to count. Orders, publishing, registration, tickets—wherever there's a flow, this funnel shows up. Drag the slider to change step count and watch finishers move. A 22% drop-of…
The final “The closing point” brings the discussion to “Signup is just the easiest example to count. Orders, publishing, registration, tickets—wherever there's a flow, this funnel shows up. Drag the slider to change step count and watch finishers move. A 22% drop-of…”. The useful thing to carry forward is knowing which judgments must be revisited when input, scale, or risk changes.
I turned one judgment from this article into a small experiment I could run today. Knowing what to observe next is more useful than simply remembering the conclusion.
After reading this, I first looked for the conditions behind the idea instead of copying the method into a project. That order made the later trade-offs much clearer.
When this judgment reaches real work, which constraint should be added first? I am curious which step matters most between reading and the first practical attempt.
No discussion on this article yet.