Product Management

Before I trust a product strategy, I want to see a clear user problem, evidence that alternatives were considered, and a review plan tied to an outcome. If those three things are missing, the roadmap is usually just a wish list with dependencies.

The best metrics are the ones that sit next to a decision, not the ones that decorate a slide. I want to know how fast a signal became a committed decision, whether the target users adopted the change, and whether the outcome metric tied to the bet actually moved. Before I trust a product strategy, I want to see a clear user problem, evidence that alternatives were considered, and a review plan tied to an outcome. If those three things are missing, the roadmap is usually just a wish list with dependencies.

The clearest signals usually live in quality of evidence behind the decision, clarity of roadmap communication, and follow-through on outcome measurement. A good archive helps future-you compare decisions over time instead of restarting each month from a vague sense that things are improving.

Keep these nearby while you evaluate:
- Atlassian product management guide: atlassian.com/agile/product-management
A practical reference for planning, teamwork, and delivery rhythms.
- Opportunity solution tree guide: producttalk.org/opportunity-solution-tree/
Still one of the clearest visual frameworks for connecting discovery to roadmap choices.
- Lenny's Podcast video archive: youtube.com/@Lennyspodcast/videos
Product conversations that tend to stay practical instead of drifting into slogans.