Blueprints
Blueprints
Blueprints are original works for technical documentation, written and maintained by Saina Veigel. Each blueprint is a plan drawn before anything is built. Every blueprint belongs to one category: thinking models that bring the questions into focus, check strategies that turn them into check methods, Proof Blueprints that make a claim robust, and Brain Function Models of the mind at work. They are authored works, published here as their reference version.
Every blueprint names its author, its edition and where its ideas were first published.
Thinking Model
Thinking Models
Thinking models show how a documentation topic is thought through before anything is built. They work with deliberate placeholders — the writer, the reader, the machine — so that the questions come into focus.
Thinking Model · Edition 1
Thinking models for technical writers
How technical writers structure complexity before they write
Ten thinking models by Saina Veigel that help technical writers structure complexity before writing, with the mental model stack and an operating-mode grid.
10 thinking models: First principles thinking · Information Mapping · Component thinking · System thinking · Task thinking · Risk thinking · Variant thinking · Metadata thinking · Publication logic thinking · Clarity thinking
By Saina Veigel · First published
Open the blueprintThinking Model · Edition 2
Cognitive psychology for technical communication
The reader’s stack: how readers take in, understand and act on technical information
The reader’s stack by Saina Veigel: ten layers of how documentation works in the reader’s mind, with a use-situation grid and a crosswalk.
10 thinking models: Noticing · Finding · Orienting · Understanding · Modelling · Holding · Remembering · Deciding · Acting · Recovering
By Saina Veigel · First published
Open the blueprintThinking Model · Edition 2
AI-enabled information systems for technical writers
The machine’s stack: how documentation becomes knowledge that people and AI systems can use
The machine’s stack by Saina Veigel: ten layers of how documentation becomes governed, traceable knowledge for people and AI systems.
10 thinking models: Bounding · Anchoring · Modelling meaning · Building units · Describing context · Connecting to the product · Retrieving and adapting · Tracing · Governing · Evolving
By Saina Veigel · First published
Open the blueprintThinking Model · Edition 2
AI systems and the machine: levels and boundaries
A cascade of definitions for the network behind every AI answer
Five levels, the machine across them and two boundaries by Saina Veigel: where AI systems end and where the machine reaches into a company.
8 thinking models: Global AI environment · Contracted access · Company AI estate · AI systems · AI function · The machine · Unconfigured AI use · AI system (AI Act)
By Saina Veigel · First published
Open the blueprintThinking Model · Edition 1
The content lifecycle under AI: stages, gates and boundaries
Eleven stages, one gate and two boundaries for documentation that the machine also reads
Eleven stages, one gate and two boundaries by Saina Veigel: who decides at each stage of the content lifecycle under AI, and what remains.
15 thinking models: Analyse · Model · Create · Verify · Approve the source · Manage and version · Translate and localise · Publish and deliver · Answer · Use and feed back · Maintain, withdraw and archive · The gate · Governance · Boundary · Source content and AI-derived output · Boundary · Answers outside the company
By Saina Veigel · First published
Open the blueprint
Check Strategy
Check Strategies
Check strategies lead from a thinking model to a check method. They open the placeholders into roles and the roles into systems, subsystems, functions and subfunctions that a check rule can name — so that a team can build its own check processes and check rules.
Check Strategy · Edition 1
The role grammar of technical information: readers, writers and compilers
Four axes that say who does what with a piece of technical information — people and systems alike
A role grammar by Saina Veigel: four axes for everyone who writes, decides, compiles, uses or writes back technical information.
10 parts: Writing · Deciding · Compiling · Using · Writing back · The actor · Qualification · Authority · Situation · The role sentence
By Saina Veigel · First published
Open the blueprintCheck Strategy · Edition 1
Who decides which value counts: roles of product information from source to answer
From three placeholders to roles a check rule can name — for every system and every person a value passes on its way
A check strategy by Saina Veigel: three placeholders opened into roles, so teams can build check rules for product information.
12 parts: Source · System of record · Master data · Integration · Derived data · Document assembly · Exchange package · Consuming system · System of engagement · Person · Acting system · Stewardship and lineage
By Saina Veigel · First published
Open the blueprint
Brain Function Model
Brain Function Models
Brain Function Models describe how a person thinks a topic through — in images, as metaphorical thinking models. They are not about machines, systems or the roles around technical information, so they are listed apart and are not part of the series “Method refinement”.
Method tools
Method tools
Method tools turn a check strategy into a working form: building blocks, templates, a worked example and a checklist for writing your own check rules.