"Most people actually want to contribute results, not cause headaches."
I heard that line somewhere in the first hour—right as the Caltrain doors jammed at the Palo Alto station—and I almost laughed out loud. Because honestly? Tell that to the senior engineer who just refactored our entire authentication service without a ticket because he "felt like it." Or the PM who thinks "ASAP" is a valid deadline for a three-week feature.
But here I am, listening to Alan Willett try to convince me that these people aren't actually trying to ruin my life. (Skeptical? Yeah, me too.)
Debugging the Manager (Ouch)
I picked this up expecting a tactical guide on how to manipulate difficult people into doing what I want. Or at least how to fire them without getting sued.
What I got was... well, kind of a bait-and-switch. But a useful one.
Willett—who is a tech industry insider, thank god, so he understands the specific flavor of ego I deal with daily—basically flips the script. The premise isn't "how to fix them." It's "how to fix your interface with them." Turns out, a lot of the "unleadable" behavior is actually a reaction to ambiguous leadership.
So I'm listening to this while staring at a spreadsheet on my laptop, and I realize: The bug isn't in their code. The bug is in my documentation. QBQ! The Question Behind the Question hammers this same point home—sometimes the problem is looking back at you in the mirror.
It's humbling. If you want a book that just validates your annoyance with your team, this isn't it. This is work. It forces you to examine your own "situational awareness." (Which is corporate speak for "read the room, Sarah.")
Tom Parks at 1.75x
Usually, business narrators fall into two categories: The "Hype Man" (too much coffee) or The "Professor" (puts you to sleep). Parks is neither. He sounds like that one VP of Engineering who actually knows how to code and has emotional intelligence. You know the type? Rare breed.
His delivery is clean. Super clean. I listen to business books at 1.75x speed by default because most of them could be blog posts. Parks holds up perfectly at high speed. He doesn't over-dramatize the "scripts" for feedback sessions, which is crucial because those sections can get cringey really fast if the narrator tries too hard.
He sounds credible. Like he's actually had these uncomfortable conversations before.
Is the ROI There?
Look, it's under 6 hours. That's basically three days of commuting for me.
The ROI is positive, but manage your expectations.
If you're dealing with a genuine clinical narcissist or a sociopath, this book is too nice. It assumes a baseline of rationality that some people just don't possess. But for the standard "Mavericks" and "Divas"—the brilliant jerks we love to hire in Silicon Valley—the scripts are actually usable. Dare to Lead also delivers on practical frameworks for tough conversations, though Brené Brown leans heavier on the vulnerability angle than Willett does.
I literally used one of the feedback frameworks on a junior dev yesterday. I didn't get an eye-roll. I consider that a victory.
Kevin (my boyfriend) asked if I was "leading the unleadable" when I asked him to take out the recycling. I told him to read the book. He declined.
Who's This Actually For?
Queue it up if you manage technical people who are brilliant but exhausting, and you're willing to admit you might be part of the problem. Skip it if you need help with truly toxic personalities—Willett assumes good faith that some folks just don't have.
Bottom line: It's practical, it's short, and it doesn't waste time with fluff. Just be prepared to do some self-reflection you didn't ask for.
