Tempo Framework
Patrick Campbell‘s claim that a shared, explicit definition of shipping cadence — what ‘good’ output looks like for each function — matters more than org design. ‘Real professionals ship’, at frequency, whatever their discipline; teams that look smart but ship slowly almost always lack agreement on tempo, not talent.
The build
- Mission metric and guiding principles at the top. What you measure and how you’ll get there. At ProfitWell the mission metric was revenue running on the product (good for acquisition and a sign the team was doing its job), with principles like ‘be the most helpful brand in SaaS’ and ‘do it for you’.
- Each org leader defines what good looks like. Concretely and per function — so many episodes per month, so many product launches per quarter, a medium launch monthly and a big one quarterly.
- Leadership becomes a gap conversation. ‘We agreed good is one launch a month; you shipped one this quarter — why?’ Each answer (‘not enough resources’, ‘this other team isn’t providing me anything’) surfaces a solvable constraint, and you keep closing the gap.
Why it beats org design
Without a shared tempo, misalignment festers silently: nine months in, a leader decides ‘Tim isn’t shipping, Tim sucks’ — when the real cause is an unset expectation, usually two teams not talking (marketing wants launches, product isn’t feeding them anything). The tempo conversation converts a personnel verdict into an org problem you can fix. Because you already vetted Tim and he was a star elsewhere, the difference is almost always the system, not the person.
See also
- Patrick Campbell on Pricing, Retention, and Bootstrapping ProfitWell — source episode
- Tactical vs Strategic Retention, Value Metric — the other core concepts from the same episode
- Shape Up — an alternative cadence model (fixed appetites, six-week cycles)