Discovery, delivery, and outcomes.
2 topics
Product discovery validates what to build before building it. Techniques: customer interviews (Jobs to Be Done framework), surveys, analytics analysis, competitive research, and prototype testing. Opportunity assessment: market size (TAM/SAM/SOM), customer willingness to pay, and technical feasibility. Prioritize with impact/effort matrices or RICE scoring (Reach, Impact, Confidence, Effort).
2 resources
Strategy connects vision to execution. Define: product vision (aspirational future state), strategy (how to win), and roadmap (sequence of bets). Frameworks: North Star Metric (single metric that captures value delivery), OKRs (Objectives and Key Results for alignment), and outcome-based roadmaps (focus on outcomes, not features). Balance: user value, business value, and technical investment (debt, platform).
Work with engineering teams effectively. Sprint planning, user story writing (As a [user], I want [action], so that [benefit]), acceptance criteria, backlog grooming, and stakeholder communication. Ship incrementally: MVP → iterate based on data. Manage scope: say no to protect focus. Release planning: feature flags, phased rollouts, and beta programs.
Data-informed decisions: define success metrics for every feature before launch. Tools: Amplitude, Mixpanel, PostHog. Key frameworks: funnel analysis (where users drop off), cohort analysis (how behavior changes over time), retention curves, and feature adoption rates. A/B testing for validating hypotheses. Build dashboards for real-time monitoring. Avoid vanity metrics — focus on leading indicators of business outcomes.