Translation and notes
A readable adaptation of the article's core ideas, with the original source clearly credited.
The essay distinguishes criticism of a person or tone from a reasoned challenge to the central claim. Better argumentative form does not guarantee a correct conclusion. What follows is an independent startup exercise, not the author's prescribed process. Imagine sales requesting a custom report for a prospect while product wants to fix user activation. Ask each side for a decision card with a proposed outcome over the next two weeks, the time required, and the work that would be delayed. Use the same planning horizon for both options.
Separate observations from forecasts on each card. A prospect asking for a report is an observation; expecting that report to close the sale is a forecast. Assign someone to clarify the buying process and remaining obstacles. Before committing to an integration, consider a manually prepared sample using synthetic data. Set a time limit, an owner, and a stopping condition. A useful response to the sample does not prove that a contract will follow. If the test starts requiring production access or a support commitment, bring the expanded scope back for a new decision rather than silently absorbing it.
Have one accountable person record the choice, the displaced work, a review date, and the information that would justify changing course. For example, a team might spend one day investigating the report, then return to activation unless new information about the buying process warrants another review. This is an illustrative limit, not a universal allocation rule. Size the test for the team's actual capacity.
A week later, compare actual effort with the estimate and check whether the agreed review happened. Assess the commercial outcome separately from the decision process: a sale can still leave an expensive obligation, and a well-designed test can end without a sale. Keep harassment or boundary violations on a separate escalation path; this exercise is not a substitute for addressing them. The practical output is a short record that the team can revisit, not a scorecard of meeting winners.
Selected advice from the article
- Suggested card: option, two-week outcome, observation, open assumption, opportunity cost, owner, deadline.
- Use synthetic data for the sample and avoid creating an unreviewed delivery commitment.
Operating takeaways
- Compare options over the same horizon, including displaced work.
- Separate observed customer requests from sales forecasts and assign follow-up.
- Bound the test with an owner, time limit, and stopping condition.
- Record the decision owner, review date, and conditions for changing course.
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.