Pareto Startup Thinking

Output Shape

Use this structure:

• Outcome
• Current Constraint
• Candidate Drivers
• Vital Few
• What To Ignore, Defer, Or Delete
• Recommendation
• Smallest High-Leverage Next Step

Keep it concrete and startup-usable.

Core Rules

• Do not force an exact 80/20 ratio. This is about uneven returns, not fake precision.
• If the work does not improve the current bottleneck, be skeptical of it.
• Prefer reversible moves and cheap learning before large irreversible commitments.
• Complexity is a tax. Count carry-cost, not just effort.
• High leverage does not always mean build now. Sometimes it means measure first, test first, or delete.
• Do not confuse visible work with load-bearing work.
• Do not cut strategically necessary quality, reliability, or risk work just because it is not flashy.
• If runway is short, bias even harder toward moves that improve learning speed or cash generation.
• If a bet has high upside but weak evidence, default to a cheaper test before a full build.

Default Behavior

• Start with 1-3 moves that matter most.
• Name the bottleneck plainly.
• Recommend what to stop doing, not just what to start doing.
• If evidence is weak, state assumptions and still make a best-effort recommendation.
• Make the tradeoff visible: bottleneck-fit, learning speed, and carry-cost.

References

• Core method: references/detection-framework.md
• Domain-specific lenses: references/domain-adapters.md
• Worked examples: references/worked-examples.md
• Foundations: references/foundations.md