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

MacInnis opens with the thesis he wants the whole conversation judged against: extraordinary outcomes are not merely helped by extraordinary effort, they are unavailable without it. He is careful about the direction of the implication. Effort is not sufficient, but he insists it is necessary, and he treats any leader who has stopped believing that as a leader who has quietly given up on the top of the distribution.

extraordinary results require extraordinary efforts

The operational test he offers is deliberately uncomfortable: comfort at work is evidence of error rather than evidence of health. That is a strong claim, and he states it flatly rather than as a metaphor.

if they ever find themselves in the comfort zone at work, they are definitely making a mistake

He also names the cost honestly rather than dressing it up. The work is supposed to be exhausting; the exhaustion is not a failure mode to be designed out.

It's supposed to be really fricking exhausting.

Asked about escalating issues, MacInnis reframes the question. The interesting failure is not the escalation, it is the silence that precedes it. He argues that withholding a useful observation because delivering it would be awkward is a choice to optimise for your own comfort at someone else's expense, and he is blunt that this is the most selfish option available to a manager.

From there he generalises into an organisational claim. Teams drift toward local comfort over company outcomes by default, and the drift is not a character flaw in any individual but a structural tendency that leadership has to counteract continuously.

His model of where energy comes from is a gradient rather than a quantity. The founder CEO holds the most intense version of the company's ambition, and each management layer outward risks losing an order of magnitude of it. He does not treat that decay as unfortunate; he treats it as the thing a leader is employed to prevent.

Every next concentric circle of management beyond the founder CEO has the potential to be an order of magnitude drop off in intensity.

He also flags, without resolving it here, that the Silicon Valley injunction to never quit is not neutral advice. He returns to that thread much later in the conversation, and it is one of the places where he explicitly disagrees with the prevailing norm of his own industry.

Lenny frames the episode around MacInnis's unusual position: chief product officer at Rippling, previously its long-serving chief operating officer, at a company valued above sixteen billion dollars with more than five thousand employees. The point of the framing is that the advice comes from someone who has run large functions inside a business that is currently winning, which matters for the argument MacInnis makes about air cover later in this section.

MacInnis attributes the formulation to Dan Gill at Carvana and then immediately widens it. His claim is that product leadership is a particular instance of management in general, and that a chief product officer is not doing anything categorically different from a chief anything officer. The frameworks transfer; only the domain vocabulary changes.

He then draws the uncomfortable implication. If the target is the ninety-ninth percentile of outcomes, the process will be uncomfortable by construction, and a leader who does not say so out loud is implicitly promising something that cannot be delivered. He is explicit that effort is necessary but not sufficient, which keeps the claim from being a motivational slogan.

Asked for concrete examples of extraordinarily hard moments, MacInnis refuses the invitation to tell a single heroic story. The effort, in his account, is distributed across a thousand small events rather than concentrated in a few dramatic ones, and the exemplars he chooses are mundane: an escalation on a Friday night, a batch of new bugs that need triage.

That is where he locates the separation between good and great teams. The claim is not that great teams work harder in general, but that they are willing to absorb the unglamorous interruption at the moment it arrives.

He also acknowledges the obvious objection to his own position: it is easy to preach intensity at a company that is winning. His response is not to deny it but to make the growth itself part of the mechanism. Rapid growth supplies the air cover a leader needs to ask for the last of someone's energy, because the contributor can see that the effort is likely to convert into an outcome worth having.

This produces a real limitation in the theory, and he states it rather than hiding it. Where growth is thirty or forty percent rather than extraordinary, the same request is much harder to justify, and the honesty of the ask depends on whether an extraordinary outcome is actually available.

Lenny offers a corroborating observation from Airbnb under Brian Chesky: success never produced a pause, only a search for more throttle. MacInnis matches it with seven years at Apple under Steve Jobs, where shipping one iPhone immediately put the team into the next one, in what they called the death march.

His justification is competitive rather than cultural. In a valuable market the competition is by definition intense, and any gap left open will be filled by someone hungrier. The organisation as a collective cannot relax, even though individuals obviously must be allowed to live their lives.

The distinction he draws is worth noting because it is where most intensity arguments go wrong: he separates grinding individuals down, which he rejects, from maintaining collective attention, which he treats as non-negotiable.