**Author:** [[3. Resources/Authors/Sarah Drasner|Sarah Drasner]] # Book Overview ![[Engineering Management for the Rest of Us Visual.excalidraw]] ## About the Author Sarah Drasner is a VP of Developer Experience at Google, where she leads teams including Angular and other web infrastructure groups. Before Google, she held senior engineering leadership roles at Netlify (VP of Developer Experience) and Microsoft. She's an award-winning speaker, O'Reilly author, and was named one of the most influential people in tech by NOOP.NL. Her technical background runs deep -- she's a former Vue.js core team member, a recognized expert in CSS and SVG animation, and the creator of career-ladders.dev, an open-source resource for career laddering that she built from frameworks she developed across her management career. She's written for CSS-Tricks, Smashing Magazine, and authored SVG Animations for O'Reilly. What makes her perspective on management distinct is that she came to leadership the way most engineers do -- sideways, without training, promoted because of technical skill rather than management aptitude. ## Central Thesis Drasner's central argument is that engineering management is a craft that can be learned, practiced, and improved by ordinary people who didn't set out to become managers. The book isn't written for natural-born leaders or people with MBAs. It's written for engineers who got promoted into management because they were good at building things, and now find themselves responsible for building teams instead. The core claim is that caring about your team -- genuinely, structurally, not just sentimentally -- is the foundation everything else rests on. Trust and vulnerability aren't soft skills that you tack on once the "real work" is done. They are the real work. Teams with generative, trusting cultures outperform teams without them, and the research backs this up. A manager's job, in Drasner's framing, is to enable the people around them to do their best work together. This sounds simple, but the book spends 24 chapters unpacking what that actually looks like in practice: how to run values exercises, how to give feedback without triggering fight-or-flight responses, how to build career ladders that create clarity instead of confusion, how to protect flow state, how to say "we" instead of "them" when talking about your team, and how to take care of yourself so you don't burn out while doing all of it. ## Why This Book Matters Most engineering management books assume you either want to be a manager or already know you're good at it. This one assumes neither. It speaks directly to the person who feels thrown into the deep end -- who knows they care about doing right by their team but doesn't have a framework for how. The fact that Drasner openly admits her own mistakes throughout the book makes it feel less like a lecture and more like advice from a friend who's been through the same panic. The book also matters because it bridges the gap between research and practice. Drasner doesn't just tell you to build trust; she cites Csikszentmihalyi on flow state, Forsgren's Accelerate on team culture and performance, and Shawn Achor's work on positive psychology, then shows you how those findings translate into things like running a values exercise or structuring a 1:1. It's grounded without being academic, practical without being shallow. --- # Chapter Summaries ## Part 1: Your Team (Chapters 1-8) ### Chapter 1: Caring for Your Team The opening chapter sets the tone for the whole book with a joke: you get good at bridges, so they promote you to be a baker. Drasner establishes that the transition from engineer to manager is disorienting because the skills that got you here won't carry you forward. Your work is no longer about your own output -- it's about enabling everyone around you. She introduces the idea that management is "interruption-driven work" so your team can be "flow-driven," and argues that the stakes are higher now because your decisions affect people's daily lives directly. ### Chapter 2: The Value of Values This is the foundational chapter that the rest of the book references repeatedly. Drasner introduces values as a tool for understanding people -- not a corporate poster exercise, but a genuine framework for figuring out what drives behavior. She walks through individual values, team values, and company values, and explains how running a values exercise (where team members pick their top five values and explain why) can build trust and reveal misalignments. The key insight: conflicts at work are rarely about good versus evil. They're usually about misaligned values, where neither person intends harm. ### Chapter 3: Trust and Vulnerability Drasner defines her job as enabling the people around her to do their best work -- together. She argues that trust is the foundation this rests on, and it's built in drops and lost in buckets. She draws on Accelerate's research showing that teams with generative, trusting cultures have the fewest outages and highest performance. The chapter introduces modeling vulnerability as a leadership tool: the manager has to go first, admitting mistakes and bad days so the team knows it's safe to do the same. She's honest about the complexity here for underrepresented minorities in tech, noting that vulnerability displayed by her male peers reads as humility, while the same behavior from her could read as incompetence. ### Chapter 4: Your Team is Not "Them." Your Team is "We." One of the book's most memorable frameworks. Drasner argues that the pronouns a manager uses reveal whether they truly see themselves as part of the team. When things go well, praise "them." When things go wrong, it's "I" -- because you're the accountable party. Never "them" when describing failures, because that shirks the responsibility you hold. This extends to the leadership team too: when you convey decisions made at the leadership table, you say "we," not "they decided." Anything else demoralizes your team and makes them distrust other parts of the organization. ### Chapter 5: Happiness and Drive Drasner connects team happiness to business outcomes using Daniel Pink's Drive and Shawn Achor's The Happiness Advantage. She introduces flow state (Csikszentmihalyi, 1975) and lists the conditions that enable it: alignment on work premises, challenging but not impossible tasks, feeling respected, fair compensation, and timely feedback. She covers the negative bias -- our brains' evolutionary tendency to remember bad over good -- and the "undoing effect" as a management tool: check in with facts, rally around positives, reject negative premises, and review actual consequences rather than imagined ones. ### Chapter 6: Long-term Care of Employees The chapter on bias, employee goals, and the trap of doing everything yourself. Drasner tells the story of shielding a direct report from political battles instead of teaching her to advocate for herself -- and how that protection didn't survive a manager transition. The lesson: teach people to fish. She covers the Stages of Inclusive Leadership Continuum (Unaware, Aware, Active, Advocate) and makes the case that trust and inclusion are inseparable. The chapter also introduces employee goal-setting and the Venn diagram of what a person wants to do versus what the company needs. ### Chapter 7: Career Laddering Drasner introduces career-ladders.dev, the open-source career laddering site she built. Her system follows a clear progression: senior means you're the best "you" possible, staff means you expand beyond yourself to teach others, and principal means creating systems that scale beyond any one person. The chapter walks through a three-step process: (1) understand the employee's five-year vision, (2) review the career ladder together where the employee self-assesses, and (3) create a 30/60/90 plan starting from the 90-day goals and working backward. She emphasizes that if you guide someone through this process and they meet the criteria, you must give them the promotion. Breaking that partnership destroys trust. ### Chapter 8: 1:1s Are Critical Drasner is unambiguous: 1:1s are the most important thing you do as a manager. She describes it as a hill she'll die on. The chapter covers structure (agendas required, even informal ones), priorities (the meeting is more for the employee than the manager), and modality (shut off your computer, don't multitask, don't take calls from your car). She shares her approach of telling reports directly that she defaults to "fix it" mode and they'll need to tell her when they just want to vent. ## Part 2: Communication (Chapters 9-15) ### Chapter 9: Communicating as a Manager The shift from doing the work to aligning people with outcomes. Drasner argues that the higher you go, the more your job becomes about written and verbal communication. The core discipline is clarity: if your entire team misunderstands a direction, you're the common denominator. She emphasizes repetition (conveying the same message through different channels), alignment with the "why," and the importance of writing from the audience's perspective. ### Chapter 10: Change Management Change is necessary, and Drasner has seen more damage from teams that failed to change than from teams that made mistakes during change. The biggest lynchpin is culture -- no change takes root unless the organizational culture supports it. She tells a personal story of joining a team where "it's impossible" was the default response, and how she spent months finding allies who valued curiosity and humility, building a shared vision before proposing structural changes. Key advice: connect people to the why, seek to understand before directing, be specific about reasoning, and support people to grow the skills they need to succeed in the new environment. ### Chapter 11: Giving Feedback Feedback is a partnership, not a pronouncement from on high. Drasner walks through the neurological reality: poorly delivered feedback hijacks the amygdala and shuts down analytical thinking. Her process: do the pre-work of understanding how someone prefers to receive feedback, check your own motivations and biases, deliver specific feedback as soon as possible, keep the conversation open, and connect feedback to the person's values and career goals. She emphasizes speaking to your own experience ("I felt X when this happened") rather than character attacks ("You are X"). ### Chapter 12: Receiving Feedback The counterpart to giving feedback, this chapter introduces ego resilience -- the ability to separate yourself from feedback enough to hear it without being destroyed. Drasner covers soliciting feedback as a leader (anonymous surveys, group feedback about specific projects, 1:1 requests with advance notice), and introduces the concept of switchtracking -- when a feedback recipient changes the subject to avoid engaging with the feedback itself. She also covers how to handle ad hominem attacks: don't tolerate them, but also don't tolerate them against yourself. ### Chapter 13: Good Meetings A meeting needs a clear purpose, an agenda, the right people (not too many, not too few), some order, and clear outcomes. Drasner covers different meeting types (cross-functional, decision-making, standups, brainstorming) and introduces the DRI (Directly Responsible Individual) concept -- every meeting and project needs one person who ultimately makes decisions when the group can't agree. She also covers DACI, RACI, and RAPID frameworks for decision-making clarity. ### Chapter 14: Managing Conflicts False harmony -- when people agree to avoid discomfort -- is just as destructive as open conflict. Drasner argues for productive conflict: separating ideas from identity, acting immediately when conflicts arise, and understanding the values driving each side. She provides practical guidance for creating psychological safety during disagreements and ensuring decisions actually get made and communicated. ### Chapter 15: Cross-Team and Open Source Collaboration This chapter extends the management lens to open-source maintainership and cross-team dynamics. From the maintainer side: create contributing guides, use issue templates, provide codes of conduct, explain why you close PRs, and assume good intentions. From the contributor side: read the documentation first, respect maintainer time, and remember that maintaining a project is often thankless work. ## Part 3: Processes and Planning (Chapters 16-19) ### Chapter 16: Prioritizing Your Team's Work Drasner covers OKRs (Objectives and Key Results) as a prioritization framework. Objectives should inspire imagination; Key Results should be specific and measurable. She walks through a three-step system: define OKRs by looking forward (what could make waves) and backward (what does the data say), break them into tangible initiatives, and create a quarterly planning spreadsheet. The hard part: saying no. If everything is important, nothing is. ### Chapter 17: How to Scope Down PRs A practical chapter on breaking large projects into smaller, reviewable pieces. Small PRs are easier on reviewers, easier to revert when problems arise, and easier to iterate on. Drasner covers branching strategies, issue and PR labels, feature flags, and the principle that each PR should have one goal. She also covers tracking what's left and working on multiple pieces simultaneously. ### Chapter 18: Speed of Execution Set direction first, then move quickly. Drasner defines MVP (Minimum Viable Product) and warns against both moving too slowly (analysis paralysis) and too fast (shipping without direction). She covers practical techniques for maintaining execution speed while keeping quality. ### Chapter 19: Splitting Time Between Product and Engineering Work The tension between shipping features and paying down technical debt. Drasner argues that splitting every engineer's time across both is often less effective than dedicating some engineers to product work and others to engineering improvements. She covers how to communicate the value of technical debt work to non-technical stakeholders, handle migrations, and celebrate engineering wins. ## Part 4: Self-Care and Growth (Chapters 20-24) ### Chapter 20: Prioritizing, High Level Drasner connects personal prioritization back to values, arguing that your schedule should reflect what you actually care about. She introduces energy-level scheduling -- matching task types to natural energy patterns throughout the day. High-energy times get strategic work; low-energy times get administrative tasks. She also covers context-shifting costs and building a high-level schedule that accounts for the reality that perfect balance doesn't exist. ### Chapter 21: Prioritizing, Day to Day The practical companion to the previous chapter. Drasner's priority order: things that are actively on fire, things that can be done quickly, things that need a scheduled block, things that might get done later. She covers creating systems that work with your strengths rather than against them, and giving yourself credit for time spent on invisible management work. ### Chapter 22: Setting Boundaries Overcommitting happens incrementally -- you say yes one thing at a time until you're completely overwhelmed. Drasner covers boundaries around meetings, mental boundaries (learning to say no), physical boundaries (exercise, sleep, stepping away from screens), and the relationship between boundaries and values: if you don't protect your values with boundaries, you don't actually live them. ### Chapter 23: Filling Your Cup Self-care as a management strategy, not a luxury. Drasner covers finding joy to build resilience, gratitude journaling (writing three things you're grateful for each day), and identifying your personal sources of energy renewal. She references her coach Jessi's question about resilience: "How are you taking care of yourself?" ### Chapter 24: Believing In Yourself The final chapter covers self-efficacy -- the belief in your own competence to act, which is related to but distinct from self-confidence. Drasner cites Bandura's research showing that self-efficacy helps with both success and resilience to failure. She covers surrounding yourself with supportive people, the difference between mentorship (advice) and sponsorship (opening doors), and ends with a reminder that taking care of yourself is intrinsically connected to whether you can do your best work for your team. --- # Key Themes and Highlights ## The Values Framework: Understanding Before Fixing The values framework runs through the entire book like a spine. Drasner doesn't treat values as a corporate exercise -- she treats them as a diagnostic tool. When two people conflict, the question isn't who's right. The question is: what values are at play, and where's the misalignment? When someone's performance drops, the question isn't whether they're lazy. The question is: are their values aligned with the work they're doing? The practical application is a team values exercise where everyone picks their top values from a list and explains their choices. This sounds simple, but Drasner argues it's most valuable precisely when it's uncomfortable -- when the team hasn't built trust yet. The act of sharing builds the trust you need. The framework also extends to boundaries. Values without boundaries are aspirational; values with boundaries are lived. If you say you value family but let work consume every evening, you're not living your values, and burnout is inevitable. ## The Pronoun Test: "We" vs. "Them" One of the book's sharpest observations: you can diagnose a manager's relationship with their team just by listening to their pronouns. Good managers say "they" for successes (giving the team credit) and "I" for failures (taking accountability). Bad managers reverse this -- taking credit for wins and deflecting blame for losses. This extends to the leadership team as well. When a manager tells their reports, "The leadership team decided we need to ship three features," they're positioning themselves as a powerless messenger rather than a participant in the decision. The better framing: explain the reasoning behind the decision, own your involvement, and open discussion about how the team can contribute. ## Flow State and the Manager's Role in Protecting It Drasner's conditions for flow state read like a checklist for team health: alignment on premises, challenge without impossibility, a sense of togetherness, respect, fair and timely feedback, fair compensation, loss of self-consciousness in the work, and belief from others. A manager can't create flow state directly, but they can create the conditions where it becomes possible -- or destroy those conditions through unnecessary interruptions, unclear direction, and unresolved conflicts. The practical implication is that a manager's work should be "interruption-driven" precisely so the team's work can be "flow-driven." This means absorbing organizational noise, providing clarity, and protecting blocks of uninterrupted time. ## Feedback as Partnership, Not Judgment Drasner devotes two full chapters to feedback because getting it wrong can damage relationships permanently. The core insight is neurological: poorly delivered feedback triggers the amygdala's threat response, shutting down the analytical thinking you need the person to engage. The framework: understand their preferred feedback style, check your own motivations and biases, deliver specific feedback tied to observable actions (not character), keep conversation open, and connect feedback to their values and growth trajectory. She introduces switchtracking -- when a feedback recipient responds to criticism by changing the subject to the giver's flaws. This is a defense mechanism, and recognizing it is half the battle. She also covers ego resilience: the ability to take feedback without being destroyed by it, which comes from having a strong enough sense of self that criticism of your work doesn't feel like an attack on your identity. ## Career Laddering as Clarity Engine Career ladders aren't just promotion criteria -- they're clarity tools. Drasner's three-level framework (senior = best individual contributor, staff = expanding beyond yourself to help others, principal = creating systems that scale) gives people a concrete picture of what growth looks like. The 30/60/90 process turns abstract career goals into actionable short-term plans. The critical point: if you guide someone through this process and they meet the criteria, you must follow through with the promotion. Breaking that contract destroys the trust the entire system is built on. Drasner also pushes back against attributing underperformance to laziness -- it's usually a symptom of misalignment, unclear expectations, or external factors the manager hasn't explored. ## Self-Care as Management Strategy The book's final section on self-care isn't an afterthought. Drasner argues that taking care of yourself is the prerequisite for taking care of your team. Energy-level scheduling (matching task types to your natural energy patterns), boundary-setting, gratitude journaling, and building a support network aren't indulgences -- they're professional necessities. Misalignment between your values and your daily work leads to slow-building burnout, and a burned-out manager can't support anyone. --- # Analytical Reading ## Main Arguments 1. Engineering management is a learnable craft, not an innate talent -- it's for "the rest of us," not born leaders. 2. Trust and vulnerability are the foundation of team performance, not nice-to-haves layered on top. 3. Values provide a diagnostic framework for understanding behavior, conflict, and motivation. 4. The pronouns you use about your team ("we" vs. "them") reveal and shape your relationship with them. 5. Flow state conditions are a manager's responsibility to create and protect. 6. Feedback is a partnership that requires understanding the recipient's neurological and emotional state. 7. Career laddering creates clarity, but only if the manager follows through on promotions. 8. Self-care and boundary-setting are professional duties, not personal luxuries. 9. Change management fails when culture isn't addressed first. 10. The higher you go in management, the more your job becomes about communication and clarity, not technical execution. ## Methodology Drasner blends personal storytelling with psychological research and practical frameworks. She draws on Csikszentmihalyi's flow state research, Forsgren/Humble/Kim's Accelerate data on team culture and performance, Daniel Pink's Drive on intrinsic motivation, Shawn Achor's The Happiness Advantage on positive psychology, and Stone/Heen's Thanks for the Feedback on the neurological challenges of feedback. The personal stories -- from the 1 a.m. PHP disaster to the employee she failed to teach self-advocacy -- ground the research in real management experience and make the advice feel hard-won rather than theoretical. She also references her own coaching relationship with Jessi Kovalik throughout, normalizing the idea that managers need coaches too. ## Strengths The book's greatest strength is its honesty. Drasner doesn't position herself as a management guru dispensing wisdom from above. She opens the book by saying she's "not the best manager in the world" and closes by saying she's "not done making mistakes." Every major framework comes with a story about a time she got it wrong. This modeling of vulnerability -- the very skill she argues managers need -- makes the advice land harder because it comes from someone who's clearly struggled with the same challenges. The practical specificity is also a strength. Drasner doesn't just say "give good feedback." She walks through the neurological reasons feedback triggers defensive responses, provides a step-by-step process for delivery, and even covers what to do when feedback goes badly. The career laddering chapter includes a link to her actual open-source career ladders. The values chapter includes a literal list of values words you can use in team exercises. ## Limitations The book is written primarily from the perspective of someone managing at well-funded tech companies (Netlify, Google, Microsoft). Some of the advice -- like setting up team off-sites, hiring executive coaches, or having the organizational clout to restructure teams -- may not translate directly to smaller companies, startups, or organizations with fewer resources. Drasner acknowledges this indirectly by saying "management isn't one size fits all," but the context is still distinctly big-tech. The book also doesn't spend much time on the hardest management situations: firing people, navigating layoffs, managing through organizational crises, or handling genuinely toxic team members who don't respond to feedback. These topics get brief mentions but not the depth of treatment that the trust-and-values material receives. This is understandable given the book's audience (new and mid-career managers), but readers facing those situations will need to look elsewhere. --- # Personal Reflection ## Key Takeaways The pronoun framework ("we" for failures, "they" for successes) is one of those ideas that's obvious once you hear it but invisible before. I've watched managers do this wrong -- distancing themselves from team failures in stakeholder meetings, taking credit for team wins in performance reviews -- and the erosion of trust is real and visible. Drasner's framing makes it concrete enough to catch yourself doing it and correct course. The values-as-diagnostic-tool approach reframes conflicts I've seen in open-source communities and cross-functional teams. When two contributors disagree about a project's direction, the instinct is to figure out who's right. Drasner's framework asks instead: what does each person value, and where's the misalignment? That question opens space for resolution in a way that "who's right?" never does. The emphasis on self-care and boundary-setting as professional duties, not personal indulgences, challenges the martyrdom culture that's common in tech leadership. Drasner's argument is simple: you can't care for others if you don't put the oxygen mask on yourself first. Energy-level scheduling and gratitude journaling aren't wellness trends -- they're management tools. ## Questions Raised - How do you apply the values framework in organizations where the stated values and actual values are deeply misaligned? - What does the "we" pronoun framework look like when you genuinely disagree with a leadership decision but have to communicate it to your team? - How do you build trust and psychological safety in organizations going through layoffs or restructuring? - Can the career laddering process work in organizations that don't have formal title progressions or budget for promotions? - How does the feedback framework adapt across cultural contexts where directness or vulnerability carry different social weight? - What's the right balance between protecting flow state and requiring the collaboration that Drasner also advocates for? ## Connections to Other Works - [[The Manager's Path]] by Camille Fournier -- a more structural/organizational companion that covers the management career ladder itself, where Drasner focuses more on the human side - [[An Elegant Puzzle]] by Will Larson -- covers systems thinking for engineering management, complementing Drasner's people-first approach - [[Turn the Ship Around!]] by L. David Marquet -- shares the "leader-leader" philosophy that maps to Drasner's emphasis on enabling autonomy rather than directing - [[Radical Candor]] by Kim Scott -- Drasner references Scott's work directly; both books center feedback but Drasner goes deeper on the neurological challenges - [[High Output Management]] by Andy Grove -- the classic that established many frameworks Drasner builds on, particularly around 1:1s and OKRs - [[Accelerate]] by Forsgren, Humble, and Kim -- provides the quantitative research that backs up Drasner's claims about trust and team culture - [[Drive]] by Daniel Pink -- the research on intrinsic vs. extrinsic motivation that Drasner applies to engineering team management - [[Thanks for the Feedback]] by Stone and Heen -- the deep dive on feedback that Drasner draws from extensively - [[Nonviolent Communication]] by Marshall Rosenberg -- referenced directly in the values chapter for its insight on hearing needs behind messages - [[Atomic Habits]] by James Clear -- Drasner applies Clear's incremental habits framework to employee development and leveling up --- # Reading Notes - "People are not pure functions; they have all sorts of interesting side effects." -- one of the best one-liners in the book - The Spiderman vs. Batman analogy for modeling vulnerability is memorable and effective - career-ladders.dev is a genuinely useful open-source resource worth bookmarking - The three-step career ladder (senior = best individual, staff = expand beyond self, principal = create scaling systems) is one of the clearest frameworks I've seen - The Losada coefficient (2.9:1 positive-to-negative interaction ratio) is debated in the literature, and Drasner acknowledges this - The "poop umbrella" metaphor for managers who protect their team from organizational dysfunction -- Drasner argues this backfires long-term - Energy-level scheduling: match high-energy periods to strategic work, low-energy to administrative tasks - "The culture of your team is only as strong as the worst behavior it tolerates" -- applies well beyond engineering teams - Drasner's 1:1 philosophy: shut off the computer, use a notepad, never take calls from a car, and tell reports directly that you default to "fix it" mode - The distinction between mentorship (giving advice) and sponsorship (opening doors and connecting to opportunities) is an important one - "Make things better. That's the job." -- Marc Hedlund quote that captures the change management chapter in six words - The book's foreword by Angie Jones is itself a trust-and-vulnerability story about calling Drasner in a management crisis - Readwise highlights: [[3. Resources/Readwise/Books/Engineering Management for the Rest of Us]]