스킬 찾기

Guide a team through questions about users, workflows, and priorities to create a user story map. Organize activities and tasks, then define a minimum viable product and later releases that each cover the full workflow.

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

• Facilitating a team story mapping workshop
• Reorganizing a flat backlog around user workflows
• Defining the scope of a minimum viable product

Analyze public reviews, app stores, and forums to identify unmet customer needs, competitor weaknesses, and reasons for switching products. Receive short customer quotes with source links, recurring themes, and hypotheses to validate in interviews.

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

• Finding recurring complaints about competitors
• Preparing hypotheses before customer interviews
• Gathering quoted evidence for sales comparison guides

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.

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

• Deciding whether to invest in an AI feature
• Comparing AI solution options by outcomes and risk
• Preparing a proposal for executive or budget approval

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.

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

• Agreeing on the user problem before proposing solutions
• Writing a concise problem statement for a PRD
• Finding the underlying problem behind feature requests

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.

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

• Estimating market size for a new product idea
• Preparing market figures for investors or executives
• Rebuilding a market estimate with unclear sources

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.

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

• Organize a flat backlog around the user journey
• Define the scope of a minimum viable product
• Split work into releases that each deliver usable value

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.

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

• Clarifying customer value before product development
• Aligning stakeholders on a launch promise
• Testing whether a product idea has a convincing story

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.

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

• Preparing revenue and retention metrics for a board presentation
• Checking whether revenue growth hides customer churn
• Comparing retention by customer start date

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

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.

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

• Prepare for the move from Director to VP or CPO
• Evaluate a leadership offer and prepare questions for the CEO
• Set priorities during the first months in a new role

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.

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

• Breaking down work that will not fit in one sprint
• Clarifying backlog items that are too large to estimate
• Separating stories with multiple acceptance scenarios

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.

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

• Pitching a new product or feature concept
• Aligning a team on the intended user experience
• Exploring whether a concept resonates before development

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.

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

• Turning requirements into user stories
• Defining testable acceptance criteria before development
• Preparing stories for backlog refinement and sprint planning

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.

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

• Practicing answers to product improvement interview questions
• Preparing for product design interview questions
• Turning scattered ideas into a clear spoken answer

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.

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

• Preparing executive alignment before a roadmap review
• Planning a conversation with a resistant stakeholder
• Including frontline users in decisions that affect them

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.

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

• Identifying stakeholders at an initiative kickoff
• Choosing whom to recruit for discovery research
• Preparing the stakeholder section of a product requirements document

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.

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

• Reviewing customer economics before increasing paid acquisition
• Comparing acquisition costs and payback across channels
• Estimating cash runway and funding needs

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.

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

• Clarifying why users abandon onboarding
• Reframing a stakeholder's feature request
• Aligning teams on the problem to solve

Guide a workshop one question at a time with visible progress and clear answer options. The skill adapts to supplied context, handles interruptions and pauses, and closes with a summary of decisions and actionable choices.

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

• Guide a product team positioning workshop
• Structure the kickoff of a discovery sprint
• Facilitate a retrospective on a failed beta launch

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.

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

• Establishing direction for a backlog without a clear strategy
• Planning a new product or major initiative
• Revisiting target customers and product differentiation

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

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

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.

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

• Prioritizing stakeholder involvement before a roadmap review
• Finding affected groups with little decision-making power
• Revisiting stakeholder strategy after a reorganization

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.

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

• Creating a working customer profile before research
• Aligning the team's assumptions about users
• Identifying assumptions to test in interviews