11 From method to tool

11 · From method to tool

A working method can remain an individual discipline, entrusted to the constancy of whoever practises it, or it can be embodied in a tool that makes it natural rather than laborious.

The reason to build a dedicated tool is that each of the four principles, today, is sustained only with effort on interfaces conceived for the single conversation. The decision log lives in a hand-maintained file; open points are lost if the operator is not disciplined; distilling the specification, tracking its changes and partitioning it into sub-specifications are entirely manual operations; the table of interlocutors — distinct by role and, where needed, by model — requires orchestrating several conversations by hand and keeping their roles separate. It was precisely this management effort — sustainable on one piece of work, insidious across many — that matured the idea of a dedicated tool. A tool that takes the method as its own native form — with the versioned specification at the centre, the decision log as a first-class structure, and several distinct digital interlocutors converging on a single shared document under the guidance of a human operator — turns a demanding practice into an ordinary way of working.

This is the justification of the tool for which this document is the foundation: not one more container of conversations, but the operational translation of a principle — that work between a human operator and a model requires a place to settle, a memory of its own reasons, and more than one perspective.

---

← 10 · Where the method costs and where it falls short · The Method · 12 · In summary →