Chapter 05 Flashcards — How to Lead a Team
flashcards seg leadership management tech-lead
What is servant leadership, and why does Google advocate it over traditional management?
?
Servant leadership is a philosophy in which the leader’s primary role is to serve the team — removing obstacles, providing resources, and creating conditions for the team to do its best work. Google advocates it because engineering teams are composed of skilled knowledge workers whose best output comes from autonomy, not control. The servant leader’s question is always “What can I do to help my team be more effective?” rather than “What should my team do for me?”
What is the difference between an Engineering Manager (EM) and a Tech Lead (TL)?
?
An Engineering Manager focuses on the people dimension: hiring, performance management, career development, team health, and psychological safety. A Tech Lead focuses on the technical dimension: setting technical direction, making design decisions, driving consensus, and unblocking engineers on technical problems. The TL is still an IC (writes code); the EM rarely writes code. Neither is a higher role — they are different, complementary functions.
What is a Tech Lead Manager (TLM), and what is its primary risk?
?
A Tech Lead Manager holds both the Engineering Manager and Tech Lead roles simultaneously — common at Google for smaller teams. The primary risk is cognitive overload: the TLM must context-switch between people concerns (morale, performance, careers) and technical concerns (design, code review, architecture). Without deliberate time management, one role inevitably crowds out the other, typically the people role suffering.
What are the three common fears engineers have when first moving into a leadership role?
?
- Loss of technical skills — time spent on coordination means less time for hands-on coding. 2. Unfamiliarity with people management — technical training provides no preparation for the ambiguity of managing humans. 3. Accountability for others’ mistakes — leaders are responsible for team outcomes, not just their own work. The chapter reframes leadership as multiplying team impact rather than doing more individual work.
What is the “hire pushovers” anti-pattern, and why is it harmful?
?
Hire pushovers: deliberately selecting less experienced, less opinionated, or less capable engineers who are unlikely to challenge the leader. It is harmful because the team’s ceiling is determined by its weakest members; a team of pushovers cannot produce great work. It also repels strong candidates, creating a self-reinforcing downward spiral. Leaders should hire people who are stronger than themselves in at least some meaningful dimension.
What is the “ignore low performers” anti-pattern, and what are its two failure modes?
?
Ignore low performers: tolerating persistently underperforming team members to avoid the discomfort of performance conversations. Two failure modes: (1) Direct harm — below-expectation output from the individual. (2) Indirect harm — high performers observe that underperformance is tolerated and conclude that standards do not matter, eroding morale and driving top performers out. Address underperformance early, directly, and with specific expectations.
What is the “ignore human issues” anti-pattern?
?
Ignore human issues: treating engineering leadership as purely technical or process coordination, and ignoring the emotional and interpersonal dimensions — team conflict, personal crises, burnout, disengagement. It is harmful because teams are made of humans; unresolved interpersonal conflict festers into dysfunction, and an unsupported team member going through a crisis becomes disengaged and leaves. Leaders must acknowledge the human dimension of their role explicitly.
What is the “be everyone’s friend” anti-pattern, and how does it conflict with honest leadership?
?
Be everyone’s friend: prioritizing social approval and personal friendship over honest leadership — avoiding difficult feedback, making exceptions for friends, letting relationships distort performance assessments. It conflicts with honest leadership because the most important thing a leader can do for a team member is give them accurate feedback that helps them grow. Friends tell people what they want to hear; managers who are friends first do the same, denying reports the feedback that would make them better.
What is the difference between being “kind” and being “everyone’s friend” as a leader?
?
Kindness means treating people with respect, empathy, and care for their wellbeing — including delivering difficult feedback thoughtfully and with genuine concern for the recipient. Being everyone’s friend means prioritizing the relationship over honesty — avoiding hard truths to preserve social comfort. Kindness is a leadership virtue; befriending reports at the expense of honesty is an anti-pattern. Honest feedback delivered with care is the highest expression of respect.
What is the “compromise the hiring bar” anti-pattern?
?
Compromise the hiring bar: lowering hiring standards under pressure from timeline, headcount targets, or hiring fatigue — approving “good enough” candidates rather than waiting for strong ones. It is harmful because a weak hire is rarely neutral: at best, below-expectation output and management overhead; at worst, technical debt, interpersonal friction, and eventual exit that costs far more than the original vacancy. Better to leave a seat empty for six months than fill it in two with a weak candidate.
What is the “treat team members like children” anti-pattern?
?
Treat team members like children: micromanaging — requiring approval for trivial decisions, prescribing solutions rather than goals, not trusting engineers to own their work. It is harmful because it is corrosive to motivation; engineers not trusted to make decisions do not develop judgment, become dependent, lose initiative, and ultimately leave for environments with more autonomy. The right approach: provide clear goals and context, then step back. Review outcomes, not process.
What does “lose the ego” mean as a positive leadership pattern?
?
Lose the ego means subordinating the leader’s need for credit and validation to the team’s needs. In practice: credit others publicly for their good ideas and work, accept feedback openly and change behavior in response to it, and admit uncertainty (“I don’t know”) rather than pretending to false certainty. Leaders who need to be the smartest person in the room create competitive, low-trust team cultures that mirror their own insecurity.
What does it mean to “be a Zen Master” as a leader?
?
Be a Zen Master means maintaining emotional equanimity under pressure so the team can remain focused and effective. A leader’s emotional state is visible and contagious — if the leader panics, the team panics; if the leader responds to setbacks calmly, the team learns to do the same. It also means asking questions (“What do you think we should do?”) rather than always issuing directives — developing judgment in team members and surfacing better information.
What does “be a catalyst” mean in the context of engineering leadership?
?
Be a catalyst means facilitating progress rather than producing it directly. A catalyst-leader identifies when teams or projects are stuck and intervenes to unblock them, facilitates decision-making when consensus fails, and drives toward outcomes rather than activities. Like a chemical catalyst, the leader enables a reaction without being consumed by it — the leader does not need to be the hero of every story, just the condition that makes the story possible.
What is “remove roadblocks” as a positive leadership pattern, and what kinds of roadblocks does it address?
?
Remove roadblocks means actively identifying and eliminating the obstacles that slow the team down. Types of roadblocks: organizational dependencies (waiting for approvals from other teams), missing resources (tools, access, information), unclear requirements or priorities, and interpersonal friction between team members. This is one of the highest-leverage activities for a leader because individual engineers often lack the organizational standing to remove structural obstacles themselves.
What is “The Unexpected Question,” and why is it a high-leverage leadership tool?
?
The Unexpected Question is the practice of regularly asking each team member “What is the one thing blocking your progress right now?” or “What is one thing I could do to make your work easier?” It is high-leverage because: (1) engineers rarely volunteer blockers proactively; (2) many blockers are organizational and fixable by a leader even if not by the engineer; (3) asking signals that the leader’s job is to serve the team; (4) repeated answers across team members reveal systemic problems. Follow-through is essential — asking without acting produces resentment.
What does “be a teacher and mentor” mean in engineering leadership?
?
Be a teacher and mentor means developing team members’ capabilities over time, not just solving problems for them. Teaching practices include: explaining why not just what, pairing on hard problems rather than just providing answers, giving specific behavioral feedback oriented toward growth, and asking “What would you do?” before offering your own solution. Mentoring extends to career advice, connecting people with opportunities, and advocating for their growth in the organization.
What does “set clear goals” mean, and why is one-time goal-setting insufficient?
?
Set clear goals means ensuring the team has a specific, shared understanding of what success looks like and explicit prioritization of competing objectives. One-time goal-setting is insufficient because engineers optimize locally — they work on what seems important to them — unless they continuously understand the team’s actual priorities. Goals stated once are wishes; goals reinforced regularly are real. The leader’s job is to continuously reorient the team toward goals, especially when distracting priorities arise.
What does “be honest” mean as a leadership pattern, and why does it require courage?
?
Be honest means delivering true information even when it is uncomfortable: critical performance feedback, candid project health assessments, and disappointing answers to “Am I on track for promotion?” It requires courage because people prefer comfortable truths and leaders are tempted to soften feedback into meaninglessness. The chapter frames honesty as respect: treating team members as adults who can handle true information and use it to grow. Dishonest leadership is a form of condescension.
What is “track happiness” as a leadership practice, and why does it matter for performance?
?
Track happiness means actively monitoring team health and individual wellbeing: asking genuine questions about how people are doing in 1:1s (not just status updates), watching for signals of disengagement (decreased participation, shorter responses, missed meetings), and acting visibly on what you learn. It matters for performance because team morale is a leading indicator of output quality, retention, and the team’s ability to sustain effort through hard periods. A demoralized team cannot perform at its best regardless of technical skill.
What is the “people are like plants” metaphor, and what does it imply for leadership?
?
The people are like plants metaphor means different people need different conditions to thrive — just as some plants need full sun while others need shade. Some engineers are primarily intrinsically motivated (need interesting problems and autonomy) while others are more extrinsically motivated (need explicit recognition and clear structures). The leader’s job is to understand what each person needs and provide it — not apply a uniform approach that works for one person and neglects another.
What is the difference between intrinsic and extrinsic motivation, and why does it matter for leadership?
?
Intrinsic motivation: doing work because it is inherently interesting, meaningful, or personally fulfilling. Associated with sustained engagement, high-quality creative work, and long-term retention. Extrinsic motivation: doing work for external rewards — salary, recognition, ratings, fear of consequences. Effective short-term but does not sustain creativity or quality. Leaders must identify which type dominates for each team member: over-investing in extrinsic rewards for intrinsically motivated engineers can actually reduce motivation (the overjustification effect).
What risk arises from a leader who treats all engineers as purely extrinsically motivated?
?
If a leader treats all engineers as purely extrinsically motivated, they create a culture where gaming metrics is rational behavior — optimizing for the appearance of performance rather than actual outcomes. Engineers learn to optimize for whatever is measured (promotion criteria, code coverage numbers, velocity metrics) rather than the underlying goals those metrics were intended to proxy. This produces shallow, metric-optimized work and erodes genuine engineering culture.
Why is early, direct action on underperformance critical, and what happens when it is delayed?
?
Early, direct action allows the underperforming engineer a genuine opportunity to improve with clear expectations — and either recover or be moved to a better-fit role before the team is significantly harmed. Delay consistently makes the problem worse: the underperformer does not improve without feedback, the harm to team morale compounds, and when action is finally taken it is perceived as sudden and unfair. Delayed action also signals to the team that the leader lacks the conviction to maintain standards.
What does it mean for a leader to “shield the team,” and when is it appropriate?
?
Shielding the team means filtering organizational noise — politics, distracting priority requests, senior leadership anxiety, bureaucratic overhead — so the team can maintain focus on their actual work. It is appropriate when the distraction has no actionable implication for the team’s work and would only create anxiety without enabling better decisions. It is not appropriate to shield the team from information that genuinely affects priorities or direction — that becomes information hoarding, which destroys trust.
Why was the “manager” title historically stigmatized at Google, and what was wrong with that view?
?
In Google’s early years, the manager title was seen as a step away from “real” engineering — taken by those who could no longer compete technically. This was a mistake because it misunderstood what management is. A great Engineering Manager is not a failed engineer but a practitioner of a different, equally demanding skill set: hiring, growing people, managing performance, creating psychological safety. Treating management as lesser produced a generation of leaders who were embarrassed by the role and under-invested in the people dimension of their teams.
Total Cards: 25
Review Time: ~20 minutes
Priority: HIGH
Last Updated: 2026-06-02