The PM Framework Wrapper
A PM's real output is a framework that wraps strategy plus a point of view — and gets everyone to the same destination
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 90%
Field's definition of what an elite product manager actually produces. Not process, and not documents: a FRAMEWORK — a shared mental model that packages the strategy and a genuine point of view so that everyone on the team knows the destination and how to get there. The framework must also be socially load-bearing: it brings people along, and it makes them stoked at the milestone. A milestone hit by a miserable team is a failure, because the team won't gel for the next one.
Origin
Dylan Field's answer at Config 2024 to Lenny Rachitelli's question about what value the best PMs bring to Figma — asked in the shadow of Brian Chesky's prior claim on the same stage that Airbnb 'got rid of' product management. Field's answer is a defense of the function, redefined around framework-building rather than process-running.
Core principles
- 01The role boundaries between PM, designer, engineer and researcher are inherently blurry — stop trying to draw the line and staff for the qualities.
- 02Process supports good outcomes but is not the job. PMs fall down when they treat the role as process.
- 03A PM must have a strategy AND a point of view. Some points of view are wrong; having none is worse.
- 04The deliverable is a framework that gives the whole team a shared head space.
- 05An outcome achieved by an unhappy team is a failed outcome — the team won't gel for the next one.
- 06Everyone is learning more of everyone else's job right now, but the roles still hold real value.
How to run it
- 1
Stop defending the boundary; staff for the qualities
Do not spend energy formally defining what separates PM, designer and engineer. Instead ensure the qualities are present across the group: PMs and designers need enough technical understanding of how the systems work; designers and engineers need a sense of the business objectives and what users want; engineers and PMs need taste, craft, a sense of the option space, and a desire to care about the visual implementation.
Pro tip Add research as a fourth leg of the stool. All of them should be in direct dialogue with users.
Watch out In most organizations these lines are already blurry. Insisting on hard boundaries fights reality and produces turf, not product.
- 2
Refuse to make the job process
Good process supports good outcomes and is genuinely important — but a PM whose identity is the process has lost sight of the problem. Field's diagnosis of PM failure is exactly this substitution.
Watch out Process is the most visible part of the PM job, which is why it becomes the whole job by default.
- 3
Go to the problem and to the users
Stay anchored in the problems you are solving. Go talk to users directly rather than consuming research second-hand.
- 4
Form a strategy and a real point of view
Have an actual strategy, and — if you are good — a point of view on top of it. Field accepts that some points of view lead to good outcomes and some don't; the taste to pick well is the differentiator. Having no point of view is not the safe option, it is the disqualifying one.
Pro tip The point of view is the thing that survives contact with the intuition-as-hypothesis-generator debate. It should be arguable.
- 5
Wrap it into a framework everyone can hold
Take the strategy, take the point of view, and wrap it all up in a framework — such that everyone knows what the destination is and how to get there. This is the PM's actual artifact: a shared head space across the team.
Pro tip Test it by asking three random team members where the team is going. If you get three answers, the framework is not built.
- 6
Land the milestone with the team stoked
Bring everyone together to the objective and make sure the arrival is celebrated. At the end of a project or milestone, everyone should be stoked.
Watch out Field's hard rule: if you hit the milestone but everyone's unhappy, 'you kind of failed' — the team won't gel and you will not get the next outcome.
In the wild
After Brian Chesky said on the Config stage that Airbnb had gotten rid of product management, Figma's PM team was rattled — Field walked into a PM dinner to find a colleague doing a Chesky impersonation to the whole team. Field's response was to reaffirm the function while redefining its output as framework-building rather than process-running.
→ A defensible articulation of PM value that survives the 'PMs are just process' critique: PMs produce the shared strategic framework nobody else on the trio produces.
Lenny raises the observation that when a PM goes on vacation everything is fine for a week or two or three — and then things start to crumble, because the PM is the glue. Field's framing explains why: the glue is the shared framework, and it decays without an owner maintaining it.
→ A concrete diagnostic — if the team drifts within weeks of the PM leaving, the framework was being held in one person's head rather than actually installed in the team.
Common mistakes
Treating the role as process
Field names this as the specific failure mode of PMs who fall down. Process helps, but a PM who runs rituals without a strategy or point of view is producing coordination overhead, not product.
Having no point of view
A neutral PM who synthesizes everyone else's opinions adds no signal. Field is explicit that the best ones have a point of view — accepting that some points of view will be wrong.
Winning the milestone and losing the team
Delivering the outcome with an unhappy, ungelled team means you have burned the machine that produces the NEXT outcome. Field calls that a failure even when the milestone lands.
Is it for you?
Best for
Product managers who feel their role reduced to coordination and status updates, and product leaders defining what to actually hire and promote for
Not ideal for
Very early startups where the founder is the PM and no shared framework is needed because the whole team fits around one table
From the transcript
“when you see people that fall down in that function is because they treat it too much like process”
“you have to go talk to users and you have to actually have a strategy and if you're really good you should have a point…”
“good product people are able to do all this and they're able to create great Frameworks that bring everyone along with them and so everyone's…”
“again create those Frameworks that bring everyone else along and those Frameworks also have a point of view and a strategy associated with them so…”
“if everyone's unhappy like you kind of failed”
From the episode
Dylan Field live at Config: Intuition, simplicity, and the future of design