Read Achilles markRead Achilles

Product Management

Roadmaps Are Negotiations, Not Plans

Every roadmap I have ever shipped — and I have shipped them across several companies, my own and other people's — was presented to the world as a plan and functioned, in practice, as a negotiation. The sooner a product…

♥ 0 Sign in to like 1 comment

This post’s retention & record terms are stated in full in the colophon below.

Every roadmap I have ever shipped — and I have shipped them across several companies, my own and other people's — was presented to the world as a plan and functioned, in practice, as a negotiation. The sooner a product manager makes peace with that, the sooner they stop being disappointed by their own documents. [author assertion]

A plan assumes the future will cooperate. A negotiation assumes interests conflict and must be rebalanced as facts arrive. Roadmaps do the second of these while dressed as the first, which is why they generate so much theatre: the quarterly review where everyone pretends the document was a forecast, when everyone in the room knows it was a settlement. [author assertion]

Look at any roadmap item and you will find a bid. Sales is bidding for the feature that closes next quarter's deal. Engineering is bidding for the rewrite that keeps the system standing. The founder is bidding for the narrative that makes the company legible to investors. The dates attached to the items are not predictions; they are exchange rates between these currencies, quoted with false precision because nobody wants to write "it depends" in a box that will be screenshotted. [author assertion]

What good product managers actually do, in my experience, is keep the negotiation honest. They make the trade-offs explicit — this for that, now for later, this customer for that segment. They re-open settled items when the facts change, without treating the re-opening as an admission of failure. And they protect a small core that is not up for trade at all: the problem being solved, and for whom. A roadmap where everything is negotiable is not a roadmap; it is an auction catalogue. [author assertion]

The failure mode I have committed most often, and watched most often, is defending the document instead of the negotiation. By the third quarter you are no longer managing a product; you are managing the gap between a slide and the truth, and the gap eats exactly the attention the product needed. The teams I have seen escape this trap share one habit: they publish the roadmap with its assumptions attached. When an assumption dies, the renegotiation happens in the open, on the record, without a culprit. [author assertion]

None of this means abandoning commitment. A negotiation that never settles is just a meeting, and teams need settled stretches in which to do deep work. The craft is in choosing the grain: fix the near term in detail, hold the far term in themes, and be explicit about which is which. Most roadmap arguments I have refereed were really arguments about grain — one side defending a promise, the other defending a possibility, both using the same boxes. [author assertion]

Here is my practical rule, bought at some cost. A roadmap should state what we believe, what we are trading, and what would change our minds — and it should be reissued, cheerfully, whenever any of the three moves. Teams forgive changes. Customers forgive changes. What nobody forgives is a surprise they can prove you saw coming. [author assertion]

Ben Cowan

All posts by Ben Cowan → · Follow Ben Cowan by RSS

The Board 20 essays 0 corrections Agent citations: —— — citation attached ≠ claim validated As of 16 November 2026 Full board →

Provenance

About this version

How this post was verified, labelled and shared — in plain language first. The complete machine-readable record is kept below, word for word, for anyone who wants to check it.

Version
1 · in good standing
Author
Ben Cowan · verified at publication
Published
6 Nov 2026
Claims
7 labelled — 7 author assertion
Citations
No external citations
Distribution
Shared with the author’s consent — including to agents acting for readers, under the author’s per-post opt-in
Content fingerprint
dfd1cd21…5778be
Full verification record

The verbatim graded record of this version: identifiers, claim classes, citation targets, hashes and standing, exactly as issued.

This record is also published in structured text for agents and tools — the same fields, word for word. View structured text

House editorial — Read AchillesAuthor verification: verifiedStanding: governingHash: dfd1cd21d50669098687f54aa4142500ad21b8cc00d3a1f6dde3beae765778be

Version & standing

Post post-roadmaps-are-negotiations-not-plans-a977b2 · version 1 (post-roadmaps-are-negotiations-not-plans-a977b2-v1)

@ben-cowan · verified state at publish: verified

Published: 2026-11-06T23:58:43.429Z · Standing: governing

Claims & citations

  • c-1: author_assertion
  • c-2: author_assertion
  • c-3: author_assertion
  • c-4: author_assertion
  • c-5: author_assertion
  • c-6: author_assertion
  • c-7: author_assertion

    Disclosure & trust

    When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule.

    When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule.

    Integrity & distribution

    Content hash: dfd1cd21d50669098687f54aa4142500ad21b8cc00d3a1f6dde3beae765778be

    Distribution: opted_in

    Canonical presentation: https://blog.readachilles.com/post-roadmaps-are-negotiations-not-plans-a977b2/

    What we retain, and why — the retention disclosure

    The retention disclosure for this version is the disclosure line of record, stated in full in the colophon fields above.