Sixteen product people down to five. That's what my quarter cost, at the same company where I'd arrived a while earlier and confidently reframed the strategy.
Here's the part that still stings. The work was good. Genuinely high quality, the kind you'd put in a portfolio. It was also so far from where the company was actually going that it was incomprehensible to anybody outside my own team, and when the resourcing conversation came round I could not make the case, because there wasn't one to make.
I hadn't understood the vision. And rather than go and get it, I doubled down on my plan — because my plan was mine, it was legible to me, and changing it would have meant admitting in public that I'd been building toward the wrong thing for a quarter.
It isn't cowardice, though. Changing the plan is uncomfortable in a specific way: it costs you status in the room, immediately, in exchange for being right later. Defending the plan costs you nothing today.
So I defended it. And I got the bill in headcount.
A Head of Product told me last month that the thing he still hasn't cracked is transferring the vision to his team, and building a strategy and a system that works with him or without him in the room. He'd accidentally described the whole job in about twenty words — and he'd described the exact thing that breaks first when a company gets squeezed.
Here's the pattern, and I've now been on both ends of it. Capability drops, or direction shifts, and the leader goes into protection mode. What they instinctively protect is the plan — the dates, the sequence, the commitments made in a room with an executive who's watching. So the plan gets defended hard, and somewhere in all that defending, the vision quietly goes soft.
Nobody notices, because nobody defends the vision in a planning meeting. It isn't on the agenda.
The plan is the disposable one
Which of the two would you actually rewrite if reality changed tomorrow?
The plan should be the disposable artifact. It's a route, it was drawn against assumptions, and about half of those assumptions have already expired. Rewriting it isn't failure — it's the plan doing its job, which is to be specific enough to be wrong in a useful way.
The vision is the thing that made anybody join. It's the reason the senior engineer turned down more money somewhere duller. It doesn't move because you lost two people, and it certainly doesn't move because a date slipped.
Change the route as often as reality demands. Change the destination almost never, and never quietly.
But here's what actually happens under pressure. The plan gets defended past the point of sense, because plans have owners and dates and visible accountability attached to them. The vision has none of that, so it erodes without resistance — it gets shortened in the deck, then dropped from the deck, then it's a sentence somebody says at the offsite with slightly less conviction than last year, and eventually your team is executing tickets with no idea what they're for.
I once worked with a team executing out of pure momentum, and someone on it asked me, completely sincerely: I know the goal we have isn't making progress, but what is that goal again? That isn't a stupid question, it's the terminal stage of a vision nobody protected. And notice that the plan was in perfect health the whole time — tickets moving, sprints closing, velocity respectable. You can run a fully functional delivery machine with the destination missing, and for a while it looks identical from the outside.
Saying the route changed without saying the destination did
So how do you do the hard version, which is publicly rewriting the route while visibly refusing to move the destination?
The move is sequence.
When you announce a delta, an owner and a drop, you finish on the vision. Unchanged. Stated in the same words you used last quarter, deliberately, so the repetition itself is the signal. Not a new inspiring framing — the same framing, because a vision that gets rephrased every quarter reads as a vision that's being negotiated.
Then you make the connection explicit rather than leaving it as an inference. Here's what we can no longer do this year. Here's what we still absolutely intend to be true in three. Here's why the second one survives the first, and here's the part of the route we're redrawing to get there.
That last sentence is the one leaders skip, and skipping it is how a re-cut reads as retreat. Your team is entirely capable of hearing a cut without losing faith. What they can't do is hear a cut and be left to guess whether the ambition survived it, because in the absence of information people assume the worse thing, and they're usually right to.
Works with you or without you
Back to the Head of Product's line, because it contains the test.
A vision that lives in your head isn't transferred, it's hosted. And a hosted vision fails the moment you're on holiday, in a different meeting, or gone — which is why the honest measure of whether you've transferred it isn't whether people can repeat it back. It's whether somebody made a tradeoff in your absence that you'd have made yourself.
Marty Cagan's Empowered is the best book I know on this. His whole argument is that a team handed a problem and a vision will outperform a team handed a list of features — and that only works if the vision actually made it out of the leader's head.
That's the diagnostic, and it's uncomfortable because it can only ever be measured after the fact. There's no way to test a transferred vision in advance, which is why leaders who care about this tend to over-invest in repetition rather than in phrasing. Say the same thing, in the same words, more times than feels necessary. It's also one of the very few leadership skills you can measure, which makes it one of the few worth paying to train.
So count it. Take the last ten decisions your team closed without you — not the ones they escalated, the ones they finished — and mark how many you'd have made the same way. That's your transfer rate, and it's the only number I know of that measures whether a vision has actually landed.
Eight or better and the vision is doing real work in your absence, so you can move your attention somewhere else with a clear conscience. Below five and whatever you've been transmitting is a plan rather than a vision, because plans don't generalize to situations nobody planned for. The difference only ever shows up in the decisions you weren't in the room for.
Run it quarterly. A transfer rate that falls while your headcount falls is the earliest warning you'll get that the vision went soft while you were busy defending dates.
This week
Two sentences on paper, and don't spend an hour on it.
Score your transfer rate out of ten, then write the vision as you'd say it out loud to one person over coffee, with no slide anywhere near you. Then write the version of it that's currently sitting in your deck. Are they the same? If the deck version is shorter, hedged, or has quietly acquired a "by 2027" that wasn't there before, you've been eroding it under pressure without deciding to.
Then say the original version out loud in your next staff meeting, in the same words you used last quarter, immediately after whatever bad news you have to deliver that day. Not before it, and not in a separate meeting a week later where it'll read as damage control. The order is the message.