Matt MacInnis, Chief Product Officer (CPO) and former Chief Operating Officer (COO) at Rippling, emphasizes that extraordinary results require extraordinary efforts and that projects should be deliberately understaffed. He shares insights about fighting organizational entropy through relentless effort, the importance of feedback and escalation, lessons learned as a product leader, and the future of business software in the AI era.

1. Extraordinary Results and Relentless Effort

Matt MacInnis stresses that extraordinary results require extraordinary efforts. This concept, which he learned from Dan Gill, CPO at Carvana, is a crucial principle that many in Silicon Valley overlook.

"If you want 99th percentile results, it's going to be really hard. It's going to be really uncomfortable. You have to keep reminding people of this. If they feel comfortable at work, they are definitely making mistakes."

He explains that this effort isn't one grand story but manifests through "countless small things" — thousands of Jira tickets. When an urgent issue or new bug pops up on a Friday night, those moments of stepping up to fix them are precisely what separates great teams from mediocre ones.

At a fast-growing company like Rippling, this effort carries even greater significance. When a company is succeeding, leaders gain the leverage to tell teams they need to "squeeze out every last drop of oil." At slower-growth companies, such effort may not translate to rewards, making it hard for team members to stay motivated. Matt calls working at Rippling "a very special and rare opportunity to experience extraordinary efforts leading to extraordinary results."

Reflecting on his seven years at Apple, he recalls the relentless development process under Steve Jobs, often called "death marches." As soon as one iPhone version shipped, work on the next began immediately. In a competitive market, any moment of complacency gives competitors an opening, so "the organization can never rest." Individual vacations are necessary, but the team as a whole must always stay vigilant.

In fact, giving a team time to rest actually lowers morale — people start drifting or thinking "What are we even doing? This isn't fun." Keeping the team continuously busy, motivated, and passionate is what maintains high morale.

2. Deliberate Understaffing and Maintaining Intensity

Matt presents a management framework where deliberately understaffing projects is preferable. Since you can never know the perfect answer when making decisions, his philosophy is that understaffing is less harmful than overstaffing.

• Problems with overstaffing:
  • Political issues arise.
  • People end up working on unnecessarily low-priority tasks.
  • This is poisonous, wasteful, slows things down, and creates unnecessary crust in the organization.

Therefore, Matt believes it's important at Rippling to deliberately understaff every project. Teams always ask for more resources, but new resources are only provided when truly appropriate.

"Good teams get tired, and that's when great teams kick good teams' asses."

This quote supports Matt's argument to always run the engine at "redline." Any moment of complacency or slowing down gives hungrier competitors a chance to break through. He says the most memorable and cherished moments were the stressful late nights that led to successful outcomes.

From Rippling CEO Parker Conrad, he gained the insight that you learn more from success than from failure. While failures teach something, seeing "how to do things right" through success is far more beneficial and informative. He advises early-career product managers and aspiring learners to "join winning teams." When he sees a resume showing someone worked at a company with tremendous growth, he immediately wants to interview them. In Silicon Valley, success breeds success — so chase success.

3. Transition from COO to CPO and Product Management Innovation

Matt recently transitioned from his long-held COO role at Rippling to CPO. He describes this as "MacInnis's wounded bird" — whenever a function falls into chaos or crisis, he focuses on it and restores order.

But R&D was the exception. He watched problems in R&D from the outside (poor architecture, failure to measure adoption metrics, etc.) with a critical eye. Rippling had hiring missteps in engineering and product leadership, and endured two years of chaos and pain. Eventually, Matt decided to step in and take over product leadership himself.

After diving into the product role for 11 months, he confesses to "feeling embarrassed about the naivety of my outside perspective." He had criticized the product team for not meeting top-level demands like "measure adoption metrics," but once inside, realized that even the basics were missing.

• Missing fundamental standards:
  • Basic standards for test coverage
  • A "factory inspection" checklist before shipping product
  • A definition of "product quality"

Matt calls trying to measure adoption metrics while skipping these basic steps "absolute madness." Over 11 months, he focused on building "greater clarity on how we get things done, better processes, better leadership."

"There is no excuse as an executive to sit outside the chaos and think you know the answer. That is a cardinal sin as an executive. You have to go and see. You have to be in the boiler room. You have to study the system from the bottom up and develop hypotheses for how to fix the system."

He emphasizes that everything must happen in its time and order. With no prior product management experience, he had to approach every problem from first principles. He says, "In principle, I don't care about adoption metrics. I care about adoption metrics when I care about them" — meaning he focuses on adoption metrics for certain product areas (like an applicant tracking system) while concentrating on foundational elements that ensure product stability and functionality in others.

When other executives asked what they need to understand about product, Matt introduces the "high alpha, low beta" framework.

3.1. The High Alpha, Low Beta Framework

• Alpha: Outperformance relative to an index. Like finding returns that beat the S&P 500 in financial markets, in product development it means generating exceptional returns through a unique market approach or solving customer problems.
• Beta: Volatility. Like high-beta stocks that swing wildly for no particular reason, in product development it means unpredictability or instability. The ideal stock has high alpha and low beta, but these are usually correlated.

Matt uses this framework to evaluate people and processes.

• People: Using Dennis Rodman as an example — a "problem" employee with "very high alpha," but a team can have room for one such individual.
• Products: Products going from 0 to 1 should pursue alpha, while mature products (like payroll) should pursue low beta by reducing unpredictability and errors.

3.2. The Role of Process: Reducing Beta and Suppressing Alpha

Matt explains that processes exist solely to reduce beta (volatility) in system outputs. However, the downside is that processes suppress alpha (creativity, innovation). Therefore, when applying processes to product teams, you must be very careful — apply them where you want to reduce beta, and avoid suppressing alpha where it's needed.

While reforming product development practices at Rippling, Matt created the "PQL" (Product Quality List) — deliberately given a peculiar name to drive cultural change and make it memorable.

"The word 'pickle' might sound a bit cheeky or funny, but I intentionally made it uniquely eye-catching as a vessel I could fill with specific meaning."

The PQL is a lightweight checklist that clearly describes standards to meet when shipping products in the simplest way possible. Matt uses this checklist to reduce system beta while minimizing negative impact on alpha.

When Parker recently installed a new application and encountered a blank screen bug, the cause was an engineer's temporary "feature flag." Matt used this incident to add to the PQL: "Only one feature flag governing the entire product is permitted at ship." This is an extreme standard that may be hard to achieve, but it's what Rippling aspires to.

3.3. Hiring Framework: SPOTAK and Case Studies

Matt uses the SPOTAK framework (Smart, Passionate, Optimistic, Tenacious, Adaptable, Kind) in hiring. He says to trust interviewers' intuition and uses this framework to effectively communicate intuitive impressions to others. It's also useful for distinguishing candidates suited for high-alpha vs. low-beta roles.

Additionally, Rippling's product team gives the same challenging case study to product candidates at all levels. While candidates may feel a sense of failure, interviewers evaluate how deeply they understand and solve problems and how they react to new information.

Matt cites one of the joys of product leadership as "getting to work with the smartest people in software." He emphasizes that product managers must be polymaths — exceptional across diverse domains.

As COO, Matt's role was to accept the product as-is and optimize everything around it. But as CPO, he realized that "the product is the high-order bit."

"Get the product right, it fits the market well, and everything else gets easy. Finance gets easy, sales gets easy, marketing gets easy, recruiting gets easy, everything gets [damn] easy."

Regarding criticism of product managers, Matt says he "hates bad product managers." Like wine: "If you say you hate Chardonnay, you've never had good Chardonnay" — it's because they've never worked with a great product manager.

4. Product-Market Fit and the Entrepreneur's Decisive Moment

Matt shares important lessons by comparing his experience at his previous startup Inkling — where he spent nine years struggling to find product-market fit — with Rippling's success. He criticizes venture capitalists who say "never give up" as "complete BS."

"We say never give up in Silicon Valley, but that's complete venture capital BS."

The only logical desire VCs have is to keep founders trying. Occasionally there are dramatic pivots like Slack or Airbnb that succeed, but these are extremely rare. Based on his experience, Matt advises founders that if their business "isn't obviously an explosive growth story by year four or five, giving up is much faster."

"Product-market fit, once it comes, is insanely exciting, and you should pursue it. And don't fool yourself into thinking you have it when you don't. That's dangerous and something you'll regret."

He uses the analogy of the "immutable market" to explain product-market fit.

"You should view your startup as conducting an experiment in the universe. You should use the analogy of drug discovery and receptor binding. Nobody at Genentech thinks they can market for better performance inside the body. The binding receptor for that drug either exists or it doesn't. And when they build the product, their goal is to find out whether the binding receptor exists."

In other words, no amount of marketing can change whether the market wants your product. When a product launches and doesn't succeed, don't try to break through with marketing. "Fate has already decided the outcome" — find the right "drug" (product) and forget trying to persuade the body to develop "binding receptors" (market demand).

Regarding Notion's success, Matt explains it as an extremely rare case of "narrative violations," made possible by the founder's unique idiosyncrasies. Every successful business violates conventional wisdom in some way. Notion's success can't be replicated, and its lesson isn't "never give up" but rather "every company succeeds based on the founder's unique characteristics."

Matt also discusses his investment experience, mentioning both successful companies (Notion, Clever, Zenefits, Rippling, Deel, Decagon, Langchain) and failed ones (Macro, Debrief, Verb Data), warning against survivorship bias. He candidly shares that he invested in 70 companies but most failed, and emphasizes that failure is common despite all the founders being brilliant.

5. Compounding + Power Law + Entropy: The Keys to Business Success

Matt presents compounding + power law + entropy as a framework for business success.

• Power Law: Many phenomena (wealth concentration, athletes' abilities, urban population concentration) follow power law distributions. The Y-axis barely moves until the X-axis reaches the 80-90% mark, then at the top 10% or 5%, rewards increase dramatically by 10x or 100x.
• Entropy: The second law of thermodynamics — everything tends toward disorder (messy sock drawers, potholes in roads). The only antidote to system decay is injecting energy.

Matt explains that every time new code is added to a codebase, system entropy increases, requiring more energy. To achieve extraordinary results, you must continuously inject energy at every stage of the game.

"Teams will sadly, because we're all human, always optimize for their local comfort rather than the overall company results. As an executive, as a leader, your job is to ferociously fight that entropy every single day."

Matt emphasized at an executive offsite that "the purest form of ambition and the most intense energy source in a business is the founder CEO." Beyond the founder CEO, each subsequent management layer may lose a degree of intensity, which is "dangerously risky."

Therefore, an executive leader's role is not to buffer the CEO's intensity but to "maintain that intensity at the highest possible level."

"There are countless members around you who advocate for comfort. Below you, there will be infinite people trying to buffer other team members from the intensity of demands. Your job is not to be one of those buffers. Your job is to maintain that intensity at the highest possible level and let the buffering happen elsewhere."

He says he "models the intensity publicly" — directly forwarding every bug he finds to product or engineering managers, immediately blocking any hiring attempts that bypass proper channels. Team responses to this intense approach aren't "it's hard" but rather "it's really energizing." They say it's great to be empowered to strive for the best results and how fortunate they are to be allowed to follow their instincts.

"No one in any leadership position wants to be 'chill'... What's worse than a 'chill' boss? Don't work under a 'chill' boss. Don't be a 'chill' boss. That's the most contemptuous label I can give. A 'chill' boss or a 'chill' PM. Don't be 'chill.' 'Chill' accomplishes [damn] nothing. Be intense. Be excellent. Be respectful. Be intense. Don't be 'chill.'"

Matt also emphasizes the importance of giving and receiving feedback and problem escalation.

"Fundamentally, the most selfish thing you can do is not give someone feedback. If you have a thought that could help someone improve and you withhold it because it might be uncomfortable, you're optimizing for your own comfort. And that is a fundamentally selfish act."

He notes that customers often hesitate to escalate issues to him as an executive, not wanting to cause trouble, but this is "literally my job" and "escalations are a gift." Rippling has an escalation team that excels at digging into true root causes of problems.

6. Rippling's Vision and the Future of Software in the AI Era

Rippling's goal isn't merely being a payroll and HR company — it aims to build "the most successful business software platform in history." Their mission is "to free smart people to focus on hard problems."

Rippling believes there's a "people primitive" at the core of everything a business does — the question of "who's doing stuff." Based on this "people record," they're integrating diverse business processes (payroll, HCM, IT, expenses, etc.) into a single system. Matt predicts that layering AI on top of this "common business data graph" will create magic.

"AI can do magic, and we haven't shipped anything in this category close to what we're going to show next year. And it will set the standard. The backflips of AI reading and writing data for users are jaw-dropping even in Rippling's internal use cases."

Rippling currently serves tens of thousands of companies but holds less than 1% market share, representing enormous growth potential. Matt says "SaaS as point solutions may be dying, but the kind of SaaS we're building will live on."

He emphasizes that data integration is essential in the AI era.

"Point solutions don't have enough data to be useful in the AI era. You need to be able to give AI a lot of context about a lot of data. That's how you can do joins and correlations."

Point solutions must rely on data from other sources, which is like "drinking data through a straw" — making it difficult to build AI software. Matt declares that "there are two ways to make money in software through bundling and unbundling, and right now is the era of bundling."

He identifies two paths to making money in the AI software market:

1. Companies selling shovels: Companies like OpenAI or Google Gemini that provide the AI models themselves
2. Companies that own the mine: Companies like Rippling that possess large volumes of data with a well-organized semantic layer

AI software companies stuck in the middle — borrowing shovels and trying to get data from other companies' mines — will face extremely difficult economics, potentially eliminating 80-90% of AI startups. He advises AI startups to have "really solid and interesting insights that enable viable unit economics."

Matt says AI is simply "a new way to change bits," and half-jokingly predicts the future may head toward a Wall-E scenario where humans move further from thinking. He also mentions investors like Mike Vernal and Sarah Guo of Conviction who are deeply focused on AI, praising their insights.

On his personal use of AI, Matt emphasizes "the synthesis of ideas and the ability to communicate those ideas very clearly to people." He gives ChatGPT or Gemini essays containing his sharp ideas and asks them to find "clever ways to express those ideas clearly." While 80% of AI output is "mediocre, low-alpha garbage," the remaining 20% serves as "an excellent thinking partner for finding new words and concepts."

7. Conclusion: The Wonder of Life and Business Passion

Matt acknowledges that his advice emphasizing intensity and relentless effort might sound "soul-crushing" to listeners. But he offers the "paradoxical counterpoint" — don't forget to appreciate the wonder of life.

"Life is amazing. The fact that we all exist on this blue marble drifting through spacetime, that each of us is a strange manifestation of consciousness, and that we're here sharpening our sticks doing something for this brief time... If we remember how insignificant we are, how meaningless all of this is, it brings liberation to the work we do and the effort we put into building."

He declares that 2025's Silicon Valley is like "Florence during the Renaissance" — an unprecedented era of creativity and invention for humanity.

"Have to work Friday night? Great! I have to pour everything I have into competing in the arena of business. Never forget that none of this matters, and that the fact we're alive doing this right now is an absolutely beautiful and amazing phenomenon. So enjoy the sport. Play with everything you've got. But never forget it's just a sport and nothing matters."

Matt concludes by saying this paradoxical perspective serves as an "important counterpoint to intensity."