When to use it
Use The Trade-Off when you have too many features and can't prioritise, when every stakeholder says their feature is essential, or when your roadmap keeps growing but nothing ships.
It's particularly effective in The Test — when you need to cut through consensus and find out what customers would actually pay for versus what the team thinks matters.
How it works in The Studio
Here's how a session works with WAiDE:
Sample output
Here's what a Trade-Off value stack looks like in practice:
| Feature | Wins | Rank | Surprise |
|---|---|---|---|
| Real-time collaboration | 6/6 | Must-have | Expected |
| Mobile app | 5/6 | Must-have | Higher than expected |
| Price: $19/mo | 5/6 | Must-have | Price won more than features |
| Integrations (Slack, Jira) | 3/6 | Nice-to-have | Team thought this was #1 |
| Custom dashboards | 2/6 | Nice-to-have | Founder's pet feature |
| AI task suggestions | 1/6 | Expendable | Lost almost every round |
| White-label branding | 0/6 | Expendable | Never survived a trade-off |
What you get
A ranked value stack showing which features are must-have versus expendable, side-by-side bundle comparison cards from each round, and a minimum viable offer built only from features that survived the trade-offs.
Your downloadable report includes the full trade-off rounds, the value stack, WAiDE's coaching observations on what you were most wrong about, and relevant Wade articles and programs.
Foundation
Rooted in conjoint analysis — a market research technique developed in the 1970s to measure how consumers value different attributes of a product. Used extensively in pricing research, product design, and feature prioritisation. Adapted here as a facilitated coaching exercise.
Why it works
Trade-off analysis works because preferences are revealed in choices, not in ratings. When you ask people to rate features from 1 to 10, everyone gives everything an 8 or above — there's no cost to being enthusiastic. When you force a choice between features in a zero-sum context, real preferences emerge. Conjoint analysis was developed in the 1970s for exactly this reason: marketers discovered that survey-stated preferences were reliably poor predictors of actual purchase behaviour, but forced-choice exercises predicted it well.
The mechanism is constraint-induced honesty. When choosing between two features in a bundle, the person must reveal which they value more — not which they think they should value, or which sounds more impressive, but which they'd actually sacrifice the other to keep. Teams doing this exercise almost universally discover that the features they thought were essential are not, and that the true core of their value proposition is smaller and sharper than they believed. This is uncomfortable and tremendously useful.
For product teams, this connects to Michael Porter's core insight in "Competitive Strategy": sustainable competitive advantage requires explicit choices about what you will not do. Companies that try to be all things to all customers end up in the middle — not differentiated enough to be the obvious choice for anyone. The trade-off exercise is a laboratory version of this: it forces explicit decisions about what stays in and what comes out, producing a minimum viable offer that is defined by its constraints as much as its features.
The mechanism: Forced trade-offs convert implicit preferences into explicit ones, and explicit preferences into a prioritised feature set. The discipline is that every item that survives the exercise has earned its place under competitive pressure — not just because someone wanted to keep it, but because it consistently won when put directly against alternatives. What's left is the core of the value proposition.
Frequently asked questions
Can I use this exercise with actual customers rather than just internally?
Yes — and that's often the most valuable application. Running trade-off exercises with customers reveals what they actually value rather than what they say they value, and it frequently contradicts the team's assumptions. If you're unsure whether to build feature A or feature B, a trade-off exercise with 10-15 target customers will produce more actionable data than any number of customer interviews where people tell you both are important. The forced choice is the key: it cannot be gamed the way a rating scale can.
What if two features are genuinely equally important and I can't choose between them?
That's useful information in itself — it means you haven't yet found the right level of specificity. When two features feel genuinely equal, it usually means they're both proxies for a more fundamental value that you haven't yet named. WAiDE will push you to go one level deeper: what specifically does each feature enable for the customer? Once you reach the underlying need, the priority usually becomes clear. If it genuinely doesn't, you may have identified a place where you need customer evidence to break the tie.
How is this different from just ranking features in order of importance?
Simple ranking is easy to do thoughtlessly and produces an ordered list without understanding the gaps between items. Trade-off forcing reveals the marginal value — how much less you're willing to accept of one thing to get more of another. The insight is in the choices under constraint: a feature that always wins trade-offs is genuinely core; a feature that always loses is expendable no matter how highly it ranks in a survey. The competitive context of each choice is what produces the signal that a simple ranking misses.
What do I do with the minimum viable offer once the exercise is complete?
Test it. The trade-off exercise produces a hypothesis about your core value proposition — the features that survived competitive pressure. The next step is to put that stripped-down offer in front of real customers and observe their response. Does the minimum viable offer still generate the demand you'd expect? If yes, you've found your core and can build from there. If not, the exercise has revealed something important: either the wrong features survived the trade-offs, or there's a feature that didn't make the cut but turns out to be essential.