Show Product Thinking on Paper

Product Thinking is the score reviewers use to judge whether you drive from problems and users, or just execute tickets. It is the hardest thing to fake and the most valued when it is visible.

Show the problem, not just the feature

Weak bullets name outputs ("built a dashboard"). Strong bullets name the problem and the insight ("Users churned because they could not see ROI, so I built a value dashboard that lifted renewals 15%").

Signal user evidence

• Reference the research, interviews, or data that shaped the decision.
• Mention a hypothesis you tested and what you learned — including when you were wrong.

Show a trade-off

Nothing signals product judgment like a decision under constraint: "Chose to ship a manual workflow first to validate demand before investing in automation." That single line tells a reviewer you think in bets, not tasks.

Checklist

• At least two bullets that start from a user problem.
• One explicit trade-off, or a "we chose X over Y because…".
• Evidence (data or research) behind a key decision.