Book summary “Managing Humans”: summary

Introduction

You spend years writing code, fixing bugs, and mastering technical systems until you accept a promotion to engineering manager. Suddenly, your daily challenges shift from predictable logic to unpredictable human behavior, fragile egos, and organizational chaos. You find yourself unprepared for the emotional toll of leading people and translating executive strategy into technical execution.

Management is the art of balancing chaotic human personalities with strict operational processes while maintaining your technical credibility. Michael Lopp examines the subtle mechanics of corporate survival, showing you how to handle difficult personalities, run functional meetings, and scale engineering cultures without losing your mind.

The book explores several core questions you will face on the job:

• How do you stop worrying and start communicating clear context to your team?
• What separates a productive architectural debate from a destructive office war?
• How do you protect deep thinkers from administrative interruptions?

1. Management Pitfalls and Communication

Insecure managers default to worry and crisis while failing to communicate context, leading to destructive rumors and broken trust.

Coping Mechanisms and Information Vacuums

Managers often fall back on default mantras born out of anxiety. Management via Worry inflicts productivity taxes by asking unfocused, paranoid questions. Management via Crisis manufactures or amplifies disasters just to feel valuable and break old processes. The empathetic version of worry is tasting the soup, where experienced leaders sample critical parts of a project to share aggregate lessons. Crises are occasionally useful for burning down dusty processes.

Ninety-five percent of people in a big company have no clue what corporate machinations are occurring or how they will be affected. Managers act as information conduits, meaning they must route incoming information to the right people. When you fail to communicate or rely on your brain as a to-do list instead of writing things down, employees get starved for context. A star developer who suddenly worries she will be fired is merely reacting to an informational vacuum about her value.

A new manager named Bill stopped taking notes during the first part of staff meetings because he assumed his team did not care about customer wins for other products. After asking them, he found they wanted to hear everything.

To fix these gaps, you can use these practices:

• Keep a notebook with you at all times and write down anything that sounds remotely interesting.
• Pass on information even if you are debating for a few seconds about whether anyone cares.
• Ask follow-up questions like what did you just hear to verify understanding.

The Dangers of Managementese

Managementese creates a high-bandwidth shorthand between managers, but using it with employees destroys trust and sounds like corporate laziness. Phrases like outside of the box, circle back, and double-click help managers process data quickly under tight deadlines, acting as a bullshit umbrella. When spoken to individual contributors, they signal that you have stopped thinking and are relying on throwaway metaphors. Employees exposed to managementese feel out of touch with leadership and lose trust.

When a team is hopelessly polarized in a debate, a local mandate acts as a decisive tool to break the deadlock and move forward. A mandate is a dictate handed down from above with no collaboration or Q and A, operating through three phases: Decide, Deliver, and Deliver (Again). For every person on the team with a strong opinion, there are four other coworkers who form a silent majority that just wants a decision.

A newly hired VP at the author's prior startup listened to weeks of infighting between incrementalists and completionists before simply stating that they were going to follow a specific direction. After a week of organizational disarray, the team got back to work.

You can navigate these decisions and conversations with specific actions:

• Dispose of the management hat when talking to individuals.
• Have conversations in a common, familiar language of a friend rather than corporate speak.
• Decide when to employ the mandate once the debate is no longer productive.
• Deliver the decision clearly so the team leaves knowing no further debate is allowed.
• Deliver (again) by taking time to individually express reasoning and invite venting with both winners and losers in a non-team setting.

2. Running Meetings and Off-Sites

Meetings and off-sites require rigorous agendas, strict rules, and avoidance of corporate cliches to drive actual technical solutions.

Off-sites are necessary when a team grows too large for organic communication. Fred hates off-sites because he equates process with a loss of free will and fears the team will return to a backlog of unfinished work. A successful off-site typically yields three new actionable ideas.

Structuring Off-Sites

You must manage off-sites carefully to secure genuine results.

• Invite only capable and willing participants who can solve the specific problem.
• Ensure every attendee has a deliverable and presents or speaks at least once.
• Hold the meeting outside the usual building to allow people to speak heresy away from constraints.
• Designate a Master of Ceremonies to manage flow and a Taker of Notes to capture actionable ideas.
• Make the off-site at least two days long to allow a bright-and-shiny inflection point after a night of sleep.

Effective off-sites must avoid lazy corporate crutches like personality tests, trust falls, and external facilitators. Personality tests provide convenient social labels that bypass genuine learning. Trust falls substitute artificial discomfort for relevant problem-solving. External facilitators lack the contextual understanding of company culture and politics required to truly drive solutions.

• Avoid personality tests.
• Avoid trust falls.
• Avoid outsiders and external facilitators.

Design and Architecture DNA

Design and Architecture DNA meetings provide a formal platform for technical leaders and engineers to vet major technical decisions without management interference. DNA meetings gather bright, drama-free engineers from across the company to analyze critical technical directions. The meeting maintains strict accountability through the threat of exclusion for non-contribution and rigorous technical scrutiny.

At a prior gig, the intense preparation for DNA meetings meant the goal of winning was absolute silence because every question had already been answered. There are five kinds of win in a DNA meeting.

• Bring respectable firepower by including the best engineers who teach and explain clearly.
• Enforce the rule that non-contributors will not be invited back.
• Authorize the team to rigorously critique and debate technical proposals without holding back.
• Exclude pure managers to keep the focus entirely on technical leadership.

Managers should not stop developing software entirely, because staying in touch with technical creation is essential for maintaining an engineering mindset. While traditional management advice suggests abandoning coding to scale, software development is constantly evolving through open-source integration and smaller teams. Managers who disconnect entirely lose touch with how their products are actually built.

The author began his career as a developer at Borland on the Paradox for Windows team, which had 13 developers on the application team and 50 total contributing engineers.

• Use the development environment to build the product and stay familiar with tools, build systems, version control, and programming languages.
• Be able to draw a detailed architectural diagram describing your product on any whiteboard at any time.
• Own a feature or fix bugs to maintain a humble perspective on small technical decisions.
• Write unit tests late in the product cycle to understand product functionality.

3. Process and Culture

Organizations need both predictable process and disruptive hacking, balanced carefully to survive scaling pain without rotting.

Engineers do not hate process inherently; rather, they hate process that is poorly explained and cannot defend itself. Growing companies pass the Dunbar number where new hires outpace cultural infection. This requires process to document values and maintain communication, which fails when enforced blindly without context.

Roland, a junior engineer, spent a weekend setting up a Perforce server and rewriting build tools. He presented it with Krispy Kreme doughnuts to fix a flawed engineering process.

The Old Guard fights the New Guard when 70 percent of program managers are crap because they cannot explain why they follow process. Between thresholds of 42 and 420 people, you must manage this transition.

The Process Myth

Healthy product companies must protect and encourage disruptive hacking to balance the rigid predictability introduced by growing management processes. As companies grow, they hire managers who introduce process and control to handle interdependencies. This creates the growth paradox where orderly structures suppress innovation. To survive, organizations must deliberately shelter small, fast-moving groups of hackers who act as disruptors and build novel things outside the mainstream.

At Borland, CEO Philippe Kahn drew on nomadic Central Asian tribes to position his engineers as barbarians rather than bureaucrats. Apple institutionalized hacking by hiding secret projects behind locked doors with elite engineers, leaving 32 open radars on a secret project.

Stables and Volatiles

Shipping version 1.0 triggers an internal war between two distinct factions of builders: Stables who value process and predictability, and Volatiles who drive risk and disruption. Stables generate process, mitigate failure, and crave calm predictability, often because they are recovering from the trauma of shipping the initial product. Volatiles hate authority, seek thrills in risk, build rapidly with technical debt, and leave a trail of disruption. Healthy companies need both factions to execute predictably and invent, requiring you to constantly negotiate temporary peace treaties.

Stephen, a temporary contractor at the author's first startup, locked himself in the ping-pong room with the greenest engineer for 10 days without sleep until they built a working application. These engineers endured 48 hours without sleep, releasing version 1.0 after 3 months. This left behind technical debt and architectural inconsistency that took years to clean up while growing to 200 people with 30 customers.

You must combat the Coast and Die mentality by watching for boredom. Boredom starts quietly as an innocuous comment and builds up over time until the employee finally resigns. You can detect boredom by observing routine changes, directly asking if the employee is bored, and actively listening to understated admissions. To prevent boredom, you must execute several protective steps:

• Keep an interesting problem squarely in front of them.
• Let them experiment and obsess.
• Remember they can only take one for the team for so long.
• Protect their time.
• Aggressively remove noise.
• Tell them what the hell is going on.

4. Managing Software Engineers

Engineers require respect for their need for consistency and deep focus, shielding them from administrative entropy.

To successfully manage software engineers, you must provide calm to their chaos by respecting their deep need for consistency and efficiency. Nerds constantly analyze decisions against past precedents. Off-the-cuff policy changes regarding space, titles, or compensation trigger silent rage because they violate predictable system rules. By understanding the rules, nerds optimize their work to require the least energy.

Awarding Kate a window office off the cuff because she is doing great work breaks unspoken rules and makes the entire team anxious about future randomness.

The Nerd Burden

Nerds chase two mental highs—the joy of unraveling a problem and complete knot domination—which require absolute protection of their time, space, and focus. The First High is the liberating moment of understanding a complex problem. The Second High is the act of creation to build a knot-free product. Achieving these states requires entering the Zone, a fragile mental space easily destroyed by interruptions.

Using a hoodie as a visual cue to stay away while chasing high-focus problem-solving states helps you maintain productivity.

To support this focus, you must execute several actions:

• Spelunk the caves of your team members by walking to their offices.
• Ask how they are protecting their focus, back to the door, headphones, or massive screen real estate.
• Identify and enforce their hoodie-like obsessions and physical cues.

Incrementalists and Completionists

Balancing real-world incrementalists and visionary completionists requires marrying their opposing strengths to build a strategic product team. Incrementalists are realists focused on motion, metrics, and shipping what is achievable within available resources. Completionists are dreamers who see long-term technical architecture and want to solve problems permanently. They often clash because they measure degree of rightness differently.

Arguing over an email exchange about whether to apply a minor improvement or rewrite the entire system correctly highlights this tension.

5. Career Paths and Transitions

Navigating corporate career trajectories requires mastering the resume pass, the phone screen, and graceful resignation protocols.

Leadership-minded engineers at growing start-ups generally face four career paths, with the vast majority ultimately staying in their current role forever on a continuous quest. The first three paths are executive roles: CEO, CTO, and VP of Engineering. A CEO is accountable for the entire company, requiring a move out of engineering into product or customer support. A CTO builds the core product technology, while a VP of Engineering manages the humans, processes, and cross-team politics. However, most engineers will follow the fourth path called 'This. Forever.', realizing that leadership comes from everywhere and work is defined by a cascading series of personal quests rather than titles.

The author notes he was once accountable for the people team, marketing, and the cafeteria at a start-up, admitting he was horrifically bad at all three.

Hiring managers spend only about 30 seconds on a résumé's first pass, scanning primarily for name recognition, job trajectory, and unique extracurriculars while completely ignoring professional objectives and skills sections. During the first 10 to 20 seconds, the hiring manager checks if they know the candidate, scans company names and networking keywords, evaluates career history and trajectory for warning flags, and looks for distinctive extracurriculars. Objectives and skills sections are skipped because they often contain unproven claims or misinformation. If a candidate moves to a second pass, the manager spends another 15 to 30 seconds reading in-depth job history for the past two or three jobs and checking educational background.

An intern described his work as 'planned, designed, and coordinated engineers' efforts for the development of a mission-critical system', which is dismissed as résumé mumbo jumbo because it conveys no actual specifics.

To survive automated filters and brief human glances, a résumé must be formatted to withstand plain-text conversion, avoid cover letters, embrace honest buzzword compliance, and provide a hook. Candidates should convert their résumé to plain text to ensure sections and dates remain cleanly formatted. Cover letters should never be included because recruiters and managers do not read them. Job seekers should embrace honest buzzword compliance by including specific technical keywords like Java or C++ that recruiters search for, provided they can discuss them at depth. Furthermore, subtle visual formatting differences can keep a reader engaged, but complex designs will frustrate an engineering manager.

• Convert your résumé to plain text to test if sections and dates remain cleanly formatted.
• Never include a cover letter.
• Include specific relevant keywords and buzzwords to pass initial recruiter searches.
• Avoid any keyword or buzzword you are not comfortable discussing at length.
• Keep to standard sections and avoid overly complex visual designs.

A college candidate successfully grabbed attention by putting a subtle gray box around each section heading, while another used a nice combination of serif and sans serif fonts.

Hiring managers evaluate phone screens based on communication flow, professional friction handling, overall feel, and whether the call ends with specific, actionable next steps. At the close of a 30-minute phone screen, the manager runs through a mental checklist. They check if there were long awkward pauses indicating poor tuning, how adversarial interactions were handled when opinions differed, and the overall subjective feel of whether the conversation flowed. Finally, they look for specific next steps such as an invitation for an onsite interview rather than vague stalling, which signals a successful screen.

• Check if long, awkward pauses occurred during the conversation.
• Evaluate how adversarial interactions or differing opinions were handled.
• Assess whether the conversation flowed and felt natural.
• Look for specific, actionable next steps at the close, and ask for them if the interviewer stalls.

An author's anecdote highlights that if a candidate is willing to pick a fight during a 30-minute phone screen, it raises warning flags about how they will behave inside the building.

Resignation Checklists

Resigning from a company requires strict adherence to transition rules to protect one's professional reputation, maintain valuable network connections, and avoid the trap of short-timer's disease. When resigning, employees often feel guilty and fall prey to short-timer's disease, leading them to make impossible delivery promises or volunteer for post-departure work. To protect their network and legacy, resigning employees must follow specific rules: do not promise what cannot be done, respect and maintain key relationships from lunch crowds or email folders, update the list of trusted past coworkers for future ventures, avoid taking cheap or scathing parting shots via email, and refuse excessive notice periods that act as professional cruel and unusual punishment.

• Rule #1: Don’t Promise What You Can’t Do.
• Rule #2: Respect Your Network by maintaining touch with key contacts.
• Rule #3: Update 'The Crew' list of trusted people you would hire at a start-up.
• Rule #4: Don’t Take Cheap Shots or send scathing parting emails.
• Rule #5: Do Right by Those Who Work for You and with You by providing written reviews.
• Rule #6: Don’t Volunteer to Do Work After You Leave unless charging a high price.
• Rule #7: Don’t Give Too Much Notice to avoid extending organizational stress.

At Borland, the author agreed to finish an import/export engine feature before leaving, realized he had six weeks of work inside a two-week window, and ultimately failed to complete it while his boss noted that no one thought he could do it anyway.

10 Key Ideas

1. Keep a notebook with you at all times and write down anything that sounds remotely interesting to avoid informational vacuums.
2. Have conversations in a common, familiar language of a friend rather than corporate speak to maintain employee trust.
3. Make an off-site at least two days long to allow a bright-and-shiny inflection point after a night of sleep.
4. Protect disruptive hackers who build novel things outside the mainstream to balance the rigid predictability introduced by growing management processes.
5. Watch closely for employee boredom by observing routine changes, directly asking if they are bored, and actively listening to understated admissions.
6. Spelunk the caves of your team members by walking to their offices and identifying their hoodie-like obsessions and physical cues to protect their focus.
7. Convert your résumé to plain text to test if sections and dates remain cleanly formatted while avoiding cover letters entirely.
8. Assess whether a phone screen conversation flowed naturally and look for specific, actionable next steps at the close.
9. Refuse excessive notice periods when resigning to avoid extending organizational stress and falling into short-timer's disease.
10. Update 'The Crew' list of trusted people you would work with again to preserve your professional network and legacy.