Managing Humans
Michael Lopp · 2007
Editorial rating
- Evidence
- 5/10
- Actionability
- 7/10
- Originality
- 6/10
The thesis
Engineering management is about understanding and navigating the peculiar psychology of smart, often difficult people in high-pressure environments. Forget the polished corporate frameworks - real management happens in the messy middle of politics, freakouts, and organizational dysfunction.
Who this is for
New engineering managers at startups or tech companies, senior engineers wondering what their manager actually does all day, and anyone who has survived (or perpetuated) Silicon Valley dysfunction.
My favorite quote
Your job is not to be everyone's friend. Your job is not to make everyone happy. Your job is to move your team forward by identifying and removing obstacles.
Why it matters
This cuts through the likability trap that snares new managers - being respected matters more than being liked.
Do this
Write down one obstacle your team faces that you've avoided addressing because it's uncomfortable. Address it this week.
Start here
Run The Rands Test on yourself - a checklist for management health. Do you have weekly one-on-ones? Do you know what your team is working on? Have you told your team what's expected of them? Can you say "I don't know" when you don't know? If you fail multiple items, fix those before optimizing anything else.
Critical summary
Lopp (aka "Rands") compiled his popular blog posts into a management guide that reads like a series of war stories from the trenches of Apple, Netscape, and various doomed startups. The book is deliberately anti-corporate - irreverent, snarky, and sometimes cynical about organizational dysfunction.
The structure is episodic rather than systematic. Each chapter tackles a specific situation: the one-on-one, the staff meeting, the freakout, the reorg, the layoff, the brilliant jerk. This makes it useful as a reference but less useful as a coherent framework.
What it gets right
- Authentic voice that resonates with engineers
- Engineer personality archetypes (completionists vs. incrementalists, stable vs. volatile) are genuinely useful
- Honest about the politics and dysfunction of real companies
- Practical scripts for difficult conversations
What it misses
- No coherent management philosophy - it's tactical without strategy
- Silicon Valley - centric; less applicable to other industries or cultures
- The snark can feel dated and occasionally grating
- Light on evidence; everything is "in my experience"
- Some chapters feel like extended rants rather than useful guidance
- Missing modern concerns: remote work, diversity, psychological safety
The book is best consumed as "one engineer manager's hard-won lessons," not as a comprehensive management manual.
Key concepts
The Rands Test
A 12-point checklist for management hygiene. Failing multiple items signals systemic problems.
Completionists vs. Incrementalists
Some engineers need to finish everything perfectly; others ship constantly and iterate. Assign work accordingly.
Stable vs. Volatile
Stable engineers deliver predictably. Volatile engineers deliver brilliance unpredictably. Both are valuable; manage them differently.
Free Electrons
High performers who thrive without structure. Give them hard problems and get out of the way.
The Twinge
That gut feeling something is wrong. Trust it, but investigate before acting.
Meeting Creatures
Different personality types show up in meetings - identify them and manage their impact on group dynamics.
Core insights
-
Managers produce through meetings
If you hate meetings, you'll hate management. Your one-on-ones, staff meetings, and skip-levels are your primary output mechanism.
-
Every engineer has a different care-and-feeding manual
What motivates one person demotivates another. Your job is to figure out each person's operating instructions.
-
The information you're missing is in the hallway
Formal communication channels miss most of what matters. Walk around, have coffee, listen.
-
Freakouts are information
When someone loses it, they're telling you something important. Don't react - investigate what triggered it.
-
Your job is to remove obstacles
Not to do the work, not to make friends, not to be liked. Identify what's blocking your team and clear it.
Implementation steps
Today
- Run The Rands Test on yourself: score honestly, identify failures
- List your team by completionist/incrementalist tendency
This week
- Identify your "volatile" engineers and ensure they have sufficiently hard problems
- Schedule informal coffee chats with two team members - no agenda, just listening
This month
- Map the "free electrons" on your team; are they getting enough autonomy?
- Address one obstacle you've been avoiding
Ongoing
- When you feel "the twinge," investigate within 24 hours
- Review your meeting portfolio monthly: cut one, improve one
Suggested 30-day practice plan
An editorial application plan created by Monolithic Vault - an interpretation of the book's ideas, not part of the original book.
- Day 1
Take The Rands Test; write down your failures
- Day 2
List your team by engineer archetype (stable/volatile, completionist/incrementalist)
- Day 3
Schedule two informal "hallway conversations" (coffee, walk, lunch)
- Day 7
Address the biggest obstacle you've been avoiding - have the conversation
- Day 14
Identify your free electrons and assign them harder problems
- Day 21
Fix one Rands Test failure (e.g., start consistent one-on-ones if missing)
- Day 30
Re-run The Rands Test; compare to Day 1
Free PDF summary
Take this analysis with you: a designed two-page field-notes sheet with the thesis, my favorite quote, the key concepts and core insights, and the full 30-day checklist. Print it or keep it - free, no signup.
Go deeper
If this analysis earned your attention, the full book goes further than any summary can. The original is always the primary source.
