Why does timing matter more than quality in product outcomes

Not more, but independently. A well-built product released into a market that is not ready fails for reasons that have nothing to do with its quality, and the same product two years later can succeed unchanged. Because timing is not an attribute of the work, no amount of effort on the work improves it, which is precisely why it gets so little organisational attention.

What does it mean for a roadmap to have silences

It means deliberate periods where nothing new ships, so that what has already shipped can be absorbed, understood and corrected. A continuous stream of releases prevents anyone from learning what any single release did. The silence is what makes the note legible, and in delivery terms it is the difference between a cadence and a queue.

You have to find the right moment

Music lives in the silence between notes. On timing in digital products, and why what a team decides not to ship shapes the product as much as what it ships.

November 15, 2024

Music is not in the notes, but in the silence between them.

— attributed to Mozart

The attribution is almost certainly spurious, which is fitting for a remark about the value of what is not there. Debussy said something close to it; so did several others. The sentence has survived on merit rather than provenance.

Silences in a roadmap

The reason it belongs in a conversation about digital products is that we are organisationally incapable of scheduling a silence.

Every planning cycle produces notes. It produces them continuously, in parallel, at a volume that makes it impossible for anyone to hear an individual one. A team ships four things in a fortnight and then cannot say what any of the four did, because the four are interfering with each other and with the seasonal variation and with a marketing campaign that started on the Tuesday.

The silence is what makes the note legible. Not a pause for rest — a pause for reading. And it is nearly unschedulable, because a calendar with a gap in it reads as waste to anyone who has not thought about queueing.

Reinertsen's argument is the technical version, and it is counterintuitive enough to be worth stating flatly: loading a development system towards full utilisation destroys its responsiveness long before it destroys its capacity. Slack is not idleness. It is the only thing that allows a system to respond to something it did not anticipate, and a product organisation with no slack has purchased throughput by selling its ability to react.

Ohno reached the same place from the factory floor without any mathematics. Just-in-time is not primarily about inventory; it is about not producing anything until the next step is genuinely ready to receive it, which requires the discipline of stopping when nobody is waiting.

Timing is not an attribute of the work

The harder half of the sentence is about markets rather than delivery.

A well-built product released into a market that is not ready fails for reasons entirely unrelated to its quality. The same product, unchanged, can succeed two years later. This is the least comfortable fact in the industry, because it means the variable that most determines the outcome is one you cannot improve by working harder. Effort on the work does nothing for it.

Which explains why it gets so little organisational attention. There is no ritual for it, no ceremony, nobody's objective mentions it. Christensen's account of disruption is largely an account of timing — incumbents fail not by being wrong about the technology but by being right about it too early or acting on it too late, and both errors look identical from inside a quarterly review.

Paul Saffo's rules for forecasting contain the most useful correction I know: look for the S-curve's early indicators rather than trying to name the date. His formulation is that change is rarely as fast as enthusiasts predict and rarely as slow as sceptics assume, and the discipline lies in holding strong opinions weakly — being willing to be wrong quickly rather than being right eventually.

Moore's chasm is the same terrain mapped for adoption. The gap between early adopters and the mainstream is not a marketing gap; it is a timing gap, and products die in it while performing beautifully for the people who already understood them.

What you can actually control

You cannot control the moment. You can control your readiness to recognise it, and your ability to move when it arrives, and both of those are consequences of how loaded your system is.

This is the practical link back to rhythm and to the ergonomics of a conjecture. A team that ships continuously and never stops has no capacity to seize anything, because everything it can do is already committed. A team with fixed appetites and deliberate boundaries — Ryan Singer's version of this is the most operational I have found — retains the ability to say yes to something unplanned, which is what finding the right moment actually consists of.

Kanban's contribution is the visible one: limit work in progress and the queue tells you the truth about your capacity, whether or not you wanted to know.

The note you do not play is a decision. It is just an invisible one, which is why nobody gets credit for it.