Define minimum viable output: who receives it, what action should they take, what minimum content enables that action — then ship at that threshold
Define the minimum viable output by identifying the recipient, the action they should take, and the minimum content needed to enable that action—then produce only to that threshold before shipping.
Why This Is a Rule
Most outputs are over-produced relative to their purpose. A report that the recipient will skim for 30 seconds to make a go/no-go decision doesn't need 10 pages of analysis — it needs a clear recommendation with supporting evidence on one page. The 9 extra pages consumed production time that produced zero additional value for the recipient's actual use case.
The three-question scoping framework prevents over-production by anchoring the output to its purpose: Who receives it? (the specific person or audience), What action should they take? (the decision, response, or next step the output enables), and What minimum content enables that action? (the irreducible information the recipient needs to act). Everything beyond the minimum is over-production — pleasant but not necessary for the output to fulfill its purpose.
This is the output equivalent of the MVP (Minimum Viable Product) concept from lean startup methodology: produce the smallest thing that achieves the desired outcome, ship it, and iterate only if feedback indicates more is needed. Most outputs don't generate feedback requesting more — the minimum was sufficient all along, and the additional effort would have been waste.
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 thresholds for each output type — cap effort to prevent perfectionism on low-stakes work (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.