Optimized flows move effort to the system

Ask most teams to optimize a flow and they start deleting steps. But step count is the wrong scoreboard. A three-step checkout that asks the customer to remember an account number, calculate a total, and decode a policy is harder than a five-step checkout where the system recalls, calculates, and explains. Optimization means finding every place the customer is doing work the system could do, whether remembering, computing, comparing, or interpreting, and moving that work inside the product. The discipline behind this is knowledge design: building systems around what people actually know, remember, and forget, so nobody needs external tools or prior expertise to succeed.

Why it matters to the business

Effort, not brevity, drives loyalty. CEB research published in HBR's 'Stop Trying to Delight Your Customers' found the Customer Effort Score predicted loyalty 1.8 times better than customer satisfaction and twice as well as NPS. CEB's follow-up finding is starker: 96% of customers who go through high-effort experiences become more disloyal, versus 9% after low-effort ones. A short flow that offloads thinking onto the customer is a high-effort flow, whatever the step counter says. Customers do not count steps; they feel the weight.

How to use it

• Audit your top flows and list every fact the customer must remember or look up; make the system recall each one.
• Find every calculation customers perform outside the product, such as totals, fees, and conversions, and build it in.
• Replace jargon and policy references with plain-language guidance at the moment of decision.
• Measure flows by customer effort and task success, not by step count or completion time alone.
• When adding a step reduces thinking, add the step.

Where teams get it wrong

Teams celebrate shipping a streamlined flow that quietly moved work off the screen and into the customer's head. Merging three clear steps into one dense form does not reduce effort; it concentrates it. The step counter improves while abandonment, errors, and support contacts rise.

Ask your team

• In our most important flow, what does the customer have to remember, calculate, or already know to succeed?
• Do we measure our flows by customer effort, or only by steps and completion time?
• Where did we recently merge or remove steps, and what happened to errors and support contacts afterward?

Customers do not count steps. They feel the weight.