Easy-to-process things feel truer, safer, and more appealing.
More quotesAt sheet 734, the phone rings.
The counter answers, returns and cannot remember whether the last pile contained 43 sheets or 53. A thousand-sheet job goes back to zero.
Next attempt: ten piles of one hundred. The phone interrupts at sheet 34 of pile eight. Seven hundred remain counted.
That is the practical force of a small win. It can survive interruption. In other work, a finished unit may give a customer something usable, remove one uncertainty or support the next decision.
Corporate programmes often counterfeit this with milestones. Seventeen workstreams reach 80 per cent; nobody outside the programme can do anything new. Activity has been divided according to ownership, then relabelled progress.
A more useful unit changes the state of the work. One customer can complete the task. One dependency is removed. One assumption meets real evidence. The finished piece still exists after attention moves elsewhere.
The opposite failure is a collection of trivial victories. Teams finish the easy pieces, publish cheerful updates and avoid the difficult dependency that determines whether any of it matters. Smallness protects work from total collapse; it does not supply direction.
The unglamorous dependency remains on the list.
The counting resumes. Pile eight reaches one hundred. Pile nine begins. Another call comes at sheet 61.
The counter puts a paperweight on the incomplete pile and writes 61 on a scrap. There are still 139 sheets on the desk, and the completed piles remain untouched.