what-not-to-do-as-product-manager
Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
Best use case
what-not-to-do-as-product-manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
Teams using what-not-to-do-as-product-manager should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/what-not-to-do-as-product-manager/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How what-not-to-do-as-product-manager Compares
| Feature / Agent | what-not-to-do-as-product-manager | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# What Not to Do as a Product Manager - Leadership Anti-Patterns A comprehensive guide outlining common mistakes and counterproductive behaviors that product managers should avoid. Understanding these pitfalls helps PMs build better relationships with teams and create more effective working environments. ## When to Use This Skill - Reflecting on your management practices - Onboarding new product managers - Evaluating team dynamics issues - Improving leadership behaviors - Coaching other product managers - Building healthier team culture ## Anti-Pattern Categories ``` TRUST KILLERS AUTONOMY KILLERS ├── Micromanagement ├── Not trusting decisions ├── Finding mistakes ├── No tools/processes ├── Mind-reading expectations └── Keeping team dependent └── Siloed conversations MORALE KILLERS CULTURE KILLERS ├── No recognition ├── Fear-based environment ├── Unequal treatment ├── Toxic behavior tolerance ├── Ridicule and belittling └── Only few feel heard └── Extra hours expectations ``` ## Quick Reference ``` Stop if you're: □ Checking in multiple times per week "just to see" □ Hunting for mistakes instead of learning □ Expecting mind-reading □ Taking credit, deflecting blame □ Making everything urgent □ Ignoring wins, focusing on gaps □ Messaging after hours to check presence □ Running meetings only you talk in □ Supporting toxic high performers □ Making people feel small Start if you're not: □ Celebrating wins publicly □ Giving private constructive feedback □ Asking for feedback on yourself □ Creating psychological safety □ Providing tools and processes □ Protecting team's focus □ Developing team autonomy □ Addressing toxic behaviors □ Respecting work boundaries □ Listening genuinely ``` --- ## Progressive Disclosure | Topic | File | When to Use | |-------|------|-------------| | Trust & autonomy issues | [context/trust-autonomy-issues.md](context/trust-autonomy-issues.md) | Micromanagement, finding faults, expectations | | Recognition & meetings | [context/recognition-meeting-issues.md](context/recognition-meeting-issues.md) | Ignoring wins, meeting overload, surveillance | | Culture & prioritization | [context/prioritization-culture-issues.md](context/prioritization-culture-issues.md) | Fear-based leadership, toxic behavior, self-audit | ## Warning Signs ``` TEAM SIGNALS TO WATCH FOR: High Turnover: ├── People leaving team/company ├── Especially high performers └── Pattern, not one-offs Silence in Meetings: ├── No one speaks up ├── No pushback on ideas └── Only you talking Hidden Problems: ├── Issues surface late ├── Surprises at deadlines └── Bad news is avoided Disengagement: ├── Minimal effort ├── No discretionary work └── Clock-watching behavior ``` ## Resources - [Radical Candor - Kim Scott](https://www.radicalcandor.com/) - [The Five Dysfunctions of a Team - Patrick Lencioni](https://www.tablegroup.com/books/dysfunctions) - [Turn the Ship Around - David Marquet](https://davidmarquet.com/turn-the-ship-around-book/)
Related Skills
making-product-decisions
Framework for structured product decision-making. Use when facing complex tradeoffs, aligning stakeholders, documenting decisions, or choosing between multiple valid approaches.
visual-cues-cta-psychology
Design effective CTAs using visual attention and gaze psychology principles. Use when designing landing pages, button hierarchies, conversion elements, or optimizing user attention flow through interfaces.
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
value-realization
Analyze if end users discover clear value. Use when evaluating product concepts, analyzing adoption, or uncertain about direction.
user-story-fundamentals
Capture requirements from user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.
typescript-satisfies-operator
Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.
typescript-interface-vs-type
Guides when to use interface vs type in TypeScript. Use this skill when defining object types, extending types, or choosing between interface and type aliases.
typescript-best-practices
Guides TypeScript best practices for type safety, code organization, and maintainability. Use this skill when configuring TypeScript projects, deciding on typing strategies, writing async code, or reviewing TypeScript code quality.
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
trust-psychology
Build trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.
theme-epic-story
Structure product work hierarchically using themes, epics, and stories. Use when organizing backlogs, planning releases, communicating with stakeholders, or breaking down large initiatives into manageable work.
tailwind-v4-configuration
Configure Tailwind CSS v4 with CSS-first approach. Use when installing, migrating from v3, setting up build tools (Vite/PostCSS/CLI), customizing themes with @theme, or configuring plugins.