The Tempo Framework
Align every team on what shipping cadence 'good' looks like, then close the gap
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 90%
A cascading alignment system where leadership sets mission, mission-metric, and guiding principles at the top, each org leader translates that into a concrete shipping cadence that defines 'good,' and leadership meetings become gap-closing conversations. Campbell argues your tempo framework matters more than your org design because misalignment on what good looks like — not bad hires — is usually why teams underperform.
Origin
Developed by Patrick Campbell at ProfitWell after the team 'got into hyperdrive about team' and hit repeated misalignment on shipping expectations.
Core principles
- 01Real professionals ship, and ship at high frequency, whatever their function
- 02Tempo alignment is more important than org design
- 03Low output is usually an org problem, not a person problem
- 04'Good' must be defined as a specific, countable cadence, not a vibe
How to run it
- 1
Set mission, mission-metric, and guiding principles at the top
Define what you do, how you measure it, and how you'll get there. At ProfitWell: automate subscription growth (mission), revenue on ProfitWell (mission metric), be the most helpful brand in SaaS and do-it-for-you (guiding principles).
Pro tip Pick a mission metric that doubles as a proof you're doing your job, not just a vanity number.
- 2
Have each org leader define what 'good' shipping looks like
Marketing, sales, product each set a concrete cadence: X episodes per month, X product launches per month, one big launch per quarter — whatever fits their function.
Watch out If you never name a countable cadence, misalignment is guaranteed and silent.
- 3
Run leadership as a gap-closing conversation
Compare actual output to the agreed 'good,' then diagnose the blocker: 'You shipped one thing per quarter, we want one per month — why?' Usually the answer is resources or a cross-team handoff, both solvable.
Pro tip When you find the same why twice, it's a systems fix (e.g. force two teams to talk), not a performance conversation.
In the wild
Campbell describes waking up nine months in thinking 'Tim sucks' because he isn't shipping — but Tim was a rock star elsewhere. The real cause was that marketing needed one announcement a month and product (Neil) wasn't providing anything to announce.
→ Getting the two people to agree 'provide one thing a month, marketing positions it' restored tempo without any personnel change.
Common mistakes
Blaming the person instead of the system
Suddenly deciding a proven hire 'sucks' months in almost always means expectations on tempo were never set and the constant gap conversation never happened — it's an org failure, not a Tim failure.
Leaving 'good' undefined
Without a countable cadence and a forum to discuss it, each leader silently assumes a different bar (one launch/quarter vs one/month), creating friction and resentment on both sides.
Is it for you?
Best for
Founders and org leaders of 10-100+ person teams who feel smart people are always planning but rarely shipping
Not ideal for
Tiny pre-product-market-fit teams where cadence is still being discovered and rigid metrics would be premature
From the transcript
“your Tempo framework is more important than your org design”
“most of the time you just haven't set an expectation of like what good looks like in terms of tempo”
“it's probably an org problem rather than like a Tim problem”
From the episode
10 lessons on bootstrapping a $200m business
Patrick Campbell (ProfitWell)