Year-Horizon Growth Portfolio
Protect growth teams from weekly-win pressure by committing to low/medium/high bets over a year-long horizon
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 85%
Because ~80% of experiments fail, holding a growth team to weekly or even monthly win quotas breeds vanity metrics and data-massaging. The fix is to commit to movement over a year, framed as a portfolio of low/medium/high bets, and to actively educate the rest of the org so expectations match the reality of how growth learning works.
Origin
Laura Schaffer developed this across her time at Twilio and rapid (and expects to at Amplitude), saying she spends a large 'pie chart' of her time educating stakeholders on the healthiest ecosystem for a growth team.
Core principles
- 01Short-timeline win pressure is conducive to vanity metrics and massaging data to fit
- 02Given enough time to fail and learn, a growth team will produce real wins
- 03Frame commitments as a portfolio: low/medium/high bets, not a single number
- 04Results are lumpy — some bets take a long time to validate, others move fast
- 05Educating stakeholders on the ~80% fail rate is core, ongoing growth-leader work
How to run it
- 1
Commit over a year, not a week
Set commitments a growth team can deliver over roughly a year rather than weekly or monthly win quotas.
Pro tip Especially important for newer teams, but useful for teams in general.
Watch out Teams beholden to short-timeline wins create an environment conducive to vanity metrics and data massaging.
- 2
Frame bets as low / medium / high
Structure the plan as a few core high-upside hypotheses ('lightning in a bottle' or 'paper mist' — unknown until run), plus safer medium bets partly validated in the prior year.
- 3
Set expectations that results are lumpy
Communicate that some wins (e.g. a pipeline-generating bet worth tens of millions) take long to validate while onboarding tweaks move faster, so movement won't be weekly.
- 4
Continuously educate stakeholders
Spend real time teaching the org the base fail rate and the healthiest operating conditions so no one shows up weekly asking 'what did you do these past couple days?'
In the wild
Schaffer contrasts a high bet at Twilio — a low-code 'Quick Deploy / create-your-own-demo' capability that generated tens of millions in pipeline but took a long time to navigate and validate — with faster-moving onboarding tweaks, to illustrate why a growth portfolio is lumpy and needs a year horizon.
→ Framing commitments as year-long low/medium/high bets kept stakeholders from demanding weekly wins and gave the team room to land large, slow-to-validate successes.
Common mistakes
Holding a growth team to a single weekly/monthly number
Given the high fail rate, short-timeline win pressure pushes teams toward vanity metrics and massaging data to fit — an environment where genuine success is impossible.
Not educating the rest of the org
If stakeholders don't understand the ~80% fail rate and lumpy timelines, they apply weekly pressure that undermines the team; educating out is core growth-leader work, not optional.
Is it for you?
Best for
Growth leaders setting expectations and planning cadence for a growth team, especially newer teams
Not ideal for
Contexts demanding fast, predictable weekly operational wins rather than validated learning
From the transcript
“any growth team that's that's beholden to short timeline wins and Improvement is always going to be dangerous that's a that's an environment that's conducive…”
“commit to something that you can kind of do over the course of a year and you know low medium high”
“there's one thing that we did that generated like tens of millions of dollars in Pipelines”
“help people understand the methods there so that they're not coming at you on a weekly basis”
From the episode
Career frameworks, A/B testing mistakes, counterintuitive onboarding tips, selling to developers
Laura Schaffer (VP of Growth at Amplitude)