A@DmZfr W &4M*4e@dsW0
Not case studies. Not process walkthroughs. These are the things I've had to work out for myself — about what design leadership actually costs, and what twenty years of working across cultures teaches you about your own assumptions.
A teenager somewhere solves a real problem. Not a hackathon problem — a real one. The river behind their town runs the wrong colour, and they work out something that helps. It works at small scale. People notice.
There is a moment in most design critiques that reveals everything. It happens when someone in the room moves from saying what they see to asking why it exists. The shift is subtle — from "the price location changes throughout the journey" to "I want to see my actions affecting the price" — but the distance between those two observations is the distance between a team reviewing work and a team genuinely thinking together.
There is a version of this story that gets told at conferences. A design leader walks into a conservative organisation, wins over the sceptics, ships the design system, and exits to applause. It is a more than satisfying arc, one that not many designers get to experience nor live to tell the tale (designer humour... ha) It is also incomplete and way too simple.
Most design principles present themselves as universal. User-centred. Accessible. Intuitive. The assumption baked into those words is that the user is roughly like you. Twenty years working across France, the UK, the Netherlands, and beyond taught me that this is mostly fiction.
