Dean Peters

Choose a prioritization method that fits your product stage, team, stakeholder needs, and available data. Get a recommended framework, practical setup steps, a scoring example, and an alternative approach with its tradeoffs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a method for recurring roadmap prioritization
• Selecting a lightweight approach when data is scarce
• Agreeing on prioritization rules with stakeholders

Assess whether a product is mature or declining, then compare extending it, replacing it, or retiring it. Use diagnostic questions, a product portfolio worksheet, and a replacement risk register with backup plans to document the next move.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing between a product refresh, replacement, or retirement
• Checking whether a mature product is entering decline
• Setting consistent plans across an aging product line

Build an evidence-backed SWOT, covering strengths, weaknesses, opportunities, and threats, for one company. It cites public sources and connects the findings to possible moves and risks that inform a specific business decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing evidence-backed material for a strategy review
• Examining a key competitor's strengths and weaknesses
• Assessing a potential partner or acquisition target

Plan stakeholder conversations before retiring a product or feature. Get an ordered sequence of meetings, with questions, commitments, warning signs, and required outcomes, adjusted to the scale and complexity of the retirement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning conversations before a product retirement
• Checking promises made by Sales before announcing
• Coordinating a retirement involving resellers

Plan the first 90 days as a VP or CPO product leader through organizational interviews, validation, and evidence-based action. Build a people assessment, identify unwritten priorities, and choose three to five changes grounded in what you learn.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning the first 90 days in a product leadership role
• Preparing questions for the CEO before accepting a CPO offer
• Validating organizational findings before making changes

Evaluate a proposed pricing change by modeling revenue per customer, conversion, cancellations, and customer acquisition cost recovery. Compare scenarios and receive a recommendation to implement, test, modify, or hold the change, with supporting calculations and risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluating a price increase for new customers
• Estimating revenue from a new premium tier
• Assessing an annual prepayment discount

Quickly look up SaaS financial metrics, including recurring revenue and customer acquisition costs. Get definitions, formulas, benchmarks, and warning signs, plus reminders of which metrics matter when reviewing features, pricing, acquisition channels, or business health.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up NRR formulas and benchmarks
• Preparing a SaaS metrics sheet for a business review
• Checking metrics before expanding an acquisition channel

Turn stakeholder requests into measurable goals, customer problems, possible solutions, and experiments. Through guided discussion, compare feasibility, expected impact, and customer fit to choose a proof of concept: a small test of a proposed solution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reframing a feature request as a customer problem
• Connecting product goals to solutions and experiments
• Explaining why one solution was chosen over alternatives

Compare a previous PESTEL analysis of political, economic, social, technological, environmental, and legal factors with current evidence. Identify meaningful changes and broken assumptions, then summarize their implications for strategy and product plans with sources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Quarterly reviews of external business conditions
• Checking assumptions after regulatory changes
• Connecting external changes to product plans

Create a clear statement of your product’s market position using Geoffrey Moore’s framework. Define the target customer, unmet need, product category, customer benefit, and meaningful differences from the alternatives buyers actually consider.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define the market position of a new product
• Sharpen differentiation against specific competitors
• Align product, sales, and marketing teams

Turn research notes and discussions into a PRD, a product requirements document for development teams. Connect customer problems, target users, proposed solutions, and success metrics, while documenting acceptance criteria, excluded work, dependencies, and unresolved questions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing requirements for a major new feature
• Turning discovery findings into an engineering handoff
• Aligning teams on scope and success metrics

Turn product management notes, frameworks, or rough ideas into a complete SKILL.md draft. Guided questions help choose the skill type, narrow its purpose, and organize instructions, examples, and common mistakes into the required structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning workshop notes into an agent skill
• Choosing the right structure for a new skill
• Formalizing a product management framework

Map a market from the buyer's perspective, covering segments, established companies, alternatives, and emerging entrants. Produce a sourced overview that distinguishes facts from assumptions and tests whether apparent gaps represent opportunities or weak demand.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping a market before deciding to enter
• Comparing competitors with existing alternatives
• Testing whether an unserved segment has demand

Design workflows where specialized AI agents share recurring product management tasks. Define each agent’s role, required information, handoffs, and human review points, then create monitoring and evaluation plans for the overall workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing parallel agents for weekly competitive research
• Defining agent roles and information handoffs
• Planning quality checks and cost monitoring

Assess a product that has stopped growing and compare extending it, replacing it, or retiring it. Guided questions separate customer demand from cost and technology pressures, producing a reasoned recommendation that may also favor continued operation without investment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing whether flat revenue signals product decline
• Comparing extension, replacement, and retirement
• Checking whether pricing or sales channels are the real issue

Compare current competitor evidence with a previous research snapshot and report only meaningful changes, with sources and dates. Flag sales comparison materials, positioning, pricing analysis, or roadmap assumptions that need updating during recurring monitoring.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking monthly changes against a previous competitor report
• Tracking competitors' pricing and plan changes
• Finding sales comparison materials that need updating

Create a customer journey map showing actions, contact points, emotions, success measures, and responsible teams at each stage. Use it to identify frustrating experiences, compare improvement opportunities, and build a shared view across departments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the customer experience from discovery to continued use
• Investigating where customers drop out
• Aligning marketing, sales, product, and support teams

Guide a product retirement through six phases, from the initial decision to closure and review. Scale the process to its impact, coordinate supporting skills, and identify missing steps when a retirement is already underway.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a product retirement from decision to closure
• Preparing sales and support before a customer announcement
• Finding skipped steps in a troubled retirement

Turn a major product initiative into a testable hypothesis with a clear target user and expected outcome. Define small experiments, measurable success criteria, and an evaluation timeframe before committing to full development.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying the expected outcome of a major initiative
• Designing small experiments before full development
• Defining measurable success criteria and deadlines

Evaluate whether a product feature deserves investment by comparing revenue or retention benefits with development and ongoing costs. Receive calculations, payback estimates, and recommendations that account for strategic value and uncertain assumptions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Decide whether to build a feature this quarter
• Compare feature ideas by financial return and strategic value
• Explain roadmap priorities to stakeholders

Structure customer research around what people want to accomplish, the difficulties they face, and the benefits they seek. Explore practical tasks, social perceptions, and emotions to clarify unmet needs and guide product positioning or priorities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Uncovering needs behind feature requests
• Organizing findings from customer interviews
• Revisiting product positioning around customer goals

Work through eight canvas sections to clarify a business problem, target users, desired outcomes, and possible solutions. Turn assumptions into testable hypotheses and choose the smallest experiment to investigate the most important uncertainty before development.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Framing the problem behind a new product idea
• Aligning a cross-functional team on assumptions
• Choosing which hypothesis to test first

Assess an industry's five competitive forces using documented evidence, including AI substitutes and supplier dependencies. Identify where profits concentrate and what pressures margins, then connect those findings to a market entry or strategy decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluating whether to enter a market
• Investigating structural causes of shrinking margins
• Assessing the threat of AI substitutes

Work through up to five adaptive questions to clarify your product’s customers, unmet needs, category, benefits, and competitive differences. Turn the answers and supporting evidence into a positioning statement and a concise summary for stakeholder review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify vague product messaging before launch
• Reposition an existing product
• Agree on target customers and competitive differences