Behind every project is a way of thinking. Here I write about what interests me — on design, strategy, and building teams.
UX design treats friction as a problem to solve. Sometimes it's part of solution. The difficulty is not removing it — it's knowing when to leave it alone.
Simplicity is not a visual style — it is a way of thinking about what a product is actually for. Four strategies that still hold up.
Putting the user first was a good idea — until it wasn't. A reflection on what responsible design might look like when you zoom out.
Speed at the wrong moment is expensive. If you solve the wrong problem well, you have still solved the wrong problem.
Good functionality and a clean interface are now the baseline. The question is no longer whether your product works — it is whether people actually want to use it.
Trend lists are everywhere. But a list of visual styles without context is like a weather forecast without understanding what causes weather.
Done well, design principles give a team a shared language. Done badly, they are a list of adjectives on a wall that nobody looks at. The difference is usually in how they are made.
Most projects start with the wrong question. Here is how I think about moving from a rough idea to something people actually want to use.
:quality(80))
:quality(80))
:quality(80))
:quality(80))
:quality(80))
:quality(80))
:quality(80))
:quality(80))