CONCEPT
The Spec Document as Chartjunk
The Tufte-derived reading of the software specification document as an extreme case of chartjunk — a communication format whose structural overhead buries the actual signal beneath ninety percent non-data ink.
The standard enterprise specification document is, by Tufte's measurement, a design failure worse than most of the charts he has criticized across four decades. A forty-page requirements document typically contains five pages of genuinely novel information and thirty-five pages of structural overhead: section headers, revision histories, stakeholder matrices, risk boilerplate, user stories written in formulaic templates, cross-references to other documents that exist primarily to be cross-referenced. The data-ink ratio is approximately 0.10 to 0.15 — worse than a cluttered bar chart with unnecessary gridlines, drop shadows, and three-dimensional effects. The format consumes the builder's effort and the developer's attention with overhead that serves organizational consumption — review cycles, approval workflows, audit trails — rather than the efficient transmission of meaning.
In The You On AI Field Guide
The harm compounds at the next stage. The developer who receives a forty-page spec must scan through sections she knows contain no decisions, searching for passages where the builder's actual intention is encoded. She parses user stories
Keep reading with YOU ON AI
Unlock the full book, 10,000+ field-guide entries, and a 1000+ thinker library. If you have a book code, register now — it takes a minute.