The Architecture of a Good Type System
I’m teaching a few classes, which is how many of these posts begin. Preparing to teach forces me to pull decisions out of muscle memory and explain why I make them.
I’m teaching a few classes, which is how many of these posts begin. Preparing to teach forces me to pull decisions out of muscle memory and explain why I make them.
Sometimes people assume I’m all over the place. I understand why. I move between strategy, design, technology, systems and creative experimentation.
There is a particular kind of website project that looks great all the way through the pitch, the strategy, the creative review and the design presentation.
Eye-tracking research on how people actually read a page — and why it's what I'm actually thinking about when I pick a font.
I rebuilt five colour palettes at the same time to find out what actually makes a system a system, not just a palette no one's clear on how to use.
Nothing reaches a client site until it has survived two rounds of me trying to break it somewhere cheaper.
People I work with joke about this. They pull something up on a call and apologize for how many tabs they have open, half laughing, half embarassed. I get it. When I'm building a design system, the tabs. Omg, the tabs.
This summer, I moved into my basement.
I've been thinking about what happens when the ground shifts underneath you. Not dramatically, necessarily. Sometimes it's just a slow realization that the things you've relied on for years are still there, but they don't work quite the way they used to.
Berlin made me think differently about design.