skills/what-not-to-do-as-product-manager/SKILL.md
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.
npx skillsauth add Chris-Maskey/opencode-config what-not-to-do-as-product-managerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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
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
| Topic | File | When to Use | |-------|------|-------------| | Trust & autonomy issues | context/trust-autonomy-issues.md | Micromanagement, finding faults, expectations | | Recognition & meetings | context/recognition-meeting-issues.md | Ignoring wins, meeting overload, surveillance | | Culture & prioritization | context/prioritization-culture-issues.md | Fear-based leadership, toxic behavior, self-audit |
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
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
testing
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.
tools
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.
development
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.