When a roadmap creates dread, the ambition usually isn't the problem. The missing resource conversation is.
At a team AMA this week, where I meet with ICs only (no managers allowed) and prompt for spicy topics, someone called out their anxiety directly. A multi-year target we’ve been pointing at through a product vision video feels far off and under-resourced, 3 or 4 years away rather than a year and a half. It’s a fair worry. A big destination with no visible path or people to get there sits in your chest.
I’ll own part of why it landed that way. We set it up by leading with the destination and leaving the resourcing implicit. When you do that, the gap between the ambition and the current capacity shows up on the team as dread, because all they can see is the distance.
Flip the order
Org follows strategy. Always. You don’t build the org and hope the strategy shows up to match it. You start with a clear strategy, then go to the people who control headcount and budget and say: here is what we can deliver by the target, and here is exactly what it takes to get there. The commitment is conditional. We commit to the outcome only if we get the resources the outcome requires.
That single move changes what a scary number is. It stops being a promise the team has to absorb and starts being a negotiation with terms. “We can do this by then, given that” is a plan. “We will do this by then,” with the “given that” left off, is a wish, and the team feels the missing clause as pressure.
The teachable part
When a roadmap is generating anxiety, the cause is usually not the size of the ambition. It’s that the ambition arrived without its resourcing attached, and it landed on people who can’t authorize the resources anyway. The fix is to make the resource ask explicit and tie the commitment to it, then put that conversation where the decision actually lives. A target with no resource conversation is just pressure aimed at the wrong altitude.