77 skills (repositories by deanpeters) · sorted by popularity
Draft an Amazon-style press release before development to clarify a product's customer value. Using Working Backwards, a method that starts with the intended customer outcome, organize the problem, benefits, and launch promise so stakeholders can assess the idea.
Plan how to approach a key stakeholder by examining their role, authority, concerns, and situation. Get tailored messaging, communication methods, frequency, mutual expectations, and a concrete next action with an owner and deadline.
Turn business goals and customer problems into a product roadmap. Define initiatives, rank priorities, check dependencies and team capacity, and organize releases with clear reasons stakeholders can review and discuss.
Build an initial customer profile from existing research, market data, and team knowledge. Organize behaviors, frustrations, goals, and buying influences into a shared working hypothesis, with assumptions clearly marked for later validation.
Calculate and interpret SaaS subscription revenue, customer churn, and revenue retained from existing customers. Compare customer groups and revenue sources to uncover retention problems, explain growth, and prepare metrics for leadership discussions.
Turn product management notes or workshop material into a structured skill, or update an existing one. Follow a workflow covering duplicate checks, drafting, validation, catalog updates, and optional ZIP packaging for upload.
Split large feature requests or user stories, descriptions of what users need, into smaller deliverable pieces. Eight patterns guide the breakdown, with acceptance criteria and checks that each piece provides value and can be developed and tested independently.
Evaluate an AI product or feature idea by connecting customer problems, business outcomes, testable assumptions, risks, and differentiation. Produce a structured recommendation with lightweight experiments, success measures, and next steps for an investment decision.
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.
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.
Clarify a problem before choosing solutions through structured questions about team assumptions, affected people, and overlooked stakeholders. Produce a completed problem canvas, a refined problem statement, and a question to guide solution exploration.
Evaluate SaaS customer economics and cash efficiency using acquisition costs, customer lifetime value, margins, and payback periods. Compare segments and channels, estimate how long cash will last, and assess whether to expand spending or improve efficiency.
Estimate market size at three levels: total demand, the market your product can serve, and the share it could realistically capture. Use supplied figures or guided research to produce calculations with explicit assumptions, sources, and constraints.
Identify stakeholders before starting outreach or research. Organize supporters, affected groups, and influencers; record resource and approval roles; check overlooked perspectives; and choose two or three people or groups to understand first.
Track competitors' public pricing in a consistent format across repeated reviews. Compare prices, plans, feature access, usage limits, and free offers with previous records, then report documented changes and possible strategic signals with URLs and dates.
Practice spoken answers to product manager interview questions about designing or improving products. Follow six steps to clarify assumptions, choose users, prioritize a problem, and compare solutions before selecting an MVP, a first version with limited scope.
Prepare for a senior product leadership role or work through challenges after taking one. Adaptive questions identify your transition stage and produce targeted recommendations on organizational leadership, executive relationships, role evaluation, and communicating business outcomes.
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.
Map stakeholders using two grids: power versus interest, and impact versus power. Compare the results to decide how closely to involve each group, identify overlooked voices, and plan concrete actions to increase their participation.
Turn user research and complaints into a clear problem statement. Identify who is struggling, their desired outcome, barriers, root causes, constraints, and emotional impact, then summarize the problem in one sentence for team discussions or product planning.
Map a user's journey into activities, steps, and tasks, then organize the work by priority and release. The skill helps teams define a usable first version, place backlog items in context, and spot missing parts of the experience.
Translate user needs into concise stories that explain who benefits, what they want, and why. Add Gherkin acceptance criteria—preconditions, an action, and an expected result—to support development discussions and testable definitions of success.
Guide a team from product positioning and customer problem research to prioritized initiatives and a roadmap. Coordinate validation, stakeholder feedback, and execution planning so the team can connect its strategic direction to concrete work.
Create a six-frame storyboard showing a user's journey from a difficult situation to a better outcome. Develop the narrative, emotions, and visual descriptions to make product concepts concrete for pitches, concept reviews, and team discussions.