Home / Articles / Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published / Versions / v1.2.0
Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published: what changed in v1.2.0
From v1.1.0 (2026-10-17, b24f1acec) to v1.2.0 (2026-10-18, this release), paragraph by paragraph.
0 paragraphs added, 3 removed, 0 changed in place, 56 unchanged. About 0 words added and 114 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
48 unchanged paragraphs, under In short {#in-short}, What they argue {#argument}, The prototype is not the mess {#brief}…
What I would ask the authors {#ask}
I would like to read the full article, and I suspect some of this is in it; I just want to buy the article is about why I have not. Three questions I would ask:
1. Does the gap close faster if the agents keep a record? A mandate, a memory and a graph of what they built, owned by the company. 2. Should the partner's code be open? It is the cleanest answer to "who will fix it" if the partner fails. 3. Is the best partner a villager underneath your explorers? Selling the maintenance of what your people build, not a replacement for it.
8 unchanged paragraphs, under What this does not claim {#limits}, Where this comes from {#sources}