Product decision
I think we should build saved history before launching.
Tests whether saved history is truly a launch requirement or a visible substitute for proving repeat use.
Examples
Thoughts worth looking at twice.
Concrete inputs produce concrete counter-views. Write the thought you are actually using to justify a decision, not a broad topic.
Good inputs
Timing decision
Waiting until the product feels clearer is the safest option.
Separates useful preparation from delay that prevents the team from learning.
Business idea
People will pay if we add more features.
Surfaces the assumption that feature depth, rather than positioning or trust, is the main reason people are not paying.
Project decision
I should quit this project because progress is too slow.
Examines whether slow progress is evidence against the project or evidence that its scope and feedback loop need to change.
Difficult conversation
This teammate is the main problem.
Distinguishes observable behavior from an interpretation and identifies what should be checked before confronting the person.
Make an input more useful
Replace “What should I do?” with the thought already pushing you toward an action. Include the actual feature, person, deadline, assumption, or tradeoff. The tool can challenge a concrete claim more fairly than a vague request for advice.