deanpeters

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

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.

Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.

Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.

Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.

Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation.

Diagnose missing, stale, conflicting, inaccessible, excessive, sensitive, or untrusted context and recommend the next source, package, data, or lifecycle intervention.

Assess whether data is fit for a specific AI product decision across provenance, quality, access, representativeness, consent, privacy, freshness, and operations.

Recommend the product, model, workflow, human, and production evaluations needed for an AI decision, based on behavior, consequences, evidence gaps, and lifecycle stage.

Diagnose AI portfolio imbalance, premature scaling, weak evidence, vendor exposure, and zombie pilots; recommend where to explore, validate, scale, pause, or stop.

Design preventive controls, detection, triage, containment, rollback, communication, investigation, remediation, learning, and reporting for AI incidents.

Turn scattered AI ambition into an evidence-aware product strategy thesis with choices, boundaries, outcomes, assumptions, and next bets. Use when direction or non-goals are unclear.

Assign human decision rights, accountability, review, contribution, escalation, and evidence duties for a material AI product or recurring operating decision.

Measure whether AI operating practices change behavior, decisions, workflows, reuse, outcomes, burden, and risk rather than merely increasing activity.

In this physical variant on brainstorming, participants use their body and inexpensive materials or objects to role-play and mimic interaction with a system, product, or experience.

This hands-on activity allows participants to communicate and document their mental model and how they think about a set of information, creating a logical structure (e.g., relationships, sequences, timing).

A fast way to capture and prioritize stakeholders.

A framework based on “influence channels” that shape and define an organization’s culture.

Visually synthesize and communicate a user’s end-to-end experience through actions, pain points, wins, and opportunities in a phased process.

Focus the power of brainstorming using a structured, visual representation of ideas—pushing you to fill out every box with new ideas.

Generate insights into relationships between concepts in a flexible and engaging way to visualize information.

Develop clear statements about your organization’s future aspirations and present activities.

Select the smallest useful PANT skill, mode, entry path, pressure, and optional companion from a messy product-management request. Use when the correct pressure test or rehearsal is unclear.

Pressure-test a product artifact, argument, or proposal when no specialist PANT scenario fits. Use for general grounding, contradictions, evidence, and readiness; not work clearly served by a specialist.

Pressure-test a product investment business case and rehearse its review. Use for benefits, costs, alternatives, economics, uncertainty, adoption, ownership, and decision conditions; not a whole business model.

Pressure-test a product recommendation for an executive decision and rehearse the review. Use for approval, sponsorship, investment, priority, capacity, or commitment requests; not general roadmap or backlog review.

Pressure-test TAM, SAM, SOM, and other market estimates. Use for market definition, segmentation, provenance, reachability, pricing, conversion, timing, sensitivity, and decision relevance; not generic market research.

Rehearse a consequential product conversation when no specialist PANT scenario fits. Use for realistic stakeholder dialogue, pressure changes, coaching, persuasion, and debrief; not artifact-first review.

Pressure-test a product roadmap and rehearse roadmap review conversations. Use for strategic coherence, outcomes, sequencing, capacity, tradeoffs, dependencies, adoption, and evidence; not sprint or backlog review.

Pressure-test product strategy and rehearse strategy reviews. Use for diagnosis, choices, coherence, differentiation, capabilities, tradeoffs, market assumptions, and measures; not roadmap sequencing or execution plans.

Generate creature acronyms that name PM dysfunctions, blockers, or winning strategies. Use when you want to give your team shared vocabulary for the animals hiding in your product work.