Context
No two problems share the same layers, even within the same company. Every project carries its own ecosystem: technical feasibility, emotional climate, legal boundaries, market timing, brand implications. I've developed a strong ability to read these layers simultaneously, see how they interact, and hold the full complexity of a problem without flattening it. And when the product is built for millions of people, the emotional layer is never just a detail. It's often the whole point.
Purpose
Purpose is what separates a pixel pusher from a designer with vision. Components are functional. Experiences have a destination, a cycle of movement, improvement, and change. Spotify didn't just organize your music library; it changed how you listen, what you discover, who you become as a listener. That's purpose at work. For me, purpose means having the ability to see a non-existent future and lead people toward it: users, teams, and organizations alike. It doesn't matter if I'm designing for an industry I love or one I'm learning from scratch. I've trained myself to form a vision for any problem I work on, and to hold that vision clearly enough that others can see it too.
Process
All the context, all the talent, all the resources, and companies still default to the safest option. I've seen it too many times. Good process is built on trust, honesty, and the courage to say "this isn't good enough." But more than anything, it means spending your energy on what makes you unreplicable, not on benchmarking against competitors. Every industry has a baseline. The interesting work happens past it. And it has to stay dynamic. This industry moves too fast for rigid frameworks. Even saying the word "process" feels like a risk, and that's exactly the point.