A company chooses a growth engine — a direction, a thesis, a bet. Then a quarter passes, and an audit of the calendar shows the bet received its first real attention two weeks ago. The gap between the strategic choice and the operating calendar is where most strategies quietly stop existing, and the document meant to cross it — the roadmap — is too often a list of features with dates on them. A working growth roadmap is built differently: as a sequence of verifiable quarterly steps, each one either closing a question or building on a closed one.
Once an engine is chosen, one assumption underneath it is fatal — the one whose failure ends the thesis, not merely slows it. The first quarter's honest job is to attack that assumption at the smallest possible scale, in the shortest possible time, before anything expensive is committed to it. A roadmap that spends its opening quarter building infrastructure for growth whose premise is untested has ordered the foundations before checking the soil. The sequence — premise first, machinery second — is the single largest difference between roadmaps that produce knowledge and roadmaps that produce sunk costs.
Each quarter on the roadmap is written as a question, an evidence gate, and a consequence. The question: what must this quarter learn for the thesis to survive? The gate: what specific result, defined in advance, closes the question — signed pilots, measured retention, a working price. The consequence: what the next quarter does if the gate is passed, and what it does if it is not. Gates written at the start are the same discipline as exit criteria written at project launch — the decision is made calmly, before anyone's standing is invested in the answer. Roadmaps without gates do not fail visibly; they slide, which is worse, because sliding consumes the one resource that never returns: consecutive quarters.
The roadmap also enforces an arithmetic that plans escape: a quarter absorbs a strictly limited amount of work. Loading a quarter past its capacity does not add scope, it adds queue — everything becomes slower and nothing becomes clearer. The roadmap assigns each quarter fewer questions than it could theoretically hold, ordered so that the cheapest fatal test runs first, exactly as prioritization demands of the annual plan. What the company funds in a quarter is a budget decision in miniature, and resource allocation is where the roadmap stops being a schedule and becomes strategy.
The finished document is short: the thesis, the chain of quarterly questions, the gates, the consequences. Its real product is a company that knows by the second week of each quarter whether it is still right — instead of discovering at the year-end review that it stopped being right in April.
We use cookies to analyse traffic and improve the site. Analytics is enabled only with your consent. Cookie Policy