비즈니스 스킬

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

Choose a small validation experiment based on your hypothesis, risks, time, and resources. Compare five methods, from technical checks to user interaction tests, and define pass, fail, and learning criteria before investing in a larger build.

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

• Choosing a validation method for a risky idea
• Planning an AI feasibility check
• Selecting a test for onboarding task completion

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

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

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

Assess how political, economic, social, technological, environmental, and legal changes could affect a product or market. Summarize external opportunities, threats, and recommended actions to support market entry decisions, strategy reviews, and longer-term product planning.

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

• Assessing risks before entering a new market or region
• Reviewing external assumptions behind an annual strategy
• Reassessing product plans after regulatory or economic changes

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

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

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

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

Analyze incoming Slack messages, emails, or escalations before replying. Separate the explicit request from the outcome behind it, clarify requirements and success criteria, and develop a reply or counterproposal while clearly labeling assumptions.

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

• Analyzing an executive's urgent request before replying
• Clarifying the outcome behind a vague feature request
• Preparing a response to an escalation email

Understand the shift from product manager to Director through scope and planning horizon. Identify role-transition difficulties and translate broad company priorities into product responsibilities and clearer direction for teams.

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

• Understanding how PM and Director responsibilities differ
• Examining difficulties after a Director promotion
• Translating vague company strategy into team responsibilities

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

Compare business growth options across existing and new products and markets. The skill connects each option to documented demand signals, rates its risk, and recommends an order of action with the assumption that could change it.

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

• Compare growth options for next year's business plan
• Check the evidence behind a diversification proposal
• Sequence growth initiatives by risk and funding needs

Review a product or AI idea across ten internal and external risk areas. Identify useful tests and measurements, separate immediate actions from ongoing monitoring, and produce a prioritized risk register with concrete next steps.

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

• Reviewing risks before adding an idea to the roadmap
• Choosing tests before committing a team and budget
• Identifying external forces that could disrupt a product

Guide a product team from a problem hypothesis through customer interviews, research synthesis, and solution experiments. Use six structured phases to gather evidence, compare options, and decide whether to build, change direction, or stop.

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

• Validating customer problems before development
• Investigating onboarding drop-off or churn
• Organizing interviews and research synthesis

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

Assess whether to retire a product or feature by reviewing customers, revenue, commitments, and migration options. Get a reasoned recommendation to proceed, wait, or maintain it with limited investment, plus an appropriate effort level.

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

• Deciding whether to retire a legacy feature
• Sizing the effort for a product retirement
• Checking commitments before announcing retirement

Draft customer announcements for retiring a product, feature, or plan. Match the message length and communication stages to the impact, explaining the reason, key dates, customer disruption, support, and next steps, including cases with no replacement.

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

• Writing a retirement notice for a product or feature
• Explaining migration from a legacy product to its replacement
• Preparing an exit announcement when no replacement exists

Research key competitors and produce cited profiles, a comparison table, and implications for a product decision. Separate facts from inferences and assumptions, highlight evidence quality, and create a consistent baseline for later comparisons.

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

• Reviewing a product's positioning against competitors
• Informing roadmap priorities with competitive evidence
• Investigating a rival's strengths after lost deals

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 product retirement decision into a practical checklist matched to its scale. Organize work by lifecycle phase, assign responsible teams, and define approval conditions while covering data, contracts, access, and financial obligations.

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

• Planning the shutdown of a legacy feature
• Coordinating a product retirement across teams
• Checking data and contract obligations before closure

Plan and document a small, temporary experiment to test one risky product assumption before development. Choose a suitable prototype approach and define participants, pass and fail criteria, timing, ownership, and a disposal plan.

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

• Testing demand for a workflow automation idea
• Documenting an experiment for a pricing hypothesis
• Checking whether users can complete a signup form

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