Feature lists are easy to write and easy to argue about. Decisions are harder - and far more useful - because each one names a bet, an owner, and a way to be wrong.
Frame each item as a bet
Instead of "build community," write "we believe a lightweight community will lift week-4 retention; we'll know if D28 returns move." Now the item has a hypothesis and a metric, and you can kill it honestly.
Shipping a feature is cheap. Learning whether it mattered is the actual work.
Make success legible up front
- State the user and business outcome before the build.
- Pick the one metric that would change if you're right.
- Decide in advance what result would make you stop.