The AMPED Cross-Functional Product Org
Redefine 'product org' as Analytics, Marketing, Product, Engineering, Design — all embedded in every stream.
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 4
- Confidence
- 85%
At Miro, 'the product org' does not mean PMs, designers, and engineers — it means AMPED: Analytics, Marketing (product marketing), Product, Engineering, and Design, with each function deeply embedded inside every persona-based stream. Embedding product marketing and analytics alongside product prevents persona-based streams from tunnel-visioning on their own user's pain points: someone always asks about the end-user experience, the enterprise requirements, or the positioning, providing built-in course-correction.
Origin
Predates Parmar's tenure at Miro (he declines credit); rooted in founder/CEO Andrey's cultural value of teamwork and breaking down cross-functional silos.
Core principles
- 01Innovation happens at the intersection of cross-functional people coming together.
- 02Embedding marketing and analytics into product teams surfaces positioning and end-user perspectives early, not downstream.
- 03A persona-based org risks tunnel vision; cross-functional embedding is the counterweight.
- 04The best work comes from bringing diverse perspectives to the problem, then creating the customer outcome together.
How to run it
- 1
Redefine what 'product org' includes
Expand the definition of the product organization to Analytics, Marketing, Product, Engineering, and Design (AMPED) rather than just PM/design/eng.
- 2
Embed product marketing into every stream
Place product marketing deeply inside each persona stream so positioning, differentiation, and packaging are considered from the start.
Pro tip Product marketing catches when a built feature fails to 'capture the imagination' of the original vision and helps sellers position it.
- 3
Let embedded functions course-correct
Rely on the cross-functional mix to raise 'did you think about the end-user experience / the enterprise requirements?' before decisions harden.
Watch out A persona-based structure without this mix drifts into adding narrow features that fragment the holistic experience.
- 4
Reinforce with shared reviews and checklists
Pair AMPED with open product reviews (small/medium work shared in a Slack channel anyone can subscribe to; big work through a formal review) and a democratized enterprise-requirements checklist so holistic and enterprise concerns are considered up front.
Pro tip Keep a checklist of the ~10 enterprise things to consider early so they don't surface downstream.
In the wild
At a bi-weekly 'Miro Connect' demo event in Berlin, a team described a feature they estimated at three months. A passing engineer who had implemented that exact problem in a prior life offered to help, went home, coded the whole thing with a pull request in three to four hours, and the core team merged it the next morning.
→ Work estimated at three months was completed in roughly three hours because a cross-functional demo ritual connected the right expertise to the problem.
Common mistakes
Defining the product org as only PM/design/eng
Excluding analytics and product marketing from the core team means positioning, differentiation, and end-user perspective get considered downstream, after the architecture has hardened, when they're expensive to add.
Letting persona streams pigeonhole into feature-adding
A pure persona-based org tends to keep bolting on features that solve one user's pain points, fragmenting the holistic experience; without embedded cross-functional voices there's no built-in course-correction.
Is it for you?
Best for
Scaling product organizations structured around personas/streams that need to keep a holistic, well-positioned product.
Not ideal for
Very early teams where everyone already sits together and formal cross-functional embedding is redundant.
From the transcript
“amp stands for like analytics marketing product engineering and design and everything that we do in the product org when we say the product org…”
“by having this cross-functional representation where product marketing team is deeply deeply embedded inside of each of these streams what we do is that we…”
“something that would have taken you know three months for this core team because they didn't have the expertise literally got got done in in…”
From the episode
An inside look at how Miro builds product: Lessons on outmaneuvering competitors, team structure, product quality, and moving fast
Varun Parmar (CPO of Miro)