THE DRAWING INDEX — SHT V

WRITE THE WHY FIRST.

A vision is the reason the thing we are making should exist, written before anything is built. Big visions break into smaller ones, and the thread back to the why never breaks.

VISION — AS DRAFTEDSHT V

VISION #3V-3

The register never stops, even when the network does.

V-7 Offline-first data layerPART

V-12 Reconnect and reconcilePART

V-13 The outage drillREALIZED

V-9 Receipts that survive a crashPART

DESIGN 50% / BUILD 30% / FEEDBACK 10%Δ2

ONE BIG WHY, BROKEN INTO SMALLER DESIGN PARTS THAT STILL POINT HOME.

VISION — IN PRACTICEHW-01

A vision in Plansheet: the reason at the top, a design board in the middle, and the three refinement loops below.

THE SAME PAGE, BUILT: THE WHY, A DESIGN BOARD, AND THE LOOPS.

FROM A SYNTH CASE, MADE TWICE ->

A PAGE, NOT A SLOGAN

A vision is a page someone can read and understand: who it is for, what done looks like, what's in scope and what's not. Not a brand statement or tagline on a wall. The point is to describe the reason for the work. And provide a durable place where it lives and the anthropology can be referenced. So the work can be checked against it later, even by people who weren't in the room when it started.

DESIGNS DECOMPOSE WITHOUT BREAKING THE THREAD TO THE MISSION

A big vision becomes a tree of smaller ones, each owning a piece, each still pointing back at the whole. Sub-visions can be reused across the tree, the way a standard part shows up on more than one drawing. When a detail gets questioned three months in, the sheet that settles it already exists, and you can trace it all the way back to the reason it was ever worth doing.

EVERY PART KNOWS WHICH WHY IT SERVES.

AND SHOWS HOW IT'S GOING

Four refinement loops ride on every vision: design, build, deliver, and gather feedback. They are driven by checklists you define for the craft, so the percentages are real work checked off, not a status someone typed. A vision shows its own progress, on its own terms. This is the living blueprint.

WHAT A VISION HOLDS

THE WHY

The reason this should exist, in words a newcomer can read and understand.

THE DOCUMENT

A core vision document supported by a dossier of media, customer personas, architecture and notes written richly and kept in a revision-tracked docs lake.

THE PARTS

Sub-visions that decompose the whole, reusable and always traceable back to the core vision they support.

THE LOOPS

Design, build, deliver, and feedback each a checklist that shows the vision its own progress.

THE FIRST SHEET ON THE TABLE

START WITH THE REASON

Write the why on a page. Break it into parts. Keep every part pointing home.

START DRAFTING BACK TO THE INDEX