Define minimum viable output

When This Fires

• Before starting any output when scoping its depth and length
• When an output keeps growing beyond its original scope
• When perfectionism is delaying shipment of something the recipient needs now
• Complements Define both good-enough criteria and over-investment… (good-enough + over-investment thresholds) with the scoping method that determines what "good enough" means

Common Failure Mode

Producer-centered scoping: "What do I want to include in this report?" produces scope based on what you know, not what the recipient needs. The report becomes a showcase of your thoroughness rather than a tool for the recipient's decision. Recipient-centered scoping asks: "What does the recipient need to act?" — a fundamentally different question that produces a fundamentally smaller output.

The Protocol

(1) Before producing any output, answer three questions: Who is the recipient? What action should they take after receiving this? What minimum content do they need to take that action? (2) The answers define your output's scope ceiling. Produce to this level and no further. (3) If you can't identify a specific recipient or action, the output may not need to exist — question whether it should be produced at all. (4) After shipping the minimum viable output, wait for feedback. If the recipient asks for more detail, provide it. If they don't, the minimum was sufficient. (5) Track: how often does a minimum viable output get a "needs more" response? If rarely, your minimum is well-calibrated. If frequently, your minimum is too lean — adjust upward slightly.