product-on-purpose/pm-skills

Acceptance Criteria generates testable Given/When/Then scenarios for a user story or feature slice. Use it when turning requirements into engineering handoff and QA sign-off criteria.

Architecture Decision Record documents a significant technical decision, its context, and consequences. Use it when choosing architecture, technology, or development patterns that future teams need to understand.

Build Risk Review names the single assumption most likely to make a product idea, feature request, or scope change fail, then returns a verdict and a no-code validation step. Use it before committing build effort or writing a PRD.

Competitive Analysis creates a structured comparison of 3-5 competitors across features, pricing, positioning, and strengths. Use it before entering a market, planning differentiation, or after losing deals.

Customer Journey Map maps a customer experience across stages, touchpoints, emotions, pain points, and moments of truth. Use it when synthesizing research into an end-to-end or phase-specific journey, and it refuses unsupported emotional or behavioral claims.

Define Hypothesis turns an assumption into a falsifiable statement with a target user, success metrics, and a validation approach. Use it before designing an experiment or A/B test to align on what success looks like.

Define Problem Statement creates a structured problem framing document with user impact, business context, success criteria, constraints, and open questions. Use it when starting an initiative, realigning work, or briefing leadership.

Design Rationale documents the reasoning behind a UX decision, including context, alternatives, trade-offs, and the choice made. Use it for significant design changes, stakeholder alignment, or preserving decision history.

Edge Cases documents boundary conditions, error states, race conditions, and recovery paths for a feature. Use it during specification or QA planning to map what can go wrong and what should happen next.

Interview Synthesis turns user interview notes, transcripts, or recordings into themes, insights, quotes, and recommendations. Use it after interviews, customer calls, or usability sessions to communicate evidence-backed findings.

Jobs To Be Done Canvas creates a JTBD canvas that captures functional, emotional, and social dimensions of a customer job. Use it to understand motivations, shape positioning, or compare competing solutions.

Launch Checklist creates a cross-functional pre-launch checklist with owners, dates, and go/no-go criteria for significant releases. Use it to coordinate engineering, design, marketing, support, legal, and operations before launch.

Lean Canvas produces a one-page business thesis across nine blocks for framing, stress-testing, or comparing product strategies. Use it when you need to make assumptions explicit and align a team on the model.

Market Sizing estimates TAM, SAM, and SOM for an external market using top-down, bottom-up, comparable, and analogous frameworks. It triangulates the results, labels confidence, and surfaces where the methods diverge or data is thin.

Meeting Agenda produces an attendee-facing agenda that defines topics, owners, timing, and desired outcomes before a meeting. It also emits a shareable summary for Slack or email plus prep, logistics, and time-boxed agenda details.

Meeting Brief produces a private prep document for a meeting where stakes, positioning, or stakeholder dynamics matter. It helps plan goals, messages, questions, risks, asks, and success signals before the conversation.

Meeting Recap produces a topic-segmented post-meeting summary with decisions and actions captured inline, plus a consolidated action view. Use it after a meeting from transcript or notes, especially when reconciling with a planned agenda.

Opportunity Solution Tree creates a visual map from a measurable outcome to customer opportunities and candidate solutions. Use it when organizing feature ideas or showing how discovery work traces back to outcomes.

Prioritization Framework runs applicable scoring methods like RICE, ICE, MoSCoW, Weighted Scoring, and Kano on a candidate list of work items. It compares the rankings and produces an executive summary when you need to choose what to do next.

Product Requirements Document creates a comprehensive PRD for features, epics, or product initiatives. Use it to align stakeholders on what to build, why it matters, and how success will be measured.

Release Notes creates user-facing summaries of shipped changes, translating features, improvements, and fixes into clear benefits. Use it when announcing updates to customers, stakeholders, or support teams.

Solution Brief creates a one-page overview of a proposed solution, including the problem recap, key features, success metrics, trade-offs, and next steps. Use it to align stakeholders or document solution intent before a detailed spec.

Spike Summary documents the results of a time-boxed technical or design exploration, including the question, approach, evidence, and recommendation. Use it after a spike ends so the team can decide whether to proceed.

Stakeholder Summary maps the people and groups with a stake in a project, including their needs, concerns, influence, and engagement approach. Use it at kickoff, when taking over a project, or when resistance suggests misalignment.

User Stories generates persona-based user stories from product requirements or feature descriptions. Use it when breaking work into sprint items, writing engineering tickets, or communicating scope.