Framework · Facilitation techniques · 3 min read
Buy a Feature
Give stakeholders a budget to 'buy' items, so trade-offs become tangible and negotiation happens in the open.
- Explain
Show the priced list and the rules; hand out budgets
- Buy and negotiate
People spend, pool money and argue for items out loud
- Debrief
Ask why items were bought, pooled or left unbought
About 30 minutes in total · works with 4–8 buyers per list
Use it when
- Several product managers each want UX time, and every request is "top priority".
- Stakeholders say yes to everything on a list, and you need them to feel the trade-off.
- You want to understand what a group values most, not only what it ranks first.
How to use it
- Price the items by effort. List 8–15 items (features, research studies, design-system work) and give each a price based on effort. Some items should cost more than one person's budget. Output: a priced list. Prepare before the session.
- Set a budget below the total cost. Give each person the same budget. Make the total of all budgets clearly less than the cost of all items, so only part of the list can be bought. Output: a budget per person, in play money or tokens.
- Let people buy and pool money. People spend their budget on items. Expensive items can only be bought when several people pool money, so they must argue for them out loud. Output: bought and unbought items. About 15 minutes.
- Listen and take notes. As facilitator, stay out of the buying. Write down the reasons people give and who teams up with whom. Output: notes on reasons and alliances.
- Debrief the result. Ask: "Why did these items win? Why did nobody buy this one? What surprised you?" Treat the result as strong input to the decision, and name who decides. Output: a priority list with reasons. About 10 minutes.
Worked example
A UX lead runs Buy a Feature with 5 product managers in a quarterly capacity session for an internal operations platform. Each product manager gets 100 points. The items cost 900 points in total, so only about half can be bought.
| Item | Price | Bought? | Why (from the debrief) |
|---|---|---|---|
| Redesign the planning screen | 300 | Yes, 3 people pooled | "It affects all our users every day." |
| Usability test of the new booking flow | 100 | Yes, 2 people pooled | "We launch next quarter and have no data yet." |
| Shared filter pattern in the design system | 150 | Yes, 2 people pooled | Two teams realised they wanted the same thing. |
| Dark theme | 150 | No | "Nice to have; nobody asked for it." |
| New icons for one product | 200 | No | Only one product manager wanted it. |
The UX lead uses the result and the reasons as input to the priority order, and states in the summary what UX is not doing next quarter.
Watch out for
- A budget that is too big. If people can buy almost everything, there is no trade-off. Keep the total budget well below the total cost.
- Prices nobody believes. If prices don't reflect real effort, the result is meaningless. Check prices with a designer or developer first.
- Treating the result as the final decision. The game shows value and trade-offs. The Approver still decides, for example with Weighted scoring.
- Skipping the debrief. Without the "why" conversation you only get a list, not the understanding behind it.
Template
Copy this into the session board or a spreadsheet.
BUY A FEATURE About 30 min
Budget per person: ____ Total budget: ____ Total cost: ____
(Total budget must be clearly less than total cost)
Item Price Bought by (amount) Total paid
1.
2.
3.
4.
5.
Debrief:
- Why did these items win?
- Why did nobody buy ___?
- What surprised you?
Who makes the final decision: