Leadership & Managing People

Leadership & Managing People

Most first-time managers fail not because they lack technical skills but because they fail to make the transition from individual contributor to someone who achieves results through others. This transition requires rebuilding nearly every instinct that made them effective before.

The Manager's Primary Job

The manager's job is not to do the work — it is to create conditions where the team can do the best work of their lives. This means:

• Providing clear objectives and the context for why they matter
• Removing obstacles that block progress
• Giving feedback that accelerates development
• Protecting the team from unnecessary organizational friction
• Making hiring and exit decisions that maintain team excellence

The managers who fail are the ones who cannot let go of doing the work themselves. Every hour a manager spends doing individual contributor work is an hour not spent on the work that only managers can do.

Feedback: The Operating System of Team Performance

Most managers avoid direct feedback because the short-term discomfort of delivering it feels worse than the long-term cost of not delivering it. The calculation is wrong. The short-term cost of an uncomfortable conversation is hours. The long-term cost of not having it is months of underperformance, team resentment, and eventually a much harder conversation.

The Radical Candor framework:

• Care personally: Do you know what this person is trying to achieve in their career? Do you know what is happening in their life that affects their work? Do they believe you are invested in their success?
• Challenge directly: Are you telling them specifically what is not working and why? Are you giving them the information they need to improve, even when it is uncomfortable?

The two failure modes:

• Ruinous empathy: You care about the person so much that you cannot give them honest feedback. The result is a person who never improves and eventually exits confused about why.
• Obnoxious aggression: You deliver brutally honest feedback without the relationship context that makes it useful. The feedback may be accurate, but the delivery creates defensiveness rather than learning.

The anatomy of useful feedback:

1. State the specific behavior or outcome (not the person's character)
2. Describe the impact — what did this behavior produce?
3. Ask what was going on from their perspective
4. Agree on what changes and by when
5. Follow up

Performance Management as a System

Performance problems almost never appear suddenly. They are preceded by signals — small misses, attitude shifts, quality degradation — that managers often rationalize until the problem becomes severe enough to force action.

Early detection:

• Weekly check-ins with a consistent format (what did you accomplish, what are you working on, what is blocking you?)
• Leading indicators reviewed weekly, not just lagging outcomes monthly
• A willingness to name the pattern early: "I've noticed X three times this month — I want to understand what is happening"

The principle of no surprises: A performance exit should never surprise the employee. If the feedback conversations have happened, the PIP is a formalization of a conversation already in progress. If the PIP surprises the employee, the manager failed at feedback.

Building Psychological Safety

Teams with psychological safety outperform teams without it on virtually every metric — innovation, error correction, and retention — because members are willing to surface problems before they become crises and share ideas before they are fully formed.

What undermines psychological safety:

• A leader who dismisses ideas publicly ("we tried that, it doesn't work")
• A culture where admitting mistakes is associated with punishment
• A hierarchy where only senior members' perspectives are sought
• A pattern where raising problems leads to "why didn't you fix it?"

What builds it:

• Leaders modeling vulnerability ("I was wrong about that, here's what I've changed")
• Explicitly soliciting dissent ("who has a different view on this?")
• Thanking people for raising difficult issues rather than treating the messenger as the problem
• Distinguishing between process failures (systemic, improve the system) and individual negligence (address directly)

The Distinction That Matters: Leading vs Managing

Managing is appropriate when:

• The path is clear and the task is to execute efficiently
• Accountability and coordination need to be established
• Performance standards need to be maintained
• Resources need to be allocated

Leading is appropriate when:

• The path is unclear and the team needs direction under uncertainty
• Organizational change requires people to shift what they believe and how they work
• Motivation needs to be created, not just maintained
• Vision needs to be articulated and made real enough to commit to

Most organizations need both. The error is treating them as the same thing. A brilliant manager who cannot lead fails when the environment changes. A brilliant leader who cannot manage builds an organization that inspires but does not execute.