77 件（deanpeters のリポジトリ） ・ 人気順
概要と使いどころ
Plan who to talk to about a sunset, in what order, and what each conversation must cover. Use when an EOL decision is made and you want the landmines found before the announcement.
日本語の概要は準備中です。原文の説明を表示しています。
Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item. Use when the decision to retire is made and you need the operational plan.
日本語の概要は準備中です。原文の説明を表示しています。
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
日本語の概要は準備中です。原文の説明を表示しています。
Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.
日本語の概要は準備中です。原文の説明を表示しています。
Research a competitive landscape with cited snapshots, a comparison matrix, and so-what implications. Use when a product decision needs competitive grounding, not a market report.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
日本語の概要は準備中です。原文の説明を表示しています。
Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.
日本語の概要は準備中です。原文の説明を表示しています。
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.
日本語の概要は準備中です。原文の説明を表示しています。
Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose where a product sits in its lifecycle and which play fits — extend, replace, or retire. Use when a product is fading and you need the call, not just the worry.
日本語の概要は準備中です。原文の説明を表示しています。
Run a product sunset end to end — decide, align, plan, prepare, announce, close. Use when you need the whole EOL process, not just one artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors to study.
日本語の概要は準備中です。原文の説明を表示しています。
Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool. Use when weighing market entry or when margins erode and nobody can say why.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill. Use when you know something needs researching but not which channel to run.
日本語の概要は準備中です。原文の説明を表示しています。
Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.
日本語の概要は準備中です。原文の説明を表示しています。
Run competitive research like an intelligence agency: eight collection disciplines (OSINT to MASINT), signal-to-inference chains, and fusion. Use when one-source research isn't enough.
日本語の概要は準備中です。原文の説明を表示しています。
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
日本語の概要は準備中です。原文の説明を表示しています。
Decode an incoming message into a structured breakdown separating the literal ask from the job-to-be-done. Use when a loaded Slack ping, email, mandate, or escalation needs a reply.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new — turning PESTEL from a workshop artifact into a radar.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
日本語の概要は準備中です。原文の説明を表示しています。
Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next.
日本語の概要は準備中です。原文の説明を表示しています。