Jan 25, 2024 · 1h 4m · in-depth
The human side of world-class engineering leadership | Michael Lopp (Apple, Palantir, Slack)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of In-Depth, veteran engineering leader and author Michael Lopp shares actionable frameworks for managing human dynamics, balancing structured execution with creative autonomy, and scaling high-performance engineering teams across hyper-growth tech companies.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Brett holds 13.6% of the talking time here. How this is scored →
Brett as informed peer 4.0 Guest teaching 5.5 Guest disagreement 1.8 Brett pushing back 1.5
speaking balance: gold is Brett, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 26:58 Reframing micromanaging founders
Lopp immediately rejects Brett's premise regarding command-and-control founders, defending visionary CEOs as intellectual sparring partners.
Hardest push from Brett ▶ 26:35 Challenging autonomy against famous micromanagersBrett directly challenges Lopp's collaborative autonomy philosophy by pointing out several companies Lopp worked at were led by notorious top-down micromanagers.
Biggest teaching moment ▶ 52:30 Etymological definition of accountability and sound judgmentLopp breaks down the misconception of accountability, educating the host on giving account rather than punitive liability.
Brett holds their own ▶ 35:20 The Benjamin Button management paradoxBrett sharply catches Lopp's paradox of becoming more directive and prescriptive with age, coining the Benjamin Button comparison that Lopp affirms.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Brett as informed peer | Guest teaching | Guest disagreement | Brett pushing back | Why |
|---|---|---|---|---|---|---|
| Tom Paquin's Life-Changing Career Advice | 0 | 0 | 0 | 0 | Introduction teaser and monologue from host Brett Berson setting up Michael Lopp's background and episode themes. No interactive dynamic occurs. | |
| Early Career Foundations at Borland Software | 4 | 3 | 1 | 1 | Brett asks about Borland Software's historical significance and notes its role as an early talent aggregator. Lopp agrees and elaborates on Borland's engineering-first culture. | |
| Why Building Software at Scale Remains Difficult | 4 | 5 | 2 | 2 | Brett asks why shipping software at scale remains difficult decades later. Lopp explains that tooling democratized creation but bad operational judgment remains a bottleneck. | |
| Defining Operational Soundness in High-Growth Startups | 3 | 6 | 1 | 1 | Brett asks Lopp to define operational soundness and an engineering utopia. Lopp explains hiring process rigor and the 71% core vs 29% exploratory time split. | |
| Protecting Wolf Time from Excessive Management Metrics | 4 | 6 | 2 | 2 | Brett probes the accounting of exploratory time. Lopp rejects measuring it, sharing how formalizing 'wolf time' at Palantir backfired. | |
| Reconnecting Engineering Teams to the Strategic Why | 4 | 6 | 3 | 1 | Brett asks what teams miss without creative autonomy. Lopp criticizes weak product managers who reduce engineers to mindless executors unaware of the strategic why. | |
| The Triad: Balancing Product, Design, and Engineering | 4 | 6 | 2 | 1 | Brett asks for a definition of excellent product management. Lopp describes the three-legged stool of design, engineering, and product with vigorous internal debate. | |
| Holistic Vision and Slack's Anti-Blocking Philosophy | 4 | 7 | 2 | 1 | Brett asks for specific product responsibilities. Lopp illustrates through Stuart Butterfield's initial refusal to allow user blocking in Slack. | |
| Navigating Visionary Founders and Fostering Rigorous Debate | 5 | 6 | 3 | 4 | Brett challenges Lopp on how autonomy aligns with reputed micromanaging founders. Lopp reframes visionary founders as aggressive debaters who yield when proven wrong. | |
| Company Culture as Shared Mythology and Founding Lore | 5 | 6 | 2 | 2 | Brett highlights Lopp's storytelling approach and asks how culture forms. Lopp explains cultural lore before admitting he is writing a prescriptive leadership book. | |
| Essential Leadership Habits for Scaling Engineering Teams | 4 | 6 | 1 | 1 | Brett points out Lopp's Benjamin Button career trajectory. Lopp details core rules like high-trust 1-on-1s, change management, and relentless communication repetition. | |
| Uncovering Core Motivations and Managing Career Paths | 4 | 6 | 2 | 1 | Brett inquires about tailoring management to individuals. Lopp illustrates uncovering intrinsic motivations, such as a coin-operated administrator at Palantir. | |
| Curiosity, Psychological Modeling, and Managing Personal Triggers | 5 | 6 | 2 | 2 | Brett asks if core drivers trace back to childhood upbringing. Lopp explores his own reaction to being told what to do and how to develop management toolboxes. | |
| Team Composition, Complementary Personalities, and Interview Limitations | 4 | 6 | 2 | 2 | Brett asks if team compositions are planned pre-hire. Lopp argues interviews only provide facades, and true operational reality only reveals itself under fire. | |
| Feedback Receptivity and Adaptability in Engineering Leadership | 4 | 6 | 3 | 2 | Brett asks about malleable engineering traits. Lopp reframes around willingness to adapt, highlighting feedback receptivity as the critical filter for leaders. | |
| Sound Judgment, Accountability, and Reliable Executive Execution | 5 | 6 | 2 | 2 | Brett asks about executive responsibilities and probes the nuance between good and sound judgment. Lopp redefines accountability as giving account and sound judgment as defensible rationale. | |
| Navigating High-Buzz Environments and Avoiding Career Irrelevance | 4 | 6 | 1 | 1 | Brett asks what core lessons connect Lopp's diverse tech employers. Lopp admits fear of irrelevance drives his curiosity to study high-buzz engineering environments. | |
| Executive Maturity and Leading at Scale: Pinterest to Slack | 4 | 6 | 2 | 1 | Brett asks how Lopp evolved across VP roles. Lopp contrasts Pinterest and Slack, noting the realization that executive decisions will always alienate a significant percentage. | |
| Tom Paquin and the Origin of Lopp's Superpower | 4 | 6 | 1 | 1 | Brett asks who shaped Lopp's outlook most. Lopp shares Tom Paquin's insight identifying human dynamics as Lopp's distinct superpower. |
Statements from this episode (26)
Lopp: Borland vastly influenced Microsoft's programming language strategy
“It was all of the languages led the charge on the languages. I would argue vastly influenced Microsoft programming language strategy.”
Contracting out engineering or design for a startup is a disaster
“I think there's literally founders who think cool, but it's going to kind of Contract out the engineering or kind of bring in some con, you know, an upside firm to do this. This is a hugely horrible, bad idea. If you're trying to build software as to not, and …”
Lopp: Building software without product managers is a disaster
“I got an engineer. He's amazing. And I got a designer and he's amazing. We don't really need product people. Like who are these folks? We know what we should do here. That's also a disaster. So like, I'm just picking one of the many sort of. Initial conditions…”
Building successful software is getting harder despite AI and modern tools
“No, I think it's getting harder, actually. Well, number one is because there's so many, when, back in the Barlow days, this is pre-web, this is software that you print on a disk and ship to humans, so you've got, you know, you're shipping it once a year, so th…”
Startups cannot excuse chaotic operations by claiming early-stage product focus
“You don't get to say that you're building a product, but actually what you're building is a company and that's an operation, whether that's the recruiting or the sales or the product process or the quality process or whatever it is. And you're building it to s…”
Scaling requires unglamorous process operators alongside visionaries like Stewart Butterfield
“You need those Stuart Butterfields. You need those Dr. Carps and those sorts of folks, but you also need like that set of folks that are just like turning the crank, building the crank and turning the crank. These are incredibly important. By the way, not sexy…”
Lopp: Autonomous engineer exploration should be continuous, not limited to hackathons
“My utopia is that engineers have a good chunk of time To do what everyone promises us during week of code or these other like one week of things. Hey, I want to build something and demo the CEO. These are great things, but that's an always thing. That's all a …”
Engineering teams should spend 71% on structured work and 29% exploring
“That's my utopia, is that there is that thing that's 71%, that's a real business and real stuff that's really clear, and we're debating it, and we're making it better, but there's also this free time to be kind of a free electron or a wolf or something like th…”
Measuring unstructured engineering time destroys the conditions for creative invention
“There is no accounting. Because it's, the moment we do that, then the project managers show up and they say, cool, have you done your wolf time? Great. Check. Let's do that. Thanks so much. Great. Good job, everyone. Now we're operationally sound. It's the sho…”
Operationalizing unstructured engineering innovation time at Palantir was a huge disaster
“I tried to operationalize this at Palantir and it was a huge disaster for most of the reason I kind of disimplied. I gave it a title. I said, this is how you achieve this and this is how we will measure this. And it suddenly became this gameable thing where ev…”
Google's famous 20% time policy was gamed and is no longer used
“I think even the Google thing got gamed. No one uses it now.”
Lopp: Bad Product Managers Strip Engineers of Creative Agency and Invention
“The bad ones create a scenario where engineering doesn't feel like they have a vote in what gets built. And the, this 29% time that we're talking about here is one of my countermeasures to that, in that an engineering culture where they don't feel they can inv…”
Lopp: Consumer software development requires an equal triad of product, design, and engineering
“Consumery software, which means you're building a software for regular humans. I would argue you have equal parts engineering, design, and product. Products there to tell the story of the customer and to influence, like, to think like the customer, to think si…”
Notorious visionary tech leaders will quickly concede when proven wrong
“Every leader that you just referred to, every single one, when I'm right, and they're wrong, and I can convince them of that in whatever scenario, they understand that. They go, yeah, well, yeah, shut up. You're right. Stop. I got it. I got it.”
Lopp: Visionary CEOs foster debate cultures to challenge their ideas
“That is part of the culture of these companies that you're talking about is that there is that, that debate culture that the CEO, she or he has created because they have a vision. They want to do the thing, but they also want their brightest and their talented…”
Company culture is defined by early founding behavior, not written values
“People try to write it down and they say, Hey, here are values and sort of thing, but that's not what it is. It's like, it's the early ways that their founders and the company treated each other.”
Lopp: Directive leadership helps people by giving them the initial momentum to start
“I think a lot of people want to be told what to do. Oh, I just threw up in my mouth. And I don't, I bet these people don't even think that, but I think it gets you started. Right? It's not, you're actually not going to do it. I'm gonna say, hey, go do this thi…”
Managers should encourage employees to leave Slack once they outgrow it
“And here's a controversial one. There's times we spent a year. I'm like, you don't need to be here anymore. You have learned everything that you're going to learn here at Slack. It's time to go somewhere else. And I wouldn't say it like that, but there's truly…”
Job interviews only reveal a facade compared to real work pressure
“It's not enough time and you don't, you got to see someone with bullets shooting over their heads to see who they truly are. It's fine. Interviews are great. You learn quite a bit, but like I've been trying for this forever. It's kind of like root out and I'm …”
Unsolicited back-channel references are far more insightful than candidate-provided ones
“I think you can learn from background. Checks, but there are people that are, they're picking the people that they're telling to you. You gotta do like unsolicited ones are actually the ones that are actually interesting because someone who hates them tells yo…”
Accountability means explaining your rationale, not being punished for mistakes
“Accountability, if you ask most people what accountability means, they say, well, it means if I don't do what I said I was going to do, I'm going to be in trouble. It's not what accountability means at all. Accountability means to give account, to give the sto…”
Lopp: Great Leaders Need 'Sound' Judgment, Not Just 'Good' Judgment
“Sound judgment is judgment which is, maybe you won't agree with it, but it is explainable, discernible, and you understand why I'm choosing to do what I do. And the reason good sounds bad, it's like, good sounds like I'm selling you on it. Like, this is a good…”
A tech professional or company can become completely irrelevant in two years
“I'm deeply afraid of becoming irrelevant and it just, it can happen in two years. You can be at that place. That's so totally not relevant anymore.”
It takes three full years to become effective in a leadership role
“You're not, you get a new role. You're not good at it for three years.”