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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "what-not-to-do-as-product-manager" with this command: npx skills add flpbalada/my-opencode-config/flpbalada-my-opencode-config-what-not-to-do-as-product-manager

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

TopicFileWhen to Use
Trust & autonomy issuescontext/trust-autonomy-issues.mdMicromanagement, finding faults, expectations
Recognition & meetingscontext/recognition-meeting-issues.mdIgnoring wins, meeting overload, surveillance
Culture & prioritizationcontext/prioritization-culture-issues.mdFear-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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

trust-psychology

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

social-proof-psychology

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

five-whys

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

cognitive-fluency-psychology

No summary provided by upstream source.

Repository SourceNeeds Review