Essays
Arguments and working notes on the relationship between people and the systems they have to use, trust, and live with, seen from where it becomes usable, where it is lived, how it learns, and what allows it to hold.
Products where the relationship becomes usable
-
When the product fails to carry the strategy
How strategic choices become visible, or invisible, through use.
-
Designing for consequence
Why some products must make uncertainty, failure, and recovery visible.
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.
-
The work between AI prototype and organisational trust
What it takes to build AI systems people can actually rely on.
Evidence how the relationship learns
-
The claim before the metric
Why better measurement starts by asking what you need to be able to say.
-
What experiments are for
How product teams, social organisations, and design leaders can build better learning systems.
-
Frameworks are scaffolds, not architecture
Why discovery and delivery need a shared learning system, not competing rituals.
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
How shared patterns become infrastructure when the organisation can carry the change.