← Back to Concept Contrast

Concept Contrast Fable

Task success rate and step success rate

Conclusion first:One number tells you whether the whole job succeeded, while the other breaks it down to see whether each step landed steadily. Looking only at task success rate misses the cost of repeated stumbles in the middle; looking only at step success rate leaves you unsure whether the final deliverable was worth it.

One number tells you whether the whole job succeeded, while the other breaks it down to see whether each step landed steadily. Looking only at task success rate misses the cost of repeated stumbles in the middle; looking only at step success rate leaves you unsure whether the final deliverable was worth it.

Fable

Two Report Cards

Old Lin's waterwheel workshop took on a job for a dye house, requiring eight waterwheels to deliver dyes, clean water, cloth rolls, and drying racks to their positions in order every day. The contract had only one clause: the last batch of cloth each day must leave the workshop on time.

In the first month, Old Lin submitted a beautiful set of books: a daily workshop output rate of ninety-seven percent. The dye-works owner was very pleased—until the night-shift workers complained that the waterwheel often jammed midway, was repaired and turned, turned and jammed again, and although delivery was ultimately met, fuel and labor costs had multiplied several times over.

Old Lin crouched by the canal again to watch. Of the eight steps, the first drew water steadily, the second often clogged when adding material, the fourth had to wait for someone to change the cloth roll, and the final drying rack was squeezed into a mess by earlier delays. Looking at the endpoint all day, it seemed everything went smoothly; looking step by step, there were several falls along the way.

He first thought of sending more people to guard the finish line and urge them on. The urging grew louder, but the blockage did not disappear. Someone else said to simply rerun from the beginning after every failure. The cloth could come out, but at night a long queue formed.

Old Lin kept separate accounts for each waterwheel: which one stopped, for how long, why it stopped, and whether it could be repaired locally. The feed inlet was changed to dual slots, cloth roll changes were prepared with advance tags, and drying racks were separated by batch to wait, no longer forcing the entire line to rerun from the start.

Three months later, the final output rate was still 97%, but the proportion of waterwheels passing smoothly was much higher, and the night shift finished two hours early. Only then did the owner understand: arriving at the same destination by running smoothly the whole way and by falling and scrambling up the whole way are completely different in cost.

From then on, Old Lin required two lines side by side in the ledger: the first line to see whether the whole job was completed, the second to see whether each step went smoothly. The larger the gap between the two lines, the more the endpoint number hides problems on the ground. Later, when he took on new work, he first asked the client which segment they were willing to pay to make more stable. Looking only at final delivery, the workshop would conceal rework; seeing each step clearly, you know whether to fix the waterwheel, add hands, or change the whole waterway. He also found that some clients care only about the endpoint, while others care more about process stability. The former will tolerate rework; the latter cannot accept midnight fixes. Once the two ledgers were separated, the workshop knew whether it was selling on-time delivery or predictable operation.

Task success rate

Measures whether a complete task succeeds from initiation to final delivery. It does not distinguish gains and losses in intermediate steps, only focuses on the endpoint state. A task may experience multiple failures and retries, but as long as it is ultimately completed, it counts as one success.

Step success rate

Measures the independent success rate of each step within a task. After each step fails, it may be retried, skipped or downgraded. A low step success rate means the system is relying heavily on fault-tolerance mechanisms to hold on, rather than executing stably.

Story Mapping

  • Task success rate 97% but step success rate 62%: high fault tolerance masks instability in underlying execution.
  • Average of four and a half retries: the direct consequence of low step success rates; every retry consumes time and resources.
  • A comparison chart of two curves: task success rate rises smoothly while step success rate fluctuates repeatedly, exposing hidden costs.
  • Convert the timed-out API call into an asynchronous queue: fix the root problem at the step level rather than relying on task-level retries as a fallback.
  • The red gap between two numbers: the most valuable signal in the real world; the larger the gap, the more the system depends on luck and retries.

In the project

The acceptance report always records two success rates at the same time. Task success rate clarifies the delivery result, and step success rate clarifies execution cost. If the gap exceeds fifteen percentage points, prioritize investigating the root causes of step failures rather than continuing to add retries. The higher the degree of automation and the longer the call chain, the more analytical value the gap between these two numbers has.

京ICP备2026014272号