Roadmaps are really just values written down and defended in public. The job is philosophy with a deadline.
Every roadmap is a values statement, whether anyone admits it or not. Deciding what a team builds next is deciding what matters most right now, and defending that decision out loud, in a room, to people who disagree with you.
I studied philosophy before I did anything resembling product work, and for a long time I thought that was an odd detour. It wasn’t. Prioritization is ethics with a deadline — you’re constantly trading one good thing for another good thing and having to explain why.
Not in the vocabulary — nobody wants to hear about a philosopher’s name in a planning meeting, and if you need one to make your point, you haven’t found the plain version of it yet. It shows up in the questions: whose problem are we actually solving, what are we quietly deciding not to fix, and are we being honest with ourselves about why.
The best product leaders I’ve worked with aren’t the ones with the cleanest frameworks. They’re the ones willing to say, out loud, “this is a values call, not a data call” — and then make it anyway, because someone has to.
Next time you’re stuck prioritizing, stop asking what’s most valuable and start asking what you actually believe matters. The prioritization usually follows.