Why? They want a promo code
Why? They think your price is too high
Why? We didn't do market research
Why? We're understaffed
Why? I haven't filled the position
Magic, right?
Well, almost.
7/ The 6th Why
Do you notice what happens as we move through the Whys?
💡 They get specific -> We progress from what happened to what caused it.
💡 And more personal -> Groups narrow to individuals.
There's one more Why & it's uncomfortable.
But that's where the growth is.
8/ Back to our example
Why haven't you filled the position?
❌ Maybe you designed an unattractive role
❌ Perhaps you didn't see the demand coming
❌ Or you are losing people faster than you can hire
These answers are raw & imply something about YOU is causing the issue.
9/ This isn't just about work
I can't get in shape
Why? No time to workout
Why? Day is packed with work
Why? My boss keeps piling on more
Why? B/c I haven't told her no
Why? B/c I can't disappoint her
Why? B/c I need the money
Wait, it's a money issue not a fitness problem?
10/ Now what?
Don't overreact to one mistake. We all make them.
Do watch for patterns of mistakes. These tend to reveal true weaknesses.
• Making decisions vs. debating decisions
• Solving real problems vs. talking about problems
• Moving work forward vs. explaining why work isn't moving
The answers will help you find the source.
The biggest energy leak isn't lazy people.
It's leaders who lack the courage to cut nonsense work.
Your job isn't to say "Yes" to every request. It's to protect your team's focus by saying "No" to work that doesn't move the needle.
• Do what you say you'll do
• Take radical ownership of mistakes
• Be honest even when it's uncomfortable
• Make decisions based on principles, not politics
5 steps to drive great outcomes w/o micromanaging 🧵
1. Set Expectations
Without agreement upfront, oversight will be random & unwelcomed:
-> Goal: What will be accomplished
-> Standards: Quality that signifies done
-> Process: How work will get done
-> Timing: When it will be done
-> Tolerance: How much risk you can handle
2. Call Your Shot
You should vary your level of oversight based on:
-> The criticality of the process
-> You confidence in the person to execute
Tell them how you'll monitor, or if you don't:
-> Whatever you do is a surprise
-> They'll think you're dumping useless work
The telltale signs you're tolerating a toxic culture:
Toxic culture isn't always loud and aggressive.
Sometimes it's quiet and passive: • Avoiding hard conversations • Letting mediocrity slide • Never challenging ideas • Accepting "that's just how it is"
Silent toxicity kills performance just as fast as the loud kind.
The most expensive mistake leaders make?
Thinking a toxic culture will fix itself if they just ignore it long enough.
Spoiler alert: It doesn't get better. It gets worse. And it spreads.
Address it now or your best people will be the first to go.
Your biggest leadership challenge isn't motivating your team. It's keeping them focused.
Every request you accept is a distraction you create.
Here are 5 ways to say No with finesse:
SAYING NO TO YOUR BOSS
• Build a capacity model that ties outcomes to headcount
• Show how new requests impact core results with data
• Use their agreed framework to make the decision for you
Script: "Based on our model, this means X drops by Y%. Worth it?"
SAYING NO TO YOUR TEAM
• Redirect their energy toward solutions, not complaints
• Make them think strategically about trade-offs
• Turn No into a learning opportunity
Script: "What would you stop doing? How does this hit our Q4 goals?"
Brian Armstrong's letter to a Product Manager is actually the perfect blueprint for any people manager.
Why? Your team IS your product.
Let's apply his 5 principles to leading people:
1. UNDERSTAND YOUR TEAM DEEPLY
• Regular 1:1s to understand motivations and pain points
• Map strengths, growth areas, and working preferences
• Listen to what energizes vs. drains each person
• Empathize with career goals and challenges
2. BE METRICS DRIVEN
• Use data to identify team performance patterns
• Make decisions based on evidence, not assumptions
• Measure output quality, collaboration, growth velocity
• Track engagement, development progress, retention risk