The 14-year itch

What changed

Fourteen years is long enough to watch entire paradigms rise and quietly recede. When I started, the craft conversation was about skeuomorphism versus flat — debates that feel almost quaint now. The tools were clunky, the handoff process was a mess of red-lined PDFs, and the idea of a designer writing production code was still considered an eccentric edge case. What's changed most isn't the tools or the titles. It's the scope. Design used to stop at the edge of the screen. Now it reaches into strategy, infrastructure, organizational structure. That's mostly good, and occasionally exhausting.

The role also got more abstract over time, and I'm still making peace with that. Early on, the satisfaction was immediate and tactile — you made something, it shipped, you could point at it. Now a lot of the most important work is invisible: a decision framework that prevents three months of wrong direction, a system that quietly scales across fifteen teams, a conversation that reframes a product problem before anyone wrote a line of code. The feedback loops got longer. The leverage got bigger. I'm not sure I'd trade it, but I notice the absence of that early concreteness.

What didn't

The fundamentals haven't moved much. Good design still requires being genuinely curious about people — not as users to optimize, but as humans with context and constraints and competing needs. It still requires the ability to sit comfortably with ambiguity for longer than feels comfortable. And it still requires knowing when to stop refining and ship the thing. Those were true in 2012 and they're true now, regardless of which AI assistant is in the sidebar or which framework the engineers have adopted this quarter.

The politics haven't changed either. Earning trust with engineering, navigating org incentives, explaining why "making it look nice" is not actually the job — these conversations are just as necessary as they ever were. If anything, the expanded scope of design has made the trust-building more important, not less. The more influence the discipline reaches for, the more it has to demonstrate it can handle the responsibility.

What still excites me

Honestly? The hard problems. The ones where nobody in the room agrees on what the question even is. The moments when a well-framed design question unlocks a product conversation that was stuck for months. I'm still excited by systems thinking — finding the underlying structure of a messy problem space and making it legible. And I'm still excited by the people who are early in this craft, who bring a kind of relentless energy to making things that I try not to let 14 years dull in myself. The itch, it turns out, doesn't go away. It just gets more specific.