How Product Managers Run Feature Prioritisation Workshops
For Product managers · Based on Mehdi's 6C Workshop Design Framework
// TL;DR
Product managers can use Mehdi's 6C Workshop Design Framework to run feature prioritisation and roadmap sessions that actually ship. Instead of a chaotic brainstorm, the 6C sequence — Connect, Collect, Choose, Create, Commit, Celebrate — primes your team with real user pain points, forces a tight scope through prioritisation, generates focused ideas, and locks in owned actions with deadlines before the room empties. Use it whenever you have a product goal, a cross-functional team, and a fixed session length. The result: a half-day session produces what usually takes weeks of async back-and-forth.
Why do product workshops so often produce ideas that never ship?
Because most product sessions jump straight to brainstorming without priming the team on real user pain points, and end when the whiteboard is full instead of when actions are owned. The 6C framework fixes both failure modes. It sequences six phases — Connect, Collect, Choose, Create, Commit, Celebrate — so your team starts from evidence, narrows to a workable scope, and leaves with committed next steps. For product managers juggling stakeholders and sprint pressure, this turns a fuzzy meeting into a shippable plan.
How do you run a feature prioritisation workshop with the 6C framework?
Start by locking in your single goal — for example, "identify and prioritise features for the next release" — plus your audience and session length. Then design each phase in order:
- Connect: Run a short warm-up asking each participant to share one product they wish they had built. It reads the room and surfaces mindset. Sell it confidently and never call it an ice breaker.
- Collect: Have participants independently list the top user pain points they're aware of, then share and cluster them on a board. This is alignment, not ideation — it connects the team to real evidence before any solutions appear.
- Choose: Use an impact vs. effort matrix or dot voting to narrow to one or two scoped problem statements. This is your foundation scope. Skip it and your Create phase becomes an overwhelming mess.
- Create: Now brainstorm — a silent brainstorm followed by group build works well — but only on the chosen problem statements. Because the team is primed and scoped, output is sharper.
- Commit: Each team member writes their name next to one action they'll take before the next sprint, with a specific deadline. This is where product workshops usually fail — don't skip it.
- Celebrate: Walk the group through the full wall of work, from raw pain points to committed actions, and name what they achieved in three hours versus weeks of back-and-forth.
How do you keep the Choose phase tight enough to be useful?
Product teams are notorious for wanting to fix everything at once. The Choose phase exists to stop that. Use an explicit prioritisation mechanism — impact vs. effort scoring, forced ranking, or dot voting — and exit with no more than two problem statements. Remind the team they cannot fight every battle. A tight foundation scope is what makes the Create phase feasible; a loose one guarantees an unworkable ideation session and a roadmap no one can execute.
Why does the Commit phase matter more for product teams than anyone else?
Because product work lives and dies by follow-through across sprints. A great feature idea that isn't owned with a deadline evaporates the moment people return to their backlogs. The Commit phase forces every participant to name a concrete action, an owner, and a date before leaving. This is the difference between a workshop that fed the roadmap and one that generated sticky notes nobody touched again. Design it as deliberately as your brainstorm.
Start your next feature session by writing down your single workshop goal, your team's makeup, and your available time — then design each of the six phases in order before you walk into the room.
// FREQUENTLY ASKED QUESTIONS
Can I use the 6C framework for a remote product workshop?
Yes. Each phase maps to remote tools — use a virtual whiteboard for Collect clustering, digital dot voting for Choose, breakout rooms for Create, and a shared action tracker for Commit. Keep the sequence intact. Remote sessions especially benefit from a confident warm-up in Connect to build energy, and a clear Celebrate mapping since remote participants lose the arc even faster.
How long should a product prioritisation workshop be?
A half-day is common for feature prioritisation. Allocate time across all six phases during your review step — a short Connect, substantial Collect and Choose to build a tight scope, focused Create, and a real Commit with owners and deadlines. Never cut Commit to save time; it's the phase that makes the whole session pay off in your next sprint.
What if stakeholders disagree during the Choose phase?
That's exactly what Choose is for — surfacing and resolving disagreement through explicit prioritisation. Use a structured mechanism like impact vs. effort scoring or dot voting so decisions are transparent rather than political. Remember Choose also recurs later, so smaller disagreements during Create can be resolved with the same tools. Exit with a scoped problem statement everyone has visibly weighed in on.