1. Introduction: In the Age of Technology, People Are What Really Matter

Scaling software products today is harder than ever. Michael Lopp, an engineering leader at Apple, puts it this way:

"The market is incredibly crowded right now. Whatever you think of, ChatGPT can make it real within three hours. The democratization of product is a great thing that gives everyone a chance — but it also makes things genuinely difficult."

Amid these changes, debate rages about the role of engineers. Do you have to learn to code, or should you focus on other skills? Even if AI writes the code, do people still matter in the end?

Lopp is unequivocal:

"What matters in the end is good judgment and excellent operations. Who makes decisions, and how those decisions get made — that's what's at the core."

In other words, no matter how far technology advances, people are the center. Lopp has practiced people-first engineering leadership at Apple, Borland, Netscape, Palantir, Slack, and beyond, and from that experience he offers practical advice on organization, product, and leadership.

2. Three Practical Tips for Building a Strong Engineering Organization

2-1. Tip #1: Encourage "Wolf Time" 🐺

The first thing Lopp emphasizes is "wolf time."

"The ideal breakdown of an engineer's time is 71% on clear, defined work and 29% freely exploring wherever inspiration leads."

That 29% is creative time that can't be measured or explained. It's time when no manager or product team interferes — time for engineers to explore whatever they find interesting on their own terms.

"I tried to formalize this at Palantir and completely botched it. The moment we called it the 'wolf team,' everyone wanted to join, and all we got were fights about who got in and how we'd evaluate it."

So Lopp builds this culture through informal conversation instead:

"You walk up to an engineer and say, 'That thing you're working on — that's a genuinely great idea. Keep going.' That single sentence sends ripples through the entire organization."

He also holds open idea-sharing sessions for an hour every Friday. "People need to know this kind of time is allowed. If they don't, they'll sneak it in between meetings, and you'll never get anything truly meaningful out of it."

Key takeaways:

• 71%: Defined work
• 29%: Creative exploration (wolf time)
• Build the culture through informal encouragement and conversation
• Run open idea-sharing sessions

2-2. Tip #2: Make Debate a Daily Practice 💬

Strong organizations are like a three-legged stool — engineering, design, and product balanced equally.

"Engineering, design, and product matter equally. Product and design carry the customer's story and simplify the user experience."

Debate is essential to this kind of collaboration:

"When teammates argue back and forth — 'No, this is a design problem,' 'No, it's a product problem' — that's exactly the process that produces great products."

Lopp admits that a culture of debate isn't easy:

"A debate culture is genuinely hard. Your ideas keep getting torn apart by people smarter than you. But without that friction, you'll never avoid garbage outcomes, and you'll never build something that lasts."

He also stresses that arguing with leadership should be encouraged:

"I love hearing stories where an employee argued with a founder and changed the direction of the company. This culture never gets written down — it's built organically through how leaders behave."

Key takeaways:

• Balance between engineering, design, and product
• Encourage regular, open debate
• Foster a culture where arguing with leaders is welcome

2-3. Tip #3: Build a Scalable Operating System ⚙️

Creating great products and organizations requires sound judgment and solid operating structure.

Lopp explains what accountability really means:

"Most people think accountability means 'I get punished if I don't deliver what I promised.' But real accountability is 'Being able to explain what I'm doing and why.'"

In other words, the ability to clearly articulate the reasoning and context behind decisions is what lets an organization grow.

"A decision made with sound judgment can withstand scrutiny, can be explained, and can earn the agreement of the people involved."

An operating system means clearly understanding the people (inputs), the product (outputs), and how the two connect to produce good outcomes.

"Building a product means building the company that makes that product. 'We're a startup, so we can cut corners' isn't an excuse. In the end, you're building a company, an operation, a scalable system."

Key takeaways:

• Accountability: Explain not just results, but the reasoning and context
• Operating structure: Predictable and understandable processes
• Recognize that you're building the product and the company at the same time

3. How to Strengthen the Relationship Between Engineering and Product 🤝

The relationship between engineers and product teams is an age-old challenge — and one that must be solved in order to build great products.

A bad product manager makes engineers lose interest in what they're actually building.

A good product manager helps engineers understand why they're building it — the full context.

Lopp says:

"Engineers are the people who figure out how. Product is the team that explains why. When an engineer says 'I'm doing it because product told me to,' it genuinely makes me angry."

"You cannot let engineers give up on understanding the why. They're the ones building it with their own hands — they absolutely need to know the reason."

He also shares an experience from Slack:

"Shortly after joining Slack, I asked, 'Why doesn't Slack have a block feature?' Co-founder Stewart Butterfield explained a clear product philosophy: information should be visible to everyone. If you add blocking, the community becomes political and loses its essence."

Key takeaways:

• Help engineers understand the why
• Product teams should share the full context and vision
• Use questions to check for understanding

4. What Makes a Great Leader? 👑

Lopp sees understanding people as the core of leadership — more than technical ability.

"Wherever I go, I encounter completely different people. Learners, the curious, pattern-seekers — there are so many different kinds of human beings."

4-1. Leadership Quality #1: Flexibility (Adaptability)

A leader must be able to adapt based on the situation and the person.

"There's a question I always ask new managers: 'When you receive feedback, how do you change the way you work based on it?' If someone can't do that, it's a serious problem."

Feedback isn't something to fear — it's information you need to grow.

Also, because a team member's real strengths only emerge through actual work together, Lopp reorganizes his team every six months:

"When you work side by side with people, you see who's strong at what. That's when I optimize the team."

4-2. Leadership Quality #2: Storyteller

Lopp hates micromanagement:

"As an engineer, being told exactly what to do is something I genuinely dislike. A great leader doesn't say 'do it this way.' They say, 'Here's a box, here are some ideas inside it — now figure it out yourself.'"

"The leader's role is to 'serve the soup and then let everyone decide whether to eat it as-is or throw in something extra — whatever they see fit.'"

This approach lets team members make their own decisions and grow into better leaders themselves.

4-3. Leadership Quality #3: Understanding Individual Motivations and Goals

Lopp names curiosity as the ultimate leadership quality:

"As a leader, you need to know exactly what each person on your team needs in order to grow. If that's too much, at the very minimum you should be curious enough to wonder."

For example:

• Engineers who love technical challenges get a steady stream of hard problems
• Employees motivated by compensation get their bonuses reliably delivered

"You need to know each person's 'core motivation.' Leaders must keep investing in that and creating opportunities for growth."

Lopp constantly asks "Why?" to understand each team member's behavioral patterns and motivations.

5. Conclusion: The Essence of Successful Engineering Is People 🧑‍🤝‍🧑

The message that runs through all of Lopp's experience and advice is: "Successful engineering ultimately depends on the dynamics of people."

"In the end, an engineering team is a vast tapestry woven together from countless individuals full of personality. The effort to deeply understand how they interact is the first step toward building an organization that can bring a product's value out into the world."

Key Concept Summary

• Wolf time: Creative free time for exploration
• Debate culture: Encouraging open discussion and even arguing with leaders
• Accountability: Explaining not just outcomes but the reasoning and context behind them
• Operating structure: Predictable and scalable processes
• Sharing the why: Helping engineers understand context
• Flexibility: Changing how you work in response to feedback
• Storytelling: Inspiring through narrative rather than directives
• Understanding individual motivation: Knowing each person's growth desires and drivers

Following Lopp's experience and advice through to its conclusion, you're reminded once more that even in the age of technology, people are at the center. Here's to hoping that this kind of human leadership and culture takes root in your organization too. 🚀