비즈니스 스킬

Build a product strategy across nine connected areas, including vision, target markets, customer value, growth, and competitive advantages. Clarify priorities, work to exclude, success metrics, and assumptions, then propose small experiments to test the strategy.

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

• Defining the direction of a new product
• Aligning target markets with customer value
• Clarifying priorities and work to exclude

Assess the external conditions affecting a business across political, economic, social, technological, legal, and environmental factors. Rank their impact and likelihood, then outline strategic responses, indicators to monitor, and contingency plans for market entry or business planning.

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

• Assessing external risks before entering a market
• Reviewing external conditions for strategic planning
• Finding opportunities in regulatory or technology changes

Design product pricing based on customer value, competitor offerings, and willingness to pay. Compare charging models, define plan tiers and included features, and outline experiments to test prices and assumptions before introducing a new pricing structure.

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

• Setting prices for a new product
• Comparing flat-rate and usage-based pricing
• Designing free and paid plan tiers

Explore three to five ways to earn revenue from a product or feature. Compare customer fit, estimated costs and returns, and risks, then design low-cost experiments and prioritize which approaches to test first.

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

• Explore revenue models for a new product
• Compare subscription and usage-based pricing
• Design experiments to test willingness to pay

Prepare a confidentiality agreement for two parties using their details, the information being shared, and the governing jurisdiction. Receive a summary, a customizable draft, and plain-language notes identifying decisions and clauses that need legal review.

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

• Preparing an NDA draft before partnership discussions
• Drafting a one-way or mutual confidentiality agreement
• Defining which shared information should be protected

Turn a product idea into a Lean Canvas, a nine-part outline of business assumptions. Define customer problems, solutions, value, channels, revenue, costs, and metrics, then identify risky assumptions and suggest experiments to test them.

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

• Organizing business assumptions for a new venture
• Clarifying target customers and the value offered
• Reviewing revenue, costs, and key metrics together

Break a feature into job stories that describe the user's situation, motivation, and desired outcome. Add six to eight observable acceptance criteria per story, defining how success will be checked, and include links to designs or prototypes.

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

• Breaking a new feature into job stories
• Writing backlog items around user situations
• Defining acceptance criteria for desired outcomes

Build a sprint plan for a short development cycle using team availability and recent delivery history. Select work that fits capacity, sequence dependent tasks, identify owners and risks, and reserve room for unexpected work.

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

• Preparing a sprint planning meeting
• Estimating capacity around leave and other duties
• Selecting backlog work that fits team capacity

Turn survey responses, interviews, and other research data into three distinct user personas. Each profile explains the outcome users seek, their main difficulties, desired benefits, an unexpected behavioral insight, and how well the product meets their needs.

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

• Creating three personas from survey responses
• Grouping interview findings by user goals and behavior
• Comparing user needs to guide product decisions

Explore features for a new product through product management, design, and engineering perspectives. Generate five ideas from each viewpoint, then select five priorities with reasoning and assumptions to test before developing the concept further.

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

• Exploring features for a startup idea
• Comparing ideas from three professional perspectives
• Choosing five ideas to validate first

Map project stakeholders by their influence and interest, then create a communication plan for each group. Specify update frequency, channels, and key messages, while identifying competing interests and suggesting ways to align people across teams.

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

• Identifying stakeholders before a launch
• Planning updates for executives and teams
• Aligning groups with competing interests

Generate improvement ideas for an existing product from product management, design, and engineering perspectives. Produce five ideas per perspective, then select the top five based on goals, potential impact, feasibility, and differentiation, with reasons and assumptions to test.

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

• Brainstorming features for an existing product
• Exploring solutions to a customer problem
• Comparing ideas from three professional perspectives

Rewrite a feature-based roadmap around the changes customers and the business should experience. The result pairs each initiative with an outcome statement, success metrics, sequencing notes, and context connecting the plan to company strategy.

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

• Turning a feature list into measurable outcomes
• Connecting roadmap initiatives to company strategy
• Defining success metrics for planned work

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

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

• Choosing the first customer segment for a new product
• Focusing limited resources on a launch market
• Comparing segments using interviews and customer feedback

Examine feature ideas for existing products to uncover risky assumptions about customer value, usability, business support, and technical feasibility. Consider product, design, and engineering perspectives, then record potential failures, confidence levels, and suggested ways to test each assumption.

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

• Reviewing assumptions behind a feature idea
• Assessing risks from three professional perspectives
• Planning how to test uncertain assumptions

Run a structured sprint retrospective, a review of a short work cycle, using team feedback and delivery results. Identify shared themes and produce two or three prioritized improvements with owners, deadlines, and measures of success.

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

• Facilitating a team retrospective
• Grouping survey responses and team feedback
• Turning problems into assigned improvement actions

Review a product plan by imagining a failed launch and tracing possible causes. Separate real risks, overblown concerns, and unspoken worries, then define mitigation actions, owners, and deadlines for issues that must be resolved before launch.

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

• Checking launch plans for possible failure causes
• Separating real risks from overblown concerns
• Surfacing assumptions the team has not discussed

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

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

• Testing demand before building a new product
• Planning landing page or waitlist experiments
• Checking willingness to pay through pre-orders

Use customer research, surveys, and usage data to define an ideal customer profile: the customers most likely to gain value, stay, and expand. Summarize their characteristics, buying behavior, goals, needs, and fit criteria to guide sales and marketing priorities.

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

• Defining ideal customers from surveys and interviews
• Finding patterns among customers who stay and expand
• Aligning sales and marketing priorities

Identify untested assumptions behind a new product idea across eight areas, including customer value, usability, business viability, technology, ethics, market launch, strategy, and team. Rate confidence in each assumption and suggest a test, producing a Markdown analysis.

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

• Checking assumptions behind a new product concept
• Reviewing launch channels and messaging assumptions
• Examining technical and team risks together

Build an Opportunity Solution Tree, a structured map linking one measurable product outcome to customer needs, possible solutions, and experiments. Use research findings to prioritize problems and define hypotheses, metrics, and success thresholds for testing ideas.

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

• Organizing customer research into a structured tree
• Prioritizing customer problems around one product outcome
• Comparing multiple solutions for a customer need

Turn a new feature into user stories: short descriptions of what people need and why. Each story includes a design reference and testable acceptance criteria, with scope intended to fit within one sprint.

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

• Breaking a new feature into backlog items
• Defining testable acceptance criteria
• Sharing user needs alongside design references

Review a product requirements document, roadmap, or strategy by challenging the assumptions it depends on. Rank potential failures by impact, likelihood, and testing cost, then propose small tests, evidence to gather, and criteria for stopping or changing course.

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

• Challenging critical assumptions before starting a plan
• Preparing a strategy document for executive review
• Choosing low-cost tests to run this week

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

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

• Checking feature assumptions before implementation
• Planning prototype usability tests
• Defining metrics and success thresholds for A/B tests