01 / 09
Cadence 2026 · Design × Engineering
The Quiet Architecture of Slow Software
There is a second kind of speed — the speed at which a tool gets out of your way. We almost never measure it.
HERO · metronome at rest, warm paper · 16:9
Mara VintA talk in six beats
Illustrative example — a fictional talk by a fictional speaker. Not a real person's content. Magazine deck rendered by talk-to-deck's own renderer (workflow-only lift of 歸藏 / op7418/guizang-ppt-skill, AGPL-3.0; no source files copied).
02 / 09
The hook
We measure the machine. We never measure the person.
We tune p99 latency to the millisecond and ship it. The p99 of a human's attention — the tax a tool charges just to be used — goes unlogged. Two kinds of speed; we only instrument one.
FIGURE · two gauges — “machine” measured, “attention” blank · 4:3
03 / 09
The claim
slowness is a design budget, not a defect.
Slow software isn't software that runs slowly. It's software designed at the pace of understanding — fewer surfaces, durable defaults, decisions made once and remembered.
04 / 09
The counter-current
Three forces push teams the other way.
None of them is stupidity. Each is a rational response to how software gets funded and judged — which is exactly why they're hard to resist.
LEAD · three arrows pulling away from the center · 16:9
05 / 09
A worked contrast — illustrative
40
features in the “fast” tool nobody can name
9
features in the “slow” tool that compose
fewer
moves to finish the very same job
Same job. The slow tool wins not by speed but by subtraction. (Numbers illustrative.)
06 / 09
The three forces, named
FORCE 01
the demo-driven roadmap
You build what shows well in a 30-second clip.
FORCE 02
the metric monoculture
Only what is logged is treated as real.
FORCE 03
the novelty treadmill
A redesign is easier to fund than a refinement.
07 / 09
The turn
Not this
Nostalgia. “Software used to be better.”
This
Subtraction under constraint — and it's fundable if you can price the surface you didn't cut.
08 / 09
The ask
Measure time-to-out-of-the-way.
Budget for refinement, not just features. Treat the interface a person didn't have to learn as the achievement — and put a number on it.
FIGURE · stopwatch relabelled “time-to-out-of-the-way” · 4:3
09 / 09
What did your users not have to learn today?
The Quiet Architecture of Slow Software · Mara Vint · Cadence 2026