Lenny's PodcastMatt MacInnis: Why he deliberately understaffs every project
How Rippling stays lean with the PICL checklist and escalations: overstaffing breeds politics, cruft, and slowdown that block 99th-percentile outcomes.
CHAPTERS
- 0:00 – 4:47
Deliberate understaffing as an anti-politics operating system
Matt opens with a core Rippling principle: deliberately understaffing projects to prevent politics, waste, and low-priority work. He frames staffing as a leadership choice where being slightly under-resourced is usually less damaging than being over-resourced.
- •Overstaffing creates politics, slows execution, and produces “cruft”
- •Understaffing forces ruthless prioritization and focus on the highest-impact work
- •Leadership is about picking the “lesser evil” when perfect staffing is unknowable
- •Avoid letting teams work too far down the priority stack
- 4:47 – 8:57
Extraordinary outcomes require exhausting effort (and why comfort is a warning sign)
Matt argues that 99th-percentile results require 99th-percentile effort, and that being in the comfort zone at work is usually a signal something is off. He describes the grind as thousands of small moments—tickets, escalations, late nights—where great teams separate from good ones.
- •Extraordinary effort is necessary (even if not sufficient) for extraordinary outcomes
- •The ‘story’ is told through many small hard moments, not one grand event
- •Winning companies can more credibly ask for ‘the last ounce of oil’ from teams
- •Relentlessness matters because competitors fill any gap you leave
- 8:57 – 16:35
Relentless intensity without burning individuals: the team must stay on the ball
Building on Apple and Airbnb analogies, Matt explains the reality of continuous pressure in valuable, competitive markets. The organization can’t relax collectively, even if individuals need breaks—otherwise competitors exploit the opening and morale can actually dip when people lack challenge.
- •No sustained “relief” after shipping; momentum matters
- •Collective team intensity is different from grinding individuals down
- •In slack periods, morale can drop and distraction rises
- •Competitive markets punish any lapse in urgency
- 16:35 – 21:10
From COO to CPO: ‘injured birds,’ leadership gaps, and fixing a dumpster-fire from the inside
Matt tells the story behind his unusual COO→CPO transition: repeated leadership hiring misses left R&D without stable executive coverage. He stepped in to bring order to a product org that was locally optimized but globally incoherent, then began rebuilding fundamentals—process, clarity, and leadership.
- •Strong executives can be dropped into chaos to restore order
- •Rippling faced years without consistent product + engineering leadership
- •Conway’s Law: an incoherent org creates an incoherent product experience
- •Fixing the system required deep, bottom-up observation—not outside critique
- 21:10 – 25:44
Product teams have a hierarchy of needs: do the basics before the dashboards
Matt describes his ‘naive outsider’ lesson: teams often aspire to advanced metrics (like adoption) before foundational quality work is in place. He emphasizes doing things in the right order—stability, test coverage, QA discipline—then instrumentation and optimization.
- •“Everything must be done in its time and order”
- •Foundational quality (tests, checklists, stability) precedes adoption metrics
- •Lead from observed specifics; don’t import playbooks blindly
- •Care about adoption where the product is mature and instrumented
- 25:44 – 28:45
High alpha, low beta: designing people, process, and product for the right kind of volatility
Matt introduces an investing-inspired framework: alpha is upside/outperformance; beta is volatility. Processes exist to lower beta, but too much process suppresses alpha—so leaders must apply process selectively based on the domain (e.g., payroll needs low beta; 0→1 bets need alpha).
- •Alpha = upside; beta = volatility/unpredictability
- •Process is a tool to reduce beta, but it can suppress alpha
- •Different product areas require different mixes (payroll vs 0→1 innovation)
- •Even teams can tolerate ‘one Dennis Rodman’ (high-alpha, high-variance)
- 28:45 – 34:25
Culture change via ‘vessels for meaning’: the PICL (Product Quality List) and factory inspections
Matt explains how he operationalizes quality at scale with a lightweight checklist and memorable naming (PICL) that becomes shared language. He shares a concrete failure (a forgotten feature flag caused a blank screen) and shows how they updated the PICL to continuously reduce volatility in shipping.
- •Memorable artifacts (names, memes) help change culture in large orgs
- •PICL/PQL defines ship-quality standards and evolves with real incidents
- •Dogfooding + CEO-as-admin surfaces real product flaws quickly
- •Feature flags are dangerous unless managed; standards can constrain them
- 34:25 – 39:04
Hiring with intuition + decoding it: SPOTAK, fit, and the ‘impossible’ PM case study
Matt defends high-quality intuition developed through many interviews, and stresses translating gut feel into communicable criteria. He shares SPOTAK as a lens (smart, passionate, optimistic, tenacious, adaptable, kind) and describes Rippling’s tactic: everyone gets the same brutally hard case study to reveal depth and behaviors under pressure.
- •Rely on intuition if you’ve earned it—then explain it clearly
- •SPOTAK helps diagnose why a candidate ‘clicked’ or didn’t
- •Fit depends on alpha/beta needs of the specific product area
- •A single hard case study across levels reveals thinking, curiosity, and resilience
- 39:04 – 42:32
COO vs CPO: why product is the ‘highest-order bit’ that makes everything else easier
Matt contrasts COO work (optimize around the product) with product leadership (shape the product itself). He argues that when product-market fit and product quality are right, downstream functions—sales, marketing, finance, recruiting—become dramatically easier.
- •COO optimizes operations around the existing product reality
- •CPO can directly improve the core driver of company success
- •Great PMs are polymaths bridging people, systems, and execution
- •Bad PMs create the anti-PM sentiment; great ones unlock leverage
- 42:32 – 51:48
The reality of product-market fit: ‘you know it when you have it’ and why VC ‘never quit’ is misaligned
Matt compares his nine-year Inkling journey to Rippling’s clear PMF and argues that PMF is unmistakable in hindsight and in real time. He critiques the Silicon Valley ‘never quit’ mantra as often serving VC incentives more than founder life outcomes, and gives a pragmatic timeline for when to consider resetting.
- •If you’re unsure you have PMF, you probably don’t
- •Success teaches more than failure; join winning teams to learn faster
- •VC incentives favor continued attempts because capital is sunk
- •After multiple pivots and ~4–5 years without clear traction, consider quitting/resetting
- 51:48 – 54:12
The ‘immutable market’ and the drug-receptor analogy: marketing can’t create demand that isn’t there
Matt argues founders overestimate launches and marketing as levers for PMF. Using drug discovery as an analogy, he says the market either has ‘binding receptors’ for your product or it doesn’t—your job is to run experiments to discover fit, not persuade reality to change.
- •Launches are tiny drops in an ocean of noise
- •Markets are ‘immutable’: awareness isn’t the same as desire
- •Startups are experiments to test whether demand truly exists
- •Avoid trying to market your way through lack of fit
- 54:12 – 1:00:42
Notion, narrative violations, and investing without survivorship bias
Using Notion as a counterexample, Matt explains ‘narrative violations’: outlier successes often break common rules (like persistence paying off). He emphasizes that companies succeed based on founder idiosyncrasies and timing—lessons can’t be copied mechanically—and he resists survivorship bias by highlighting that most investments go to zero.
- •Power-law outcomes mean checklists can’t capture outliers
- •‘Narrative violations’ are often essential to exceptional success
- •Notion’s persistence worked because of the founders’ unique traits, not as a universal rule
- •Most startup bets fail; listing only winners is misleading
- 1:00:42 – 1:11:33
Compounding + power laws + entropy: leadership as continuous energy injection
Matt connects business performance to physics and distributions: power laws make the top-end rewards explode, while entropy steadily degrades systems. The only antidote is constant energy—leaders must fight drift toward comfort, enforce standards, and mirror the founder’s intensity across management layers.
- •Power laws: being top 5–10% yields 10–100x outcomes, not linear gains
- •Entropy: systems decay; codebases accumulate disorder with every added line
- •Teams naturally optimize for comfort unless leadership counteracts it
- •Managers should mirror CEO intensity; buffering happens elsewhere
- 1:11:33 – 1:14:32
Escalations and feedback as gifts: public intensity, root causes, and ‘don’t be a chill boss’
Matt makes the case that withholding feedback is selfish and that escalations are invaluable inputs for improving both product and process. He describes Rippling’s escalation muscle (true root cause analysis), his habit of public feedback, and why intensity feels invigorating—not soul-crushing—when it’s tied to meaningful outcomes.
- •Withholding constructive feedback prioritizes your comfort over improvement
- •Escalations are a gift—especially from customers
- •Root-cause means fixing the system that created the problem, not just the symptom
- •Model intensity publicly (channels, loom reviews, inspections); avoid being ‘chill’
- 1:14:32 – 1:24:17
Rippling’s platform ambition + AI’s impact on SaaS: data gravity, bundling, and ‘AI is just a new way to flip bits’
Matt reframes Rippling as a business software platform built on the ‘people primitive’ and a unified data graph. He argues AI will punish point solutions that lack first-party data and context, pushing the industry toward bundling; Rippling’s advantage is owning the ‘mine’ of integrated business data.
- •Rippling’s vision: broad platform on top of the people record + unified data graph
- •Point solutions struggle in AI era due to thin context and brittle integrations (often flat files)
- •Bundling/unbundling cycles: this is a bundling moment driven by data needs
- •AI changes the interface to software (‘flipping bits’), but data + reliability remain crucial
- 1:24:17 – 1:36:16
AI Corner + closing perspective: use AI for language, then zoom out on life before the lightning round
Matt shares his pragmatic AI use: refining language to communicate ideas, not generating the ideas themselves. He closes with a philosophical counterweight to intensity—work is a sport inside an astonishing, brief human life—then ends with a lightning round of books, favorites, and personal tidbits.
- •AI is a non-judgmental thought partner for sharpening phrasing and communication
- •Most AI output is mediocre; the value is in the occasional strong suggestion
- •Intensity is sustainable when paired with perspective: ‘none of this matters, and it’s amazing’
- •Lightning round: key books, favorite show/product, mottos, and radio-persona origin story
