Home / Articles / Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published / Versions / v1.3.0
Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published: what changed in v1.3.0
From v1.2.0 (2026-10-18, 4baace0c6) to v1.3.0 (2026-10-18, de821285d), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 53 unchanged. About 0 words added and 2 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
1 unchanged paragraph
Summary: Harvard Business Review published "Turn Vibe-Coded Prototypes Into Tools Your Company Can Actually Use" on 16 October 2026, by José Parra Moyano and Karl Schmedders of IMD, Olivier Laplace of Vi Partners and Benjamin Torben-Nielsen of Roche. Its argument, as its summary and Olivier's post put it: AI has made building software feel almost free, so the prototype is the easy part and turning it into a tool people rely on is the hard part, which they call the deployment gap; nobody in-house knows how an AI-designed tool is built; build where you are different and partner where specialists live the problem. I agree with almost all of it, and I think this site has already answered the question in a set of articles, with Simon Wardley's explorers, villagers and town planners as the frame. The gap is not a place to stop; it is a handover between people with different skills. The prototype is not the mess; it is thea bestbetter brief anyonethan willany write.document. The architecture an agent designed can be known, if the agents leave a record: a mandate, a memory and a graph. Their bonus test is the town planner's accountability by another name. And the answer to "who will fix your mess?" should never depend on one partner: if the code is open, anyone can. I have read the public summary and Olivier's post, not the full article, which is behind a paywall.
4 unchanged paragraphs, under In short {#in-short}
• The prototype is not the mess. It is thea bestbetter brief anyonethan willany ever write.document.
12 unchanged paragraphs, under What they argue {#argument}, The prototype is not the mess {#brief}
The word "vibe" is part of the problem. In Explorer coding I proposed a better name for it, from Simon Wardley's explorers, villagers and town planners. What people are doing when they build an app by talking to an agent is exploring, with the fast feedback loop that made spreadsheets win. And what they build is thea bestbetter brief anyonethan willany ever write:document: what the user actually wants, in a form that runs. The citizen developer makes the same case for the people outside IT who are now building: it is the spreadsheet grown up, and spreadsheets ran the world for decades despite their errors.
36 unchanged paragraphs, under The gap is a handover {#handover}, "Nobody knows how it is built" can be fixed {#record}, The bonus test is accountability {#bonus}…