When Over What

The right idea at the wrong time is the wrong move.¶

A few months ago I shipped a strategy memo I’d been carrying for weeks. It was good. It was right. It also landed three days after a major reorg announcement, when half the leadership team was busy explaining the reorg to their reports. The memo bounced. Not because the argument was wrong. Because the moment was wrong. Three weeks later, after the reorg dust settled, I shipped it again with one paragraph changed. It became the strategy.¶

That’s when I started taking when as seriously as what. What you ship is product strategy. When you ship it is operating. They aren’t the same skill. The “what” people get cited in retrospectives. The “when” people compound.¶

Most goal-setting frameworks ask “what should we ship?” That’s the easier half. The harder half is “when does this land?” Whose decision is upstream of mine? What does the company know now that it didn’t know a month ago? What does the team have the energy to absorb this week versus next? Goals shouldn’t feel like a to-do list. They should feel like a calendar.¶

The cost of bad timing is invisible. Nobody writes a postmortem for the right idea that landed wrong. They just call it a bad idea and move on. I’ve watched ten ideas get killed because their author shipped the same week as a competing announcement, a layoff, a board meeting, or a holiday. None of those people did the wrong work. They did the right work in the wrong week.¶

The fix isn’t a calendar app. It’s the discipline of asking, before every meaningful ship, what else is in the room when this lands. What is the room thinking about right now. What can it absorb. What is upstream that has to land first. Most of design and product leadership is reading the room weeks ahead.¶

When over what. Most of the time.¶