I've spent 16 years designing enterprise systems that actually ship, and learning the hard way that the gap between great design and great product is almost always an organizational problem, not a craft problem. I work at Staff level because that's where design has the most leverage: shaping systems instead of screens, aligning teams instead of just delivering artifacts, and building the infrastructure that lets everyone around me move faster and build better.
Clarity in complex systems. My work lives in data-heavy enterprise SaaS, fleet management, supply chain, operational tooling. These aren't glamorous domains, but they're where bad UX has real consequences. When an executive can't find critical data, a decision gets delayed. When a vendor can't complete a workflow, a shipment gets missed. I design for the stakes, not the showcase. Reducing cognitive load in information-dense interfaces. The hardest design problem isn't making something beautiful, it's making something with 200 data points feel manageable. I've built dashboards that cut executive task time by 60%, not through simplification, but through intelligent information architecture and action-centered design. Shipping scalable infrastructure, not one-off screens. A design that can't scale isn't a good design, it's a liability. I've led design systems serving 15+ enterprise domains and 35+ designers. The work I care about is the kind that keeps working after I leave the room.
I've learned that the strongest design systems aren't mandated from the top, they're adopted because they make everyone's job easier. I build governance models that give designers and engineers real ownership, because teams that feel ownership become the system's strongest advocates. I mentor by teaching designers to think in systems before they think in screens. The questions I push are always: what happens at scale, who else needs this, and what breaks first under edge cases. I partner with engineering early, not at handoff. The best product decisions happen at the intersection of design intent and implementation constraint, and you only find that intersection if you're in the
room together from the start.
Early in my career I thought design systems were about components. I've since learned they're about trust. A component library nobody adopts is just a well-organized Figma file. The real work is building something teams believe in enough to contribute to, and that requires governance, communication, and treating adoption as a product problem in its own right.