Making Tradeoffs Legible

Every product decision is a tradeoff. You choose this over that — this user over that user, this timeline over that feature set, this metric over that metric. The question isn't whether you're making tradeoffs. You always are. The question is whether you're making them explicitly, with full visibility into what you're giving up, or whether you're making them implicitly, in ways that aren't visible to the team and can't be revisited later.

Implicit tradeoffs are everywhere in product development. The feature that got cut 'because there wasn't time' was actually a prioritization decision — but because it wasn't framed that way, no one wrote down why, and six months later the team is having the same argument with no memory of how it was resolved. The metric that got chosen as the team's north star was implicitly deprioritizing other metrics — but because that tradeoff wasn't named, it shows up as confusion when the north star metric looks great and something else is quietly declining.

Legibility is the solution. Not more process — just the discipline of naming what you're choosing and what you're choosing to give up.