Leadership Handbook

There is a version of leadership that gets described in job postings, performance reviews, and company all-hands meetings. And then there is the actual job. They overlap — but the gap between them is where most new leaders get surprised.

When someone is promoted into a leadership role, the announcement typically emphasizes vision, impact, and opportunity. The congratulations flow in. What doesn't get said clearly: the thing you were rewarded for doing well is no longer your primary job. You are now responsible for creating the conditions in which other people do that thing.

A promotion into leadership is the organization saying: we trust you to make decisions and own outcomes in ways you haven't owned them before. That transfer comes with two things that are rarely stated explicitly. First, your manager is still accountable for everything you do — if you fail, it is on them. They are taking on risk and investing in you. Second, you are starting with training wheels, not finishing the race. The work gets harder, not easier. The expectation is that those wheels come off — that you grow into the areas where you're not yet ready.

This reframes what the title actually means. It is not a reward for past performance. It is a bet on future development, made by someone who has decided the bet is worth the risk. Leaders who treat promotion as arrival — as the end of proving themselves — misunderstand what they've been given.

There is a related shift that catches most new leaders off-guard: the safety net disappears. Up to the point of promotion, most career systems are designed to guide your development and catch you when you stumble. After it, that system stops working in your favor. Retire any remaining expectation that the organization is designed to set you up for success. You are now one of the people responsible for setting the organization, your team, and your manager up for success. Often abruptly, you're expected to align the pieces around you — rather than waiting for the pieces to be aligned for you. ↳ Will Larson — 'Staff Engineer: Leadership Beyond the Management Track' (2021)

Individual contribution is visible and measurable in real time. You write the code, close the deal, design the interface — and you can see the result. Leadership is different. Your output is other people's output. Your decisions create conditions that manifest as results weeks or months later, often through chains of cause and effect you can't fully trace.

This is disorienting for high performers. The feedback loops that told you how you were doing — immediate, concrete, yours — disappear. They are replaced by slower, more ambiguous signals that are harder to interpret and easier to rationalize. Skilled individual contributors often struggle in their first leadership role not because they lack intelligence or dedication, but because the job requires a fundamentally different relationship with accountability.

The research on this point is worth knowing. Intelligence — the single most-studied predictor of leadership effectiveness — accounts for about 4% of the variance in outcomes. Personal qualities, behaviors, and traits explain relatively little. What explains far more: the quality of the relationship between leader and group, the clarity of shared goals, and whether people feel the leader is genuinely acting on the group's behalf. The ultimate proof of leadership is not what the leader is like or does — it is what the people they lead do. Without followership, there is no leadership; there is only a title. ↳ Haslam, Alvesson & Reicher — 'Zombie Leadership' (The Leadership Quarterly, 2024)

One of the most persistent confusions in the early stages of a leadership role is conflating management and leadership. They are related but distinct. Leadership is setting a vision and bringing people toward it — inspiring, aligning, making the 'why' behind goals clear. Management is something different: the act of making the people around you better. Figuring out who they are, what they're good at, what motivates them, and then aligning the work with their role and their growth areas.

You can be a leader without being a manager. You can be a manager without being a strong leader. Sometimes both live in the same person. Often they don't. Understanding which role you're actually in — and which one you're being evaluated on — prevents a great deal of misdirected effort.

Strip it down further and the manager's job is exactly two things: deliver an aligned result, and enable the success of the people on your team. Everything else — the frameworks, the models, the leadership philosophies — is in service of those two things or it's noise. ↳ Russ Laraway — 'Stop Overcomplicating It' (First Round Review) / 'When They Win, You Win'

The work of leadership can be roughly organized into three categories that rarely appear in job descriptions: decisions, context, and relationships. Leaders make some decisions directly, but more important they shape the conditions under which hundreds of decisions get made by others. They provide the context — the why — that enables autonomous good judgment at scale. And almost everything hard in leadership happens through relationships: feedback, alignment, retention, navigating tension upward. Everything else is in service of these three things.

• You will spend a significant portion of your time in meetings that don't feel productive — and your job is often to make them more productive, not to escape them.
• The people who report to you will hold back information from you — sometimes intentionally, more often because they don't know what you need to know. Creating conditions where information flows upward is an active management task.
• Your emotional state is legible to your team in ways you cannot fully control. If you're anxious, they will be anxious. If you're disengaged, they will disengage. This is not unfair — it is the structural reality of the role.
• Some of the best decisions you make will be unpopular. Some popular decisions will be wrong. Learning to distinguish between the two — and to make good decisions anyway — is a core leadership skill.
• You are now managing up, managing across, and managing down simultaneously. These three directions often have conflicting requirements, and you will regularly have to disappoint someone.
• When leadership makes a decision you disagree with, your job is to implement it as if you made it yourself — not to signal to your team that you're on their side against the organization. Distancing from decisions you're responsible for implementing damages the chain of authority you depend on.
• People and roles evolve at different rates. What you signed up for in year one may look very different in year five — the job grows harder and more complex as the organization matures. Leaders who succeed long-term are those who keep growing with it.

Most new leaders are surprised by how isolating the role can be. You are no longer a peer to the people you manage. You are not fully a peer to the leaders above you. The social fabric of your work life has shifted, and you may not have built relationships at the new level yet. This is normal. It is also something you need to address intentionally, because leaders without peer support make worse decisions and burn out faster.

The isolation can be managed. As you build trust up and down the chain, you will develop a small number of people you can think out loud with, vent to, and test ideas against. Not everyone is a candidate for this — some people lack the maturity to maintain a close relationship with their boss without it affecting how they work. Take it slowly. But the goal is to reach a state where you have trusted agents at multiple levels: people who keep you informed, help you stay calibrated, and give you someone to laugh with in hard stretches. ↳ Jocko Willink — 'Leadership Strategy and Tactics: Field Manual' (St. Martin's Press, 2023)

Many new leaders feel like they're not quite ready for the role — that they're not fully qualified, and that someone might figure it out. This anxiety has a name: imposter syndrome. It is worth reframing. The leader who feels unready is the leader who prepares. They study, they ask questions, they think carefully before acting. The opposite — the leader who is completely certain they're ready, who doesn't feel the need to prepare or listen — is the one who destroys teams.

The anxiety is not a sign of unsuitability. It is a sign of appropriate humility about a genuinely hard job. The goal is not to eliminate it but to use it productively: as a reason to prepare more thoroughly, ask better questions, and treat the role with the seriousness it deserves. ↳ Jocko Willink — 'Leadership Strategy and Tactics: Field Manual' (St. Martin's Press, 2023)

If you are reading this before stepping into a leadership role, consider these questions carefully:

• Do you want the actual job — not the title, not the salary, not the status, but the work of developing people, navigating ambiguity, and being accountable for things you can't directly control?
• Are you willing to be less visibly competent in the short term while you develop new skills?
• Do you have the emotional capacity to hold other people's difficulties without taking them on as your own?
• Are you internally driven — motivated by the work itself and the impact you can have — or primarily by external recognition? External motivation produces different decisions under pressure.
• Do you have enough support — mentors, peers, a relationship with your own manager — to navigate what's coming?

None of these questions have wrong answers. Some excellent people should not be in leadership roles — not because they aren't capable, but because the job is genuinely not what they want. Knowing that before you commit is valuable.

Organizations that understand this build dual tracks: separate growth paths for individual contributors and people leaders, so that seniority and compensation don't depend on taking a management role. If your organization doesn't have one, you can still make the choice explicitly. The traditional link between promotion and management responsibility is a convention, not a law. ↳ Google Project Oxygen / BetterUp — betterup.com/blog/project-oxygen

A related trap once you are in the role: Proof of Worth tasks. Because leadership is a generalist role that works alongside specialist functions, many cultures — implicitly or explicitly — require leaders to perform non-core tasks just to demonstrate they deserve to be in the room: writing SQL queries, taking detailed notes, answering support tickets, sitting in on every call. Early in a role, some of this is useful context-building. Continued indefinitely, it consumes the time that should go to the highest-leverage work only the leader can do. The question to ask regularly: is this task something I'm doing because it provides genuine leverage, or because I feel I need to prove I've earned my seat? ↳ Shreyas Doshi — 'Advanced time management principles' (x.com/shreyas)

Authority is the formal right to make decisions and direct others. Influence is the actual ability to shape what people do. New leaders often confuse these — assuming that the title gives them the second when it only grants the first.

Authority is assigned. It comes with the role. But authority alone does not make people want to do good work, exercise good judgment, bring you problems early, or stay when they have other options. Those things require influence — and influence has to be earned.

The distinction matters at a fundamental level. Leadership is less about power *over* followers and more about power *through* them — getting people to want to contribute, rather than making them. A leader who relies primarily on compliance produces the minimum required. A leader whose team is genuinely motivated by the work and the direction produces something that cannot be extracted by authority alone. ↳ Turner (2005) — via Haslam, Alvesson & Reicher, 'Zombie Leadership' (The Leadership Quarterly, 2024)

Authority can compel compliance. It cannot compel engagement. A leader who relies primarily on authority gets the minimum required output from people who are waiting to see if they actually have to follow through. This produces mediocre results and is exhausting for everyone involved.

Authority is most useful when decisions need to be made quickly, when there is genuine disagreement that cannot be resolved by consensus, or when someone is not meeting a clear expectation and needs to understand there are consequences. Using it constantly — or as a substitute for building relationships — signals something is wrong with how leadership is being exercised. General Dan Caine, a career military leader, recounted that he gave approximately two direct orders across his entire 33-year career. The rest was persuasion, example, and earned credibility. ↳ General Dan Caine — via Ryan Holiday, '24 Leadership Principles' (ryanholiday.net)

There is also a subtler problem: authority changes the person who holds it. When people are put into positions of power, three things happen reliably. They focus more on their own needs and concerns. They focus less on the needs and concerns of others. And they begin to act as if the rules don't apply to them. This isn't a character flaw — it is a documented pattern that affects almost everyone under conditions of persistent authority. The leader who is aware of this tendency, and actively works against it, is the exception. ↳ Bob Sutton — 'Fight Like You're Right, Listen Like You're Wrong' (First Round Review)

Influence accumulates through consistent behavior over time. The primary sources are competence, character, and care.

Competence

People follow leaders who demonstrate sound judgment — not necessarily technical expertise in the team's work, but the ability to frame problems clearly, make reasonable decisions under uncertainty, and course-correct when wrong. Competence in the relevant domain matters early on; competence in judgment and decision-making matters throughout.

Character

Does the leader say what they mean? Do they do what they say they'll do? Do they treat people consistently, regardless of who is watching? Character is assessed through patterns, not statements. 'I have an open door' means nothing if people who walk through it get subtle pushback for raising problems.

Care

People extend trust to leaders who demonstrate genuine interest in their success and wellbeing — not performative interest, but the kind that shows up in how feedback is delivered, how workload is managed, how recognition is given, and whether the leader advocates for their team in rooms the team isn't in.

Much of what leaders need to accomplish requires influencing people they have no authority over: peers in other functions, senior leaders, external partners. This is where formal authority is entirely useless and influence is the only currency.

Building influence laterally requires the same foundations — competence, character, care — but the relationship-building is more deliberate. People who lead well across organizational lines understand what matters to the other person, invest in relationships before they need something, and create situations where both parties benefit from cooperation.

The mechanics matter. Imparting energy is often more important than sharing information. People like you when they feel liked by you — when you greet them in a way that signals you're genuinely glad to see them, when you listen with enough focus to ask specific follow-up questions rather than nodding while mentally elsewhere. Acknowledge your own fallibility honestly. Offer unvarnished opinions rather than managed ones — the people worth building relationships with can tell the difference. And end every meeting on a high note: the feeling you leave someone with is what they'll remember about you. ↳ Chris Fralic — 'How to Become Insanely Well-Connected' (First Round Review)

Before they earn a title, aspiring leaders often make one of two opposite mistakes with their opinions. The first: stating a position and then immediately backing down at the first sign of pushback — changing their view before any new information has been shared. This looks like a lack of conviction, and senior leaders notice it.

The second mistake is the mirror image: holding positions so rigidly that no amount of new information or argument moves them. This looks like an inability to function on an executive team where trade-offs require genuine give-and-take.

The calibration that earns trust is different from both: form a view, be willing to defend it, and change it when the argument — not the social pressure — warrants it.

Effective leaders don't split the world into a binary of leaders and followers — they move in and out of both roles depending on what the situation requires. Until you learn to follow genuinely, you can only lead through others' resignation rather than real alignment. The people around you will comply rather than commit, and the difference shows up in every hard moment.

The most effective leaders spend more time following than leading. In practice this means: be clear about your true priorities and don't dilute yourself across everything. For things you disagree with only slightly, let someone else lead and give them your genuine support. A useful test: 'Will this matter to me in six months?' If not, follow. Give your support quickly to other leaders working to make improvements — someone trustworthy leading a project will almost always find a good outcome, even if their starting approach isn't yours. Make your feedback explicitly non-blocking. If you find yourself uncomfortable letting a trusted person move forward, examine whether the issue is them or your own difficulty ceding control. ↳ Will Larson — 'Staff Engineer: Leadership Beyond the Management Track' (2021)

Most people have worked with someone who thinks they're never wrong — who leans in, dominates the debate, and continues until their view wins or time runs out. They are often right. But right in a way that empties the room: over time, what they interpret as persuasion is the resignation of their colleagues.

The shift required is from winning arguments to reaching understanding. This means going into a meeting not with the goal of getting agreement but with the goal of agreeing on the problem, understanding what people in the room actually need, and identifying what has to happen before alignment is possible. Three disciplines help:

• Listen through questions. Ask three good questions before sharing your perspective. Questions asked with genuine intent open up a conversation, create safety for others to contribute, and free the answerer from the obligation to defend their position. They sharpen the conversation rather than narrowing it.
• Define the purpose. In any discussion that feels stuck or circular, pause and confirm what the group is actually trying to decide. 'Just to check — our goal here is to decide whether to postpone the launch by two weeks?' Named purpose often dissolves an argument before it begins.
• Read the room. If the room is ready to make a decision, land it. If the room isn't ready, don't force it. Forcing a decision the room isn't ready for produces the appearance of alignment and none of the reality. ↳ Will Larson — 'Staff Engineer: Leadership Beyond the Management Track' (2021)

Hiring feels like a search problem — find the best available candidate for the role. It is actually a series of harder decisions that most hiring processes aren't designed to surface: what the role actually requires, what 'best' means in this specific context, and how much weight to give different kinds of evidence.

The most common hiring mistake happens before any candidate is considered: the role isn't clearly defined. Not just the job description — the actual decisions the person will make, the problems they will need to solve, and what success looks like in the first year. Without this, every candidate evaluation becomes impressionistic and the hire is essentially random.

• What are the three or four decisions this person will make most frequently, and what does good judgment in those decisions look like?
• What does this person need to accomplish in the first 90 days to be considered on track?
• What is the hardest part of this role, and what does the person need to handle it?
• What failure modes are you most worried about, and what in a candidate's history should make you confident or nervous?
• What strengths do we not already have on the team — and are we hiring to complement the team or replicate it?

Interviews are a poor predictor of job performance. This is well documented and consistently ignored. They are systematically biased toward confident, articulate people who are good at interviews, which is not the same as being good at the job. Work samples, structured references, and past-behavior interviews are more predictive.

The best interview questions are specific enough to resist a prepared answer, and open enough to show how someone thinks. The most revealing questions ask about the past, not the hypothetical:

• Among the people you've worked with, who do you most admire and why? — reveals values and what they notice in others.
• What do you want to do differently in your next role? — reveals honest self-assessment and what they learned.
• Tell me about a time you took unexpected initiative. Then: tell me about another. — the follow-up matters; a pattern is harder to manufacture.
• When was the last time you changed your mind about something important? — reveals intellectual honesty and whether they update on evidence.
• Why shouldn't we hire you? — tests self-awareness and candor under pressure.
• What have I not asked you that I should have?

Most reference calls are useless because they are conducted poorly. References become valuable when you ask specific questions about specific situations, probe for detail when answers are vague, and pay attention to hesitations and what isn't said. The most informative question is often: 'What would you say this person's growth areas are?' — then stay quiet until you get a real answer. You are also looking for rate of improvement: not just where someone is now, but the direction they're moving.

• Similarity bias: preferring candidates who remind you of yourself in ways that may not be relevant.
• Halo effect: letting one positive signal overwhelm the overall evaluation.
• Affinity bias: rating candidates higher when you liked the conversation, independent of their answers.
• Overconfidence in gut feel: treating a strong intuition as evidence rather than a signal to investigate further.

When interviewers disagree significantly, that is information — not a problem to be resolved by the most senior person in the room. Understand what each person saw that others didn't, and why.

The question is not 'Is this person good?' but 'Given what we know, what is the probability this person succeeds in this role, in this organization, at this time?' A genuinely strong candidate who is a poor fit for the specific context is a worse hire than a strong candidate who fits well.

Hiring is not one-directional. A candidate with any seniority or options is evaluating the organization at the same time the organization evaluates them — and the 'do you have any questions for us?' portion of the interview is where they do it. Strong candidates increasingly ask pointed questions at this stage, and how a hiring manager answers them shapes the decision as much as anything from earlier in the process. It's worth knowing what these questions actually test, because you will be asked them:

• 'Why is this role open?' Growth, replacement, and restructuring are all normal answers. A pause before the answer, or a version that avoids the direct question, tells a candidate there's a story underneath — and invites a harder follow-up.
• 'What's something the team is genuinely bad at?' A polished non-answer — the humblebrag disguised as a weakness — signals practiced evasion. A specific, honest answer signals a team that can look at itself clearly, which is exactly what a strong candidate is trying to assess.
• 'How does the team handle disagreement with a decision from leadership?' Vague reassurance about alignment reads as either dishonest or unreflective. A described process — where it's raised, what happens, whether reasons are given even when decisions don't change — reads as a team that actually functions.
• 'What does success look like at six months, and what does failure look like?' The failure half of this question is usually unscripted, which means your answer reveals what failure mode you've actually seen in this role before — whether the role is ambiguous, political, or genuinely hard in a specific way.

None of this means fabricating comfortable answers. It means recognizing that hesitation, deflection, and polish read as clearly to a candidate as they would to you if the roles were reversed — and that the honest answer, even when it's not flattering, is usually the one that earns trust rather than costs it. ↳ Louise Deason — 'Nine Questions I Now Ask in Interviews' (louisedeason.substack.com)

The first 90 days of a new hire are the highest-leverage period for setting someone up for long-term success. They are also the period that most organizations and leaders treat as primarily an HR administrative function. The result is predictable: new hires who take far too long to become effective, and who form lasting impressions that are hard to change.

New employees need three things in their first weeks: clarity about what success looks like, enough context to make good decisions, and relationships with the people they'll need to work with. Most onboarding programs deliver compliance training and org chart orientation. These are not the same things.

Clarity

What are the specific outcomes expected in the first 30, 60, and 90 days? What decisions does the new hire own, and which require consultation? Without explicit answers, new hires either over-step or under-perform.

Context

Context means understanding why things work the way they do: the history behind current decisions, the relationships between teams, the unwritten rules about how decisions actually get made. Leaders can accelerate this by sharing it deliberately — including the things that won't appear in any document.

Relationships

The speed at which a new hire becomes effective is largely determined by the quality of their relationships with peers and cross-functional partners. Leaders who facilitate deliberate introductions — with context about why each relationship matters — compress the time to effectiveness significantly.

• Meeting weekly (or more frequently) in the first month, with enough time to surface confusion before it becomes a problem.
• Sharing a guide to how you work — your communication preferences, what you care about, where you tend to be wrong. This builds psychological safety faster than anything else.
• Actively introducing the new hire to key stakeholders, not just copying them on an announcement email.
• Sharing context about organizational dynamics, politics, and history that would take the new hire months to learn otherwise.
• Giving feedback early and specifically — not waiting for the 90-day review.
• Asking directly: what's confusing? What are you missing? What would make the next 30 days more productive?

One of the manager responsibilities most often deferred is career development. Most managers treat it as a later-stage conversation, after the person has proven themselves. This is backwards.

When someone joins, they have ambitions. If those ambitions go unacknowledged, people assume the organization doesn't care about them and begin looking elsewhere within months. A brief, genuine conversation in the first weeks — what do you want to learn here, where do you want to be in two years — signals that the manager sees them as a person with a trajectory, not a function to be filled. That signal has outsized retention value.

Performance problems don't usually arrive as emergencies. They arrive as small signals: a deliverable that's late, work below the usual standard, a change in someone's engagement or behavior. What leaders do in response to those early signals determines whether the situation improves, stabilizes, or deteriorates.

The most common response to early performance signals is avoidance. Leaders tell themselves they need more data. They're worried about being wrong. They don't want to damage the relationship. These are understandable instincts. They are also the primary reason that manageable performance problems become terminations.

Early feedback — given promptly, specifically, and with genuine care — is one of the highest-leverage things a leader can do. It respects the person enough to give them accurate information about how they're doing. And it means that if the performance problem continues, everyone involved has been treated fairly.

• Does the person know what's expected? Sometimes underperformance is a clarity problem, not a capability or motivation problem.
• Do they have what they need to meet expectations? Resources, information, authority, support from other teams?
• Do they know there's a problem? Leaders sometimes assume feedback has been given clearly when it has been given only obliquely.
• Is something happening outside work? A person in the middle of a difficult personal situation may need a different kind of support.
• Has something changed at work? A role change, a team change, a loss of a colleague they depended on — these affect performance in ways that aren't always visible.

Most leaders conflate feedback and coaching. Feedback tells someone what happened and what needs to change. Coaching helps them figure out how to change it — and builds the capability to keep improving without the manager in the room. A team that can only perform well with active feedback is fragile. A team that has internalized how to think about its own performance is robust.

What coaching actually looks like

Coaching is primarily questioning, not advising. When someone brings a problem, the coaching response is not to solve it — it is to ask questions that help them solve it themselves: What do you see as the root cause? What options have you considered? What are the trade-offs? What's your instinct? The leader's job is to sharpen the thinking, not to replace it.

Two specific questions make this discipline concrete rather than aspirational. First, when someone gives you their initial answer, resist the urge to act on it — ask 'And what else?' The first answer is rarely the real one; it's the socially acceptable one, or the first thing that came to mind. Asking again, once or twice, surfaces what's actually going on and often produces the person's own best thinking, which they wouldn't have reached if you'd jumped in after the first response.

Second, when someone comes to you visibly stressed or stuck, resist assuming what kind of help they need. Ask 'How can I help?' rather than immediately offering advice, taking over the task, or reassuring them. Often what they need is simply to be heard, or to think out loud — not a solution. Assuming the wrong kind of help wastes your time and can leave the person feeling more managed, not less stuck. ↳ Michael Bungay Stanier — 'The Coaching Habit' (Box of Crayons Press, 2016)

The corollary: when someone makes a costly mistake, the first question is not how to discipline them but what they learned. IBM CEO Tom Watson once called an executive into his office after a venture had lost ten million dollars. The executive assumed he was being fired. Watson reportedly told him: 'Fired? I just spent ten million dollars educating you. I want to be sure you learned the right lessons.' A mistake that has already been made is sunk cost. The only question is whether it produces capability going forward. ↳ Ryan Holiday — '24 Leadership Principles' (ryanholiday.net)

• Be specific about what you've observed, not general about your impression. 'The last three reports were submitted late and contained errors' is actionable. 'Your work quality has been off' is not.
• Ask before you explain. 'I've noticed X. What's your read on it?' often surfaces information you didn't have.
• Check whether the person is in a headspace to hear feedback before delivering it — asking first makes it more likely to land.
• Be clear about what needs to change and by when. Vague aspirations don't give people enough to work with.
• Follow up. A performance conversation with no follow-up signals you weren't serious.

How feedback is framed determines whether it gets heard. A critique delivered as accusation produces defensiveness. The same substance delivered as a question about what the leader could have provided produces collaboration. Compare:

• Instead of 'You didn't get this done on time' — try 'What support could I have given you so we could have finished this on time?'
• Instead of 'You didn't understand the objective' — try 'I don't think I explained the objective clearly enough. What was your read on it?'
• Instead of 'Your communication with the client was off' — try 'I think I've let some standards slip here, and that's on me. Here's what needs to change going forward.'

This is not a technique for avoiding accountability. It is the opposite: a genuine recognition that most underperformance has a setup dimension — something the leader failed to provide. Owning that makes the feedback land. And more often than it looks, the ownership is accurate. ↳ Jocko Willink — 'Leadership Strategy and Tactics: Field Manual' (St. Martin's Press, 2023)

Most feedback fails not because it's unwelcome but because it's vague, late, or unverified. Three rules that address all three problems:

• Immediate. As soon as someone steps off the path or veers into dangerous territory, let them know. Delayed feedback loses the moment and loses specificity.
• Granular. Give specific examples of the mistake and how things would look different if the behavior changed. 'Your communication style ' needs work' tells someone nothing. 'In Tuesday's meeting, you interrupted the client twice before they finished their sentence, and they disengaged for the rest of the call' tells them exactly what to change.
• Verified. Have the person repeat back what they heard until what they're saying matches what you mean. Too often people believe they know what's expected of them — and still fail to meet expectations. The gap is almost always in the translation, not the intent. ↳ Michael Lopp (Rands) — First Round Review

The most common reason feedback conversations fail is not cowardice or unclear language — it is self-expression. The feedback giver has been sitting with frustration, and when finally given the opening, they use it to vent. They describe the damage in detail. They want the person to understand how they felt. They want acknowledgment of wrongdoing. At the end of the conversation, the recipient is defensive and demoralized — and has no clear idea what they should do differently.

A feedback conversation is a sales conversation. Its purpose is behavior change — not catharsis, not having the last word, not teaching someone a lesson. Before speaking, apply one filter: Is this strategy or self-expression? Strategy means only saying the things genuinely likely to move the person toward change. Self-expression is everything else. Strategy is roughly 10% of what you initially want to say.

Practically: process the emotion before entering the room, not during. Talk to a trusted person beforehand. Come in with neutral or positive energy — your recipient will be more open when they believe your intent is good, and most people cannot fake good intent for long. Then ask them to reflect back what they heard: 'What parts are resonating most with you?' This surfaces misunderstandings and lets the person commit to change in their own words — which is more powerful than anything you can say for another twenty minutes. ↳ Wes Kao — 'Strategy, Not Self-Expression' (newsletter.weskao.com)

The same discipline that applies to giving feedback applies to receiving it. Most leaders don't get accurate feedback about themselves because they don't chase it actively enough. When someone is reluctant to give feedback, don't let them off the hook — keep asking. Use silence after a vague answer; it creates space for the real answer to emerge.

When someone does give you useful criticism, reward it. Thank them explicitly. Praise the act. And most importantly: take action on it if you can. A leader who visibly changes behavior in response to feedback builds a reputation for being safe to be honest with — which generates more honest feedback in a compounding loop.

Don't confine feedback-seeking to scheduled meetings. Chase it in one-to-two minute conversations between engagements — after a presentation, after a difficult decision, after a team meeting. The compounding effect of small, frequent feedback loops over months produces far more calibration than quarterly 360 surveys. Sheryl Sandberg actively chased a banker for feedback during Facebook's IPO process. The relentlessness is the point. ↳ Kim Scott — Radical Candor / First Round Review

You will make mistakes as a manager. You will give feedback that lands wrong and damages someone's confidence. You will make a decision that seemed logical but turns out to be completely misguided. You will forget something important you promised to do. You will lose your patience when you should have stayed calm. The question is not whether this will happen. It's what you do after.

The skill that most distinguishes great managers is repair: going back after you've made a mistake, owning it specifically, and reconnecting. When you own your mistakes completely and specifically, something unexpected happens — your team trusts you more, not less. The manager who never acknowledges errors is the one people leave. The manager who comes back and says 'I put you in an impossible position and I'm sorry for the stress that caused' builds trust even through the mistake. ↳ Terrible Software — 'The Management Skill Nobody Talks About' (terriblesoftware.org)

• Be specific about what you did wrong. Not 'mistakes were made' or 'things could have gone better,' but 'I interrupted you three times in that meeting and dismissed your concerns. That was wrong.'
• Don't make it about you. This is not the time for a long explanation of your stress levels or why you acted that way. The repair is about acknowledging the impact on the other person.
• Actually change the behavior. An apology without changed behavior is empty words. If you keep making the same mistake, it is no longer a mistake — it's a choice.
• Give it time. One conversation doesn't instantly repair broken trust. It's a starting point, not a finish line.

Most managers spend disproportionate time on struggling performers while their best people receive relatively little attention. The logic seems sound — the people who are struggling need help, and the people who are succeeding are fine. But 'fine' is not the same as 'developing,' and high performers who don't grow leave.

A related trap: expecting from others what you expect from yourself. Leaders who set exceptionally high personal standards are often perpetually frustrated with their teams because they hold everyone to the same bar. Marcus Aurelius found a different approach. According to Cassius Dio, 'so long as a person did anything good, he would praise him and use him for the service in which he excelled, but to his other conduct he paid no attention.' The standard is for you. For others: find what is strong, lean into it, and meet people where they are. ↳ Ryan Holiday — '24 Leadership Principles' (ryanholiday.net) · Cassius Dio

The highest-leverage time investment a manager can make is often in their strongest performers. These are the people with the most room to develop further, the most potential impact on the team, and the most options if they feel neglected. A neglected high performer doesn't complain loudly — they update their resume quietly. ↳ Molly Graham — '6 Counterintuitive Rules for Being a Better Manager' (First Round Review)

One of the best measures of long-term leadership success is that the organization around you increasingly benefits from, but does not rely upon, your contributions. Many leaders reach senior positions by being the go-to person — the one who makes the call, carries the context, solves the hardest problems. That capability is what got them there. It is not what makes them effective at the next level.

The transition from essential to adjacent is difficult because it requires giving away work you're good at — and trusting that others will get to a good answer even if they'd take a different path than you would. When you make a key contribution, pause and ask: what would it take for someone else to make that contribution next time? Then invest in making that happen rather than repeating the contribution yourself. This is not abdication — it is the deliberate transfer of capability into the organization.

• In meetings: shift from giving answers to asking questions. Ask the questions that open the problem up rather than closing it. Pull in the person who hasn't spoken. Take notes — it frees others to contribute more and destigmatizes the work.
• In decisions: write down your reasoning before announcing it. Documentation transfers judgment in a way that presence in the room cannot. Others can act on written reasoning without you being there.
• In sponsorship: the most senior form of development is not mentorship (advice) but sponsorship (actively advocating for someone's advancement in rooms they're not in). Sponsor over mentor. ↳ Will Larson — 'Staff Engineer: Leadership Beyond the Management Track' (2021)

The decision to end someone's employment is among the hardest a leader makes. It is also, when it is necessary, one of the most consequential things a leader can do for the health of a team. Leaders who avoid this decision when it's clearly required pay for the avoidance for months or years.

A termination may be appropriate when: the person cannot or will not meet clear expectations despite genuine support and feedback; their behavior is damaging to the team in ways that cannot be corrected; or the role has changed in ways that require capabilities the person doesn't have and can't develop in the timeframe required.

The test is not 'Is this person a good human being?' The test is whether there is a realistic path to this person meeting the requirements of this role, in this organization, at this time. If the honest answer is no — and if the feedback process has been fair — then the decision is clear, even if it is painful.

Before addressing what to check, it's worth naming why leaders delay this decision even after the answer is clear. Kim Scott identifies four specific rationalizations leaders use to avoid acting — recognizing them by name makes them harder to hide behind:

• 'Things will get better.' Ask directly: better how, and what exactly are you or the person doing differently that would cause it? If there's no concrete answer, this is a hope, not a plan.
• 'Someone in the seat is better than no one in the seat.' Often false. An underperforming person in a role can cost more — in rework, in the team's confidence, in the standard it sets — than an open seat costs in lost capacity.
• 'Let's transfer them to another team.' This frequently just relocates the same problem and burdens a different manager with the same decision, later and with less context.
• 'The termination will hurt morale.' Usually the reverse: tolerated underperformance is what damages morale, because it signals to the rest of the team that standards aren't real. ↳ Kim Scott — 'Radical Candor' (St. Martin's Press, 2017)
• Has the person received clear, specific, documented feedback about what needs to change?
• Have they had a genuine opportunity to address it — with support, resources, and reasonable time?
• Is the standard being applied consistently with other team members?
• Have you consulted HR or legal as required by your organization?
• Are you certain the problem is the person, not the role, the team dynamics, or something you could address differently?

• Do it in person, in private, early in the week (not Friday afternoon).
• Get to the point quickly. Long preambles are unkind, not kind.
• Be clear about the decision: 'We've decided to end your employment' not 'We're going to have to make some changes.'
• Explain the severance and next steps practically.
• Allow the person to respond. Listen. Don't argue.
• End the meeting. A termination conversation that goes on for an hour does not help anyone.

Two further principles worth holding onto. First, don't hand off the conversation to HR — it is the manager's responsibility, and doing it yourself is part of what makes it humane. Second, be generous where you reasonably can: with severance, with a reference, with help finding the next role. The person you're letting go today may be a colleague, a client, or a reference for someone else tomorrow, and how they're treated on the way out says as much about your leadership as anything else you do. ↳ Joel Peterson — 'Firing with Compassion' (Harvard Business Review, 2020)

Teams don't become effective by accident. The conditions that allow a group of people to produce results together — trust, clear roles, shared goals, productive conflict — have to be created deliberately. This is the leader's job.

The most consistent finding in research on team effectiveness is that high-performing teams have high psychological safety — an environment where people can raise concerns, ask questions, share half-formed ideas, and disagree with each other without fear of ridicule or retaliation. This is not the same as comfort or congeniality. Teams with high psychological safety have more conflict, not less — but productive conflict rather than silence or politics.

Psychological safety is primarily established by the leader's behavior, not by team-building exercises or declared values. The team watches how the leader responds when someone raises a problem, challenges a decision, or makes a mistake. Those responses — not the stated norms — define the actual culture.

Research consistently shows that the variables people assume matter most have surprisingly little effect on team effectiveness. Google's Project Aristotle found that colocation, consensus-driven decision making, extroversion of team members, individual performance levels, workload size, seniority, team size, and tenure all had relatively weak effects. What matters is how the team communicates, whether people feel safe to speak up, and whether the leader creates the conditions for both. Project Aristotle identified five factors that distinguish high-performing teams from the rest: Psychological Safety, Dependability, Structure & Clarity, Meaning, and Impact. ↳ Google re:Work — Project Aristotle research on team effectiveness (rework.withgoogle.com)

A companion study — Project Oxygen — asked the same question about individual managers rather than teams. Google's People Innovation Lab launched it with the explicit goal of proving that manager quality has no impact on performance. The data proved the opposite. Statistical analysis of performance reviews, engagement surveys, and employee interviews found that manager quality made a substantial difference — and identified eight consistent behaviors that distinguished the best managers from the rest, in ranked order: is a good coach; empowers and does not micromanage; cares about success and well-being; is productive and results-oriented; communicates well (listens and shares); supports career development; has a clear vision and strategy; and has relevant technical skills.

Two things about this list are worth sitting with. First, coaching is at the top — not strategy, not technical expertise, not results. Second, technical skills rank last. Being excellent at the work does not make someone an effective manager of people who do that work. This is the data behind what Ch01 describes as the competence trap: the skill that earned the promotion is the least predictive of success in the role it unlocked. ↳ Google re:Work — Project Oxygen research on manager effectiveness (rework.withgoogle.com) · BetterUp / Madeline Miles

The O.C. Tanner Institute's 2023 Global Culture Study quantified the impact of specific leader behaviors on employees' sense of belonging and community at work. The effects are large enough to be striking:

• Connects the purpose of my work with what I value: +194% odds of a strong sense of community.
• Clearly communicates what success looks like: +133%.
• Introduces me to potential mentors: +122%.
• Is a strong advocate for my development: +104%.
• Champions my decisions: +78%.
• Works to understand what I do: +63%.

The top behavior — connecting the purpose of someone's work to what they personally value — nearly triples the odds of a strong community. This is not a soft outcome. Teams with high belonging have lower turnover, higher engagement, and better performance. The behaviors that produce it are specific and learnable. ↳ O.C. Tanner Institute — 2023 Global Culture Study

Teams function poorly when people are unclear about who owns what, or when individual goals conflict with team goals. The leader's job is to create enough clarity that people can make good decisions independently.

• Every team member should be able to articulate the team's top three priorities and how their own work connects to them.
• When two people could both reasonably claim responsibility for something, one person should have explicit ownership.
• The team should have a shared understanding of what success looks like at the end of the quarter, not just at the individual level.

The absence of visible conflict on a team is usually not a sign of alignment — it's a sign of suppressed disagreement. Problems that don't surface in meetings surface later, in the form of passive resistance, poor implementation, or people going around the decision-maker.

Leaders who build teams capable of productive conflict model disagreement themselves, distinguish between productive tension and unproductive conflict, make it safe to change one's mind, and close debates with clear decisions rather than letting ambiguity persist.

Individual development is not just a manager-to-report conversation. The best teams create conditions where people develop through the work itself — through ownership, stretch assignments, honest feedback from peers, and visibility into how their contributions connect to outcomes that matter.

Recognition matters more than most leaders think, and it is more specific than most leaders make it. Generic praise is wallpaper. Specific recognition — naming what someone did, why it mattered, what it says about them — is signal. Sending recognition upward through the organization, so that people two levels above become aware of strong work, has outsized impact on retention and motivation. ↳ First Round Review — 'The 25 Micro-Habits of High-Impact Managers'

Teams accumulate norms — unspoken agreements about how decisions get made, what behavior is acceptable, what gets rewarded. Writing those norms down as explicit values can be useful. But the order of operations matters: values consolidate change that has already happened; they cannot start it. Stating that you value psychological safety does not create it. Consistently modeling the behavior that psychological safety requires — and holding leaders accountable when they undermine it — creates it. The written value comes after, to make the change durable and legible to newcomers.

Before writing down a team value, test it against three questions:

• Is it reversible? Can you restate it as a legitimate opposite without the result being nonsensical? If not, it's probably an identity statement ('we are excellent') rather than a guide to behavior. Reversibility is what makes a value a real choice rather than a platitude.
• Is it applicable? Can someone actually use it to navigate a real decision — in a planning session, a performance review, a hiring discussion? If the value is so broad that two reasonable people can't agree whether it applies to a given situation, it won't guide anything.
• Is it honest? Does it describe how effective people on this team actually behave today — not how you wish they would? A slightly aspirational value can work if the behavior is already mostly there. A purely aspirational value becomes a trap for well-intentioned people and is ignored by everyone else.

The practical implication: don't introduce team values to drive cultural change. Drive the cultural change first — through your own behavior, through who you hire and promote, through what you recognize and what you hold accountable. Then document the values to make that change permanent and accessible to people who weren't there when it happened. ↳ Will Larson — 'The Engineering Executive's Primer' (O'Reilly, 2024)

As a leader, your standards are the maximum of what your team will deliver. Not the minimum, not the average — the ceiling. Your team's output will rise to meet your expectations and rarely exceed them. This is not a comfortable fact, but it is a clarifying one: if the team's work is consistently passable rather than strong, the place to look first is not the team's capability but the bar you are setting and holding.

The obstacle to raising standards is almost never a leader who wants mediocrity. It is a leader who believes their standards are already high — and therefore stops looking for the gap. The most common signal that standards have drifted: when challenged on quality, the team reaches for one of these three defenses:

• 'It's good enough.' This is almost always used before reaching the actual threshold of good enough. The tell: applying the MVP label to work that is minimum but not viable.
• 'There's a speed/quality tradeoff.' True in theory; invoked in practice well before the team is actually close to that boundary. Most teams have significant room to improve on both dimensions before a genuine tradeoff appears.
• 'We're past the point of diminishing returns.' Usually said before returns actually diminish — used to justify stopping, not as the conclusion of an honest analysis.

A related challenge: you cannot watch everything. You need your team to hold standards in the moments when no one is looking — which is most moments. That requires them to have internalized the standard, not just complied with it when under observation. The distinction shows up in the work they bring you without prompting. ↳ Wes Kao — 'Are Your Standards Too Low? In Defense of Raising the Bar' (newsletter.weskao.com)

Rigorous thinking is the norm that any idea can be examined, and that careful examination is a sign of respect for the idea — not rejection of it. Teams without this norm produce two failure modes: half-baked ideas that the manager has to veto repeatedly (which trains the team not to bring ideas), or ideas that go unquestioned until they fail in execution.

The opposite of rigorous thinking is lazy thinking — making assumptions you don't even realize are assumptions. Lazy thinking treats the hard part of a problem as 'the details' that someone else will handle. It relies on a black-box middle step: idea → [something happens] → great outcome. The black box is where most projects actually fail.

Building the norm requires that it starts at the top. When you model rigorous examination of your own ideas — naming the risks, identifying the assumptions, acknowledging what could go wrong — you signal that this is what thinking looks like here. The goal is a team where members stress-test their own ideas before bringing them to you, and where the vetting process ends with the person realizing for themselves why an idea needs work, rather than being told.

The regular one-on-one with each direct report is not a meeting. It is the primary instrument through which a manager does the actual work of management: understanding how people are doing, removing obstacles, giving feedback, coaching toward development, and building the kind of relationship that makes honest conversation possible. Most leaders underinvest in it or run it badly.

The one-on-one is not a status update meeting. If the majority of the time is spent on 'what did you work on this week,' the format has been captured by the wrong purpose. Status can be shared asynchronously. The one-on-one is for things that require human conversation: what's hard, what's unclear, where the person is stuck, what they're worried about, how they're developing, what they need from you.

Think of it as having three modes that should each get airtime, though not necessarily in the same meeting every time:

Operational

What is blocking progress? What decisions need to be made? What context does the person need that they don't have? This is the mode most one-on-ones default to entirely — and the mode that matters least, because much of it can be handled asynchronously.

Developmental

How is the person growing? Where do they want to go? What are they working on improving? What feedback do they need? This is the mode most one-on-ones skip — and the mode that most directly determines whether people feel valued, stay, and develop.

Relational

How is the person actually doing — as a human, not just as an employee? Is there something going on that is affecting their work or energy? Is there anything unsaid that needs to be said? This mode builds the trust that makes the other two modes possible.

• Let the report set the agenda, at least in part. Ask them what they want to cover before the meeting. This signals that the time is theirs, not yours — which changes how they use it.
• Be fully present. No multitasking. No glancing at other screens. The one-on-one is one of the few times you are entirely focused on one person. Wasting it by being distracted is noticed and remembered.
• Never cancel. Canceling a one-on-one sends a louder signal than the meeting itself — that this person's time and concerns are lower priority than whatever replaced the slot. If you must reschedule, do it in advance and hold the rescheduled time.
• Ask before you advise. When someone brings a problem, your first move should be a question, not a solution. 'What are you considering?' surfaces their thinking before you overlay yours.
• Follow through. If you commit to something in a one-on-one — to remove an obstacle, make an introduction, provide information — do it before the next one. Consistency here builds the trust that makes the rest of the conversation honest.
• Reserve time monthly for career development. Weekly one-on-ones tend to be absorbed by operational urgency. Put a monthly conversation explicitly about development on the calendar so it doesn't get crowded out.

• What's the most important thing you're working on right now, and how is it going?
• What's getting in your way?
• What's something you wish I knew that I might not?
• What's one thing I could do differently that would make your job easier?
• What are you learning? What do you want to learn more about?
• Where do you see yourself in two years, and how does this role serve that?
• Do you feel like your work is challenging enough? What would stretch you more?
• Are you enjoying the work? What do you find most and least energizing?

One of the most effective things a manager can do early in a relationship is to give their direct report a guide to how they work. Not as a curated self-presentation, but as genuine transparency about the things that are hardest to learn about a manager from observation alone.

• How you give feedback. In the moment or scheduled? How direct, and what should someone do if they disagree?
• How you like to receive feedback. What's the best way to tell you something you don't want to hear?
• Your communication preferences. When do you want to be looped in?
• What you care about most. What do you notice and reward?
• Your failure modes. Where do you tend to be wrong? What should someone do if they think you're making a mistake?
• What the first months should look like. What does success look like at 30, 60, 90 days?

The most valuable and most skipped section is the failure modes. It requires genuine vulnerability. But that vulnerability is precisely what builds psychological safety faster than anything else — because it models the thing you're asking for from others. ↳ Jay Desai — 'The Indispensable Document for the Modern Manager' (First Round Review)

Not every one-on-one starts from the same place. A useful diagnostic before each conversation: where is this person right now? Someone dealing with job insecurity, health problems, or financial stress is not in a position to engage meaningfully with long-term career goals. Maslow's hierarchy — from basic needs through safety, belonging, esteem, and self-actualization — is a useful mental model here.

One of the most overlooked functions of the one-on-one is translation: helping your direct reports understand not just what the organization is doing, but why. Strategy communicated with genuine rationale — why this direction, why now, what it means for their work — produces engagement and accountability. The clearer the 'why,' the more they can act autonomously within it. ↳ Dunya Kirkali — 'Make 1:1s Matter' (blog.incrementalforgetting.tech)

Communication is not something leaders do in addition to their work. It is the work. The information environment a leader creates — what gets shared, with whom, in what form, at what cadence — determines whether the people around them can make good decisions, act with confidence, and bring problems early.

Every message a leader sends, every meeting they run, every question they ask or fail to ask is a communication. Silence is a communication. Because you cannot prevent communication, the only question is whether to do it deliberately or by default.

Effective leaders layer their communication: the core message is simple enough to be repeated in a sentence; the next level adds context and rationale; the full detail is available for those who need it. And they consider the second-order audience — not just the people in the room, but the people those people will talk to next. ↳ Andrew Bosworth — 'Communication is The Job' (boz.com)

Before adding any new meeting, the right question is: what is the problem this meeting is supposed to solve? If the answer is 'we need to stay aligned,' there is almost certainly a better solution — asynchronous documentation, a shared dashboard, a brief written summary. For the meetings that do survive the audit, one discipline determines whether they're productive: know what kind of meeting it is before it starts — decision, information-sharing, or idea-generation. ↳ Peter Drucker — 'What Makes an Effective Executive' (Harvard Business Review, 2004)

Leaders systematically underestimate how much information their team needs to do good work. Teams end up making decisions based on incomplete information, duplicating work already done elsewhere, and disengaging when they feel they're operating blind.

Explaining the 'why' is necessary but not sufficient. The why has to connect all the way back to the person receiving the message — otherwise it lands as noise. A CEO who announces profitability and explains that this is why they cut costs has communicated the organizational why. What the team hears is different: 'You removed resources we depended on.' The thread of why runs from the strategic rationale all the way down to what it means for the person in front of you. ↳ Jocko Willink — 'Leadership Strategy and Tactics: Field Manual' (St. Martin's Press, 2023)

Most leaders have an information gap in the opposite direction: bad news travels slowly upward. Your boss hates surprises — not because they're controlling, but because being caught flat-footed makes them look out of touch. Apply the same standard in reverse: your manager should never learn something important about your function from someone other than you.

Managing up is the discipline of actively creating the conditions your manager needs to trust you, give you autonomy, and advocate for your work. Fifteen principles, from Wes Kao: embrace it; punchline first; show your thinking; flag issues early; solutions not complaints; information hierarchy; close the loop; communicate better before labeling it micromanagement; over-communicate; proactively assert; share your view; anticipate questions; know when to exit; be explicit about needs; this never ends.

A useful calibration: your area of responsibility is 100% of your time, but it may be 10% of your manager's time. The responsibility for managing upward belongs to the person with more bandwidth to focus on the relationship — which is you. ↳ Wes Kao — '15 Principles for Managing Up' (newsletter.weskao.com)

The most common managing-up failure is a gap in the loop: say what you're going to do; do it; tell your manager you're doing it; tell your manager you did it. A communication that pre-empts the follow-up questions signals judgment as much as the content does.

The Minto Pyramid Principle inverts the natural order of thinking: answer first, supporting arguments beneath, evidence under each argument. The SCQA framework structures any communication: Situation (agreed context), Complication (what's changed), Question (what should we do), Answer (recommendation, supported by discrete, non-interleaved arguments). ↳ Barbara Minto — 'The Pyramid Principle' · Michael Dearing, Harrison Metal — Heavybit 'Executive Communication'

Delegation is one of the highest-leverage leadership tools and one of the most poorly executed. Done well, it develops people and frees the leader for higher-value work. Done poorly, it creates confusion and resentment.

Delegation is not task assignment. A task assignment tells someone what to do. Delegation gives someone ownership of an outcome, including the authority and discretion to determine how to achieve it. Accountability without authority is demoralizing.

Every manager operates somewhere on a spectrum between two failure modes: the micromanager, over-involved in everything; and the absentee manager, so committed to not micromanaging that they disappear. In the middle is thought partnership.

Some of what gets labeled micromanagement is actually a response to insufficient communication from the person being managed. Before concluding a manager is a micromanager, ask honestly: am I proactively giving them what they need to trust the work is happening? ↳ Wes Kao — '15 Principles for Managing Up' (newsletter.weskao.com)

The Eisenhower Matrix — urgent vs. important — hits a ceiling at senior levels. Radical Delegation goes further: instead of starting with the unimportant and working up, it starts with the full set of important tasks and delegates most of those too, with a clear delegation contract — delegation just short of abdication, as Charlie Munger described Berkshire Hathaway's system. ↳ Shreyas Doshi — 'Advanced time management principles' (x.com/shreyas)

Team dysfunction is rarely dramatic. It is usually quiet: energy disappears from meetings, people route around each other, and results drift in a direction nobody is willing to name.

Patrick Lencioni's five dysfunctions build on each other from the bottom up: Absence of Trust enables Fear of Conflict, which enables Lack of Commitment, which enables Avoidance of Accountability, which enables Inattention to Results. Diagnosing which level is broken tells you where to intervene. ↳ Patrick Lencioni — 'The Five Dysfunctions of a Team' (2002)

Talk to team members individually. Ask what's working, what isn't, and what they think needs to change. The pattern across those conversations tells you more than any one conversation does.

Trust, once broken, returns through the accumulation of small, consistent behaviors over time: communicate even without answers (silence gets filled with worse stories); keep your word visibly; recommit to stated values under pressure. Vulnerability-based trust — believing you can be honest about a mistake without it being used against you — is the harder kind to rebuild, and the one Lencioni's pyramid is actually built on. ↳ Matt Mallory — 'Three Steps to Rebuilding Trust Within Your Team' (Fisher College of Business, Ohio State University)

Every leader has an operating system — a set of ingrained tendencies, default responses, and habitual patterns that determine how they show up under pressure. Most leaders don't know what theirs is. They discover it, in real time, when something goes wrong.

• How you respond to conflict — do you move toward it, away from it, or against it?
• How you respond to uncertainty — do you decide quickly, defer, or gather more data?
• How you respond to criticism — do you take it in, defend against it, or shut down?
• How you respond to failure — your own, and others'.
• What triggers disproportionate reactions in you — and what those reactions look like to other people.
• Whether you are internally driven — motivated by the work and its impact — or primarily externally driven, seeking recognition and validation. This distinction matters because it predicts the decisions you'll make under pressure.

One of the most effective and underused tools in a leader's kit is explicit disclosure: telling the people you work with how you actually operate. Done honestly, this accelerates psychological safety by modeling vulnerability first, and gives people information they need to work with you effectively rather than learning your failure modes the hard way.

Most leaders have an incomplete picture of how they come across. When you receive feedback that surprises you — especially if it's consistent across multiple sources — the appropriate response is curiosity, not defense.

What defensiveness actually looks like

• Arguing against the feedback or asking for proof of it.
• Explaining the context that makes the feedback unfair.
• Acting as though you were already aware of the issue.
• Providing your own feedback to the giver immediately afterward.
• Expressing visible discomfort, irritation, or disbelief.
• Complaining about the feedback to someone else later.
• Going quiet in a way that signals displeasure.

Each of these teaches the person giving feedback that the cost wasn't worth it. The only response that keeps the channel open is genuine acknowledgment and, where relevant, follow-through.

• A zero-sum mindset. Treating organizational resources, credit, and success as fixed pies.
• A sense of entitlement. The belief that your position grants you deference rather than responsibility.
• Being motivated by compliments. Optimizing for looking good rather than being right.
• Relationships with pure takers. Advisors who only validate accelerate the loss of calibration.
• Pretending you know. 'I don't know — let's find out' is a signal of intellectual honesty, not weakness.
• Keeping grudges. Poisons working relationships and signals it's dangerous to disagree with you.
• Telling people how busy you are. Communicates that they are an inconvenience.

A related mechanism: the hubris trap. When leaders are placed on a pedestal — celebrated disproportionately — the psychological distance this creates undermines effectiveness. Team members become less willing to give honest feedback and more likely to let the 'great leader' carry the load. The antidote is actively maintaining the connection between yourself and the people you lead. ↳ Haslam, Alvesson & Reicher — 'Zombie Leadership' (The Leadership Quarterly, 2024)

Liz Wiseman's research distinguishes leaders on a single underlying assumption: Multipliers believe people are smart and will figure it out; Diminishers believe nothing gets solved unless they solve it. Three recognizable patterns: the Rescuer (jumping in before someone struggles); the Rapid Responder (answering so fast people stop bringing half-formed thoughts); the Idea Fountain (generating so many ideas the team chases yours instead of developing their own). ↳ Liz Wiseman — 'Multipliers: How the Best Leaders Make Everyone Smarter' (2010)

Time management in leadership is fundamentally different from time management as an individual contributor. The problem is not how to be more efficient. It's how to be in the right places, given that there is always more to do than can be done.

Leaders have time constraints, but their more fundamental constraint is attention. A leader who is in back-to-back meetings all day is present for none of them in the way that produces real value.

Snacking is doing easy, low-impact work — psychologically rewarding, but it consumes time that should go to harder, more important work. Preening is low-impact work that is highly visible. If you find yourself drawn to work primarily because it will be recognized, that is a signal worth taking seriously. ↳ Will Larson — 'Staff Engineer: Leadership Beyond the Management Track' (2021) · Hunter Walk

Most leaders wait until something has gone wrong before thinking seriously about their emotional health. Emotional fitness — self-awareness, empathy, curiosity about feedback, resilience, owning your impact — is most valuable as an ongoing proactive practice, like physical fitness, rather than a reactive repair. ↳ Dr. Emily Anhalt — 'Hit the Emotional Gym' (First Round Review)

The LNO framework classifies every task before working on it: Leverage tasks (only you can do them, excellence has outsized impact) deserve your best work; Neutral tasks need competence, not excellence; Overhead tasks need minimum viable effort or delegation. ↳ Shreyas Doshi — 'Advanced time management principles' (x.com/shreyas)

Peter Drucker: effective executives ask 'What needs to be done?' — not 'What do I want to do?' — and concentrate on no more than one or two things at a time. A related discipline: focus on opportunities rather than problems. Solving a problem restores the previous state; pursuing an opportunity creates a new one, and only one of them compounds. ↳ Peter Drucker — 'What Makes an Effective Executive' (Harvard Business Review, 2004)

A to-do list is a theory. A calendar is a commitment. Slotting tomorrow's tasks into actual calendar blocks forces honesty about how long tasks take and surfaces the real constraint: if priority tasks don't fit, something has to come off the list, not get done badly. ↳ Shreyas Doshi — 'Advanced time management principles' (x.com/shreyas)

The highest-leverage work a leader does is insight work: developing a genuine point of view on strategy, synthesizing what's being learned. It is almost never urgent and almost always important — and systematically crowded out by satisfying operational tasks. General James Mattis argued it is unconscionable for a leader to get their education solely by experience, one mistake at a time, because the people who depend on their judgment pay for each mistake. ↳ General James Mattis — via Ryan Holiday, 'Leadership Principles' (ryanholiday.net) · Shreyas Doshi

One of the most insidious leadership failure modes is the gradual loss of calibration — the slow drift from accurate self-assessment toward a distorted picture that is more comfortable but less useful.

• Information gets filtered: people stop telling leaders things they don't want to hear.
• Confirmation bias accumulates.
• Success creates overconfidence.
• The echo chamber closes: dissenters have learned it's not worth it.

Bob Moses, a leader of the civil rights movement, was described as having 'a capacity for reflection and distance from the thing that you are very much in the midst of and even leading.' George Washington described the same capacity as the 'calm light of mild philosophy.' Both describe the leader who can be present without being captured. ↳ Ryan Holiday — '24 Leadership Principles' (ryanholiday.net) · Thomas Ricks, 'Waging a Good War'

Your emotional tone is organizational infrastructure. If you signal fear, the room becomes fearful. Leaders who understand this calibrate not just what they say but how they say it, intentionally.

At higher levels, what you know — and who you share it with — is a significant responsibility. Leaders who share sensitive information loosely, even with good intentions, erode trust with the people above them.

Vanity metrics are surface-level and impressive; clarity metrics reveal the hidden gears that drive actual performance. Leaders who rely primarily on vanity metrics know how they look but not how they're doing. ↳ Lloyd Tabb — 'I'm Sorry, But Those Are Vanity Metrics' (First Round Review)

When someone keeps asking for more data, the issue is often not data — measurement requests can be a proxy for trust deficits. Push past the surface request to what concern the metrics are meant to address. ↳ Will Larson — 'The Engineering Executive's Primer' (O'Reilly, 2024)

The ability to deliver hard news — clearly, compassionately, and without distorting the message to make it easier to deliver — is among the most important and underrated leadership skills.

Before a hard conversation, ask: Does this person feel like I've got their back? What do they actually need from me — not what do I need to deliver? What would a reasonable path forward look like from their side of the table? ↳ Maggie Leung — 'These 13 Exercises Will Prepare You for Work's Toughest Situations' (First Round Review)

• Say the hard thing early. Don't bury it in preamble.
• Use direct language. 'We're eliminating this role' not 'We're making some organizational adjustments.'
• Explain the reasoning — not to justify the decision, but to give the person context they need.
• Be clear about what happens next — for them and for you.

After delivering hard news, stop talking. Give the person time to process. Listen fully to the response without becoming defensive.

Naming the negative you're trying to avoid causes the person to think of it. 'I'm not saying this to discourage you' plants the word 'discourage.' Lead with what you want them to think or feel, not the negative you're hoping to avoid. ↳ Wes Kao — 'Avoid Incepting Negative Ideas' (newsletter.weskao.com)

Conflict avoidance is one of the most expensive habits in leadership. Conflicts that don't get addressed calcify and exact ongoing costs.

Task conflict

Disagreement about the best way to solve a problem — the most productive form, and should be encouraged.

Relationship conflict

Interpersonal friction. When two people are in conflict, there is almost always truth in each person's account. Listen to one, challenge them to find the substance in the other's view, then do the same in reverse, then reconnect them. ↳ Andrew Bosworth — 'Two Things Can Be True' (boz.com)

Political conflict

Competition for resources, credit, or influence — the most corrosive and least visible. Leaders who don't engage with organizational politics don't avoid them, they simply lose them. A game-theory diagnostic before any cross-functional effort: who are the players, what are the rules, what does each player value, what resources are available, what outcomes are actually achievable. ↳ Esko Lehtme — 'How to get what's available: Game theory' (tsoon.com)

A position is the solution someone has already decided on; an interest is the underlying concern that led them there. Separate the person from the problem; ask what's actually driving their position; generate options before committing to one; use objective criteria. Know your BATNA (Best Alternative to a Negotiated Agreement) before the conversation starts. ↳ Roger Fisher & William Ury — 'Getting to Yes' (Harvard Negotiation Project, 1981)

Disagreement on outcome (they don't think the problem is real) needs a different response than disagreement on mechanism (they share the goal but dislike the approach). Diagnose which one you're facing before defending your position.

Every leadership career will include periods of genuine uncertainty. How you show up in those moments defines your leadership more than how you show up when things are going well.

A 2024 survey of 556 senior executives found leaders typically navigating several major strategic challenges concurrently: changing customer expectations, transforming the business model, managing CEO/leadership transition, competition from new entrants, hybrid work, accelerated growth, international expansion, talent, disruption, and post-merger integration. ↳ Vince Molinaro — 'Community of Leaders' (2024) / Leadership Contract Inc.

The impulse under pressure is to project confidence — often the wrong instinct. People can tolerate an incomplete picture better than discovering the confidence they were shown was manufactured.

• Be honest about what you know and what you don't.
• Separate what is within your control from what isn't.
• Communicate more, not less, even without new information. Silence reads as bad news.
• Stay grounded — your emotional state is contagious.

If you've had the same discussion three or four times without resolution, write the strategy. Good strategy is boring — its purpose is to enable quick, confident decisions, not showcase innovative thinking. Write all your brilliant ideas in a separate document, delete it, and then write the strategy. ↳ Will Larson — 'Staff Engineer' (2021) · Camille Fournier

Kotter's eight steps: establish urgency; build a guiding coalition; develop a vision and strategy; communicate the vision; empower broad-based action; generate short-term wins and consolidate; anchor in culture. The sequence is the point. ↳ John Kotter — 'Leading Change' (Harvard Business Review Press)

Organizations are not machines — they are complex adaptive systems: large numbers of elements interacting nonlinearly, self-organizing without central direction. You cannot control a complex system; you can only influence the conditions within it. Leaders who succeed in genuine uncertainty build adaptive capacity: high psychological safety, distributed information, short feedback loops. ↳ Complex Adaptive Systems theory — Stacey, Holland et al.

Cognitive biases affect every leader's decisions, including yours. The goal is not to eliminate them — that isn't possible — but to know which biases are most likely to affect you in which contexts, and to build processes that compensate for them.

Confirmation bias

Seeking and weighting information that confirms existing beliefs. Particularly dangerous when evaluating people and strategy.

Attribution error

Explaining other people's failures as character flaws while explaining your own failures as situational.

Sunk cost fallacy

Continuing to invest in a failing course of action because of what's already been spent.

Availability bias

Overweighting recent or memorable events. The most recent hire failure makes us overly cautious; the most recent success makes us overconfident.

Overconfidence

Systematic overestimation of our own accuracy and predictive ability. Leaders are especially susceptible after periods of success.

In-group bias

Favoring people who are similar to us in background, style, or identity. Produces homogeneous teams that miss perspectives their leaders lack.

Anchoring

Over-relying on the first piece of information encountered. In salary negotiations and budget discussions, the first number stated shapes all subsequent judgments.

Halo / Horn effect

One positive or negative trait colors the entire evaluation.

Status quo bias

Preference for the current state, even when change would be beneficial. Leaders use this bias to justify inaction by describing it as stability.

Optimism bias

Underestimating the probability and impact of negative outcomes. Results in project timelines too short, budgets too lean, risks underplanned-for.

These templates are not scripts. They are starting points — structures that have worked in the types of conversations that leaders most often handle poorly. Adapt them to your context and your voice.

• 1. Start with the person's state, not the agenda: 'How are you doing — genuinely?' If they're dealing with something significant, address that first.
• 2. Open yourself to their needs: 'What do you need from me right now?'
• 3. Surface day-to-day reality: 'What's something frustrating you right now that I might not be aware of?'
• 4. Personal development: 'Where are you on the goals we set together? What would you like to work on next?'
• 5. Translate strategy: share what you're hearing from leadership and what it means for them.
• 6. Dynamic topics last: sensitive or complex topics go at the end.
• 7. Close by confirming anything you've committed to do, and by when.

• 1. 'Where do you want to be in two years? Three years?'
• 2. 'What do you want to learn while you're in this role?'
• 3. 'What aspects of your current work do you find most energizing? Most draining?'
• 4. 'What would a stretch assignment look like for you right now?'
• 5. 'How can I help you get where you want to go?'
• 6. Schedule this monthly — not annually.

• 1. When someone brings a problem, resist the urge to solve it first.
• 2. 'What do you see as the root cause?'
• 3. 'What options have you considered?'
• 4. 'What are the trade-offs of each?'
• 5. 'What's your instinct about the right path?'
• 6. 'What would you need to feel confident moving forward?'
• 7. Your role is to sharpen their thinking, not replace it.

• 1. Open with observation, not judgment: 'I want to talk about something I've noticed. Over the last few weeks, [specific observation].'
• 2. Ask for their perspective before explaining yours: 'What's your read on this?'
• 3. Be clear about what needs to change: 'What I need to see is [specific behavior or outcome] by [timeframe].'
• 4. Ask what they need: 'What would help you get there?'
• 5. Confirm understanding: 'Can you tell me how you're thinking about this?'

• 1. Get to the point: 'I want to be direct with you. We've decided to end your employment, effective [date].'
• 2. Give the reason briefly: 'As we've discussed, [clear, honest reason].'
• 3. Cover the practical details: severance, benefits, equipment, last day.
• 4. Give them space: 'I know this is a lot to take in. What questions do you have?'
• 5. Do not negotiate the decision. Listen with respect. End the meeting.

• 1. Frame what you're about to share: 'I have some difficult news I want to share with you directly.'
• 2. State the news clearly — avoid softening it to the point of ambiguity.
• 3. Explain the context and reasoning.
• 4. Be honest about what you know and don't know yet.
• 5. Give them room to respond: 'What questions do you have?'
• 6. Discuss what happens next.

• 1. Talk to each person separately first.
• 2. In the joint conversation: establish that the goal is a path forward.
• 3. Have each person articulate what they need — not what the other did wrong.
• 4. Identify where those needs are compatible and where they conflict.
• 5. Establish specific agreements about working together going forward.
• 6. Check in after an agreed period to see if the agreements are holding.

• 1. Do not tell them to calm down.
• 2. Become an ally first. Reflect their frustration back at a slightly lower intensity: 'You're right — that's completely unacceptable. How long has this been going on?'
• 3. Once intensity drops, shift to solving: 'Here's what we're going to do about this.'
• 4. Separate the short-term fix from the longer-term fix.
• 5. If you contributed to the situation, say so explicitly.

Questions organized by purpose. Use them in reflection, in one-on-ones with a manager or mentor, in hiring, or in peer discussions. The most useful questions are often the ones that are hardest to answer.

*For interviewers — designed to reveal past behavior and judgment*

• Among the people you've worked with, who do you most admire and why?
• What do you want to do differently in your next role?
• Tell me about a time you took unexpected initiative. Follow-up: Can you tell me about another?
• When was the last time you changed your mind about something important?
• Why shouldn't we hire you?
• What have I not asked you that I should have?
• For the last few companies you've been at: when you left, why did you leave? When you joined the next one, why did you choose it?
• Imagine yourself in three years. What do you hope will be different about you then compared to now?
• What's something outside of work you're irrationally passionate about?
• What would your previous manager say is the area you most need to grow in?

*For weekly and monthly check-ins with direct reports*

• What's the most important thing you're working on right now, and how is it going?
• What's getting in your way?
• What's something you wish I knew that I might not?
• What's one thing I could do differently that would make your job easier?
• Where are you on the development goals we set together?
• Are you enjoying the work? What's most and least energizing right now?
• Do you feel like you're being challenged enough? What would stretch you more?
• Is there anything unsaid between us that we should talk about?
• How can I support you better?
• What's something frustrating you right now that I might not be aware of?
• How can I help you? What do you think? How can I improve my communication with you? What's next for you?

*For helping people think through their own problems — ask, don't tell*

• What do you see as the underlying root cause of the problem?
• What options, potential solutions, or courses of action are you considering?
• What are the advantages and disadvantages of each?
• What would the worst possible outcome be? What's the most likely outcome?
• What have you already tried?
• What is your initial inclination for the path you should take?
• Is this an either/or choice, or is there something you're missing?
• What would happen if you did nothing at all?
• How would you define success in this scenario — and how will you know?
• If you had to advise a friend facing the same decision, what would you tell them?
• How would you describe the current reality? What are a few options for improvement? What will you commit to do — and by when?
• What's been the best part of your week so far? ↳ Michael Marquardt — 'Leading with Questions' · Marilee Goldberg, Mark Harper (ConocoPhillips), Ron Edmondson

• Where do you want to be in two years? In five?
• What do you want to learn while you're in this role?
• What aspects of your work do you find most energizing? Most draining?
• What would a stretch assignment look like for you right now?
• Who do you most want to be like in 10 years, and what are they doing that you're not doing yet?
• Are you happy in this role? What would make it better?
• What would you do differently if you had my position?

• What do we want to be true in a decade that is not true today?
• What is our current competitive advantage, and is it durable?
• What are the most pressing threats we will face over the next twelve months?
• What are we missing or forgetting? Where should we be placing our best energy?
• What have others done to solve this problem successfully?
• What metrics will we use to determine whether our intervention worked?
• What rule or assumption would you break just to see what new ideas emerge?
• What matters most right now? What is one problem I can turn into an opportunity?
• How will I be more strategic? How can I make swift yet smart decisions?
• What can we learn from this? How can we do it better next time? ↳ Gayle Lantz (WorkMatters) · Ron Edmondson — via Michael Marquardt, 'Leading with Questions'

• What did you think this job was going to be, and how does it differ from what it actually is?
• In what situations do you still default to individual contributor mode?
• Who do you talk to honestly about how the job is going? If nobody, why not?
• What feedback have you received that you initially dismissed and later realized was accurate?
• What are you most defensive about? What does that defensiveness protect?
• Is the pace at which you're currently operating sustainable for another year?
• Do people feel safe with me? How do I know?
• Am I motivated by the work itself, or primarily by how it looks?
• Am I spending more time with my struggling performers than my strongest ones?
• Would my reports gladly work for me again? If I have to ask, it's probably no.
• Why might my current approach not be working — even if it has worked before?

*Separating people from problems, finding common ground*

• How can we separate the people from the problem?
• What goals are actually in conflict here?
• What does each side want — and what do they need underneath that want?
• How can I encourage each side to view the conflict from the other's perspective?
• What are the common areas of interest between the two sides?
• How can each side get what it needs without requiring the other to lose?
• What objective criteria will we use as a basis for our decisions?
• How can we disagree in an agreeable fashion? ↳ William Ury — 'Getting to Yes' (Fisher, Ury & Patton) / 'Getting Past No'

*A daily/weekly/monthly self-check rhythm across four domains*

People

• Daily: Do I need to check in on someone?
• Weekly: Do I have a 1-on-1 scheduled with everyone?
• Monthly: How is team morale on average?

Project

• Daily: Are all projects on track? Any tickets blocked because of me?
• Weekly: Do I need to update anyone on project status?
• Monthly: Do all projects still make sense, or is sunk cost keeping something alive?

Process

• Daily: Anything to discuss at stand-up?
• Weekly: Are the tickets groomed for next week?
• Monthly: Is the process too bloated — can we automate something?

Me

• Daily: Am I prepared for my meetings? How am I feeling, 1-10?
• Weekly: Did I carve out time to learn something new?
• Monthly: Am I living up to my expectations? Am I available enough for my team?

*Google's 13-question Project Oxygen manager feedback survey*

• My manager gives me actionable feedback that helps me improve my performance.
• My manager does not micromanage.
• My manager shows consideration for me as a person.
• The actions of my manager show that he/she values the perspective I bring to the team, even if it is different from his/her own.
• My manager keeps the team focused on our priority results and deliverables.
• My manager regularly shares relevant information from his/her manager and senior leaders.
• My manager has had a meaningful discussion with me about career development in the past six months.
• My manager communicates clear goals for our team.
• My manager has the technical expertise required to effectively manage me.
• I would recommend my manager to other team members.
• I am satisfied with my manager's overall performance as a manager.
• Open: What would you recommend your manager keep doing? What would you have your manager change? ↳ Google Project Oxygen — manager feedback survey instrument

The ideas in this handbook are grounded in research and practitioner experience accumulated over decades. What follows is an annotated reading list — a guide to going deeper, not a full bibliography.

The Manager's Path — Camille Fournier

The clearest practical progression through technical leadership levels.

High Output Management — Andy Grove

Grove's framework for managerial leverage — how leaders create output through others.

An Elegant Puzzle — Will Larson

Systems-level thinking about engineering leadership.

The Making of a Manager — Julie Zhuo

An honest account of what it's actually like to step into leadership for the first time.

Zombie Leadership: Dead Ideas That Still Walk Among Us — Haslam, Alvesson & Reicher (The Leadership Quarterly, 2024)

Peer-reviewed correction of eight persistent myths about leadership. Leadership is a relationship, not a property; the proof of leadership is what followers do.

Leadership Strategy and Tactics: Field Manual — Jocko Willink (2023)

Imposter syndrome reframe, thread of why, Extreme Ownership feedback framing, Reflect and Diminish de-escalation, trusted agents at multiple levels.

Staff Engineer: Leadership Beyond the Management Track — Will Larson (2021)

Safety net disappears at senior levels; to lead you have to follow; from essential to adjacent; snacking and preening; good strategy is boring.

The Engineering Executive's Primer — Will Larson (O'Reilly, 2024)

Values consolidate change already in motion, not start it; measurement requests as trust proxies.

Work Rules! — Laszlo Bock

An evidence-based look at what predicts performance in hiring and management.

The Five Dysfunctions of a Team — Patrick Lencioni

The widely-used model of team dysfunction, built on a trust foundation.

Radical Candor — Kim Scott

The relationship between caring about people and being honest with them.

Thinking in Bets — Annie Duke

Decision quality under uncertainty.

The Pyramid Principle — Barbara Minto

The McKinsey framework for executive communication: answer first, arguments beneath, evidence under each argument. Source of the SCQA structure.

Leading with Questions — Michael Marquardt

Questioning as a leadership discipline.

Humble Inquiry — Edgar Schein

Why asking is more effective than telling in most leadership situations.

Thinking, Fast and Slow — Daniel Kahneman

The foundational text on cognitive bias and judgment.

Mistakes Were Made (But Not By Me) — Carol Tavris & Elliot Aronson

How intelligent people convince themselves they were right when they weren't.

Leadership and Self-Deception — The Arbinger Institute

An exploration of self-deception in leadership.

Getting to Yes — Roger Fisher, William Ury & Bruce Patton

Principled negotiation: separate people from problems, focus on interests not positions, generate options, use objective criteria.

Crucial Conversations — Patterson, Grenny, McMillan, Switzler

A framework for high-stakes conversations.

Leading Change — John Kotter

The eight-step model for organizational transformation.

The following articles and essays were drawn on directly in developing handbook content, organized loosely by the chapters they informed.

Communication is The Job — Andrew Bosworth (Meta CTO)

*boz.com*

Layering messages, second-order audiences, communicating defensively. Informed Ch09.

Two Things Can Be True — Andrew Bosworth

*boz.com*

Mediating conflict by steel-manning each side to the other. Informed Ch16.

15 Principles for Managing Up — Wes Kao

*newsletter.weskao.com*

The 10% asymmetry, the 4-step communication loop, anticipating questions. Informed Ch09, Ch10.

Are Your Standards Too Low? — Wes Kao

*newsletter.weskao.com*

Your standards are the maximum your team will deliver, not the minimum. Informed Ch07.

Strategy, Not Self-Expression — Wes Kao

*newsletter.weskao.com*

A feedback conversation is a sales conversation, not catharsis. Informed Ch05.

Avoid Incepting Negative Ideas — Wes Kao

*newsletter.weskao.com*

Naming a negative frame plants it even when denied. Informed Ch15.

Rigorous Thinking: No Lazy Thinking — Wes Kao

*newsletter.weskao.com*

Stress-testing ideas before bringing them; the black-box middle step. Informed Ch07.

Advanced Time Management Principles — Shreyas Doshi

*x.com/shreyas*

LNO framework, Radical Delegation, Proof of Worth tasks, calendar as commitment. Informed Ch01, Ch10, Ch13.

Make 1:1s Matter — Dunya Kirkali

*blog.incrementalforgetting.tech*

Maslow as a 1-on-1 diagnostic; Gemba mindset; structured agenda sequence. Informed Ch08.

How to get what's available: Game theory — Esko Lehtme

*tsoon.com*

Five-question diagnostic for organizational politics. Informed Ch16.

Why People Really Quit — Kim Scott

*Medium*

Absentee / thought partner / micromanager spectrum. Informed Ch10.

24 Leadership Principles — Ryan Holiday

*ryanholiday.net*

General Dan Caine, Mattis, Bob Moses, Marcus Aurelius / Cassius Dio, Watson IBM. Informed Ch02, Ch05, Ch13, Ch14.

The Coaching Habit — Michael Bungay Stanier (2016)

*boxofcrayons.com*

The AWE Question and the Lazy Question. Informed Ch05.

Multipliers — Liz Wiseman (2010)

*thewisemangroup.com*

The Accidental Diminisher — Rescuer, Rapid Responder, Idea Fountain. Informed Ch12.

What Makes an Effective Executive — Peter Drucker (HBR, 2004)

*hbr.org*

What needs to be done vs. what you want to do; meeting-type discipline. Informed Ch09, Ch13.

Getting to Yes — Fisher & Ury (Harvard Negotiation Project, 1981)

*pon.harvard.edu*

Principled negotiation and BATNA. Informed Ch16.

Nine Questions I Now Ask in Interviews — Louise Deason

*louisedeason.substack.com*

What a hiring manager's own answers reveal to candidates. Informed Ch03.

Lies Managers Tell Themselves to Avoid Firing Someone — Kim Scott, via Tom Tunguz

*tomtunguz.com*

Four rationalizations for delaying a necessary termination. Informed Ch06.

Firing with Compassion — Joel Peterson (HBR, 2020)

*hbr.org*

Don't hand off to HR; be generous with severance and references. Informed Ch06.

Three Steps to Rebuilding Trust Within Your Team — Matt Mallory

*fisher.osu.edu*

Communicate without answers, keep your word visibly, recommit to values. Informed Ch11.

Project Oxygen: An Inside Look — BetterUp / Madeline Miles

*betterup.com*

The Google study that tried to prove managers don't matter and proved the opposite. Informed Ch01, Ch07.

2023 Global Culture Study — O.C. Tanner Institute

*octanner.com*

Quantified impact of leader behaviors on belonging. Informed Ch07.

Hit the Emotional Gym — Dr. Emily Anhalt (First Round Review)

*review.firstround.com*

Seven traits of emotional fitness as a proactive practice. Informed Ch13.

The Indispensable Document for the Modern Manager — Jay Desai (First Round Review)

*review.firstround.com*

The manager user guide / readme. Informed Ch08, Ch12.

I'm Sorry, But Those Are Vanity Metrics — Lloyd Tabb (First Round Review)

*review.firstround.com*

Vanity metrics vs. clarity metrics. Informed Ch14.

The Essential Questions... — Julie Zhuo (First Round Review)

*review.firstround.com*

Would my reports gladly work for me again? Informed Ch08, App C.

6 Counterintuitive Rules for Being a Better Manager — Molly Graham (First Round Review)

*review.firstround.com*

Management is not leadership; spend time with high performers too. Informed Ch01, Ch05.

Fight Like You're Right, Listen Like You're Wrong — Bob Sutton (First Round Review)

*review.firstround.com*

The magnification effect; power poisoning. Informed Ch02.

How to Become Insanely Well-Connected — Chris Fralic (First Round Review)

*review.firstround.com*

Imparting energy matters more than sharing information. Informed Ch02.