[{"data":1,"prerenderedAt":219},["ShallowReactive",2],{"writing-article-\u002Fwriting\u002Froadmaps-are-arguments":3,"writing-index":142},{"id":4,"title":5,"body":6,"cover":126,"coverAlt":126,"date":127,"description":128,"draft":129,"extension":130,"featured":129,"meta":131,"navigation":132,"path":133,"readingTime":134,"seo":135,"stem":136,"summary":137,"tags":138,"__hash__":141},"writing\u002Fwriting\u002Froadmaps-are-arguments.md","Roadmaps Are Arguments, Not Schedules",{"type":7,"value":8,"toc":117},"minimark",[9,18,21,26,29,32,35,39,42,49,55,61,67,70,74,85,88,91,95,98,101,104,108,111,114],[10,11,12,13,17],"p",{},"There is a moment in most roadmap reviews when the conversation stops being about the product and becomes about the dates. Someone asks whether the third item can move forward a month. Someone else points out that the second item depends on a team that is already committed. The room settles into a negotiation about sequencing, and the question that mattered, ",[14,15,16],"em",{},"why this, at all?",", quietly leaves the building.",[10,19,20],{},"That moment is not a failure of project management. It is a symptom of using the wrong artifact for the job.",[22,23,25],"h2",{"id":24},"what-a-calendar-can-and-cannot-hold","What a calendar can and cannot hold",[10,27,28],{},"A delivery schedule answers a narrow question: given a known scope, when will it be done? That is a useful question. It is also a question that assumes the scope is known, the uncertainty is low and the work is mostly execution.",[10,30,31],{},"Product work rarely meets those conditions. The scope is a hypothesis. The uncertainty is the point. The work includes learning that may invalidate the plan.",[10,33,34],{},"When a roadmap is formatted as a schedule, it inherits the schedule’s assumptions. Dates imply certainty. Rows imply scope. A Gantt bar implies that the work is understood well enough to be decomposed. None of this is stated, which is what makes it dangerous: the format argues for a confidence the team does not have.",[22,36,38],{"id":37},"what-a-roadmap-is-actually-arguing","What a roadmap is actually arguing",[10,40,41],{},"Strip away the dates and a roadmap is a sequence of claims. A good one makes four of them explicit.",[10,43,44,48],{},[45,46,47],"strong",{},"This is the problem worth solving."," Not the feature, the problem, with evidence about who has it and what it costs them. If the roadmap cannot name the problem, the rest is decoration.",[10,50,51,54],{},[45,52,53],{},"This is why now."," Timing is a real constraint: a market window, a regulatory change, a platform shift, a customer commitment, a piece of technical debt that has become an operational risk. “Because it is on the list” is not a reason.",[10,56,57,60],{},[45,58,59],{},"This is what we are not doing."," A roadmap without exclusions is a wish list with better typography. The exclusions are where strategy becomes visible, because they show what the team is willing to lose.",[10,62,63,66],{},[45,64,65],{},"This is what would change our mind."," Every bet has a condition under which it stops being a good bet. Writing that condition down is what turns a plan into a learning loop.",[10,68,69],{},"A roadmap that contains those four claims can survive a change in dates. A roadmap that contains only dates cannot survive a change in anything.",[22,71,73],{"id":72},"replace-the-date-column","Replace the date column",[10,75,76,77,80,81,84],{},"The most useful change I have made to roadmap formats is replacing the confidence-free date column with two columns: ",[45,78,79],{},"confidence"," and ",[45,82,83],{},"what would move it",".",[10,86,87],{},"A date with no confidence is a guess wearing a suit. A date next to “medium confidence, depends on the platform migration landing in March” is a decision others can reason about. They can see the dependency, weigh the risk and decide whether to fund a way around it.",[10,89,90],{},"The same applies to prioritisation. A ranked list hides the reasoning; a list of bets with evidence, cost and expiry invites it. The second is harder to produce and much harder to misuse.",[22,92,94],{"id":93},"when-the-date-is-real","When the date is real",[10,96,97],{},"Some dates are real. A contractual commitment, a regulatory deadline, a seasonal launch, a partner integration. Those are not product bets in the same sense; they are obligations with a fixed external constraint.",[10,99,100],{},"The mistake is letting a handful of genuine commitments set the grammar for everything else. Separate the two explicitly. Call the fixed items commitments, with the external reason attached. Call the rest bets, with the evidence and the trade-off attached. Use different formats, different review cadences, different language.",[10,102,103],{},"Mixing them produces the worst of both: the flexibility of a bet with the accountability of a promise, and no clarity about which is which.",[22,105,107],{"id":106},"the-test-of-a-roadmap","The test of a roadmap",[10,109,110],{},"Here is a simple test. Hand the roadmap to someone who was not in the planning sessions and ask them to explain what the team believes and what it has chosen not to do. If they can reconstruct the argument, the artifact is doing its job. If they can only read the dates, it is a schedule pretending to be a strategy.",[10,112,113],{},"A roadmap should be arguable. Not in the sense of causing conflict, but in the sense that a reasonable person can look at it and say, “I disagree with this bet, and here is why.” That is a sign the reasoning is visible.",[10,115,116],{},"A roadmap nobody can argue with is not alignment. It is a queue.",{"title":118,"searchDepth":119,"depth":119,"links":120},"",2,[121,122,123,124,125],{"id":24,"depth":119,"text":25},{"id":37,"depth":119,"text":38},{"id":72,"depth":119,"text":73},{"id":93,"depth":119,"text":94},{"id":106,"depth":119,"text":107},null,"2026-10-14","There is a moment in most roadmap reviews when the conversation stops being about the product and becomes about the dates. Someone asks whether the third item can move forward a month. Someone else points out that the second item depends on a team that is already committed. The room settles into a negotiation about sequencing, and the question that mattered, why this, at all?, quietly leaves the building.",false,"md",{},true,"\u002Fwriting\u002Froadmaps-are-arguments",3,{"title":5,"description":128},"writing\u002Froadmaps-are-arguments","A roadmap is a set of claims about why these problems, in this order, with these trade-offs. When it becomes a delivery calendar, the reasoning disappears and the promises take over.",[139,140],"product-strategy","decision-making","tB--5-nPobG4dgEz_DBG8-QNqdIy7S0rXo80Cg5SVS0",[143,152,154,161,167,173,179,187,193,200,206,213],{"path":144,"title":145,"summary":146,"date":147,"tags":148,"featured":132,"readingTime":151},"\u002Fwriting\u002Fwhat-ai-changes-about-product-work","What AI Changes About Product Work, and What It Doesn’t","The cost of producing a prototype, a spec or a synthesis has collapsed. The cost of knowing what is worth building has not. That gap is where product judgement now lives.","2026-11-04",[149,150],"ai","product-thinking",4,{"path":133,"title":5,"summary":137,"date":127,"tags":153,"featured":129,"readingTime":134},[139,140],{"path":155,"title":156,"summary":157,"date":158,"tags":159,"featured":129,"readingTime":151},"\u002Fwriting\u002Fdiscovery-is-a-budget","Discovery Is a Budget, Not a Phase","Treating discovery as a stage before delivery assumes uncertainty is front-loaded. It isn’t. Discovery works better as a recurring spend that every cycle pays into.","2026-09-23",[160,139],"discovery",{"path":162,"title":163,"summary":164,"date":165,"tags":166,"featured":129,"readingTime":151},"\u002Fwriting\u002Fcost-of-a-decision-you-didnt-make","The Cost of a Decision You Didn’t Make","Deferred decisions feel safe because nothing visible happens. But indecision charges interest, in rework, lost context, and options that quietly expire.","2026-08-19",[140,150],{"path":168,"title":169,"summary":170,"date":171,"tags":172,"featured":129,"readingTime":134},"\u002Fwriting\u002Fthe-feature-was-never-the-problem","The Feature Was Never the Problem","A feature request is a compressed problem statement with the reasoning removed. If you ship the request without unpacking it, you often solve the smallest part of the problem.","2026-06-30",[150,160],{"path":174,"title":175,"summary":176,"date":177,"tags":178,"featured":129,"readingTime":134},"\u002Fwriting\u002Fprioritisation-is-about-evidence","Prioritisation Is a Story About Evidence","Frameworks like RICE do not make decisions. They make assumptions comparable. The quality of a prioritisation is the quality of the evidence and the honesty about what gets displaced.","2026-05-12",[139,140],{"path":180,"title":181,"summary":182,"date":183,"tags":184,"featured":129,"readingTime":151},"\u002Fwriting\u002Fstakeholders-are-not-obstacles","Stakeholders Are Not Obstacles","“Stakeholder management” often frames other people as friction. But they hold information the product team lacks. Treat them as co-owners of the constraint, not gatekeepers.","2026-03-24",[185,186],"practice","leadership",{"path":188,"title":189,"summary":190,"date":191,"tags":192,"featured":129,"readingTime":151},"\u002Fwriting\u002Fthe-quiet-power-of-constraint","The Quiet Power of a Good Constraint","Constraints are usually treated as obstacles. A good one narrows the search space, forces a real choice, and makes the work more honest.","2026-02-10",[150,139],{"path":194,"title":195,"summary":196,"date":197,"tags":198,"featured":129,"readingTime":151},"\u002Fwriting\u002Fwhen-research-stops-being-useful","When Research Stops Being Useful","Research becomes decorative when it is disconnected from a decision. More interviews will not fix a team that has not agreed on what it is trying to learn.","2025-12-02",[199,160],"research",{"path":201,"title":202,"summary":203,"date":204,"tags":205,"featured":129,"readingTime":151},"\u002Fwriting\u002Fthe-product-review","The Product Review That Actually Changes the Product","Most product reviews are status meetings with slides. A useful one changes a decision, and that requires a different format, a different question set and a named owner.","2025-10-21",[185,140],{"path":207,"title":208,"summary":209,"date":210,"tags":211,"featured":129,"readingTime":134},"\u002Fwriting\u002Ftools-dont-make-the-product","Tools Don’t Make the Product","A new tool cannot fix an undefined workflow. It usually makes the disagreement faster, more visible and more expensive.","2025-09-09",[212,185],"tools",{"path":214,"title":215,"summary":216,"date":217,"tags":218,"featured":129,"readingTime":151},"\u002Fwriting\u002Foutcomes-are-a-habit","Outcomes Are a Habit, Not a Metric","Teams say they are outcome-driven but manage by output because output is legible. Outcomes require a cadence of looking at behaviour and the discipline to change course.","2025-07-15",[139,185],1795010564315]