Reading tradeoffs
Surface what a decision gains, loses, and defers instead of arguing preferences.
Most product arguments are two people naming different costs and pretending they disagree about the same thing.
Your checkout has a guest option. Growth wants to force account creation to lift 90-day retention; the guest path converts 6 points higher today. Both cite real data. The room is split and looking at you.
How do you move the decision forward?
Disagreement is usually about hidden costs
When two credible people argue past each other, it's rarely because one is wrong. It's because each is holding a different cost in view. The growth PM sees the retention a guest checkout leaks; the conversion PM sees the customers an account wall turns away. Both are right about their cost and blind to the other's.
Reading a tradeoff means refusing to argue the conclusion until both costs are on the table in the same units. Not "accounts are better" versus "conversion is better" — but "we lose ~6 points of conversion to gain some unproven slice of 90-day retention." Once the exchange is stated plainly, the room is arguing about a number instead of a taste.
How to read a tradeoff
- 01
Name the gain
What does this option actually get you, stated as a number or a mechanism — not an adjective?
- 02
Name the loss
What does it cost, in the same units where possible. If you can't name a cost, you don't understand the option yet.
- 03
Name what it defers
The sneaky third bucket: what does this delay, foreclose, or make harder to change later? Reversibility is a cost too.
- 04
Find the exchange rate
State the exchange as a trade: this much of X for that much of Y. Now it's a judgment about magnitude, not identity.
- 05
Anchor to the binding constraint
Which number is the business actually short on right now? The tradeoff resolves against the constraint, not in the abstract.
Arguing preferences vs reading the exchange
Preference argument
Each side defends a conclusion.
- "Accounts are just better."
- Costs stay implicit
- Whoever is more senior wins
- The decision doesn't survive new data
Tradeoff read
Both costs, one set of units.
- "6 points of conversion for X retention."
- Every option has a named loss
- The constraint decides
- The decision updates when the numbers do
Insight
Think of a decision your team made recently that later felt wrong. Was the losing cost ever actually named out loud — or did it only become visible after you'd paid it?
Don't win the argument. Make the exchange rate legible, then let the binding constraint decide. The PM who names the cost of their own preferred option is the one people trust.