dangerous_animals_of_pm_generator

Purpose

Guide product managers through a 5-question facilitation that maps real jobs, pains, and frustrations onto creature acronyms — then outputs a session-starter prompt for a dedicated exploration. Use this to name the "Dangerous Animals" lurking in your product work (dysfunctions, anti-patterns, blockers) or the "Beneficial Beasts" worth cultivating (strategies, behaviors, mindsets).

This is not a framework document — it's a creative reframing tool. Naming a dysfunction gives your team shared vocabulary to talk about it without pointing fingers.

Key Concepts

The Creature Acronym Pattern

Creature names map PM realities onto animal imagery through acronyms:

Four Acronym Rules

1. Animal nouns only — The acronym must spell an actual animal species noun from the chosen category. FROG, TOAD, NEWT, SALAMANDER, AXOLOTL are valid. CROAK, SLIME, LEAP, AGILE, STINKS are not. If it isn't a creature name, it isn't a creature.
2. Short and punchy — 3–8 letters. Avoid overly complex names, but never sacrifice a great animal noun for brevity.
3. Sentence-like structure — Acronym words should work together grammatically. "Highest Paid Person's Opinion" reads like a phrase, not random initials.
4. Emotional impact — The name should create a vivid, memorable image. ZEbRA and WoLF work because they trigger an instant visual and a gut reaction.

Pains, Gains, and Jobs Framing

The facilitation collects three lenses before generating beasts:

• Jobs — What PM tasks or outcomes are you trying to achieve?
• Pains — What makes those jobs hard?
• Obstacles — What specific behaviors, personalities, or dynamics block you?

These map directly onto which creatures get created and what they represent. Specific inputs produce specific beasts.

Two Beast Modes

• Dangerous Animals Enumeration — Creatures representing dysfunctions, blockers, anti-patterns. Good for retrospectives, team charters, naming what's already happening.
• Beneficial Beasts List — Creatures representing strategies, mindsets, behaviors worth cultivating. Good for culture-building, onboarding, and making positive behaviors memorable.

When to Use This

• Team retrospectives where you need a low-threat way to name dysfunctions
• Stakeholder conversations about PM culture and working agreements
• Personal reflection on what's blocking your best work
• Icebreakers for PM workshops or offsites
• Explaining PM anti-patterns to non-PM audiences with humor

When NOT to Use This

• As a substitute for direct feedback in serious performance conversations
• When the team isn't psychologically safe enough to name dysfunctions honestly
• When you need a formal framework output (use positioning-statement or jobs-to-be-done instead)

---

Application

This interactive skill asks 5 questions one at a time, building a creature profile from your real PM context. Wait for the user's response to each question before moving on.

---

Question 1: Your Jobs

Agent asks: "What jobs or tasks are you, as a product manager, struggling to accomplish?"

Offer 4 enumerated options:

1. Stakeholder alignment — "Getting buy-in across exec, engineering, design, and sales when priorities conflict"
2. Discovery and validation — "Running research to find and validate real customer problems before building"
3. Roadmap prioritization — "Making defensible decisions about what gets built, cut, and deferred"
4. Team delivery — "Keeping cross-functional teams unblocked, coordinated, and shipping"

Or describe your own job in your words.

User response: [Selection or custom]

---

Question 2: Your Pains

Agent asks: "What are the main challenges or pains you face in accomplishing this job?"

Offer 4 enumerated options (adapt based on Q1):

Example options (if Q1 = Stakeholder alignment):

1. HiPPO dynamics — "Decisions driven by the highest-paid person's opinion, not evidence or customer insight"
2. Misaligned incentives — "Different departments optimizing for their own metrics, not shared outcomes"
3. Death by committee — "Too many stakeholders with veto power, too few with accountability"
4. Invisible decisions — "Strategic pivots made in hallways and offsites that surface as done deals"

Example options (if Q1 = Roadmap prioritization):

1. Scope creep — "Features growing beyond original intent, quietly consuming time and quality"
2. Shiny object syndrome — "Executives chasing competitor features instead of customer jobs"
3. Resource illusions — "Commitments made without checking engineering capacity"
4. Technical debt blindness — "Pressure to ship new things while old things quietly break"

Or describe your own pain in your words.

User response: [Selection or custom]

---

Question 3: Specific Obstacles

Agent asks: "Are there specific obstacles, frustrations, or frustrating personalities you encounter that you'd like to name?"

Offer 4 enumerated options:

1. Personality archetypes — "The scope-creeper, the HiPPO, the seagull manager, the ZEbRA"
2. Process bureaucracy — "Approval chains, committee decisions, change management overhead that buries momentum"
3. Engineering-PM friction — "Technical debt blockers, sprint overload, misaligned definition of done"
4. Market and competitive pressure — "External forces constantly reshaping priorities mid-quarter"

Or describe your specific obstacle, frustration, or personality — the more specific, the better the creature.

User response: [Selection or custom]

---

Question 4: Beast Mode

Agent asks: "Would you like to explore a Dangerous Animals Enumeration or a Beneficial Beasts List?"

Offer 2 options:

1. Dangerous Animals Enumeration — "Creatures that name dysfunctions, blockers, and anti-patterns you're navigating right now"
2. Beneficial Beasts List — "Creatures that represent strategies, mindsets, or behaviors worth cultivating in yourself or your team"

User response: [1 or 2]

---

Question 5: Animal Kingdom

Agent asks: "What category of living thing would you like to explore?"

Offer 4 enumerated options:

1. Jungle animals — Lions, gorillas, crocodiles, pythons (power, predation, patience, constriction)
2. Ocean creatures — Sharks, octopus, anglerfish, remora (depth, camouflage, lure, parasitism)
3. Birds — Eagles, seagulls, ostriches, peacocks (vision, noise, avoidance, display)
4. Insects — Ants, bees, wasps, fireflies (swarms, hierarchy, stings, misdirection)

Or name your own category (zoo, deep sea, Arctic, mythological, etc.).

User response: [Selection or custom]

---

Output: Generate the Creatures

After collecting all five responses, generate 4–9 creatures directly using the user's jobs, pains, and obstacles as source material. Do not output a prompt to run elsewhere — name the beasts now.

For each creature, use template.md format:

## [Animal Name] — [ACRONYM expansion]
*[Animal type] | [Beast mode]*

[One sentence describing what this creature represents and what makes it dangerous or beneficial.]
[One sentence describing the specific trigger — when does this creature appear in the PM's world?]

Acronym rules (apply to every creature):

• The acronym must spell an actual animal species noun from the chosen category. Start here — pick the animal, then build the acronym. Never work backwards from a characteristic or action.
  • ✓ Valid: FROG, TOAD, NEWT, SALAMANDER, AXOLOTL, SIREN, AMPHIUMA
  • ✗ Invalid: CROAK, SLIME, LEAP, AGILE, STINKS, Alpine, SPAWN
• Words work together like a phrase, not random initials.
• Name should trigger a vivid, gut-level reaction.

After the creatures: Offer 3 next options:

1. Name more creatures from the same session context
2. Flip to Beneficial Beasts — name the creatures that counter these dangers
3. Export a one-pager naming all creatures (suitable for a team retro or charter)

---

Examples

See examples/sample.md for a full worked conversation and creature output.

Mini excerpt — a creature generated from a stakeholder alignment / ocean creatures session:

## SHaRK — Stakeholder Holding a Roadmap Knife
*Ocean creatures | Dangerous Animals*

Attends every planning meeting, asks probing questions, says nothing is wrong.
Surfaces after the meeting — when you find out the roadmap changed in a
conversation you weren't in.

---

Common Pitfalls

Pitfall 1: Using Characteristics Instead of Animal Nouns

Symptom: CROAK, SLIME, LEAP, AGILE, STINKS, SPAWN — words that describe what an animal does, sounds like, or looks like, rather than what it is.

Consequence: The creature loses its identity. The whole point is that the animal name carries the metaphor — a TOAD already conjures something puffed-up and warty before you read a single letter of the acronym.

Fix: Start with the animal noun, then build the acronym. Ask "what real animal from this category fits this dysfunction?" first. Then make the letters work. Never start from the dysfunction and hunt for matching initials.

---

Pitfall 2: Acronyms That Are Too Forced

Symptom: "PLATYPUS — Product Leader Always Talking About Your Poorly Uncertain Solutions"

Consequence: The creature doesn't stick. Humor requires economy. Longer = forgettable.

Fix: Keep it to 3–6 letters. Cut until the acronym reads like a real phrase, not a scrabble rack.

---

Pitfall 2: Generic Inputs, Generic Beasts

Symptom: Q2 answer is "things are hard" or "we have communication issues"

Consequence: The creature prompt generates vague, universally applicable beasts that don't name your situation.

Fix: Push for specificity in Questions 1–3. "Our CPO reshuffles the roadmap after every board meeting" produces a far more vivid creature than "leadership misalignment."

---

Pitfall 3: Choosing the Wrong Mode

Symptom: Selecting Dangerous Animals when the team needs encouragement; selecting Beneficial Beasts when the team needs to name dysfunction honestly.

Consequence: The output doesn't match the moment.

Fix: Dangerous Animals = naming what's happening now. Beneficial Beasts = building toward what should happen. When in doubt, name the danger first — you can't fix what you can't see.

---

Pitfall 4: Using Creature Names to Avoid Real Conversations

Symptom: Calling someone "the WoLF" in a 1:1 instead of addressing the behavior directly.

Consequence: Humor creates distance. Sometimes distance helps open a conversation; sometimes it replaces one.

Fix: Use creature vocabulary to open conversations, not close them. "We seem to have a WoLF pattern right now — can we talk about what's driving it?"

---

References

Related Skills

• skills/jobs-to-be-done/SKILL.md — Informs the pains, gains, and jobs framing used in Questions 1–3
• skills/proto-persona/SKILL.md — Defines the PM persona that owns these challenges
• skills/discovery-process/SKILL.md — Surface-level obstacles here often point to deeper discovery gaps

External Frameworks

• Clayton Christensen, Jobs to Be Done — Pains/gains/jobs framing used in the facilitation intake
• Geoffrey Moore, Crossing the Chasm — Origin of HiPPO as a PM term of art

Provenance

• Adapted from prompts/Dangerous Animals of Product Management Beast Generator.md in https://github.com/deanpeters/product-manager-prompts
• Created by Dean Peters, September 2024. CC BY-NC-SA 4.0 (see repo LICENSE and LICENSING.md); commercial use requires expressed written permission from Dean Peters.

---

Skill type: Interactive Folder: skills/dangerous_animals_of_pm_generator/ Dependencies: Standalone — no required skill dependencies