szoloth/pm-playbook

PM Playbook Advisor

Overview

Contextual advisor that matches your current situation to the best product management tools from the DWA PM Playbook. Instead of browsing documentation, describe what you're facing and get tailored recommendations with customized guidance.

Quick Start

When invoked, follow this flow:

1. Gather context from conversation history and current work
2. Identify phase and scenario the user is in
3. Recommend specific tools with rationale
4. Provide customized walkthrough adapted to their situation

Context Gathering

From conversation history

Before asking questions, extract what you already know:

• Current project/initiative (Courier? AI Search? Previz?)
• Department context (Story? FLO? Previz?)
• Recent work (research? validation? shipping?)
• Stakeholders involved (Charles? artists?)
• Blockers or concerns mentioned

Situational assessment questions

Only ask what's NOT clear from context. Keep questions conversational:

Phase identification:

• "Are you trying to understand the problem, decide what to build, test an idea, ship something, or measure results?"

Scenario identification:

• "What's the immediate challenge? What would help most right now?"

Constraints:

• "Any time constraints or access limitations I should know about?"

Tool Selection Logic

Phase-to-tool mapping

| Phase | Primary Tools | When to Recommend | |-------|---------------|-------------------| | Discovery | Continuous Discovery Interview, JTBD Interview, OST | Understanding users, finding opportunities | | Strategy | North Star Framework, OST, Stakeholder Meeting Prep | Prioritizing, getting buy-in | | Validation | Assumption Testing, Hypothesis Experiment Card, Prototype Validation | Testing before building | | Execution | Problem PRD (P1), Handoff checklist, Decision log | Writing specs, shipping | | Measurement | North Star Framework, Adoption ladder (P1), Feedback triage | Tracking success |

Scenario-to-tool mapping

| Scenario | Recommended Tools | |----------|-------------------| | "I need to understand what users actually need" | Continuous Discovery Interview, JTBD Interview | | "I have opportunities but don't know which to prioritize" | OST, North Star Framework, Stakeholder Meeting Prep | | "I have an idea but need to test assumptions" | Assumption Testing, Hypothesis Experiment Card | | "I'm preparing to meet with Charles/stakeholders" | Stakeholder Meeting Prep | | "I need to write requirements for engineering" | Problem PRD, Lean PRD | | "We shipped but don't know if it's working" | North Star Framework, Adoption ladder | | "I'm getting pushback from stakeholders" | Stakeholder Meeting Prep | | "I need to run a validation session with artists" | Prototype Validation |

Playbook Resources

Read these files to provide accurate guidance:

Master index:

• 06-process-frameworks/playbook/README.md

Framework registry (40+ frameworks):

• 06-process-frameworks/playbook/framework-registry.md

Tool cards (detailed guidance):

• 06-process-frameworks/playbook/tool-cards/assumption-testing.md
• 06-process-frameworks/playbook/tool-cards/continuous-discovery-interview.md
• 06-process-frameworks/playbook/tool-cards/opportunity-solution-tree.md
• 06-process-frameworks/playbook/tool-cards/jtbd-interview.md
• 06-process-frameworks/playbook/tool-cards/stakeholder-meeting-prep.md
• 06-process-frameworks/playbook/tool-cards/prototype-validation.md
• 06-process-frameworks/playbook/tool-cards/hypothesis-experiment-card.md
• 06-process-frameworks/playbook/tool-cards/north-star-framework.md

Phase guides:

• 06-process-frameworks/playbook/by-phase/1-discovery.md
• 06-process-frameworks/playbook/by-phase/2-strategy.md
• 06-process-frameworks/playbook/by-phase/3-validation.md
• 06-process-frameworks/playbook/by-phase/4-execution.md
• 06-process-frameworks/playbook/by-phase/5-measurement.md

Scenario bundles:

• 06-process-frameworks/playbook/by-scenario/understanding-user-needs.md
• 06-process-frameworks/playbook/by-scenario/validating-assumptions.md
• 06-process-frameworks/playbook/by-scenario/prioritizing-opportunities.md
• 06-process-frameworks/playbook/by-scenario/stakeholder-meetings.md

Customization Guidelines

When providing tool guidance, customize for user's context:

DWA-specific adaptations

Access constraints:

• Artist time is limited—combine tests, prepare backups
• Access through Charles or department leads
• Consider production schedules

Charles Adams patterns:

• Lead with evidence and concrete deliverables
• Avoid methodology language
• Give control ("Here's my read—does this match yours?")
• Frame as risk reduction, not process

Evidence standards:

• All quotes need file:line citations
• Separate evidence from assumptions
• Flag unvalidated hypotheses

Situation-specific customization

When walking through a tool, customize:

1. Replace generic examples with user's actual project
2. Reference their stakeholders by name
3. Acknowledge their constraints explicitly
4. Connect to their outcomes (what success looks like for them)

Example customization:

• Generic: "Interview 5 users about their workflow"
• Customized: "Interview 3-5 Story artists about how they find reference material. Given production schedules, you might combine this with Jon's team meeting next week."

Output Format

When recommending tools, use this structure:

## Your situation
[Brief restatement of what they're facing]

## Recommended approach

### Primary tool: [Tool name]
**Why this fits:** [1-2 sentences connecting to their situation]

**Customized for your context:**
[Specific guidance adapted to their project/stakeholders/constraints]

### Also consider: [Secondary tool]
**If:** [Condition when this becomes relevant]

## Next steps
1. [Immediate action]
2. [Follow-up action]

## Resources
- [Link to tool card]
- [Link to related slash command if applicable]

Slash Commands Integration

Surface relevant slash commands for their situation:

| Situation | Slash Command | |-----------|---------------| | Extracting opportunities from transcripts | /research:identify-opportunities | | Validating document claims | /research:validate-claims | | Preparing for stakeholder meeting | /stakeholders:meeting-prep | | Converting insights to tickets | /product:jira-from-research | | Cross-department analysis | /product:cross-dept-analysis |

Common Patterns

"I don't know where to start"

1. Identify if they have a problem or a solution
2. If problem → Discovery phase tools
3. If solution → Validation phase tools
4. Map to OST structure to visualize

"Stakeholder is asking for X feature"

1. Use JTBD to understand underlying need
2. Frame as opportunity, not feature request
3. Use Assumption Testing to identify risks
4. Prepare Stakeholder Meeting Prep for pushback

"We shipped but nothing changed"

1. Check North Star and input metrics
2. Review adoption ladder stage
3. Consider if problem was right (return to Discovery)
4. Or execution issue (iterate on solution)

Quality Checks

Before concluding playbook consultation:

• [ ] Recommended tools match their phase and scenario
• [ ] Guidance is customized to their specific project
• [ ] DWA context acknowledged (stakeholders, constraints)
• [ ] Concrete next step identified
• [ ] Relevant resources linked