Frameworks as Job Aids, Reps as the Goal
Adopting a framework is never the goal; getting reps through the full loop is.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
Large and transforming companies routinely read about how a Silicon Valley company works and treat installing that company's frameworks as the objective. Cutler's counter-model: a framework is a job aid — a learning tool a team uses to stay on track, which they should freely reinvent when it stops working. What the company actually needs is reps: protected pods where a team can go through the full loop of shipping and learning, adapting the advice on the small rather than installing it wholesale.
Origin
Cutler's synthesis from coaching enterprise and non-Silicon-Valley product teams at Amplitude. He points to Teresa Torres's continuous discovery and opportunity solution tree as examples of genuinely universal techniques that travel well across contexts, in contrast to arcane niche activities.
Core principles
- 01Most product advice is written from and for the Silicon Valley startup context, optimised for the first big arc of growth and pure digital products.
- 02Big companies overestimate their systemic drag; high performers underestimate how much luck and inertia carried them. Both are fundamental attribution bias.
- 03A framework that a team never reinvents when it stops working has become a ritual.
- 04Prefer universal techniques — ones any team at any maturity can find accessible — over context-locked ones.
How to run it
- 1
Name your structural inertia honestly
Identify the real constraints: executives who have never shipped product, an assumption that there is only one way to do things, annual budgeting and planning cycles, a large IT industrial complex. These are not excuses; they are the terrain.
Watch out Naming inertia is step one, not the conclusion. Teams that stop here throw up their hands.
- 2
Read all Silicon Valley advice contextually
Ask what context produced this advice. Most of it comes from startups optimised for scaling problems, never disrupted by anything but their own growth, and building pure digital products — not logistics, not global legacy brands.
Pro tip Writers of such advice should add the caveat themselves: this may not work at your company, but maybe it can.
- 3
Create pods where a team can get reps
Build small protected areas where a team can go through the entire loop — shipping product, shipping, and learning from it — rather than trying to transform the whole organisation at once.
Pro tip The target is a full loop, not a demo. If the pod cannot ship and learn, it is theatre.
Watch out This is adjacent to the Innovation Lab pattern and inherits its failure modes; the pod must be doing real work in the real business, not a sandbox.
- 4
Demote frameworks to job aids and reinvent them when they stop working
Treat any framework you adopt as a learning tool that keeps the team on track. Grant explicit permission to modify or discard it. Cutler notes the companies that do well are exactly the ones that reinvent the things they're using when things aren't working out.
Pro tip Ask the team quarterly: which part of this framework is now ceremony? Then cut it.
Watch out If you can't articulate what the framework is helping you learn, you have adopted the artefact and not the practice.
In the wild
An Amplitude customer, Anheuser-Busch, built BEES — a liquor distribution app that lets a bodega order beer directly — which became one of the biggest B2B businesses in the world, and grew into logistics use cases.
→ A company nobody would file under 'modern product org' shipped a category-leading product, showing that the high-performing/low-performing spectrum hides a whole universe of companies riding different waves.
Angela, a leader at Lego, is transforming one of the most iconic brands in the world into something digital, across thousands of people, where the impact of the work might not even be visible within her tenure.
→ Cutler describes the work as clicking despite being genuinely hard — a role model case that no Silicon Valley framework install would have produced.
Common mistakes
Treating framework adoption as the end goal
Companies read how Figma works, conclude 'we've got to use these frameworks', and score themselves on installation rather than on whether the team ships and learns faster.
Deploying a tool out of context
Cutler observed that people putting tools into play out of context sometimes produced worse effects than not doing it at all.
Is it for you?
Best for
Product leaders in large, transforming, non-Silicon-Valley companies who keep failing to make imported best practice stick.
Not ideal for
Small startups already running fast full loops — they need less framework scepticism, not more.
From the transcript
“for a lot of those companies they see adopting the Frameworks as the end goal”
“the way that I tend to think about Frameworks is that they're more like a job aid they're more like a learning tool that the…”
“the idea that you can create these little bastions where a team can get in the Reps meaning shipping shipping product shipping and learning like…”
From the episode
What differentiates the highest-performing product teams
John Cutler (Amplitude, The Beautiful Mess)