Essays
Arguments and working notes on the relationship between people and the systems they have to use, trust, and live with, grouped by the four lenses I work through: where that relationship becomes usable, where it is lived, how it learns, and what allows it to hold.
Products where the relationship becomes usable
-
Designing for consequence
Why some products must make uncertainty, failure, and recovery visible.
-
When the product fails to carry the strategy
Customers meet the strategy the product carries out, whatever the deck says.
People where the relationship is lived
-
When the surface comes loose
What we are actually trusting when we trust a system we do not understand.
-
What the screen owes
Design quality stays an argument about taste until an organisation agrees what each moment owes the person using it.
Evidence how the relationship learns
-
The claim before the metric
Why better measurement starts by asking what you need to be able to say.
Organisations what allows the relationship to hold
-
Fragmentation and flattening
Two opposite failures produce the same symptom: no one agrees what the brand is. The costly mistake is treating them as one.
-
A design system is an organisational system
When coding agents read the system, its governance becomes mechanical, and whoever can merge decides.