Contrarian leadership truths from Rippling's COO-turned-CPO

Executive overview

Most leadership advice optimises for comfort. Matt MacInnis argues the opposite: extraordinary outcomes demand extraordinary effort, and teams that find themselves in the comfort zone have already made a mistake. Entropy is the enemy — left unchecked, teams always optimise for local comfort over company outcomes.

The antidote is relentless energy injection: surface every bug publicly, demand escalations, mirror the founder's intensity rather than buffering it from the team. The leader's job is not to shield people from intensity — it is to preserve and transmit it.

Extraordinary effort as a leadership principle

• Extraordinary effort is necessary (though not sufficient) for extraordinary outcomes.
• If your team is never uncomfortable, something has gone wrong.
• The separating moments between good and great teams are the Friday-night escalations, not the grand events.
• Winning gives you the air cover to demand more — people lean in when they believe it will yield something.
• Counter-intuitively, slack time drops morale; keeping people fired up and busy sustains it.
• "Good teams get tired. That's when great teams kick the good teams' asses."

Deliberate understaffing

• You can never staff a project exactly right — so decide which error to make.
• Overstaffing is the worse error: it generates politics, cruft, and work on lower-priority items before you know if they're necessary.
• The right posture: deliberately understaff every project, then add resources where the evidence demands it.
• The goal is a team that always feels slightly dehydrated — wanting more water, but not yet dangerously so.

Fighting entropy

• Entropy — the second law of thermodynamics — means systems decay toward disorder unless energy is constantly injected.
• Every line of code added to a codebase increases its entropy and demands more human energy to maintain.
• Teams will always drift toward local comfort over company outcomes; this is human nature, not malice.
• An executive's job is to fight that drift tooth and nail, every day: flag every bug, enforce back-channels on every hire, hold the line on every standard.
• The founder CEO is the purest source of energy and ambition. Every concentric circle of management can drop off intensity by an order of magnitude — that compounding loss is dangerous.
• Don't buffer the team from founder intensity. Mirror it.

Power law thinking

• Outcomes don't follow a linear distribution — they follow a power law.
• Being in the top 10% doesn't yield 10% more reward; it yields 10x or 100x more.
• The implication: building to 80–90% quality barely moves the needle on outcomes.
• Relaxing the organisation even slightly can collapse the Y-axis, not just trim it.

Process as beta suppression

• Alpha: outperformance, creativity, unpredictability. Beta: volatility.
• Processes exist for one purpose: lowering beta (reducing output volatility). Their cost is suppressing alpha.
• Apply process only where you want low beta (e.g. payroll — you never want surprises). Avoid it where you need alpha (e.g. zero-to-one product work).
• When hiring: match alpha/beta profile to the role. High-alpha people are valuable but one per team is enough (the Dennis Rodman rule).
• When building product tooling: create a vessel for meaning with a memorable name, then fill it. At Rippling, the product quality checklist is called the Pickle — deliberately idiosyncratic so it sticks.

Feedback and escalation as gifts

• Withholding feedback is selfish: you're optimising for your own comfort at the cost of the other person's growth.
• Demand feedback; give it directly. It doesn't mean feedback is beyond challenge, but silence isn't the alternative.
• Escalations from customers are gifts, not interruptions — they expose root causes that can improve the whole system.
• Real root-cause analysis means tracing back through the software that caused the data error, and the system that produced the software.
• Rippling runs a dedicated escalations team whose job is to get to real root causes, not close tickets.

Product market fit and when to quit

• Product market fit is unmistakable when you have it. If you're asking whether you have it, you don't.
• "Never quit" is VC propaganda — venture capitalists have no way to take their money back, so they always benefit from you continuing.
• You learn more from success than from failure. Join a winning team; success begets success.
• A useful heuristic from investing: ask people for relevant experience, not advice. If they have no relevant experience, their advice is worthless.
• The drug-discovery analogy: binding receptors either exist or they don't. You can't market your way to product-market fit. Run the experiment; accept the result.
• At year four or five with multiple pivots and no obvious rip-roaring growth, the honest move is often to reset — clean cap table, new energy, next thing.
• Notion is a narrative violation, not a template. Every company succeeds on the idiosyncrasies of its founder; you can't replicate Notion because you're not Ivan.

Hiring frameworks

• SPOTAC: Smart, Passionate, Optimistic, Tenacious, Adaptable, Kind. Use it to decode your intuition after a candidate conversation, not as a top-down checklist.
• Use a single, impossibly difficult case study for every product candidate regardless of seniority. Candidates always feel they failed; you learn how many corners they see around.
• Good candidates: make progress, ask questions, don't get defensive when new information invalidates their solution.
• Rely on intuition — experienced intuition built on thousands of interviews is a trained model. Decode and express it rather than suppress it.

COO to CPO: lessons from jumping in

• Being a great generalist executive means being tossed into any broken function and restoring order. The exception is R&D — until you're in it.
• Product teams have a hierarchy of needs. Criticising failure to measure adoption metrics is insane if the team hasn't yet established test coverage standards or basic quality checks.
• Conway's law is real: a locally-optimised, globally-incoherent org ships a locally-optimised, globally-incoherent product.
• Never sit outside a mess and theorise. Get in the boiler room. Study the system bottom-up. Develop hypotheses from what you observe.
• Product is the highest-order bit. Get it right and everything else — sales, finance, recruiting, marketing — gets easier.

On AI and the future of SaaS

• Point solutions are in trouble in the AI era — they lack the data breadth to power good AI.
• To build useful AI you need to own the data (the mine) or sell the shovels (models). Building on top of both without owning either crushes unit economics.
• Rippling's structural advantage: all business data (people, spend, IT, payroll) in one graph with a consistent semantic layer — the AI has context no point solution can match.
• "There are two ways to make money in software: bundling and unbundling. You just have to get the timing right." This is a bundling moment.
• 80–90% of current standalone AI businesses will likely fail due to unviable unit economics.

Closing perspective

• None of this matters — and that's the point. Business is a sport. Play it with everything you have, but never forget it's just a sport.
• Silicon Valley in 2025 is Florence in the Renaissance. The level of invention happening right now is unparalleled in human history.
• The intensity is invigorating, not soul-crushing. Leaders who demand high performance give their teams permission to follow their instincts and push for the best result.
• Don't be a chill boss. Chill doesn't accomplish anything.