#Product Management
Usability Test Plan — Tasks, Script and What to Watch For
Plan a usability test for a prototype or live feature: goals, participants, realistic tasks, a moderator script, what to observe and how to report the findings.
A/B Test Plan — Hypothesis, Sample Size and Stop Rules
Plan an A/B test before you run it: the hypothesis, primary and guardrail metrics, a sample size estimate from your baseline and traffic, duration and the rules for calling it.
Outcome Roadmap — Now, Next, Later Without Fake Dates
Turn a list of planned features into an outcome-based roadmap with now, next and later columns, the problem each item solves and how you'll know it worked.
Interview Synthesis — From Raw Notes to Themes and Opportunities
Turn customer interview notes into themes, supporting quotes, opportunities to explore and open questions, with every finding traced back to the evidence.
Experiment Readout — What We Learned and What We'll Do
Write up an experiment's results honestly: what you tested, the numbers, whether the result is trustworthy, what you learned and the decision, including when the answer is no difference.
Jobs to Be Done Map — What Customers Are Really Trying to Get Done
Map the jobs your customers hire a product for: the main job, the steps, the outcomes they measure, what they use today, and where your product can help most.
User Stories — With Acceptance Criteria Engineers Can Test
Break a larger feature into small, independent user stories in build order, with testable acceptance criteria, a first thin slice and splitting suggestions.
Release Plan — Rollout, Feature Flags and Rollback
Plan how a feature reaches users safely: rollout stages, feature flags, who sees it first, the metrics to watch, when to pause and how to roll back.
Saying No to a Feature Request — Clear, Kind and Final
Write a clear, respectful reply declining a feature request from a customer, executive or colleague, with the reason, what you'll do instead and what would change your mind.
Metric Drop Investigation — Find Out Why a Number Moved
Work through a sudden change in a product metric step by step: check the data first, segment the change, list causes, and plan what to check next.
Launch Plan — Everything That Has to Happen Before Launch Day
Plan a product or feature launch across product, engineering, marketing, sales, support and legal, with owners, dates, a launch day runbook and success measures.
Feature Request Triage — Themes, Not a Pile of Asks
Sort a pile of feature requests from customers, sales and support into problem themes, count the evidence behind each, and decide what to explore, park or decline.
PRD One-Pager — The Problem, the Bet and How We'll Know
Write a short product requirements document: problem, goals and non-goals, users, key requirements, success metrics, risks and open questions, ready for review.
Post-Launch Review — What Happened Against What We Expected
Review a launch a few weeks later: results against the goals you set, what customers did and said, what went well or badly, and the decisions and follow-ups that come out of it.
RICE Prioritization — Score the Backlog and Show the Math
Score backlog items with RICE (reach, impact, confidence, effort) from your own estimates, rank them, and flag the scores that rest on weak evidence.
Product Strategy One-Pager — Vision, Bets and Trade-Offs
Draft a one-page product strategy: the vision, target customers, the problems you'll solve, your key bets, what you won't do, and how you'll measure progress.
North Star Metric — One Number and the Inputs That Move It
Choose a North Star metric that reflects the value customers get, with the input metrics your teams can move and the counter-metrics that keep it honest.
Customer Interview Guide — Questions About Past Behavior, Not Opinions
Plan a customer discovery interview: who to talk to, how to open, questions about what people actually did, follow-ups, and a note template, with consent built in.
Release Notes — What Changed, Written for Users
Turn a list of changes, tickets or a changelog into release notes users will read: what's new, what improved, what was fixed, and anything they need to do.
Edge Case Review — What Breaks Before Users Find It
Review a feature or spec for edge cases, error states, permissions, data limits, abuse and accessibility gaps before it's built, with what the product should do in each case.
Opportunity Brief — Is This Problem Worth Solving
Write a short opportunity brief before committing to build: the problem, who has it, evidence, size, why now, risks and the smallest way to learn more.
Team OKRs — Outcomes, Not a List of Features
Write objectives and key results for a product team that measure changes in customer behavior and business results, not features shipped, and tie them to company goals.
Competitive Product Teardown — Where We Win and Where We Don't
Compare your product with competitors and alternatives on the jobs customers care about, find real gaps and strengths, and decide what to do about them.
Stakeholder Update — Weekly Status Without the Spin
Write a weekly product update for stakeholders: progress against goals, what shipped, risks with owners, decisions needed and what's next, in a format busy people read.