Credibility comes from showing up for the hard, boring and unpopular work, not just the decisions. It also means knowing when your hands in the work start getting in the way.
“Never ask your team to do something you wouldn't do yourself.”
Common usage
What it means
Your willingness sets the ceiling on theirs.
In practice
Take an occasional shift on the least glamorous work: the ticket queue, the holiday on-call, the documentation nobody wants to write.
“Leaders eat last.”
Simon Sinek. Book of the same name, 2014, drawn from a Marine Corps custom.
What it means
The leader's comfort comes after the team's.
In practice
When there's a late night or a crunch, be there. When there's a perk, it goes to the team first.
“Lead from the front.”
Common military usage
What it means
Model the behavior you expect, visibly and first.
In practice
If you want fast acknowledgments and early escalation, do both yourself where the team can see it.
Go and see
Toyota. Genchi genbutsu, from the Toyota Way 2001, the company's statement of its values. Principle 12 in Jeffrey Liker's book The Toyota Way, 2004.
What it means
Go to where the work happens instead of relying on reports about it.
In practice
Sit with a stakeholder while they use your team's tools. Pair with an engineer on a gnarly bug for an hour.
“Eat your own dog food.”
Common software industry usage
What it means
Use what your team builds. You'll feel the friction your users feel.
In practice
Run your own requests through the same ticket process everyone else uses.
The player-coach balance
A manager's output is the output of the organization under them.
Andy Grove. Paraphrased from High Output Management, 1983.
What it means
Your personal output matters far less than what your team produces. Hands-on leaders are valuable, but the trap is real.
In practice
Being in the trenches means sharing the hard parts, not claiming the fun parts. Before picking up a technical task, ask whether it would grow someone on the team instead.
Not the chief expert
A tech leader’s job is not to be the best engineer, analyst or admin on the team. It’s to build a team where each person is better than you in their own specialty, then point all that expertise in the same direction.
What the job actually is:
- See the big picture and connect the moving pieces across teams.
- Set priorities and sequence the work.
- Shield the team from noise and remove blockers.
- Grow people, play to their strengths and help them work through weaknesses.
- Make the call when experts disagree or when the tradeoff is a business decision, not a technical one.
“If each of us hires people who are smaller than we are, we shall become a company of dwarfs. But if each of us hires people who are bigger than we are, we shall become a company of giants.”
David Ogilvy. Ogilvy on Advertising, 1983.
What it means
Ogilvy reportedly gave new office heads a set of Russian nesting dolls with this message in the smallest one. Leaders who hire to stay on top shrink the organization. A leader's job is to build a team that outperforms any individual, including the leader, and to get it pulling the same direction.
In practice
When hiring, look for the person who will outperform you in their lane. Treat being out-expertised by your team as a sign of success, not a threat.
Multipliers and diminishers
Liz Wiseman. Multipliers: How the Best Leaders Make Everyone Smarter, written with Greg McKeown, 2010.
What it means
Diminishers need to be the smartest person present and end up shutting others down. Multipliers draw out the intelligence of everyone around them.
In practice
In discussions, ask questions first and share your opinion last. Ask "What do you think we should do?" and mean it, then build on the answer rather than replacing it.
“The conductor doesn't make a sound.”
Benjamin Zander. Shortened from a line in his 2008 TED talk. The idea also runs through The Art of Possibility, written with Rosamund Stone Zander, 2000.
What it means
A conductor's power comes from making the musicians powerful. Nobody expects the conductor to be the best violinist.
In practice
Judge your week by how well the orchestra played, not by how many notes you played yourself.
“What got you here won't get you there.”
Marshall Goldsmith. Book of the same name, written with Mark Reiter, 2007.
What it means
Technical excellence often earns the promotion into leadership. Leaning on it after the promotion becomes a liability.
In practice
When you feel the pull to solve it yourself, ask whether that's the best use of the team's leader.
Build on strengths.
Peter Drucker. A theme of The Effective Executive, 1967, not a direct quotation.
What it means
Drucker argued that the leader's task is to align people's strengths so the team's weaknesses stop mattering. Nobody needs to be good at everything.
In practice
Assign work by strengths. Cover gaps with pairing and complementary roles instead of forcing everyone to be well-rounded.
Warning signs you’re competing with your own team:
- You’re the tiebreaker on every technical debate.
- Discussion stops once you share an opinion.
- You review or rewrite most of the work before it ships.
- You feel uneasy when someone knows more than you about something.
- People bring you answers to approve instead of problems to solve.
Stay technical, for the right reason. Keep enough depth to ask sharp questions, spot risk and earn credibility with the team. Use that depth for judgment, not to compete with the experts you hired.
