Back to what-not-to-do-as-product-manager

skills/what-not-to-do-as-product-manager/context/trust-autonomy-issues.md

Trust and Autonomy Issues

what-not-to-do-as-product-manager

Document

Anti-patterns that kill team trust and autonomy.

Anti-Pattern Categories Overview

DESTRUCTIVE BEHAVIORS MAP

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

Trust & Respect Issues

Micromanagement

❌ DON'T: Meet multiple times weekly just to check progress
❌ DON'T: Need to know every detail of how work is done
❌ DON'T: Question every decision team members make

WHY IT'S HARMFUL:
├── Signals distrust
├── Slows down delivery
├── Prevents ownership
├── Kills creativity
└── Drives talent away

✓ INSTEAD:
├── Set clear goals and expectations
├── Check in at appropriate intervals
├── Trust your team's expertise
└── Focus on outcomes, not methods

Finding Faults

❌ DON'T: Spend time hunting for mistakes
❌ DON'T: Make team feel constantly under surveillance
❌ DON'T: Act like you're the only one with answers

WHY IT'S HARMFUL:
├── Creates fear of trying new things
├── Kills innovation
├── Damages psychological safety
├── Leads to hiding problems
└── Destroys team confidence

✓ INSTEAD:
├── Focus on learning from mistakes
├── Celebrate calculated risks
├── Create blameless post-mortems
└── Model vulnerability yourself

Mind-Reading Expectations

❌ DON'T: Expect team to know what you need without saying
❌ DON'T: Get frustrated when they "don't get it"

WHY IT'S HARMFUL:
├── Sets people up to fail
├── Creates unnecessary stress
├── Wastes time on misalignment
└── Damages relationships

✓ INSTEAD:
├── Be explicit about expectations
├── Document requirements clearly
├── Ask if your instructions were clear
└── Create feedback loops

Autonomy & Empowerment Issues

No Tools or Processes

❌ DON'T: Withhold tools/processes that help success
❌ DON'T: Create situations where failure is inevitable

WHY IT'S HARMFUL:
├── Creates unfair blame situations
├── Prevents team success
├── Shows lack of investment
└── Breeds resentment

✓ INSTEAD:
├── Provide necessary resources
├── Document processes clearly
├── Train on tools and expectations
└── Remove blockers proactively

Keeping Team Dependent

❌ DON'T: Build systems that require your constant input
❌ DON'T: Hoard knowledge and context
❌ DON'T: Be the bottleneck for all decisions

WHY IT'S HARMFUL:
├── Creates single point of failure
├── Slows everything down
├── Prevents team growth
└── Burns you out

✓ INSTEAD:
├── Build self-service systems
├── Share context broadly
├── Delegate meaningful decisions
└── Create documentation