The Five Markers of High-Performing Product Teams
Coherence, stubborn beliefs, faith in product, matching words to actions, contextual skills.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 90%
After roughly 500 leader one-on-ones and 300-400 workshops across companies from two-person startups to Lego, Amazon and Ikea, Cutler distilled what actually separates high-performing product organisations. The list is deliberately mechanism-free: each marker can be reached many ways, but a team missing one of them stalls regardless of talent. Used as an audit, it points at which layer is broken rather than which tool to buy.
Origin
Cutler's own synthesis from four years as product evangelist at Amplitude, where he ran hundreds of coaching sessions and workshops with product teams worldwide.
Core principles
- 01Structure follows strategy — and as a company grows, the physics of structure catches up with it.
- 02High performance is a continuum you keep re-earning, not a state you achieve.
- 03Culture and values are the fabric underneath the markers, not a sixth item — but only if expressed as behaviours, not nouns.
- 04Common-sense markers are not easy markers; the difficulty is putting them in motion.
How to run it
- 1
Audit strategy-structure coherence
Check that funding approach, incentives, org chart and technical architecture all support the current strategy. Startups get away with fluidity; as you scale, mismatch becomes the dominant drag.
Pro tip If brilliant people are visibly failing, suspect this marker first — it is the one talent cannot compensate for.
- 2
Check for strong opinions, loosely held
Look for a small set of stubbornly held beliefs — the power of product, closeness to customers, a strategic bet, a pricing stance — that the team refuses to abandon even when short-term signals argue against them, balanced by genuine willingness to update on everything else.
Pro tip The tell is a team holding a position through a quarter where it doesn't yet make sense.
Watch out Stubbornness without the loosely-held half is just dogma.
- 3
Look for a slightly irrational belief in the power of product
High performers treat product as a layer cake: today's success was set in motion by decisions years ago. That belief requires a leap of faith no A/B test, spreadsheet or ROI model can supply — because the gap between a six-craft and a nine-craft product is never justifiable on data alone.
Pro tip This belief usually traces to founders or leaders who have personally seen craft compound before.
Watch out You cannot rationalise your way into this marker; teams that demand proof before investing in craft never get it.
- 4
Test leadership coherence — do words and actions match?
A domineering leader who is openly domineering is coherent. A leader who preaches empowerment and customer obsession while behaving otherwise is not. Coherence, not style, is the marker.
Pro tip Ask people what leadership actually does, not what leadership says it values, and compare.
- 5
Assess contextual skills, not generic pedigree
Skills matter, but they must be mediated by the environment. Ten years of B2B SaaS does not automatically equip someone for a messy bottom-up-plus-top-down motion. Draw the line between generic craft and the specific weirdness of your problem space.
Pro tip Companies with a knack for bringing raw talent up over 3-9 year tenures perform as well as companies that only hire vetted geniuses.
In the wild
Founders Klaus and Jon built AppFolio on two stubbornly held beliefs: go where the money flows and stay extremely close to customers, and never treat quality as something you sacrifice — adopting test-driven development and pair programming early because they believed quality shouldn't be a trade-off at all.
→ AppFolio became, in Cutler's words, a gem of a vertical B2B SaaS company, with those two beliefs settling debates that other companies relitigate forever.
Amplitude had to decide where to draw the line between hiring someone who is a pro at ten years of B2B SaaS versus someone who could embrace a messy bottom-up plus top-down product motion requiring more strategic thinking.
→ The skills marker was reframed as contextual fit rather than generic seniority.
Common mistakes
Writing culture documents in nouns
Saying 'we believe in ownership' says almost nothing — ownership in an individualistic culture looks completely different from ownership in a collectivist one. Only naming the specific behaviours that represent ownership tells anyone what the culture actually is.
Treating high performance as an achieved state
Plenty of companies flying high a year ago are not flying high now. Performance is a continuum, and coasting on a past peak is how the markers quietly decay.
Is it for you?
Best for
Product leaders, founders and heads of product diagnosing why a talented org is underperforming.
Not ideal for
Very early startups whose strategy is still in flux — structure coherence is not yet a meaningful constraint.
From the transcript
“the first thing you notice is the companies that are very high performing have coherence between the structure of their company and their current strategy”
“there is a leap of faith and there's a leap of faith that no amount of data or no amount of a b testing or…”
“saying that you believe in ownership without the addition of like what we would do successfully in Spencer and other people to successfully is talk…”
From the episode
What differentiates the highest-performing product teams
John Cutler (Amplitude, The Beautiful Mess)