Fine-tune the use casePick the one closest to you
A product program forteams facing
You agreed the product priorities. Why does every department still want something different?
Because the list was agreed in one meeting and read five ways after it. Sales wants the deal-closer, Support wants the fixes, Finance wants the margin feature, and the squads build whoever shouted last. This program aligns what your department heads know, believe and do about your product's priorities, in four one-hour team sessions.
Make it for your team
Execution readinessExample scores for a team like yours. Add your website to estimate your own. Measured once your team plays. Ready at 80.
Where it usually breaks41Today92/ 100After the 4 team sessions
Ready to executeShared knowledgeHigh riskFive departments, five different versions of the list
Shared convictionHigh riskEach department believes its request is the exception
Shared practiceMedium riskRequests go straight to the squads, around the list
4 sessions~50 min each8–12 people per teamNo facilitatorThe gap
What you'd typically hear if five of your product people answered alone.
SESSION 1 · FILL THE GAPSAnswered alone
Finish the sentence: when my department needs something that is not on the product priority list, I…MMira…take it to the next priority review and make the case there.
JJonas…ask the squad lead directly. They know me.
AAylin…escalate to the head of product.
TTomas…wait. It will come up eventually.
RRosa…honestly, I'm not sure the list is real.
What it costs you if nobody notices
Shared knowledgeThe list is read five waysWhen every department remembers a different version of what was agreed, the squads hear five priorities and pick their own.
Shared convictionEveryone is the exceptionA department head who believes their request is special goes around the list, and every other head learns to do the same.
Shared practiceThe squads get whiplashWork started on a side request is work stopped on the priority, and the thing everyone agreed on ships late.
The program that closes the gap
Four one-hour sessions. Every one of your department heads, behind one list, and one door for everything else.
Session
Shared knowledgeShared convictionShared practice
S1Know the listAgrees what is on the priority list, in what order, and why each item is there.
Shared knowledge1Quiz each other on what's actually on the priority list2Agree what the priority list saysShared conviction3Decide the priority list as the CPO wouldShared practice4Agree what is on the priority list5Rehearse the moment a side request lands on your desk
DemoS2Stand behind itShows you whether each department believes the order, and where they would break it.
Shared knowledge1Test what each department head actually believes about…Shared conviction2Face what it costs if the priority list doesn't hold3Decide as the CPO would on an off list requestShared practice4Test whether every department would actually hold the line…5Rehearse the moment a department head faces a request that…
DemoS3Rank the real requestsRanks the same product requests alone, compares the orders and aligns on what comes first.
Shared knowledge1Quiz each other on the rule for ordering product requestsShared conviction2Decide the build order for five real product requestsShared practice3Rank five real product requests by what it costs the…4Sort five real product requests into the order the squads…
DemoS4Handle the side requestPractises the request that is not on the list: what to say, where it goes, what never bypasses the list.
Shared knowledge1Learn and align on exactly what to do with a request that…Shared conviction2Decide how to handle an off-list request as the CPO wouldShared practice3Rehearse the move for a side request4Rehearse the exact words
DemoPlay it yourself · a short demo · one exercise from session 3 · Get the Order Right
Alone first. Then the team agrees on one answer.
This is a taste, not the whole session. “Rank the real requests” runs 4 exercises with your own team, on a call or in a room. Here is one of them, on the real screens, played with four AI teammates, so you can feel how a session works.
Rank the real requests · Get the Order Right00:00MJLSYouRank five real product requests by what it costs the company to make them waitOn screen: Rank these five product requests from most to least costly to leave waiting, alone
You are playing with 4 AI teammates. Every screen opens on its briefing: read it, then tap I’m ready.
Readiness intelligence · what you'll see as teams play
Know which of your department heads stand behind the list, and where you should step in, before the squads hear five priorities again.
Your company › Readiness intelligence › One product priority listEvery department stands behind one list of what gets built first
Readiness index92%Ready+51 pts25% participation + 25% progress + 50% alignment · Ready at 80
Shared knowledge48 → 88Shared conviction37 → 71Shared practice44 → 80
Participation94%8 of 8 people played at least once
Progress75%3 of 4 planned sessions completed
Alignment41% →78%25 of 32 points aligned
Failed alignment pointsWhere you should step in
The order of the five requestsNot aligned in 13 of 32 playsShared knowledgeYour Sales and Support leads · 9 people
Is my request really the exception?"Not yet, we still have concerns" in 2 playsShared convictionYour commercial leads · 6 people
Your department heads could play this next week. Add your website to make it yours.
- 01 · 5 minConfirm the assumptionsCheck what we inferred about you and edit any text in place. Your edits are locked.
- 02 · 1 link per teamInvite your teamAny browser, any device. No account, nothing to install.
- 03 · after each playWatch readiness fill inYou see who played, what they agreed, and where to follow up.
Used by teams at
Free until you play live · ISO 27001 · EU data
Free until you play live · ISO 27001 · EU data