If the CEO Isn't in the Room, You Don't Have a Roadmap
The meeting starts at 10. The CEO comes in, drops a date on the table — "we need this live by March" — and leaves. The room goes quiet for a moment. Then everyone looks at you.
And you start building a roadmap.
This is the most common mistake I see first-time CPOs and CTOs make. Not the technical decisions. Not the hiring choices. It's this: confusing a roadmap with a delivery plan.
A roadmap is not a Gantt chart. It's not a list of features with dates attached. A roadmap is a negotiation — about priorities, trade-offs, and what you're willing to not do. And like all negotiations, it only works if the right people are in the room.
When the CEO walks out after dropping a deadline, they haven't given you a roadmap. They've given you a constraint. Those are different things. A constraint tells you the destination. A roadmap is how you decide what to put on the truck.
The two meetings that will kill your quarter
The first is the one I described. Key stakeholders missing. A date on a whiteboard. Everyone nodding. Nobody actually agreeing on what "done" means, or what has to give to get there.
The second is more insidious. It's the monthly reset — where everything agreed last month gets thrown out and rewritten from scratch. The team that spent three weeks designing a feature finds out it's been deprioritised. Again.
Both meetings share the same root cause: the people with decision-making authority aren't doing the work of deciding. They're delegating a negotiation disguised as an execution problem.
Roadmap is negotiation. Not delivery.
Say it out loud in your next planning meeting and watch the faces. Half the room will nod. The other half will look confused — because they've been trained to think of roadmap planning as a scheduling exercise.
It isn't. When you sit down to build a roadmap, you're making bets. You're saying: of all the things we could do, these are the ones we believe will matter most. That belief has to be shared — by product, by engineering, by the business. If the CEO isn't in that room, their priorities aren't in that room either. And they will show up later, usually at the worst possible moment.
Every yes is a hidden no
There's something nobody tells you when you step into your first product or tech leadership role: your capacity for decisions is not infinite. Every time you say yes to a feature, a project, a sprint goal — you are simultaneously saying no to something else. Usually to a lot else.
The problem is we are wired for yes. We want to help. We want to grow. We want to show stakeholders we heard them. No feels like failure; yes feels like progress. So we keep adding things to the roadmap without removing anything, and we call it ambition.
It isn't. It's avoidance.
The best product leaders I know treat the roadmap as a budget. Not a budget of money — a budget of attention. And like any budget, it is finite. When you add a line, something else gets less. You can pretend otherwise, but the team knows. They're the ones staying late to service the debt of all the yeses nobody wanted to revisit.
This is what leadership actually looks like
Anyone can walk into a room and collect requirements. You open a Confluence page, you write down what everyone said, you leave. That's administration. That's not leadership.
Leadership is walking into that same room, listening to everything everyone needs — really listening, not waiting for your turn to talk — and then making the call. Here is what we are going to do. Here is what we are not going to do. Here is why.
And then — this is the part most people skip — bringing everyone with you on that decision. Not issuing a decree and moving on. Explaining the reasoning. Acknowledging what you're leaving behind. Giving people enough context to understand why their priority didn't make the cut this time, and what would need to change for it to.
That last part is what companies most often get wrong. They have plenty of people willing to make hard calls. They have far fewer people willing to do the slow, uncomfortable work of taking others along for the journey. Of saying "I know this isn't what you wanted, and here's what I need you to understand about why." Of sitting with the discomfort of someone's disappointment instead of avoiding the decision altogether.
The best leaders I've worked with didn't come in with the answer. They came in with questions. They sat quietly while others talked. They listened in a way that made you feel genuinely heard — not processed. And then, after the room had aired everything out, they said something that stopped everyone. Not because it was new. Often it was something someone else had already said, twenty minutes earlier, buried in a longer point. But they said it in a way that suddenly made it obvious. Clear. Agreed.
That's synthesis. That's the skill nobody puts on a job description but every good team desperately needs at the top. Not the loudest voice. Not the fastest decision. The person who can hold the whole mess in their head, find the signal in it, and hand it back to the room in a form everyone can move on.
You can't do that if you're the one talking the whole time.
When everyone wants everything
Eventually you will be in a room where every stakeholder has a number one priority. Sales needs the enterprise features. Marketing needs the integrations. The CEO needs the thing they promised the board. Engineering needs to pay down the debt that's been slowing everyone down for six months.
This is not a roadmap problem. It's a prioritisation problem. And there's only one question worth asking:
What is the single thing that requires the least amount of work and delivers the most results?
This is the intuition behind Weighted Shortest Job First — a methodology from lean product development that formalises what good PMs already know intuitively. The value isn't always in the biggest feature. It's often in the small thing that unblocks everything else. The API integration nobody demanded loudly but that three teams have been waiting on for months. The performance fix that makes the sales demo not embarrassing.
Best bang for the buck isn't a compromise. It's a strategy.
How to run the meeting that actually works
Three things. First: no roadmap meeting without the decision-makers. If the CEO can't come, reschedule. If they won't come, that's a conversation you need to have before the meeting — not after.
Second: make the trade-offs explicit. Don't just say "we're building X." Say "we're building X, which means we're not building Y until next quarter." Put both on the slide. Force the discussion.
Third: document what was decided — and what was deliberately left out. The monthly reset happens when people forget what they agreed to deprioritise. Write it down. Send it out. Make the implicit explicit.
The no is not a failure of ambition. It's the thing that makes the yes mean something. And the roadmap that sticks isn't the most detailed one — it's the one everyone in the room actually agreed to.