10 contrarian leadership truths every leader needs to hear | Matt MacInnis (Rippling)

28 Dec 2025 · 1 h 36 min · 38 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Lenny's Podcast Episode Notes

Episode Title

10 Contrarian Leadership Truths Every Leader Needs to Hear

Guest

Matt MacInnis, Chief Product Officer at Rippling

Episode Overview

In this episode, Matt MacInnis shares insights on leadership, product management, and the importance of maintaining intensity in a rapidly evolving business environment. He discusses ten contrarian truths that challenge conventional wisdom, emphasizing the need for extraordinary effort in achieving extraordinary results.

---

Key Concepts and Discussions

  1. Extraordinary Results Demand Extraordinary Efforts
  2. Core Principle: Achieving exceptional outcomes requires being uncomfortable and pushing beyond the comfort zone.
  3. Key Takeaway: Remind teams that if they are comfortable, they might be making a mistake. Great achievements come from relentless effort.
  1. Deliberate Understaffing
  2. Philosophy: Matt advocates for deliberately understaffing projects to avoid politics and inefficiency.
  3. Impact: Overstaffing leads to distractions and less focus on priority tasks, creating waste and slowing down progress.
  1. Transitioning from COO to CPO
  2. Observation: Matt discusses his transition and the surprises he faced in leading product management.
  3. Learning: He emphasizes the importance of understanding product management and refining processes to improve product quality.
  1. High Alpha, Low Beta Framework
  2. Definition:
  3. Alpha: Outperformance relative to an index.
  4. Beta: Volatility of a person or process.
  5. Application: High alpha individuals are valuable during product development phases, while low beta processes are preferred in operational contexts.
  1. The Reality of Product-Market Fit
  2. Insight: Founders often overestimate their product-market fit; true fit is clear and undeniable.
  3. Advice: Founders should consider quitting if they don't see clear signs of success, rather than prolonging a failing venture.
  1. Fighting Entropy in Organizations
  2. Energy and Intensity: Leaders must infuse energy into their organizations to combat entropy, which leads to decay and inefficiency over time.
  3. Leadership Role: The intensity of the founder must be mirrored throughout the organization to maintain high performance.
  1. Feedback and Escalation
  2. Culture of Feedback: Encourages open communication about issues, emphasizing that withholding feedback is selfish and detrimental to team growth.
  3. Escalations: They are viewed as gifts that can lead to improvements; leaders should welcome escalations from customers and team members.
  1. The Role of AI in Business
  2. Future of SaaS: Highlighting a shift from point solutions to integrated platforms that leverage AI and first-party data.
  3. Insight: Companies need comprehensive data to build effective AI products; relying on disparate systems can hinder success.
  1. The Importance of Founder's Idiosyncrasies
  2. Unique Insights: Successful companies often reflect the unique qualities and experiences of their founders.
  3. Investment Strategy: Investors should recognize the idiosyncrasies that can lead to the success of startups.
  1. Life Philosophy
  2. Perspective: Life is short and existence is a miracle; this should inspire intensity and purpose in work.
  3. Balance: Maintain a sense of levity and perspective amidst the intensity of business challenges.

---

Key Takeaways

  • Leaders must sustain high energy and intensity to achieve extraordinary results.
  • Deliberate understaffing can enhance focus and productivity.
  • Feedback should be encouraged to foster a culture of continuous improvement.
  • Embrace the unique strengths of founders to drive company success.
  • Perspective on life and business can help maintain motivation and clarity.

---

Notable Quotes

  • "Extraordinary results require extraordinary efforts."
  • "If you ever find yourself in the comfort zone at work, you are definitely making a mistake."
  • "Escalations are a gift."

---

Conclusion Matt MacInnis offers a refreshing and contrarian viewpoint on leadership and product management, emphasizing the need for relentless effort, effective feedback, and a perspective that views challenges as opportunities for growth. This episode serves as a reminder for leaders to maintain intensity while fostering an environment that embraces learning and adaptability.

---

Additional Resources

  • [Rippling](https://www.rippling.com): Unified workforce management platform.
  • [Lenny's Newsletter](https://www.lennysnewsletter.com): For more insights and episodes.

---

Where to Follow Matt MacInnis

  • [X (formerly Twitter)](https://x.com/stanine)
  • [LinkedIn](https://www.linkedin.com/in/macinnis)

Where to Find Lenny

  • [Lenny's Newsletter](https://www.lennysnewsletter.com)
  • [X (formerly Twitter)](https://twitter.com/lennysan)
  • [LinkedIn](https://www.linkedin.com/in/lennyrachitsky/)

For more episodes, visit [Lenny's Podcast Website](https://www.lennysnewsletter.com?utm_medium=podcast#)

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

Extraordinary Results Require Extraordinary Efforts

0:45 to 5:00

Discussing the necessity of discomfort and effort in achieving high outcomes.

“So many people have teams that are not functioning incredibly well.”

Management Frameworks for Effective Leadership

5:00 to 7:00

Exploring effective management strategies to keep teams focused and motivated.

“Talk about why that's so important, what you think people need to hear.”

The Case for Understaffing

7:00 to 11:00

Understanding why deliberately understaffing can lead to better performance.

“engineering team that you've got a triage those are the moments where great players and great teams are separated from good players and good teams.”

The Importance of Staying Hungry

11:00 to 12:00

When teams relax, they risk falling behind competitors.

“So you make your best guess, and then you manage to that best guess, and you learn as you go.”

Learning from Success Rather Than Failure

14:00 to 16:36

Discover why successful experiences provide more valuable lessons than failures.

“The key, though, is that it has to go well.”

Transitioning from COO to CPO at Rippling

16:36 to 19:42

Explore the motivations and challenges behind Matt's move to Chief Product Officer.

“And the reason you're here, recently you moved into CPO, Chief Product Officer at Rippling, which is very exciting and very rare.”

The Importance of Foundational Work in Product Development

19:42 to 22:26

Understand the foundational elements necessary for successful product management and development.

“And that really started about a year ago in sort of I realized I was going to do it and express that to Parker in December.”

Balancing Alpha and Beta in Product Management

22:26 to 28:00

Learn about the dynamics of high alpha and low beta in product roles and processes.

“There is just no excuse as an executive for sitting outside of the mess and thinking you know the answers.”

The Balance of Process and Innovation

28:00 to 28:58

Learn how to balance process and creativity in product development.

“Processes are for decreasing volatility in the output of the system.”

Creating Cultural Change with 'The Pickle'

28:58 to 30:48

Discover how naming conventions can drive cultural change in teams.

“Yeah, so it's actually a really important thing.”
Show all 38 chapters

Navigating Product Quality and Feature Flags

30:48 to 33:14

Understand the challenges of managing product quality and feature flags.

“And so just yesterday, we shipped a product to Parker.”

Hiring for High Alpha and Low Beta

33:14 to 35:20

Explore the hiring frameworks for identifying high alpha and low beta candidates.

“the system with hopefully only a modicum of negative impact on the alpha for how we build product.”

Frameworks for Evaluating Product Candidates

35:20 to 38:58

Learn about innovative interview frameworks for product management roles.

“And so one of the frameworks that I use for this is SPOTAC.”

The Joys of Product Management

38:58 to 41:22

Understand the unique and fulfilling aspects of leading product teams.

“And I've found that to be kind of an eye-opening new thing for me that has been fun.”

Finding Product Market Fit

41:22 to 42:01

Discuss insights on achieving product market fit from personal experiences.

“A lot of times people outside product don't understand these sorts of things.”

Comparing Product Management to Chardonnay

42:01 to 42:38

Learn how product management experiences can parallel personal tastes in wine.

“And one of my favorite wines is, I don't like Chardonnay.”

The Journey to Product Market Fit

42:38 to 46:24

Discover the emotional and experiential journey of finding product market fit.

“There's a line that this venture capitalist whose name I will not mention said, which was that product market fit is a sort of thing where you absolutely know it when you see it.”

The Reality of Venture Capital

46:24 to 46:49

Understand the true nature of VC incentives and their impact on entrepreneurs.

“Everybody's acting in accordance with their incentives in Silicon Valley.”

When to Quit: A Founder's Dilemma

46:49 to 48:24

Gain insights on recognizing when it's time to move on from a startup.

“Everybody's, of course, acting, behaving in accordance with their incentives.”

Understanding Market Receptiveness

49:26 to 53:56

Explore the analogy of drug discovery to explain market receptiveness to products.

“This begs the question of just when is it time to quit?”

Lessons from Notion's Journey

53:56 to 56:00

Analyze the unique path of Notion and the lessons learned from their persistence.

“For me, it was a very liberating mindset because now I just have to find the right drug and I can forget trying to convince the body to develop the binding receptors for whatever it is that I'm building.”

Persistence and Founder's Idiosyncrasies in Success

56:00 to 57:28

Learn how the unique traits of founders contribute to the success of their companies.

“They went to Japan and sat in kimonos and meditated on what they were going to build.”

Investing Insights: The Nature of Success and Failure

57:28 to 59:50

Explore the nuances of venture capital investing, including notable successes and failures.

“They spot that element of spikiness and greatness in a candidate investment, and they convert that to a commitment.”

Power Law, Entropy, and Extraordinary Outcomes

59:50 to 1:02:04

Understand the impact of power law distributions and entropy on business performance.

“And I love to give you names of companies that don't exist anymore because it's self-serving and a horrible survivorship bias to just list the good ones.”

Fighting Entropy: The Importance of Energy in Leadership

1:02:04 to 1:10:00

Discover strategies for maintaining high energy and intensity in organizational leadership.

“They get 10x the reward or 100x the reward.”

The Importance of Intensity in Leadership

1:10:00 to 1:10:59

Learn why being intense and dedicated is crucial for business success.

“And again, this advice comes from where we started, which is this is what success looks like because somebody that is less chill than you is going to find that crack and come after your market.”

The Role of Feedback in High Performance

1:11:00 to 1:13:15

Understand why ongoing feedback is essential for team performance and growth.

“And there's only so long you can maintain that.”

Rippling's Business Vision and Growth

1:13:16 to 1:15:22

Discover Rippling's ambitious vision for creating a comprehensive business software platform.

“No, you went and you found the software that created the data error, and then you found the system that created the software that created the data error, and you solved all that back to the top.”

The Future of SaaS and AI Integration

1:15:23 to 1:18:04

Explore the challenges and opportunities for SaaS in the age of AI technology.

“company has to do, be it AI or manual, traditional GUI based software is like, is who's doing stuff, who owns it, who's accountable.”

Navigating the Challenges of AI Startups

1:18:05 to 1:20:52

Learn about the difficulties AI startups face and the importance of first-party data.

“The answer implied here is this kind of compound startup idea of you need to do a lot of things for people, for them to continue to pay for your software.”

Advice for Founders in the AI Space

1:20:53 to 1:24:00

Gain insights on what founders in the AI sector should focus on to succeed.

“what I'm hearing is it's less about how difficult it is to build the SaaS product.”

Transitioning to AI Discussion

1:24:00 to 1:24:25

Introduction to the topic of AI and its usefulness in work.

“would be bullshit yeah i don't have anything back to my point earlier i don't have like I don't have enough relevant experience in the abstract to like dole out on a podcast on that topic.”

AI as a Thought Partner

1:24:25 to 1:25:59

Matt shares how he uses AI tools to refine communication and ideas.

“And the question is just what's one way you've found AI to be useful in your work day to day?”

Balancing Intensity and Perspective

1:25:59 to 1:28:36

Discussion about the intensity of work and the importance of perspective on life.

“I don't know if you've played with Claude much, but I actually find Claude is better at writing and words and language.”

Lightning Round Introduction

1:28:36 to 1:29:04

Introduction to a rapid-fire question segment with Matt.

“And it's super important as a counterpoint to the intensity that we talked about.”

Book and Media Recommendations

1:29:04 to 1:32:02

Matt shares his favorite books and a recent TV show he enjoyed.

“What are two or three books that you find yourself recommending most to other people?”

Favorite Products and Life Mottos

1:32:02 to 1:34:10

A conversation about favorite products and a life motto shared by Matt.

“Is there a favorite product you recently discovered that you really love?”

Wrap-Up and Final Thoughts

1:34:10 to 1:35:28

Matt shares final thoughts and how listeners can reach out.

“I love for people that weren't watching this YouTube, you like lean really close to the mic to get that, to get that, uh, radio personality voice.”
Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00It is really important to me that we feel that we've deliberately understaffed every project at the company. If you overstaff, you get politics, you get people working on things that are further down the priority list than necessary. That is poison. It's wasteful. It slows you down. It creates cruft. You've been a longtime COO at Rippling. Recently, you moved into CPO, Chief Product Officer at Rippling. Something you talk a lot about is that extraordinary results require extraordinary efforts. If you want to be in the 99th percentile in terms of outcomes, it's going to be really difficult. You got to sort of remind people that if they ever find themselves in the comfort zone at work, they are definitely making a mistake.

0:37It's supposed to be really freaking exhausting. You're a big fan of escalating issues. Fundamentally, the most selfish thing you can do is withhold feedback from someone. When you think a thought that would help someone improve and you avoid giving it to them because it would make you uncomfortable, well, you're optimizing for your own comfort. And it's fundamentally selfish. So many people have teams that are not functioning incredibly well. Teams will always optimize for local comfort over company outcomes. The purest form of ambition and most intense source of energy in the business is the founder CEO.

1:07Every next concentric circle of management beyond the founder CEO has the potential to be an order of magnitude drop off in intensity. That is fucking dangerous. As an executive, as a leader, your job is to preserve that intensity at its highest possible level. You've had a couple of really interesting experiences with your own startup. We talk in Silicon Valley about never quit, but that is complete, absolute venture capital bullshit. Today, my guest is Matt McGinnis, chief product officer and formerly longtime chief operating officer at Rippling. If you don't know much about Rippling, it's a massively successful business, last valued at over$16 billion.

1:46They have over 5 ,000 employees. And Matt has been instrumental to that success. He's also got a really rare combination of brutal honesty, a ton of experience building a very complex and very successful business, and being able to clearly articulate what he has learned really well. Matt shared a lot of insights and advice that I have not heard anyone else on this podcast share, and I left this conversation feeling that every leader needs to hear his advice. A huge thank you to Albert Strashim and Sunil Rahman for suggesting topics and questions for this conversation. If you enjoy this podcast, don't forget to subscribe and follow it in your favorite podcasting app or YouTube.

2:22It helps tremendously. And if you become an annual subscriber of my newsletter, you get a year free of 19 incredible products. An entire year of lovable, replet, bold, gamma, innate, and linear, devin, post-talk, superhuman, dscript, whisperflow, perplexity, warp, granola, magic patterns, raycast, chap, urd, mobbin, and stripe atlas. Head on over to Lenny's newsletter.com and click product pass. With that, I bring you Matt McGinnis after a short word from our sponsors. This podcast is sponsored by Google. Hey folks, I'm Amar, product and design lead at Google DeepMind. Have you ever wanted to build an app for yourself, your friends, or finally launch that side project you've been dreaming about?

2:59Now you can bring any idea to life. No coding background required with Gemini 3 in Google AI Studio. It's called Vibe Coding and we're making it dead simple. Just describe your app and Gemini will wire up the right models for you so you can focus on your creative vision. Head to ai.studio slash build to create your first app. This episode is brought to you by Datadog, now home to EPPO, the leading experimentation and feature flagging platform. Product managers at the world's best companies use Datadog, the same platform their engineers rely on every day, to connect product insights to product issues like bugs, UX friction, and business impact.

3:36It starts with product analytics, where PMs can watch replays, review funnels, dive into retention, and explore their growth metrics. Where other tools stop, Datadog goes even further. It helps you actually diagnose the impact of funnel drop-offs and bugs and UX friction. Once you know where to focus, experiments prove what works. I saw this firsthand when I was at Airbnb, where our experimentation platform was critical for analyzing what worked and where things went wrong. And the same team that built experimentation at Airbnb built Epo. Datadog then lets you go beyond the numbers with session replay.

4:09Watch exactly how users interact with heat maps and scroll maps to truly understand their behavior. And all of this is powered by feature flags that are tied to real-time data so that you can roll out safely, target precisely, and learn continuously. Datadog is more than engineering metrics. It's where great product teams learn faster, fix smarter, and ship with confidence. Request a demo at datadoghq.com slash Lenny. That's datadoghq.com slash Lenny.

4:42Matt, thank you so much for being here and welcome to the podcast. Thank you for having me. I want to start with something that I know is really important to you, something you talk a lot about that I don't think people hear enough on podcasts like this, which is that extraordinary results require extraordinary efforts. Talk about why that's so important, what you think people need to hear. I mean, this is a term, that phrasing I actually attribute to a friend of mine, Dan Gill, who's the chief product officer at Carvana, which as a company also doesn't get enough credit for how much of a tech company it actually is.

5:16Super interesting. And I think as a general framework for me, not just, and a lot of what I say with you today is not really specific to product in any way. We should actually talk about that. It's like the product function is an instantiation of like the general concept of management. Like being a chief product officer is not that different from being a chief whatever officer, you have to apply the same frameworks and concepts to get people to achieve goals together. But one thing that is like absolutely universal that I think we honestly, I think we forget it in Silicon Valley or a lot of people don't sort of internalize it is that if you want to accomplish something truly extraordinary, if you want to be in the 99th percentile in terms of outcomes, it's going to be really difficult.

5:56Like it's going to be really uncomfortable. And you got to sort of remind people of that, that if they ever find themselves in the comfort zone at work, they are definitely making a mistake. Like they have definitely screwed up somehow. It's not that an extraordinary effort is sufficient to an extraordinary outcome, but it is 100 % true that it is necessary. And so I do use that framework as a sort of guiding principle in my own leadership. To make this even more real for people, what are examples of moments that were extraordinarily hard? It is not about any sort of grand single story. I think the truth, the story is actually told through a thousand little things.

6:37And so for me, the story is told through a thousand Jira tickets, not through a thousand grand events. the extraordinary effort thing is is is an reminder that like it's supposed to be really freaking exhausting it's supposed to be so like on friday night when you get hit with an escalation on friday night when you get sort of you know hit with a bunch of um new bugs from someone in the engineering team that you've got a triage those are the moments where great players and great teams are separated from good players and good teams. And it's so easy to say this at a company like Rippling because we're winning.

7:20As a company, for all of our foibles, and we should spend time today talking about where things are not perfect and not great, but the growth rate of the company on the revenue foundation that we have is extraordinary, really, really compelling. And it gives you as a leader the air cover to get up in front of your team and say, hey guys, I need the last ounce of oil that you've got left. And if your company's not growing very quickly, if things aren't that great, if your growth rate is 30 % or 40%, it doesn't feel as good as a contributor in that business to lean in and give everything you've got on Friday or Saturday or Sunday because you don't know that it's going to yield much.

7:58And so extraordinary results, outcomes demand extraordinary efforts. But if there's no chance at an extraordinary outcome, it's very hard to get the extraordinary effort. And so I like to remind people at Rippling, at least, that it's so rare to have the opportunity to be able to be a part of a team where the extraordinary effort that you do put in on Friday or whatever, whenever it is, is actually contributing to an extraordinary result. It's a very special and rare thing, And it gives me a superpower as a leader because I can lean on that when I, you know, when I'm wringing the oil out of somebody who's in the bored and tired zone.

8:38I saw the same thing actually at Airbnb with Brian Chesky. It always felt like things were going great. And like maybe we could take a break after something we shipped was killing it. And it always felt like the opposite. It always felt like how do we press the gas pedal further? How do we go faster? How do we go bigger? There's never like a moment to take a break. I spent seven years at Apple and learned under Steve Jobs, you know, when he was the CEO learned what we called the death march, which is what we did to the engineers. It was like, as soon as you shipped one version of the iPhone, like you were just immediately thrown into the into the pit of building the next one.

9:16And there was no break. It was just, it was just relentless. And talk about an extraordinary outcome. At the end of the day. uh there is no relief it just like every in a competitive market and and if the market is valuable it's competitive no question if you leave anything on the field if you sort of leave a crack for your competitor like 100 chance they're going to go fill that crack and so you have to be relentless there can be no relaxation of the organization it doesn't mean people can't come and go or people can't take vacations or sort of live their lives of course and you can't it's not like people are human beings.

9:52You can't grind the individuals down, but the team as a collective group of people has to be sort of on the ball all the time. There can't be a break. And if you leave one, you're just begging for the slightly more hungry competitor to come in and eat your lunch. And, you know, that's the beauty of capitalism. Also, very counterintuitively and maybe the more optimistic perspective here is when you do give your team space to just twiddle their thumbs, bad things start to happen. Morale actually dips in my experience. People get distracted. They're like, oh, what are we even doing? It's not interesting.

10:30I find that keeping people busy and motivated and fired up, even though you may think they'll be happier taking a many week break and slowing things down, I find they get more. Morale actually goes down in those moments. So here's a management framework that I use fairly often. As an executive, you don't know how to get any decision exactly right. It's not knowable. You don't know how much budget to allocate. You don't know how many people to put on a project. You don't know how to set a deadline for when you're going to ship something. But of course, you have to set some default. So you make your best guess, and then you manage to that best guess, and you learn as you go.

11:06because in software development and in business in general, everything's emergent. These are not things that are knowable top down or a priori. And so you take a best guess. And knowing that you're not going to get the right answer, you need to decide whether oversteering or understeering relative to your perceived midpoint is better. And so let's talk about staffing. Like when you staff a project, is it better to overstaff or is it better to understaff, knowing that you can't get it right. Well, it's better to understaff. If you overstaff, you get everything you just said. You get politics, you get people working, I think most importantly, on things that are further down the priority list than necessary.

11:50You have like 20 things on a stack rank list and like, you know that you got to do the top five, but the next 15 down, it's kind of ambiguous, but you've overstaffed the project. So like the next 10 things down are getting worked on before you even know if they're necessary. That is poison. It's wasteful. It slows you down. It creates cruft. And so it's very clear that understaffing is less evil than overstaffing. In this particular framework, the advice is understaff deliberately, always. And then the wisdom, the wisdom element is to know not to under understaff and sort of knowing the difference between those two things.

12:22And so that's the way we work at Rippling. Everyone is constantly asking for more resources. And of course, where we can afford to and where it's appropriate, new resources arrive. But it is really important to me that we feel that we've deliberately understaffed every project at the company. There's a previous guest, I forget who this was. They use this metaphor of they want their team to be dehydrated, to always be wanting more water. And then eventually they're too dehydrated and okay, we need someone to help. Interesting. Yeah. There's a line along the lines of extraordinary efforts I want to make sure I read because I think this is really good.

12:58This may be a way to summarize what you're saying, that good teams get tired and that's when great teams kick the good team's asses. Yes, this was a quote actually from Sunil and he found it from a women's basketball team coach. And it is to my point earlier about like, you got to run the engine in the red line at all times because the minute you let your guard down, the minute you slow down, the minute you relax, the minute you leave a crack for your competition, the great teams are going to come in and kick the good team's ass. And it's like, you know, sports, I'm not a very sporty guy, But sports analogies are sort of irresistible because at the end of the day, business is a game.

13:34You know, none of this matters. We're not going to carry it to the grave. It's like you're here. You're here to do this stuff because it somehow fulfills you while you're on the planet. And I love the sport of business. And I find that that sports, notwithstanding the fact that I watch very little of it, isn't is a very that military. You know, those are very ripe sources of parallel concepts to apply in leadership. I find also those most intense, stressful, long nights are the moments you remember most and remember most fondly back to when you're building something. The key, though, is that it has to go well.

14:06As you said, if you are succeeding and winning, all of this is romantic in the end and nostalgic. Remember that time we built this thing and worked late nights and shipped this thing? If it doesn't go anywhere, you don't feel that. So I think that's a really important component of this is you need to be winning and succeeding. I mean, one thing that I've learned from Parker is Parker's our CEO at Rippling. He, you know, he said, you don't you don't really learn from your mistakes, you learn from your successes. And it's like, you do, of course, and he would admit you learn a bit from mistakes.

14:37But I do think that this is sort of feel good bullshit that, you know, it's like, well, you know, you didn't succeed, but you know, at least you learn something. I've had failures. Like when I look back at the nine years I spent working on Inkling from day one in 2009 until we sold that business to a private equity firm in 2018, up the curve of Silicon Valley coolness, back down the other side into obscurity. Like, of course, I learned and grew a ton during that time. But in now what I think is six or seven years, I'm trying to do the math, seven years coming up on at Rippling. I've learned so much more because I've seen success.

15:13Like I've seen rapid, wild, crazy off the charts success of the business. And it's more informative. Like there's more to glean from seeing how it's done right than there is to glean from seeing how it's done wrong. If I tell you you're going to get on an airplane and one maintenance technician has seen it done right a hundred times and the other maintenance technician has seen it done wrong a hundred times, but he learned from his mistakes. Like it still hasn't had any success himself. I mean, give me a break. There's not even a comparison which plane you're going to feel more comfortable on.

15:39And so I do think that like learning from your mistakes thing is a bit of a feel good trope that actually has very little substance in reality. It's it's and it's why as an early career product manager or it's why like. Frankly, at any stage of your career, when you want to learn, you should join a winning team. Like it's cool to go and start a company at 22. Good luck to you. The odds are not in your favor. but the folks who, when I look at a resume and I see that someone's joined, they were at like really good companies when those companies were super exciting and in crazy growth mode. I'm like, I instantly want to interview that candidate because I want to hear what they learned from being part of a winning team.

16:17And that's, that's sort of one of my go-to heuristics when I'm looking at candidate profiles. And I think it's an under-told trope, like, sorry, not an under-told trope, it's a piece of advice that I don't think people embrace enough in the Valley that like success begets success and you should chase success. Speaking of success and learning, you've been a long time COO at Rippling. And the reason you're here, recently you moved into CPO, Chief Product Officer at Rippling, which is very exciting and very rare. I don't see a lot of COOs moving into product. Let me ask you why that, why did you move into that role?

16:56I feel like you've been killing it at COO. Maybe that's the reason. Be careful what you're good at. And also just what, what are some surprises about this, about moving into product? Because a lot of people imagine what it's like, and then you're actually doing it. The story at Rippling is pretty interesting. And I'll tell it because I think it explains why, you know, why I'm making this transition, but this isn't really about me. I think it's sort of a pattern that your listeners would find useful. In general, your best executives are the ones that you can mostly toss into any challenge and they will bring order to chaos.

17:33They will fix the thing. And I do appreciate the terms that people have used at Rippling for me, you know, talking about McGinnis's injured birds, where at any given moment, some function is in disarray or in jeopardy. And I go and focus very carefully on that function to get it back in order, batting 800 maybe, you know, like not always wild success, but I did that anywhere, everywhere except R &D. I would be where I would, you know, think about helping out with components of the sales organization, like our channel team, or I spent time, you know, building out the recruiting function a few times when it needed to be sort of rethought in response to our growth.

18:21And, but never R &D. And so I sort of, I would have my feet up on the table looking out across the floor at this dumpster fire off in the distance, just sort of emitting smoke and wondering if someone was going to go in and deal with that. And the smoke takes various forms. And when you're growing as quickly as Rippling is growing, it's not always something that necessarily even impacts customers, but it's the sort of thing where you're like, fuck, that architecture is not right. They're not measuring adoption correctly. From the outside, I actually had quite a few criticisms that I could lob in.

18:51And And what happened at Rippling was we made some hiring mistakes. I think the folks that we had in those roles would agree that they weren't the right people. We had a hiring mistake in engineering leadership where the product leader at the time had to sort of run engineering. We subsequently had a mistake in product hiring, and a lot of us had to sort of pitch in. And Parker and I sort of stared at each other through two years of this kind of disarray or this chaos or this agony of things, just never really having good executive leadership over both engineering and product at the same time.

19:24And I remember Parker sort of slumped down in his seat and said, oh, fuck, I have to run another search. And I said, no, like the gig's up, I'm going to go do it. And he really sprung up in his seat. He's like, really? Like, you'll go do that? I'm like, dude, this is what the business needs. And so that's what I did. And that really started about a year ago in sort of I realized I was going to do it and express that to Parker in December. I really took it on in January of 25. And so it's been 11 months of learning. Jumping into the product role when the product function itself, although staffed with really talented people, wildly under understaffed and without a single spiritual leader on top of it to drive consistency and process excellence, had become locally optimized but globally incoherent.

20:15And if you know Conway's law, you are destined to ship your org chart. And so with a locally optimized, globally incoherent team, you had a locally optimized, globally incoherent product experience that needed to be resolved. And so my efforts over the last 11 months have been to establish greater clarity in terms of how we do things around here, better process, better general leadership, hiring and firing. I mean, just doing the sort of cleanup on aisle three that needed to be done, even though, again, a lot of the people in the team were quite talented and doing an excellent job of managing their specific domains.

20:52Jumping into the product role has been quite eye-opening. I feel a little bashful about the naivety of my view from the outside a year ago. Product teams have a hierarchy of needs, and we like to sort of point at the failures to meet elements of that hierarchy higher up the triangle and sort of impugn the failure of that organization for not, as an example, measuring adoption metrics very carefully and not closely tracking those metrics as a means by which to drive execution. When I jumped in, I was like, man, we need to establish some basic standards for test coverage. We need to establish some basic standards for how we do what I call a factory inspection on a product once it's ready to roll off the assembly line.

21:54do we have a checklist for what we call product quality? And what does product quality mean? Those basic things weren't there. And so the idea that we should be spending time measuring adoption metrics is absolute insanity. You're skipping a lot of steps between here and there. And so we have made great strides. And I think it's translating to product quality improvements for our customers. But I feel, as I said, a little dumb for the way I was thinking about it before I jumped into the deep end. There is just no excuse as an executive for sitting outside of the mess and thinking you know the answers.

22:33It's a cardinal sin as an executive to do that. You need to go and see. You'd be in the boiler room. You need to study the system bottom up and develop hypotheses for how to amend the system. And that's what I've been doing. I love hearing this because so many people have teams that are not functioning incredibly well. And hearing from someone that is not a long-time product person come in and try to fix these problems, I think is really useful and interesting for people to hear. So to dig into this a little bit more, was the big lesson and kind of eye-opening moment that there's a lot of kind of foundational work that needs to happen to achieve this outcome that you're trying to achieve, which is measure engagement and adoption well Is it like tracking and metrics and data science?

23:15Is that kind of the lesson there? The lesson is that everything must be done in its time and order. And you can move really, really quickly. You can, you can, there's no sort of excuse not to move with urgency on all of these things, but you got to do them in order. And you have to, you have to lead bottom up. Like you got to lead from the specific circumstances you observe. And I think for me, one of the best things that's happened over the last 11 months is that I've gained a greater trust in my own instincts. That the sort of patterns I've matched across other functions do indeed apply in product.

24:09but I have both the advantage and disadvantage of not having led a product function before and therefore must think about every problem from first principles. I have no choice. I can read shit on the internet. I can like listen to clear thinkers on topics and import their ideas, but I'm very reluctant to import an idea without breaking it down into its constituent parts and figuring out how it applies at Rippling. And so I don't actually give a shit about adoption metrics as a matter of principle. I care about adoption metrics when I care about adoption metrics. Like I realized that that's a tautological statement, but it's like, I'll get there.

24:47And so in certain parts of our product, I really do care about adoption metrics. I care a lot about adoption metrics in our applicant tracking system, our recruiting product, because it's in a really good place from a usability standpoint. It's very well instrumented. It's got like very happy users. It's got an awesome growth profile. And so we should be really focused on the adoption metrics because I think that's going to be an important ingredient to low churn over time. You know, removing friction from the implementation process, as an example, there are other parts of our product where I would say I don't care at all about adoption and am much more focused on foundational things like I said earlier, test coverage or whatever, just to make sure that the thing is stable and good and delivering exactly what it's supposed to deliver once it's adopted.

Read the full transcript

25:27Now that you're on the inside of the product team, what's something that you think people outside of product, say Matt two years ago or other, I don't know, go to market leads, other execs should hear, need to understand about product that they don't until they're on the inside? I'll give you another framework that I like to use. In the financial world, there's this concept of alpha. Alpha is outperformance relative to the index. So that's why you have seekingalpha.com as a very popular website. What they mean by that is you're looking to buy something, some combination of assets that will outperform, let's say, the S &P 500, if that's your benchmark.

26:09So alpha is the outperformance relative to the index. And then you have the concept of beta. Beta is just volatility. Beta is not good. A high beta stock jerks around for no particular reason. It's like discorrelated with the index. It's very high beta. great if you're an options trader, but other than that, it's not really something you want in an asset. And so your ideal stock is a very high alpha, very low beta stock. They don't really come in that shape because alpha and beta tend to be correlated, but that's what you want when you buy a financial asset. So what's the analogy? I think you have high alpha people who are very valuable.

26:47And you also have low beta people who are also very valuable people. Dennis Rodman, basketball player, nut job, very high alpha. And there's room on every team for one. Dennis Rodman is a favorite of mine. It's like you can have one difficult employee who's got a ton of upside. and so this alpha beta thing i use it pretty often when contemplating what kind of person i want and also what kind of process i want so when you're building a product from zero to one you're probably proceed pursuing alpha you're looking for some angle on this market or this customer problem where the product is actually going to provide an outsized return relative to whatever the default solution is when you have a more mature product or if you have somebody in the product operations group or whatever, you probably want a more low beta environment where it's like it cranks it out, it does it very reliably.

27:44Our payroll product, we badly want the payroll product to be very low beta. We really don't want the payroll product to have any unpredictability or aberration. And so we're willing to accept more process. And here's a fundamental principle of design in an organization, which is that processes, processes in a business exist for the sole purpose of lowering beta. Processes are for decreasing volatility in the output of the system. The downside of a process is that it suppresses alpha. And you have to be super, super careful and judicious in the application of process in the product team to know that you're lowering beta in the places where you want to do that without suppressing alpha in the places where you need it.

28:34And so as we've gone through the last year of reforming the way that we build product at Rippling, it's been a game of recognizing those places where I need to implement a touch of process, just a touch. Other places where I need to implement a very clear, rigid process where I don't want alpha, I just want low beta. And so examples of this are, let's say, our product quality list, which we lovingly at Rippling call the pickle. Why pickle? Yeah, so it's actually a really important thing. I think if you want to bring about cultural change in a team, like, look, we have 1 ,300 people in our R &D organization.

29:08It's a big ship that we have to steer. If you want to create a moment that sticks in people's brains and sort of becomes a zeitgeist or something that they latch onto, you got to create an entity, a vessel for meaning, and then you got to fill that vessel with your meaning. A meme, you might say. Yeah, well, sure. A meme is actually a good example of this in common culture. I, in pop culture, I think it's why when people come to the table with ideas from the outside, I welcome those outside ideas. But the first thing I ask the person to do is to tell me what they mean without using those words.

29:43So when someone comes in and says, hey, I want to do this thing on strategy, I'm like, cool, tell me what you mean without using the word strategy. And it forces them to break it down into its constituent parts. And if they can articulate it clearly without using that word, I know that they know what they're talking about. And if they just fumble around with the word strategy again, I'm like, OK, you actually haven't thought this through. And so with the pickle, with the product quality list, it's like I could come up with some generic term for this. But I really want a new joiner at the company to understand that this is an idiosyncratic thing to Rippling.

30:11This is unique to us. You want to understand this thing. I also want it to become a component of common parlance in the day-to-day work of the product management and engineering teams. And so Pickle, as cheeky or silly as it sounds, was deliberately sort of angular or stood out as a vessel I could fill with a particular meaning. And so we have a product quality list. And the product quality list is lightweight in the sense that it just articulates in the simplest ways, the standards we want you to meet when you ship a product. It doesn't apply to every product. Not every line applies to every product, but it's comprehensive and it provides me with a framework for iterating over time as we learn.

30:50And so just yesterday, we shipped a product to Parker. This is part of our process. When we ship a new product, it goes to Parker, who is the big admin for Rippling at Rippling. If you're not aware, Parker is the sole payroll administrator for rippling for all 5 ,200 employees. He personally runs payroll always. There is no exception for all 5 ,200 people. He does complain about it sometimes, but it's a remarkable achievement for the software and perhaps for him. And so he also installs any new app that we're going to install for ourselves because we dog food the hell out of everything we build.

31:22Yesterday, he goes to install this new application. We're about to ship a new app for feedback, allowing people to give one another's feedback in their companies and he installs it and he goes in and it dumps him onto an empty screen and he's like what the fuck is this what is this what's going on like hey wow talk about fail so i um chop another one of my fingers off i'm down to nine and uh i'm like what did we miss what we missed was there was a fucking feature flag fucking feature flag i'm just i'm not allowed to say feature flag without fucking in front of it because like feature flags are the bane of my existence and the worst things in the world that constantly cause problems engineers put one in temporarily and forget it's like shims if you're building a house and the general contractor puts little shims in places and then forgets that they put the shims there and then builds a wall over them and eventually the shim fails and all of a sudden your door doesn't fit like feature flags are super dangerous and need to be managed carefully so fucking feature flags anyway we had one parker installs it they forgot to disable the feature flag he gets a blank screen when he installs the application.

32:26What did I do? My reaction was, ugh, go back to the team, give them direct feedback, tell them not to make that mistake again, but also ask the question, how do we miss this in the factory inspection process? And the answer is, we didn't have any line item in the pickle for feature flags. And so I added a line to the fucking pickle that said, you are allowed to have one feature flag that governs your entire product at ship. It's an extreme standard that might not be achievable, but it's the standard we aspire to. This framework, the pickle, given these lightweight checklists, iterated on consistently in response to everything we learn as we go, constitutes a very nice lightweight way to lower the beta of the system with hopefully only a modicum of negative impact on the alpha for how we build product.

33:21And so that's, you know, you asked me a very simple question. I gave you a very long winded answer, but these frameworks help me design systems that scale, you know, across one going to 2000 technical workers. Wow. Okay. By the way, PICL, is that, is that like an acronym or it's just like, I like this word we're going to call it PICL? Product quality list. Product. Okay. I see. So it's the consonant. Okay. P-Q-L, which how could you pronounce it other than PICL? I'm imagining all your decks have little pickle emojis. The pickle emoji thing, the dancing pickle in Slack. There's a lot of, yeah, it lends itself to a bit of fun.

33:58What I think about is Pickle Rick. Do you get that reference? This is a Rojac test. Okay. So this high alpha, low beta, I love this concept. So the idea is depending on the team, depending on the problem, we need a high alpha, low beta person or actually we're okay with a lot of variance for this specific project. Yeah, we're willing to accept a bunch of volatility in this area in exchange for the upside we get from the creativity and risk-taking of these people or the lack of process that sort of gives them the latitude to do what they want to do. And so when you're hiring, you're looking for, again, is this person low beta or not?

34:29For sure. I mean, it's really quite a useful way. You know, when you meet a candidate and you, I mean, my modus operandi, and I think, you know, with talking about hiring for a second, And I think I've spent a lot of time with teams at Rippling talking about how I hire. And it is born of batting practice. It would be super interesting to actually be able to rewind the tape on my life and sort of contemplate how many candidates I've met in every context. Many thousands, maybe tens of thousands. I don't know. It's a lot of batting practice and a lot of model training in my brain. And so I rely a lot on my intuition, which of course HR people say you're not supposed to do.

35:12That's complete bullshit. If you have a good intuition, you should absolutely rely on your intuition. And what you have to do after you have a reaction to a candidate when you're looking at hiring somebody is you need to decode your intuition so that it can be expressed to other people productively. And so one of the frameworks that I use for this is SPOTAC. It's a very ugly acronym. There's a hat tip to somebody out there in the universe who originally thought of this. It's not me, but I adopted it. And it's that people are smart, passionate, optimistic, tenacious, adaptable, and kind. Those five things.

35:48Six, can't even count. I told you I lost a finger, right, when I made a mistake. So I was down one. Nine to go. Spotac isn't by itself a good top-down framework, but when you're thinking about, oh, why did this candidate just like, why did it not click? Why did I not like them? You go down the list, you're like, oh yeah, I know this person. It's that they were not excited about the idea. They weren't passionate. It's that they talked shit about their previous manager and that they were a victim of the performance of their last two companies. That's what it was. They're not optimistic. you know it's the the framework is super useful to evaluating people and i think the the alpha beta framework is also super useful when you come away from a conversation you're like i like that guy i think he'd be really really good why is it that i don't think he would do a good job on this product in particular and the answer is like this is a high alpha product area and he's a low beta person valuable but definitely not the right fit for this and so i think it's really useful in that context as well i love all these frameworks you're speaking to this audience frameworks frameworks frameworks yeah so high high alpha low beta sometimes high beta is okay spotac um in hiring is there anything else that you find really useful before we move on to a different topic when i first started working in the product organization i was introduced to a an interview framework or an interview tactic that i hadn't really used much at all i think in my career, which is that every product person at every seniority level is given the same case study.

37:26And the case study is extraordinarily difficult. It requires you to think about many, many dimensions simultaneously to think about data propagation issues. It's quite technical. And the rubric that we use to sort of evaluate performance of that case study is it gives you guidance on what for us like an entry level PM looks like what a junior mid-career senior executive PM might look like and everybody comes away from that interview feeling like poop like they had failed it whereas on our side of it we're like wow that person got really far like they saw around three or four corners in a really impressive way.

38:08There was 10 they didn't see around, but they saw around four of the hardest ones. And they were not defensive when we gave them new information that called in the question, the validity of their solution. And they were willing to interrupt us to ask more questions and, and, and like a lot of the sort of basic human interaction models. I, you know, you never think that like giving someone an impossible task and even including the L5 person versus the VP on the same thing would be productive. And let's just say our recruiting team still sort of kvetchis a bit about this and feels like we eliminate people too aggressively at this stage of the interview process.

38:41But I've found the wisdom in it and think it's actually quite useful to give everyone the same simple, complicated prompt and just see, hand them a drill bit, give them the concrete wall and see if they can get a millimeter or an inch into the concrete. You know, they're never going to get all the way through the wall. It doesn't matter. You're going to learn a lot. And I've found that to be kind of an eye-opening new thing for me that has been fun. I mean, look, the joy of product and the joy of product management and the joy of being part of product, I think there's a bunch of joys, actually, if I could give you a sort of running list.

39:11But like one of the big joys is that you get to work with some of the smartest people in software. Engineers are very smart. They're not always the best sort of social entities. Salespeople are awesome social entities. They're not always the best systems thinkers. You go down the list, but the magic of product management is that you kind of have to be talking about the mini CEO. I think it's kind of a stupid misnomer, but there's some wisdom there. And I think the wisdom is that you have to be a polymath. Like you've got to be really good at working with other people. You've got to be good at communications and articulation.

39:46You've got to be good at project management. You've got to be good at the science and the math and the engineering. It's really fucking cool. And so I think one of the great joys of this job for me has been interacting with like the tippity top of the smartest and most polymathic people in the industry. I'll say one other thing about what I love about leading product, which is as a COO, my job was to accept the product as it was and optimize everything around that. My job was to make sure that the product operations, in our business, the interface to the insurance carriers, the interface to the payment entities, the government regulators, that stuff all just sort of worked.

40:26It was to make sure that our sales engine, our marketing engine, all the go-to-market at stuff, like optimized itself around what the product was. It was about recruiting and making sure we got people into work on the product, you kind of go down any function that isn't in R &D. And I had some hand in trying to figure out how to make that function work to the best of its ability, given what the product was. And now that I lead product, I'm like, Oh, wow, this is the high order bit. Not that I didn't sort of understand that. But like, now I really get that product is the high order bit. If you get the product right, it fits in the market.

41:04Everything else gets easier. Finance is easier. Sales is easier. Marketing is easier. Recruiting is easier. Everything gets fucking easier. And so I think the other joy of leading the product function is that I get to set the highest order bit in the business's success to one. This is really great to hear. A lot of times people outside product don't understand these sorts of things. and look down on product a lot of times, especially sales folks, CEOs, a lot of times. I love that you're seeing this and realizing this and recognizing just how important and interesting and challenging this work is and just how awesome PMs are.

41:44As you know, a lot of people are very anti-product manager. Why do we need product managers? We don't need them. Just let everything down, all this process. I have a distinction there, which is I'm anti-shitty product manager. That's exactly how I put it. If you hate product managers, you just haven't worked with a great product manager. Look, I love wine. Wine's one of my things. And I've learned a lot about wine. And one of my favorite wines is, I don't like Chardonnay. And I'm like, no, no, no, no, no. Chardonnays are the most fucking amazing varieties of wine in the world. You just haven't had good Chardonnay.

42:14And there's a Chardonnay out there for you. Product management. It's like, you don't like product management. You think product managers suck. It's like, well, you just haven't had a good Chardonnay yet. Once you have one, you can't unlearn it. you know like let's find that pm asap no let's find that chardonnay but let you have with some chardonnay you met you touched on this product market fit point and i want to double down on this thread you had a you've had a couple really interesting experiences of struggling to find product market fit with your own startup you said you worked on it for nine years you said okay and then with rippling uh complete opposite extreme product market fit up into the right what's something you've learned about just that that you think people maybe don't understand about what it feels like, what it takes to get to product market fit, how things change.

42:59There's a line that this venture capitalist whose name I will not mention said, which was that product market fit is a sort of thing where you absolutely know it when you see it. And therefore, if you don't absolutely know it, you don't have it. And this kind of gets back to my point about learning from mistakes versus successes. It's like, ah, man, over and over again, over the course of the many years that I spent at Rippling, sorry, Inkling. We thought we had it. We thought we had product market fit, maybe, maybe, you know, and in hindsight, with the benefit of now having experienced solid product market fit, it was so, so obvious that we didn't.

43:45And like, I've invested in like 60 companies or 70 companies. I don't know. it's not something I actively do. Um, but, but opportunities by virtue, I think of my, my role at Rippling sort of show up and I talk to lots of entrepreneurs and I love it and I find it super stimulating and I love the fresh ideas. And it's just something I do as a real cherry on top of the sport that I play already. Um, but when I get the investor updates for the guys who've been it for like three four you know years and i read the updates from them that i sent to my investors in 2011 and 2012 i'm kind of heartbroken we talk in silicon valley about never quit but that is complete absolute venture capital the incentive of venture capitalist is to put money into your company and milk you dry.

44:45They never get their money back. There is no way for them to take that investment back. And so the only logical desire that they would have is for you to keep trying against all odds. Because there is the occasional example where someone pivoted from A to X and it was wildly different and it worked. Slack was originally some sort of a gaming company and became corporate chat. Airbnb, maybe. It's like there's some examples of companies having made wild pivots and succeeded, but man, is that rare. I mean, just so exceedingly rare. And I think it's important to remember, I'm 45 years old. We're going to be on the planet.

45:25I mean, the average age of a man in the United States when he dies is something in the mid-70s. I got 20, 30, maybe if I'm lucky, 40 years left on the planet, very conscious of the time that I have. And like, I don't regret what I did at Inkling. I learned a lot. It informed what I do now. I don't think the chapter I'm in right now could have come without the chapters before it. And so it's a, it's a beautiful, wonderful thing that I did what I did. But when I read the investor update and I'm like, you're where I was and you are not getting out of this. the silicon valley try until you die mindset is not pro-entrepreneur it's pro-venture capitalist and i know why that is but i think it's important to say out loud that you should fucking quit you should reset the clock you should reset the cap table because trust me product market fit when it arrives is insane and it's exciting and you should pursue it and never delude yourself into believing you have it when you don't.

46:24It is dangerous and regrettable. How's that for a speech? Beautiful. The anti-VC speech. I got more where that came from. By the way, it's not anti-VC. It's anti-VC propaganda. Everybody's acting in accordance with their incentives in Silicon Valley. The executives, the founders, the venture capital. Everybody's, of course, acting, behaving in accordance with their incentives. And the venture capitalists have very strong enduring incentives that have shaped the dynamic of how Silicon Valley works. There's nothing wrong with that. It's just really, really important to point them out and scream at them for the 25-year-old entrepreneur who has no fucking clue how this stuff works.

47:12Trust me, the 45-year-old entrepreneur or the 50-year-old venture capitalist who have been in the game for a while, they get it. They've observed it. They know what it's like. The system is there to take advantage of the people who don't. Or at least it is the easiest prey for the incentive structures. Not for venture capitalists as individual people who are beautiful and wonder all of them are just really wonderful people. It's just that the incentive structures lead to some real harm, I think, in certain cases. And the thing I find is when you do quit, VCs, I'm always just like, hey, let me know when you're starting your next thing.

47:42I'm excited to invest. They're rarely, unless they're not a great VC, the rarely are they just pissed at you for like, how could you possibly not make this work? That's the thing, like as a founder, when it's time to throw in the towel on your business and you're so obsessed with giving money back to the cap table, I always remind the entrepreneur like, hey, if you're in the seed investing game, your forecast is zero. Your assumption on every investment is that it's going to go to zero. Any seed investor who doesn't take that stance is off their rocker anyway. You know, they're a very bad investor.

48:16Seek investors who play the long game, who want to be in your second and third company and are willing to take a bet on the first one and let it go to zero so that you can get on with stuff. I mean, this is like, I've had that conversation many times. This episode is brought to you by GoFundMe Giving Funds, the zero-fee donor advised fund. I want to tell you about a new DAF product that GoFundMe just launched that makes year-end giving easy. GoFundMe Giving Funds is the DAF, or donor advised fund, supported by the world's number one giving platform, and trusted by over 200 million people. It's basically your own mini foundation without the lawyers or admin costs.

48:52You contribute money or appreciated assets like stocks, get the tax deduction right away, potentially reduce capital gains, and then decide later where you want to donate. There are zero admin or asset fees and you can lock in your deductions now and decide where to give later, which is perfect for year-end giving. Join the GoFundMe community of over 200 million people and start saving money on your tax bill, all while helping the causes that you care about most. Start your giving fund today at gofundme.com slash Lenny. If you transfer your existing DAF over, they'll even cover the DAF pay fees.

49:26That's gofundme.com slash Lenny to get started. This begs the question of just when is it time to quit? You know, people hearing this might be like, oh man, like what are some signs that, okay, it's time to wrap it up. Here, look, history provides us with a clear guide. When you look at companies having hit it big, they hit big pretty quick. It's very, very dangerous to be late to the party. It's very, very dangerous to be early to the party. And the vast majority of the time, that's the problem. You know, like rippling had it been started in 2014 would not be what it is today. I think rippling had it been started today would not be what it is five years from now today.

50:06And so I think like timing is a lot and it's very hard to control for. But when you get the timing right, and the market is real and the product works, product market fit, like I said earlier, it's super clear. And so if I were to pick a number out of a hat just from my lived experience, I think it's very important. One aside, don't ask people for advice. Ask people for relevant experience. If you ask them for advice, they will always give it. But if you ask them for relevant experience, they rarely have any to offer. And if they don't have any to offer, then don't ask for their advice. So ask people for relevant experience.

50:42And I try to do this with my own entrepreneurs when I work with them. It's like, let me offer you whatever relevant experience I have. And my relevant experience on this topic of when to quit is like, I think we could have called it after the second or third pivot, which was somewhere around year four. It is, of course, very important to believe in what you're building and to be persistent. consistent. But there is definitely no shame in saying, look, we pivoted once or twice. It's not catching. I got to go do the next thing. And I think like if you're year four, year five in your entrepreneurship journey, and it's not just obviously a screaming, rip roaring growth story, it's extraordinarily difficult.

51:27This is so extremely rare. So beyond even already the rare scores you're going to face from the outset that now is going to convert to something crazy. So that's hard to hear, I guess. But man, it can be really liberating when you're like, fuck it, I'm going to do this. I have the energy. I'm going to do it again. I'm just going to do it with a clean sheet. That is really helpful. You have this really fun way of describing product market fit around receptors and drugs. Oh, yeah. Yeah. I think this is like a really fundamentally misunderstood dynamic. um when i when founders message me and they're like hey like like my linkedin posts and my tweet for this launch i do it i retweeted i like it whatever nobody follows me on twitter anyways doesn't matter but like i you know i do that and then um but i think to myself like this is not what this is about like this is not this is not how great companies are built it can be a nucleating a nucleating event, but it's not a major thing because nobody cares about your company.

52:27Like your launch doesn't matter. Big fat pull the slingshot back launches amount to the teeniest thimble of water in the ocean of noise about startups and companies. And so you just got to build it brick by brick, bottom up, and these launches don't really amount to much. And so how do you think about that? Like, how do you think about the insignificance of your launch? You think about all the effort you're putting into building a product that you believe is going to have product market fit. Well, if you recognize that the market is immutable, no amount of tweeting, LinkedIn posting, advertising is going to change whether the market wants your product.

53:08It's not, it might raise awareness about your product, but it's not going to change whether somebody wants it. Then you take a different mindset. You have to view your startup as running an experiment in the universe to see what you get in return for that. And this analogy of like drug discovery and binding receptors is like nobody at Genentech thinks they can market their way to better performance inside your body. The binding receptors for that drug, they exist or they don't. And when they build their product, their goal is to find out whether the binding receptors exist. But fate already has decided the outcome.

53:45This is absolutely true of every software product you build. Fate has already decided the outcome. The market's either going to latch onto your product and run with it or it's not. Do not ship the product, find a lack of success, and then try to market your way through that because the binding receptors likely don't exist. For me, it was a very liberating mindset because now I just have to find the right drug and I can forget trying to convince the body to develop the binding receptors for whatever it is that I'm building. What I love about your advice here is you were an early investor in Notion, which is one of the classic stories of it took them, I think it was four years to get to something.

54:20They moved to Japan. They worked on the whole thing. And so is there a lesson from there? Like, is that a rare example where it actually worked? And that's not an example to be inspired by because it's extremely, extremely rare. Let's talk about alpha beta again. Okay. As an investor, you might build a checklist of things you want to make sure are true or false about a company and hope that that's going to yield the kind of like investment success you're looking for. Does it have this kind of founder? Does it have, you know, is it a C corp in Delaware? where boom, boom, boom, boom, boom, boom, boom.

54:51And these checklists are all about what? They're all about suppressing beta. They're about avoiding avoidable mistakes. They're about bringing stability. Jeff Lewis is an investor who has many angular views on things. And I think one of his most enduring phrases is narrative violations. This idea that the common wisdom must be violated in some way by every company that has an outsized success. It is absolutely true. And when I give these general observations on the patterns in Silicon Valley, the most successful businesses inevitably violate something on that list in some really important way.

55:36And so Notion, you can't replicate Notion's success as an entrepreneur. You can't replicate it because you're not Ivan. You can't replicate it because you're not Notion. You can't replicate it because it's not 2010 when they started the company. Do the math on that. Or 2011, actually. These guys stuck with it. They went through hell. They pivoted. They went to Japan and sat in kimonos and meditated on what they were going to build. And by hook slash crook, they got to where they are today as a really wildly successful business in an extraordinarily difficult market where building businesses is virtually impossible in productivity.

56:20It is dominated by Google and Microsoft. Carving out your own niche in that market is just unthinkable. And so I look at Notion as having succeeded by virtue of the narrative violation of persistence. I don't think it's a good idea for very many people. It happened to work for them. And I look at it as being a function of the founding team and their specific idiosyncrasies, The absolute insistence on craftsmanship from Ivan, this is him. That's his thing. The takeaway lesson is not give up or don't give up. The takeaway lesson is certainly not go do what Notion did. The takeaway lesson is that every company succeeds on the foundations of the idiosyncrasies of the founder.

57:11The idiosyncrasies of the founder. Rippling succeeds for almost the polar opposite reasons that Notion succeeds. But in both cases, the companies succeed on the idiosyncrasies of the founder. And so embracing that, recognizing those idiosyncrasies, that's what great investors do. They spot that element of spikiness and greatness in a candidate investment, and they convert that to a commitment. And then, of course, the investor or the good ones accept what they get in exchange from that for the universe, from the universe. I love that we went in this direction. I wasn't planning to talk about your investing career.

57:47Just to give people a reason to listen to this and maybe rewind, and I want to ask another question around investing. What are some other companies you invested in early? First of all, okay, so I sort of hate the question. Like, what are some other companies you've invested in? That's a fair question, but the problem is I'm going to give you a bunch of companies I've invested in that won. You know, that are like really notable. So what I would like to do instead of answering that question, I'm going to give you here, let me, let me give you some, some, like some bait. Like I was one of the first investors in notion.

58:16I was perhaps the first, I don't know, ask Ivan clever, which had a great exit. I was one of the first investors in Zenefits. If you've heard of it, I was before I joined one of the first investors in Rippling and then more recently like invested in, here's a funny one. I was one of the first investors in deal, if you've heard of them. I was able to exit, I was able to exit that position and then, you know, hopefully that company's going to zero with their criminal behavior, but whatever. I was, but more recently, like, you know, if you know, like Decagon, which is doing some really cool stuff on the AI front.

58:58Killing it. I mean, Langchain, like great so those are some companies that you maybe you've heard of but like how about like i invested in macro the founder was derrick lee macros out of business i invested in debrief ned roxson it's it's out of business you know i invested in verb data with david hertz out of business i'm reading from a list i invested in um what's the number 70 companies according to this list where i track things and like most of them went to zero and all those founders were awesome All those founders were kick ass. And all those founders put a shit ton of energy into building their businesses.

59:33And they went to zero. And they're enduring relationships. I can call on any of those people, I think, maybe with the exception of Deal. And, you know, call in a favor and have, and I've, you know, I've got a few subsequent. And actually, a lot of them joined Rippling, believe it or not. So, I don't know. Companies I've invested in is a long list. And I love to give you names of companies that don't exist anymore because it's self-serving and a horrible survivorship bias to just list the good ones. I love that answer. I think you're being modest in the context of your hit rate is clearly very high.

1:00:07Even one or two incredibly successful companies out of 70 is a win in VC. And so you're doing very well. But I think that's a really important perspective. when you see people's logos on their websites of all the companies they've invested in, you have no idea how many they've, how many at-bats they've had. It's good practice to ask people to give you the full list. What are your favorite failures that you've invested in? Oh, no, I'm not actually, okay. Well, obviously, like, you know, we don't spend time on it, but I think it's actually a good question. Yeah, like, what are some of your, what are your best failed investments?

1:00:37Show me the logos of the companies that didn't work out. It's a really, it's a juicy question. Yeah. There's a topic around this area that I wanted to spend time on, And I haven't heard anyone think of things this way, which is this idea you talk about of compounding plus power law plus entropy and how that's a really useful frame to think about business. So you kick this conversation off sort of invoking the extraordinary outcomes demand, extraordinary efforts line. Hat tip to Dan Gill. And these are part and parcel. Like, man, understanding the nature of the universe is a pretty good way to work within it.

1:01:19And so like power law distributions happen everywhere. It explains why so few people control so much wealth. It explains why Steph Curry is just so vastly better than the next guy down on the list on the basketball team. It explains why populations are concentrated into a really relatively small number of mega cities in the world. It's like power law distribution just plays out everywhere. And like once you see it, you can't unsee it. It sort of plays out in many dynamics. People tend to think that like the world plays on a more linear relationship where the X and Y axis are sort of Y equals X.

1:01:54But that is absolutely not the case. And the implications are profound. It's like if you build something to 80 or 90 percent, the Y axis is barely budged yet. You haven't like hit the inflection point in terms of reward. And so the implication of the power law more broadly is that people who are in the top 10%, the top 5%, don't just get 10 % or 20 % more reward. They get 10x the reward or 100x the reward. It's really dramatic. Entropy, the second law of thermodynamics, is a very simple concept. It's the reason your sock drawer becomes messy. It's the reason that potholes form. It's the reason we have to put so much energy into maintaining the aircraft we fly to keep them safe because they really, really, really want to fall apart.

1:02:37And that's the nature of things. If you abandon a city for a few months, it starts to go fallow. And so entropy is just this concept that shit tends toward disorder. and the universe, I mean, life itself is a temporary victory against entropy. You and I should not exist. The sun gives energy to the planet. It organizes stuff that we can eat and we fight entropy until we lose the battle somewhere, as I said earlier, at the age of 70 or 80, if we're lucky. What does this have to do with product? This is really about effort. The only antidote to entropy, the only antidote to decay in a system is energy.

1:03:24You got to inject energy. So if you have a code base, every line of code that you add to that code base increases the entropy of that system and demands ever more energy from human beings to go in and tend to it to make sure it doesn't break. and if you want to achieve greatness, if you want an extraordinary outcome, and in particular, if you want to be in the top 10%, top 5 % on the x-axis so that the y-axis is through the roof, then you have to relentlessly inject energy at every single step of the game. Teams will sadly, but because we are all human, teams will always optimize for local comfort.

1:04:08over company outcomes. Not because they get together and think we should do that, although unions do do that unequivocally, deliberately. But even in a collection of product managers or engineers, what's going to happen over time is entropy is going to creep in and people are going to optimize for local comfort. Your job as an executive, as a leader, is to fight that entropy tooth and nail every single day. It means that every time you see a bug, every time you see a bug, not most of the time, every time you go and you drop it at the feet of the product manager or the engineering manager, every time in public, preferably.

1:04:51It means that every time someone comes to you to hire someone and says that they have skipped the back channel, every time you're like you can't hire this person unless you do the back channel. It means that when you get into the bored and tired zone on any process that you as the executive have got to demand the 99th percentile of energy because otherwise entropy creeps in and the system decays. You have to do this. One of the messages that I delivered recently at our big executive big, like our top 75 manager off-site that we do roughly every 18 months, was a reminder that if the purest form of ambition and the purest and most intense source of energy in the business is the founder CEO, that every next concentric circle of management beyond the founder CEO has the potential to be an order of magnitude drop off in intensity.

1:05:52And that is fucking dangerous because if you go to two layers and it's two orders of magnitude drop off and signal an intensity, that is a very dysfunctional organization. So what I said to the team was, it's not that you need to buffer people from the intensity of the CEO. It's that you need to absolutely mirror that intensity. There are plenty of constituents in the business around you who will advocate for relaxing. There is an infinite supply of people under you who will buffer other team members from the intensity of the demands. Your job is not to be one of those buffers. Your job is to preserve that intensity at its highest possible level and let the buffering happen somewhere else.

1:06:39And that's the point is that entropy creeps into the system insidiously and slowly over time off your radar. And you have to maintain that intensity every minute of every day to try and fight it. If you want to stay at the extreme right end of the power law that obviously governs the outcome of everything that we build. what does that look like to pass along that intensity like what does that feel like what does that look like so say parker comes to you this bug sucks i got this broken screen you cut like you you cut off your finger maybe that's the example okay still got them i got all 10 i'll give you concrete examples um actually the joke that i sort of played on this one when i presented to the to the team was that the next sort of slide in my presentation was with the sound effect, the Slack huddle thing.

1:07:36And Parker's icon in Slack is just, he uses the generic yellow, the egg. Yeah. Which, you know, it's like, it's funny. And so everybody knows the yellow egg is like, is Parker. And so the next slide in the presentation was boop, boop, boop, boop, boop, boop, boop, which is the sound that Slack makes when someone calls you. And it was Parker Conrad is inviting you to a huddle. And then the next slide was Parker Conrad is modeling personal intensity. And the idea is if you know, you know, like you've ever been dragged into it, like, I want to talk about this fucking problem right now. And whatever you're doing, unless it's an interview, like I want you to come and have a conversation with me.

1:08:13That intensity is one place where it plays out. Every product team at Rippling, and we have a lot them now have public feedback channels. I am in there upside down on everything I find when I use those products. And I just model for everybody that this is how at least I want to do it, which is, I don't like this. I don't understand this. Tell me why this is this way. Boom, boom, boom, boom, boom. And people jump in and respond. The factory inspection process that I mentioned, which is where at the end of the assembly line, I jump out with the pickle and we talk about all of the elements. You have to record a loom of every major flow through the product.

1:08:47I personally review every one of those flows. I got a backlog I got to catch up on today and provide feedback to people always in a public channel so that every other product manager and engineering manager can jump in and see how the process has worked for other teams. It's about modeling the intensity publicly so that other people can say, okay, this is how we do things around here. And it gives the reaction from the team that received the message that you have to inject that energy every minute of every day and that there are no exceptions was not like, ooh, that's exhausting. The reaction is, oh, that is so invigorating.

1:09:25It's like so wonderful to hear that we're going to achieve these great outcomes, or at least we have a shot at doing so, and that you're empowering me to follow my instinct, which is to really like push for the best result. The reaction universally is like, what a relief that I get to go be intense because nobody in a position of leadership wants to be chill. And like, what's worse than a chill boss? No, don't work for a chill boss. Don't be a chill boss. It's the most pejorative label I could give you. Chill boss or chill PM. Don't be chill. Chill doesn't accomplish shit. Be intense. Be good.

1:10:05Be respectful. Be intense. Don't be chill. And again, this advice comes from where we started, which is this is what success looks like because somebody that is less chill than you is going to find that crack and come after your market. Is that the gist? For sure. I mean, again, if you're chill and you move the X axis down 10 or 20 points, the Y axis collapses. It doesn't just drop 10 or 20%. The Y axis collapses. And this is just kind of true in everything we do. So yeah, if you want to win, you should probably try. This is what I always say to people trying to build lifestyle businesses. There's always this idea, I'm going to build a side business.

1:10:50I'm going to make recurring income. It's going to be amazing. And I, in my experience, anytime there's a market or something shows up, that's juicy and there's ways to make money. Somebody is going to come at you and work harder, raise more money. And there's only so long you can maintain that. Well, man, there's a whole other podcast episode on the concept of leverage. If you sell your time, you've only got 24 hours a day to give. But if you can create a product that that scales, you know, the, the, the marginal cost of a unit of that product is zero like software. It's going to be competitive, man.

1:11:25Sell your time. It's not gonna be super competitive, but like sell that, you achieve that level of leverage. And there's just going to, there's, it's a pretty efficient market. To close out this, uh, thread of intensity and adding energy to everything. Something I've heard about you is you're big on, uh, escalating. You're a big fan of escalating issues. And also you always tell people to never not give you negative feedback, to always share feedback, to not hide anything. Well, I mean, fundamentally the most selfish thing you can do is withhold feedback from someone. Who are you optimizing for when you do that?

1:11:54What are you optimizing for when you think a thought that would help someone improve and you avoid giving it to them because it would make you uncomfortable? Well, you're optimizing for your own comfort and it's fundamentally selfish. It's the most selfish thing you could possibly do is withhold feedback that would otherwise be useful to someone because you don't want to be uncomfortable. Well, that's not how high performance teams operate. So I demand feedback and I give it. And it doesn't mean that when I give feedback, it's not open to being questioned or discussed. I mean, of course it is.

1:12:29But like when I observe something, I try to say it. That's the feedback topic. The part of this that has been interesting to me is that people withhold escalate, the customers withhold. Customers don't want to escalate to me as an executive. Even like the founders in whose businesses I've invested who use Rippling are reluctant to hit me up when something goes wrong because they don't want to bother me. But it's literally my job, literally my job to find things, problems, and make them better. And by virtue of making those specific things better, to iterate on the processes so that the system that builds the system can get better.

1:13:09There's no greater gift to me as a product executive than receiving an escalation from a customer. We have an escalations team at Rippling, which sounds weird, but it's people who are just particularly skilled at pistol whipping other people in the company to get to real root causes, real root causes, not like throw away the word root cause, like, we fixed the data error and shut the ticket down. No, you went and you found the software that created the data error, and then you found the system that created the software that created the data error, and you solved all that back to the top. Escalation seems extremely good at that, at Rippling.

1:13:47So we have sort of a dedicated little team that does this for us. Escalations are a gift. And I'd say if you're a listener right now on this podcast, and you are a Rippling customer, and you have shit that you think we should know, So the fact that I might already know it is not a reason for you to withhold the gift of your feedback. So it's an attitude that I take to this every day. I've got a little cue of some stuff that I've, you know, minor things that are from the last couple of days from people who had some nits and issues that I'm just like, I've got them cued up on my to do list today.

1:14:15And I'm going to take them to the product teams directly. Like, I'd like to understand what happened here. Not in a negative way. I just think we'll all get better if we study this one. And so, yeah, escalations are a gift. Feedback like that is a gift and nobody is ever inconveniencing me when they do it. For people that are listening to this and feeling like, man, this is so stressful and intense and just like, I don't know if I want to work this way. Give them a sense of just how successful Rippling is. I think a lot of people may not even have heard of Rippling. A lot of people are like, yeah, it's doing great.

1:14:46What are some things you can share that are public or not public that give people a sense of just how massive this business has become? People look at Rippling from the outside. I think they think of us as like payroll and HR or whatever, which is cool. Like it's a bit like saying Microsoft is a desktop operating system company or, you know, it's like every company starts from somewhere and grows out from there. We see ourselves as building the most successful business software platform in history. In fact, that's the mission statement of our product organization under the umbrella of the mission statement of the company, which is to free smart people to work on hard problems.

1:15:17And like when you translate that from where we are today to where we think we're taking things. It's like, we really do believe that like the core of every workflow and everything that a company has to do, be it AI or manual, traditional GUI based software is like, is who's doing stuff, who owns it, who's accountable. And so the people record is a really important component of that. You can argue that the customer record is also very important. And of course, some big businesses have been built on that primitive as well. But we think the people primitive is actually much more important. And the only thing that hasn't been done here is like somebody hasn't been ambitious enough to build a good business on top of that primitive workday is terrible software.

1:15:49Everybody agrees on that. Workday agrees on that. Good luck to them. But they have failed, actually, despite their success, to build a really broad general purpose software platform for business software on the foundation of the people primitive. So we're going to do that. And we're successful because we deliver on that promise at the scale we're at today. The fact that you can do, and this is not a sales pitch or sort of like an advertisement for Rippling. I just think it's important to sort of contemplate that when you bring together a bunch of disparate business processes into one system on a common business data graph, an object graph, a data lake with a consistent interface, you can do some pretty magical things.

1:16:27So we do payroll, we do HCM, we do IT, we do spend, we are about to launch a new product in the category of business intelligence and data management. And there's a whole bunch of other stuff coming beyond that. And then you layer in AI on top of this, where we alone, where we alone have all of your business data organized into this nice, neat package with a beautiful semantic layer on top of it, the AI can work magic. And we have shipped nothing, nothing yet in this category that I would say gets anywhere near what we're going to show next year. And it is going to set the standard. It is going to be the most, like the backflips that the AI is doing, reading and writing data for the user just on our internal use cases at Rippling is jaw-dropping.

1:17:16So I'm super excited about the tailwind this is going to create for us. You ask about what can I share about the success of the company, what I can say. There are tens of thousands of companies that now run on Rippling. We're less than 1 % of the market. And the market cap at$16 billion, I think now undervalues where we are from a revenue perspective by a long shot. There is just so much upside to do what we're doing. SaaS might be dead-ish in terms of point solutions, but long live SaaS in terms of what we're building. Let me follow that thread. And in AI, there's been a lot of talk about AI is going to replace SaaS, as you maybe just said.

1:17:55People are going to vibe code their way to their payroll system, which I know, good luck to the employees of those companies. And so what I'm hearing here is that you actually do believe a lot of SaaS companies that are selling individual solutions are in big trouble. The answer implied here is this kind of compound startup idea of you need to do a lot of things for people, for them to continue to pay for your software. Is that the gist? No, I think the gist is a really good quote. I forget who it's attributable to, but it's, you know, there's two ways to make money in software, bundling and unbundling.

1:18:29And you just got to get the timing right. So this is a period of bundling. Point solutions don't have enough data in the age of AI to be useful. You've got to be able to provide the AI with a lot of context about a lot of data so it can do things. It can do joins. It can do correlations. And so if you're a point solution, you're in hard water because you've got to now rely on data from other sources. You've got to integrate to third-party systems. And when you integrate to a third-party system, even the best ones are still sort of drinking their data through a straw, which is a real problem. I mean, you know, there are the biggest HCM software company you can think of integrates to the other biggest payroll software company you can think of through flat files via SFTP.

1:19:20Like, what are they going to do? What are they going to do? This is never going to work. It's just no way. And so I literally have no idea what they're going to do. They're just not going to build AI software, I guess. Like point SaaS is sort of in a rough spot, especially when you cleave two really important systems apart and say they have to integrate. It's very, very hard. The other thing that I would say about the world of even just like not SaaS, but AI software is that point solutions in the AI world are also in a rough spot for the same reason. It's like if you're selling the shovels like OpenAI and Google with Gemini, you can make money.

1:19:53And if you own the mine like Rippling with the data, you can make money. If you're somewhere in the middle building AI software that then tries to use the shovels from the shovel provider, but then also needs to rent out the mine or get the ore out of somebody else's mine and start refining it, you're in a very difficult place from an economic standpoint because you're not going to be permitted by either of those parties to build a big business on their backs. That's just not how it's going to work. They're going to demand value capture that crushes your unit economics. So I look at the landscape of AI companies that I've seen, and I think you have to have a really durable, interesting insight that gives you a shot at viable unit economics to be an interesting business.

1:20:45And that is going to kill off 80 or 90 % of the stuff that I see right now as standalone AI businesses. So what I'm hearing here, I love that you correct me when I get these things wrong, and that's exactly what I want. what I'm hearing is it's less about how difficult it is to build the SaaS product. It's about do you have first-party data that allows you to build an incredible AI product on top of what you've got. Yeah, because look, SaaS software is a bit flipping. All SaaS software applications are bit flippers. Like it's an interface changing values into data. It's what it does. It's a really hard product.

1:21:20Like Rippling, one of Rippling's superpowers is we're a coin sorter. You dump like, you know,$20 ,000 for an employee in the top of the coin sorter and it figures out what goes to the government, what goes to health insurance, what goes to your 401k, what goes to you, and it has to move all that money very, very reliably and seamlessly, very challenging software to build and manage, what's it doing? Even that is just flipping bits in a database. And so AI is a new way to flip bits. AI is just a new way to flip bits. Hopefully a way that like abstracts us a little bit further from having to think because our future is WALL-E.

1:21:56It's going to be great. speaking of WALL-E actually I have this Matic robot you have one of these it's like a it's like a human it's like a self-driving car robot basically a self-driving car people build this robot that cleans your house it's maybe I didn't mention that it's like a house cleaning robot that just like goes around it's like a Roomba you should get one they're expensive but incredibly cool and actually in WALL-E there's a scene where they actually have basically what these things look like so it's not so far That movie was actually quite prescient, perhaps with the exception of the gravity-defying daybids.

1:22:32Yeah. I don't know, but that's not good news. You've seen that movie. Oh, man. So on this AI stuff, which I'm hearing is you're probably going to see a lot more consolidation where these point solution companies realize they need this data. This is existential. They're going to combine and merge and bundle, as you described. It's possible. I am not a part of an investigator on this stuff. I think like there's some really interesting investors out there who, who I think are thinking quite deeply about this. And in particular, uh, like I, the conviction, which is like Mike for now and Sarah Goa.

1:23:03Like, I think those are two investors who are hyper-focused on AI. And when they made the decision to sort of take that approach at the time, I thought like, as, um, that's kind of narrow. Uh, now I'm like, no, no, no, that was the right move. And it just means that they have a very deep, deep, deep set of hypotheses that they've formed over the course of kind of seeing every AI deal in the Valley. And there are better people to ask this question of than I am. And I think if you're an entrepreneur, I recommend them to you because I think they're really smart. Awesome. I love those guys. Also, Sarah and Ilad have a podcast called No Priors that I'd also recommend.

1:23:40We'll point to you in the show notes. so on this ai note i guess is there anything else that you think would be really helpful for founders that are working in this space building an ai startup to here they think you're seeing of like here's how you need to here's what you need to do to win in an ai company oh so much like i actually think that if i were to give you an answer to this question right now it would be bullshit yeah i don't have anything back to my point earlier i don't have like I don't have enough relevant experience in the abstract to like dole out on a podcast on that topic. But I, you know, I wish them luck.

1:24:17I love that. Circling back to your advice, don't ask for advice, ask for a relevant experience. And I love that that's what your mind immediately went. I'm going to take us to AI Quarter, which is a recurring segment on this podcast. And the question is just what's one way you've found AI to be useful in your work day to day? Is there something that you found it unlocked? I mean, it's not a super exciting thing, but I'll say like where I use, so like one of the most important functions that I perform as an executive is the synthesis of ideas and the ability to communicate those ideas very clearly to people.

1:24:48So when I talk about like the product quality list and the pickle as something that we've come up with internally, I do turn to, um, to AI, chat GPT and Gemini where I, I take like a really, let's say, angular view of some topic. And I give, really, I write the essay for the AI. And I'm like, look, this is the crisp idea I want to communicate. Help me come up with pithy ways to articulate these things. And 80 % of what it outputs is trash. It's just like sort of middle middle of the road, average, low alpha junk. But it is a thought partner, a nonjudgmental thought partner where in 20 % of the stuff it comes out with, I'm like, it's pretty good.

1:25:32That's a new word I didn't think of that does kind of hit the nail on the head for this concept. And so if I believe that my job is to sort of bring brains along on the journey for some sort of change that I'm trying to bring about, then the most important tool is language. And I do find that ChatGPT and Gemini do a great job of helping me refine how to articulate the concepts that I want to articulate. They are not useful in coming up with the ideas themselves. That's an awesome tip. I don't know if you've played with Claude much, but I actually find Claude is better at writing and words and language.

1:26:05I have not spent a lot of time with Claude. I have used it, but by virtue of this conversation, I'll probably go give her a shot. There we go. So yeah, they're all great. But there's something about Claude that is just at writing specifically is much better. But they're all getting better all the time. It's always there's always some new. Matt, we've covered so much ground. We've touched on everything I was hoping to touch on. Before we get to our very exciting lightning round, is there anything else that you were hoping to share? Anything else you wanted to touch on or leave listeners with? We've spent a lot of time talking about intensity and the grind and the need to just always be operating at the 99th percentile.

1:26:45and um i think if you listen to that in a vacuum it's very easy to believe that that intensity is soul crushing that that it's a negative um that it's maybe not something that you want and i i think there's a backstop for me that i didn't talk about today that i think i i is important to share, which is that life is amazing. That like the fact that we all exist on this blue marble, drifting through space and time, that we are some weird instantiation of consciousness, each of us, and that you're here for such a short period of time whittling your stick, doing something. That like, if you remember how insignificant we are and all of this is, It brings this levity to what we do and to the work we put into building this because this is like Silicon Valley in 2025 is Florence in the Renaissance.

1:27:56It's crazy. Like the amount of creativity and insane invention and progress that's happening for our species right now in this place is absolutely unparalleled in all human history. You got to zoom out and appreciate that magic. And so then you turn around, you're like, fuck, I got to work on Friday night, right? Like I've got to go give it my all. I got to go compete in the arena of business. Just you have to, you never, you have to never forget that number one, none of this matters. And number two, it is an absolutely beautiful and amazing phenomenon that we get to be alive doing this right now.

1:28:35So like play the sport, play it with everything you've got, but never forget that it's just a sport and that none of it matters. And it's super important as a counterpoint to the intensity that we talked about. That is beautiful. I think about pale blue dot, Carl Sagan's whole thing. Just stunning photograph that literally changed the way I think about who I am as a person when I saw it. Yeah. Well, going in a completely different direction with that, Matt, we reached our very exciting lightning round. All right. I've got five questions for you. Are you ready? Okay. Here we go. What are two or three books that you find yourself recommending most to other people?

1:29:16Okay, two or three books. Give me a heads up on this. So like one, one book is conscious business. I don't have Conscious Business in front of me because it's actually at the office because we have Conscious Business Reading Club at Rippling. And every member of my current, my product leadership team is going through this right now. Conscious Business, Fred Kaufman, it's been used in many businesses, LinkedIn, most notably as a framework for thinking about effectively, it's a user manual for human beings. So if you are a leader, a manager, an executive, whatever, particularly younger, like people in their 20s and 30s who are just sort of getting the hang of being a CEO or a product leader for the first time, this book is absolute fucking gold.

1:29:51It was recommended to me by Brian Schreier at Sequoia when he was on my board at my previous company. I took way too long to take him up on the advice. Wished I had read it sooner. Highly recommend Conscious Business. Changes your life. Number two, thinking and systems. Donna Meadows. I always mispronounce her name. Donella Meadows. she died partway through writing this manuscript. Her fellow professors picked it up and finished it for her. It is the best generic framework for thinking about how systems work. You will extrapolate from this book to every aspect of your life after you read it. And then the third is classic 1960s, The Effective Executive.

1:30:27It's an anachronism. It uses weird pronouns for the secretary and the executive. I'll let you guess which ones. But the book itself is so chock full of simple enduring advice on how to be effective at leading teams and uh the good shit is the stuff that's been in print for 70 years and that's that's one of them beautiful i love the first one is you don't have it because you're using it with your team yeah constantly you mentioned at one point uh before we started recording you have like eight copies of that book that you just give everyone yeah and we hand it out like candy okay is there a favorite recent movie or tv show you've really enjoyed um yeah so i'm a little embarrassed by this answer but i'm gonna be honest please um there's a new series called heated rivalry and it's about i'm canadian and i'm gay so it's about two hockey players um in canada rivals between the bruins and the maple leaves although they don't use those names who are like just heated rivals on the ice and it's a huge thing that the world is watching but actually they're secret secretly in love with each other and they start hooking up.

1:31:32And it's been labeled by the media as smutty but delightful. And I would say that's accurate. So it might not be for everybody, but it is a smash hit right now. It's on HBO Max and Crave. And it's only six episodes. But like I said, a little embarrassing because it's a little chintzy, but it's a lot of fun. It's also really fun to see gay people represented in the media as though they're normal. And soon to be on Netflix with the acquisition if that goes through. Oh yeah, that's crazy. Amazing. Okay. Is there a favorite product you recently discovered that you really love? My fellow coffee maker.

1:32:09I love my fellow coffee maker. It's got an interface that lets you like set light, medium, dark roast. It changes the temperature. It blooms the coffee. It tells you how many grams of coffee to put into the basket. Slick interface, high quality coffee. It's like, it's definitely awesome. And so I have actually have one in the office and one at home and one in the garage. wow that is a favorite product you have three of them in the same space yeah yeah oh no in the office okay fellow is also a rippling customer and that's like a a nice side effect when we get to have they ever escalated anything to you no if you're listening and you're from fellow i want to hear all your gripes perfect two more questions do you have a favorite life motto that you find yourself coming back to often in work or in life it's a dark one and i'll share this one sort of partially for the humor of it, but it's actually sometimes useful.

1:32:58At least it's sort of a moment of smiling when it happens. It's like the motto comes from my dad who said, Matt, nothing's ever so bad in life that it couldn't get worse. And it's like, we were going through some shit yesterday at work and we were like, fuck, now that happened. And I looked at the CTO and I'm like, dude, nothing's ever so bad that it couldn't get worse. And we had a good laugh and continued to brace for whatever might come next. So not exactly uplifting, but fun to use. No, it is uplifting. I'm an optimist and I find myself thinking that often with my wife. Just like, it could be worse.

1:33:32It could be worse than this. Definitely could be worse. And it might get there. So let's ensure it's less worse version. Final question. Something you shared with me is that you were a DJ when you were a younger person. Can you just give us a little DJ voice to give people a sense of your other skills? it's not dj lenny it's it's radio personality and yeah i used to do the greatest hits of all time with his from the 60s the 70s the 80s and a little bit of the 90s 101.5 the hawk yeah you can turn it on it's very inauthentic but it sounds good on the radio uh it's cool i did it when i was in high school i ended up doing the midday uh the midday segment when uh right before I went to college and what a gift, what a huge gift in my most formative years to have developed like, uh, an ability to be in front of a microphone comfortably, you know, cause here we are.

1:34:28I love for people that weren't watching this YouTube, you like lean really close to the mic to get that, to get that, uh, radio personality voice. Yeah. You gotta be able to hear like the saliva in the mouth. Incredible. It's like the same person talking. Like if you're not watching this, you're like, where did that guy come from? Uh, that was great. You nailed it, Matt. Uh, this was incredible. I really appreciate being here. I really appreciate sharing all this advice that I have not heard other people share. Two final questions. Is there something you want to plug, point people to? And how can listeners be useful to you?

1:34:55Look, my life is rippling. I point people there. And this is my life's work. It's going to be a banger. So stay tuned. And the way that you can help me is that if you're a customer, you got to tell me when you have problems. Because that's how we get better. What's the way they get to you? Is there any place you want to point people to? DM me on Twitter. is easy at stay nine you can email me my last name at rippling.com um and uh i'll go that far without giving out my phone number how's that perfect the perfect boundary yeah matt thank you so much for being here it's my pleasure thank you for having me lenny and uh congrats on all the success with this podcast it's been great same to you it's always a good sign at the end of a conversation we're like oh i gotta get me some of that stock of that gotta get into that rippling so it's a good buy recommended but you're you know hard to get hard to come by all right man thank you so much thanks thank you so much for listening if you found this valuable you can subscribe to the show on Apple Podcasts Spotify or your favorite podcast app also please consider giving us a rating or leaving a review as that really helps other listeners find the podcast you can find all past episodes or learn more about the show at lennyspodcast.com.

1:36:11See you in the next episode.

From the publisher

Matt MacInnis is the chief product officer and former longtime COO at Rippling, a unified workforce management platform valued at over $16 billion.

We discuss:

1. Why “extraordinary results demand extraordinary efforts”

2. Why you should deliberately understaff projects, and how to know when you’ve gone too far

3. Matt’s transition from COO to CPO and what surprised him about leading product

4. The “high alpha, low beta” framework for evaluating people, processes, and products

5. When founders should quit their startups (hint: much earlier than VCs want you to)

6. How to fight entropy in your organization through relentless energy and intensity

—

Brought to you by:

Google Gemini—Your everyday AI assistant: https://ai.dev/

Datadog—Now home to Eppo, the leading experimentation and feature flagging platform: https://www.datadoghq.com/lenny

GoFundMe Giving Funds—Make year-end giving easy: http://gofundme.com/lenny

—

Transcript: https://www.lennysnewsletter.com/p/10-contrarian-leadership-truths

—

My biggest takeaways (for paid newsletter subscribers): https://www.lennysnewsletter.com/i/181916584/my-biggest-takeaways-from-this-conversation

—

Where to find Matt MacInnis:

• X: https://x.com/stanine

• LinkedIn: https://www.linkedin.com/in/macinnis

• Email: macinnis@rippling.com

—

Where to find Lenny:

• Newsletter: https://www.lennysnewsletter.com

• X: https://twitter.com/lennysan

• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/

—

In this episode, we cover:

(00:00) Introduction to Matt MacInnis and Rippling

(04:38) The importance of extraordinary efforts

(08:37) The challenges and rewards of relentless effort

(10:11) Your job as a leader is to preserve intensity

(12:39) You learn far more from success than failure

(16:34) Transitioning to chief product officer

(19:54) Fixing product management at Rippling

(25:27) The “high alpha, low beta” framework

(28:55) The PQL framework

(35:16) Hiring frameworks and team dynamics

(36:52) A helpful interview tactic

(40:00) Leading as a COO vs. a CPO

(42:34) The reality of product-market fit

(46:38) The problem with venture capital

(49:29) When founders should quit their startups

(41:48) The immutable market

(54:13) Lessons from Notion’s success

(57:43) Investment strategies and narrative violations

(01:00:42) The power of compounding, power law, and entropy

(01:07:02) Maintaining intensity and fighting entropy

(01:11:33) The importance of feedback and escalations

(01:14:31) Rippling’s vision and success

(01:17:48) AI’s impact on SaaS and business software

(01:23:42) AI corner

(01:26:23) Final thoughts and lightning round

—

Referenced:

• Rippling: https://www.rippling.com

• Sunil Raman on LinkedIn: https://www.linkedin.com/in/sunilraman

• Dan Gill on LinkedIn: https://www.linkedin.com/in/dangill

• Carvana: https://www.carvana.com

• Brian Chesky’s new playbook: https://www.lennysnewsletter.com/p/brian-cheskys-contrarian-approach

• Parker Conrad on LinkedIn: https://www.linkedin.com/in/parkerconrad

• Inkling: https://www.inkling.com

• Akshay Kothari on LinkedIn: https://www.linkedin.com/in/akothari

• Notion: https://www.notion.com

• Conway’s law: https://en.wikipedia.org/wiki/Conway%27s_law

• Seeking Alpha: https://seekingalpha.com

• Dennis Rodman’s website: https://dennisrodman.com

• Dancing pickle emoji: https://slackmojis.com/emojis/456-dancing_pickle

• Pickle Rick: https://en.wikipedia.org/wiki/Pickle_Rick

• SPOTAK: The Six Traits I Look for When I’m Hiring: https://finance.yahoo.com/news/spotak-six-traits-look-m-181335267.html

• Geoff Lewis on LinkedIn: https://www.linkedin.com/in/geofflewis1

• Zenefits: https://en.wikipedia.org/wiki/TriNet_Zenefits

• New banking records prove Deel paid thief who stole trade secrets from Rippling: https://www.rippling.com/blog/new-banking-records-prove-deel-paid-thief-who-stole-trade-secrets-from-rippling

• Workday: https://www.workday.com

• Matic robots: https://maticrobots.com

• Wall-E: https://www.imdb.com/title/tt0910970

• Conviction: https://www.conviction.com

• Mike Vernal on X: https://x.com/mvernal

• Sarah Guo on X: https://x.com/saranormous

• No Priors: https://linktr.ee/nopriors

• Gemini: https://gemini.google.com

• ChatGPT: https://chatgpt.com

• Claude: https://claude.ai

• Bryan Schreier on LinkedIn: https://www.linkedin.com/in/bryanschreier

• Heated Rivalry on HBO Max: https://www.hbomax.com/shows/heated-rivalry/50cd4e99-04ee-427b-a3b4-da721ed05d9c

• Fellow coffee maker: https://fellowproducts.com/products/aiden-precision-coffee-maker

—

Recommended books:

• Pale Blue Dot: A Vision of the Human Future in Space: https://www.amazon.com/Pale-Blue-Dot-Vision-Future/dp/0345376595

• Conscious Business: How to Build Value Through Values: https://www.amazon.com/Conscious-Business-Build-through-Values/dp/1622032020

• Thinking in Systems: https://www.amazon.com/Thinking-Systems-Donella-H-Meadows/dp/1603580557

• The Effective Executive: The Definitive Guide to Getting the Right Things Done: https://www.amazon.com/Effective-Executive-Definitive-Harperbusiness-Essentials/dp/0060833459

—

Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.

—

Lenny may be an investor in the companies discussed.



To hear more, visit www.lennysnewsletter.com

More from Lenny's Podcast: Product | Career | Growth

All 287 episodes
10 contrarian leadership truths every leader needs to hearLenny's Podcast: Product | Career | Growth · 1 h 36 min
Listen in VO