The Five Ingredients of a High-Performing Team
Clear goals + a why, results culture, team-first, ownership, and fun — in that order
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 88%
Across Dropbox, Typeform, Canva, Grammarly, Miro, and Webflow, Tan found the same five ingredients in every high-performing team. The subtle part is the tension between them: a hard results culture naturally produces internal competition, so team-first behavior must be deliberately engineered — by the leader modelling it and by feeding context between people even when it doesn't help their own metrics.
Origin
Melissa Tan, synthesized from her time at Dropbox and advising/leading growth at Typeform, Canva, Grammarly, Miro, Ro, and Webflow.
Core principles
- 01Metrics answer 'what'; the mission answers 'why' — you need both
- 02Monetization is a signal that people find the product valuable, not the purpose
- 03Results-orientation creates competition unless team-first is actively countered into it
- 041 + 1 = 3 comes from refusing to locally optimize
- 05Fun is a performance input in high-pressure environments, not a perk
How to run it
- 1
Set clear goals with a North Star and its levers
Name the North Star metric (at Webflow: ARR), then break it into the leading indicators that drive it — activation rate, number of customers acquired, etc. Each sub-team gets clear goals from that decomposition.
- 2
Attach a mission — the why
Pair the metrics with the reason: at Webflow, building delightful experiences and supporting users on their journey. Monetization is the measurement, not the mission — it's a signal that users find real value, especially when they keep paying and retaining.
Watch out A team goaled purely on revenue with no why will optimize the metric against the user.
- 3
Build a results-oriented culture
Make it unambiguous that the team is measured on impact, that goals are broken into individual levers, and that each person knows how their success is measured.
- 4
Counter-engineer team-first behavior
Because clear individual results invite competition, actively push against it: as the leader you hold the full context, so route it to people who could contribute to work outside their own scope — even when it doesn't feed their own impact. Then lead by example by helping other teams yourself.
Pro tip Timebox any work you personally absorb: 'I'll do this for a quarter, then we hand it off.' Your own dropped balls are the signal you took on too much.
Watch out If people can only be rewarded for what they personally drove, they will stop helping each other and the team locally optimizes.
- 5
Instill ownership, and have fun
Give each person meaty scope they can run independently and a proactive 'what am I going to do about this block?' mindset. Then deliberately keep it fun — in high-pressure environments, the more fun you infuse, the better everything works.
In the wild
Nobody at Webflow was driving pricing and packaging, so Tan took it on — including enterprise pricing, even though she oversaw self-serve — because it was a huge opportunity area. She used it to show her team that helping the company beyond your scope is the norm.
→ It set the team-first tone by example. She also received feedback from her own team that she sometimes takes on too much, which is why she now timeboxes absorbed work and names a hand-off point.
Common mistakes
Letting impact-based reviews breed internal competition
When performance is tied purely to 'how much of that impact was yours versus your teammates',' people stop sharing learnings and start locally optimizing. The leader has to explicitly encourage cross-team contribution that doesn't feed anyone's individual metric.
Helping everyone until you drop your own commitments
Being good at many things pulls you into everything and leads to burnout and lost focus. The signal that you've overextended is when things you're ultimately responsible for start slipping.
Is it for you?
Best for
Growth and product leaders diagnosing why a team with clear metrics still isn't performing
Not ideal for
Teams whose output genuinely isn't measurable, where a results-oriented culture would create false precision
From the transcript
“I think it first starts with the team having a really clear really clear goals.”
“the reason why the what is monetization is that's just a good signal that people find your product valuable”
“I think that's what ends up being like a situation where 1 + 1 = 3. You're not locally optimizing”
“if you start to see things that are starting to drop that you're ultimately responsible for, that's a signal that you're you're taking on too…”
From the episode
Building high-performing teams
Melissa Tan (Webflow, Dropbox, Canva)