Reading Notes

Matt MacInnis on Extraordinary Efforts, Power Law and Entropy, and Building Rippling

Source: Matt MacInnis on Extraordinary Efforts, Power Law and Entropy, and Building Rippling

Notes — Matt MacInnis on Extraordinary Efforts, Power Law and Entropy, and Building Rippling

Four questions [Adler frame]

Q1. What is it about? A management philosophy built from first principles, combining physics (power law distributions, thermodynamic entropy) with practitioner experience at Rippling (~$16B, 5,000 employees), Apple (Steve Jobs era), and a failed startup (Inkling, 2009–2018). The episode covers: why sustained high intensity is structurally required; the alpha/beta framework for matching people and processes to product contexts; the PQL as a quality system; SPOTAC as a hiring decoder; why PMF is unambiguous when present; and why “never quit” is VC propaganda.

Q2. How is it argued? Through layered analogies (power law in sports and cities; entropy in houses and codebases), direct experience (the Inkling failure, the Apple death march, the Parker-discovers-blank-screen incident), and a small number of memorable named frameworks. MacInnis explicitly grounds his advice in relevant experience rather than general principles — he frequently says “I don’t have relevant experience here, so I won’t advise on this.”

Q3. Is it true? The power law point is empirically well-supported across many domains. Entropy as a management metaphor captures a real tendency — systems drift toward local comfort without active energy injection. The FOMU/VC propaganda points about “never quit” are a minority view but well-supported by base-rate data on startup success. The alpha/beta framework is a useful mental model but does not eliminate the difficulty of the calibration judgement. [?] The drug-receptor PMF metaphor implies more certainty about market acceptance than is probably warranted — many companies have found PMF iteratively rather than discovering a pre-existing fit.

Q4. What of it? The most operationally useful outputs are: the deliberate understaffing heuristic (under-staffing is less harmful than over-staffing, and the direction of the error matters); the PQL as a low-process-overhead quality system; and the escalation-as-gift framing (which runs against most corporate instincts). The power law + entropy frame is useful as a check on complacency: when things are going well, the reason to keep pushing is structural, not motivational.

Glossary

Extraordinary efforts demand extraordinary outcomes — MacInnis’s guiding principle (attributed to Dan Gill, CPO at Carvana): 99th-percentile outcomes require 99th-percentile efforts. Not a motivation claim but a power-law claim.

Deliberate understaffing — the principle that when you cannot get staffing exactly right, under-staffing is the less-harmful error. Over-staffing generates politics and pulls work toward lower-priority items. The wisdom is knowing not to under-under-staff.

Power law — a non-linear distribution where outcomes are dominated by a small number of extreme values. In product/business: the top 5–10% of effort does not get proportionally more reward; it gets orders of magnitude more. See Power Law and Entropy.

Entropy (business) — the tendency of any system to drift toward disorder without active energy injection. Teams optimise for local comfort; codebases accumulate technical debt; processes calcify. Leadership’s job is to fight entropy continuously. See Power Law and Entropy.

Alpha/beta framework — alpha = outperformance potential (creative upside); beta = volatility (unpredictability). High-alpha people and processes are valuable where creative risk-taking is needed; low-beta people and processes are needed where reliability is required. Processes lower beta and suppress alpha simultaneously. See Alpha-Beta Framework.

PQL (Product Quality List) — nicknamed “the pickle” (PQL → pronounced like pickle). A lightweight per-product checklist of minimum shipping standards. Iterated in real time as quality failures surface new gaps. Designed to lower beta in exactly the places where variance is costly.

SPOTAC — MacInnis’s hiring-evaluation acronym: Smart, Passionate, Optimistic, Tenacious, Adaptable, Kind. Useful not as a top-down checklist but as a framework for decoding post-interview intuitions (“why didn’t that click?”).

Drug-receptor PMF metaphor — MacInnis’s framing for product-market fit: market receptors either exist for your product or they do not; no amount of marketing creates receptors. The job is to find the product-receptor combination, not to convince the market to develop receptors for what you have built.

Never quit (VC propaganda) — MacInnis’s view that “never quit” culture serves venture capital incentives (investors cannot retrieve capital, so persistence is always in their interest) at the expense of founders who could spend their limited time on a better-fit opportunity. Relevant experience: his own nine-year Inkling journey; position: quit by year four, second or third pivot, if it is not obviously working.

Key passages

On the power-law implication for effort [§ Extraordinary efforts section] “If you build something to 80 or 90%, the Y axis is barely budged yet. You haven’t hit the inflection point in terms of reward… 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.”

On deliberate understaffing [§ Understaffing section] “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.” — The reasoning: with limited certainty about what to build, staffing the top five items creates pressure to work on items 6–20 before their necessity is established.

On processes suppressing alpha [§ Alpha/beta section] “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.” — The design problem: implement process where you want low beta; avoid it where you need alpha.

On the founder-CEO as the intensity origin [§ Entropy section] “The purest form of ambition and most intense source of energy in the business is the founder CEO. Every 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.” — The implication: middle management’s job is not to buffer the founder’s intensity but to mirror it.

On withholding feedback as selfish [§ Feedback section] “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 — you’re optimizing for your own comfort.”

On PMF clarity [§ PMF section] “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.” — MacInnis attributes this to a VC (unnamed). His experience at Inkling: they thought they had it repeatedly. In retrospect, after experiencing Rippling’s growth, it was obvious they never did.

On compound SaaS vs point SaaS for AI [§ AI section] Point-solution SaaS struggles in the AI era for two reasons: (a) insufficient first-party data for meaningful AI utility; (b) dependence on integrations that are always “drinking data through a straw.” Companies that own a broad data graph (Rippling’s “people primitive”) and the shovels (OpenAI, Google) are the positions with durable economics. The middle — AI software built on third-party models and third-party data — will be squeezed by both.

Connections to other wiki pages