Translation and notes
A readable adaptation of the article's core ideas, with the original source clearly credited.
The essay distinguishes postponement by the work that replaces the deferred task. Choosing something more important differs from staying occupied with something less important. A completed checklist alone cannot settle that distinction. What follows is an independent exercise for a small team, not a process or case study supplied by the author.
Imagine an order-management team that tidies its support report every week without deciding why the same error returns. Inspect one closed ticket: what did the customer attempt, what did the team answer, and was the underlying problem resolved? Write the pending decision as a choice between changing the error message, repairing the order flow, or collecting more evidence. Assign responsibility for gathering evidence and authority for the final choice. Record what would support or contradict each option rather than asking everyone for a general opinion about customer experience.
For this hypothetical exercise, try reproducing the reported sequence in a test environment, with permission and synthetic data rather than a live order. Set an effort limit and name the expected output: a reproducible failure, or a precise account of what remains unknown. Do not label the second outcome a fix. If access or consent is unavailable, record the blocker and stop. Keep a separate list of deferred obligations, including who is waiting, the consequence of delay, and the next response time; an internal report redesign and a failed customer order need not receive the same treatment.
Close the review by recording what changed in your understanding, which option you chose, and what the customer should eventually notice. A prettier report is not evidence that the original issue disappeared. If investigation is complete but repair is pending, name the owner and review date explicitly. Start with one case rather than imposing a new reporting system on the company. The proposed exercise succeeds when a previously hidden decision becomes explicit and its effect is checked, while unfinished obligations remain visible.
Selected advice from the article
- Suggested worksheet: case, open decision, options, evidence needed, owner, effort limit, result, review date.
- When evidence is insufficient, name the unanswered question and the next observation instead of treating agreement as proof.
Operating takeaways
- Separate a support response from evidence that the customer's problem was resolved.
- Write one pending decision with explicit options and an accountable owner.
- Use a bounded reproduction with synthetic data; report uncertainty honestly.
- Record the impact and next response time for deferred obligations.
- Review the chosen action and its customer-visible result, not just ticket closure.
Quick feedback
What did this article make clearer for you?
Choose a reaction or share a question or experience. Useful responses can shape future notes.
This is a free adaptation, not a word-for-word republication of the original article.