Beyond the Screen: Why the Era of AI Calls for Systems-First Design Leadership

If you’ve been following the design conversation recently, you’ve likely seen the intense focus on how generative AI is shifting our industry. Tools can now generate layout variations, write copy, and create component systems in seconds.

For design leaders and hiring managers, this evolution naturally brings up a fundamental question: When execution becomes automated, what does high-impact design leadership look like?

To me, the answer is clear: We are transitioning from an era of screen production to an era of systems orchestration.

The highest-leverage product design has never been about pushing pixels in Figma. It has always been about making sense of complex, ambiguous problems, aligning cross-functional teams, and building scalable, human-centered systems that drive measurable business outcomes.

Throughout my career—beginning with an architectural foundation, moving through graduate research in Human-Centered Design & Engineering (HCDE) and Construction Management at the University of Washington, and leading enterprise product design at Amazon—this systems-first approach has been the foundation of my work.

Here is how that perspective shapes how I design, lead teams, and approach modern AI-enabled products.

"When execution becomes automated, the true differentiator isn't how fast you can draw a screen—it's how deeply you understand the system behind it."

1. Moving from Screen Production to Systems Orchestration

My path to digital product design started in architecture and construction management. In physical architecture, you learn an essential truth very quickly: a gorgeous blueprint is meaningless if the structural loads don’t balance or the mechanical systems don't fit.

Enterprise software functions the same way.

At Amazon, leading UX across complex B2B ecosystems like Fulfillment by Amazon (FBA) and AWS, the most challenging problems were never about visual styling. They were about understanding intricate backend data models, high-stakes seller workflows, and cross-border operational dependencies.

AI is fantastic at generating UI variations, but it cannot architect the end-to-end operational logic of a complex product. As design leaders, our role is to orchestrate that broader ecosystem:

  • Designing clear mental models that make complex systems feel natural and effortless.

  • Building user trust and transparency into AI-assisted interactions, ensuring users always feel in control.

  • Designing for continuity across multi-surface, multi-channel user journeys.

2. Turning High Technical Complexity into Intuitive Clarity

Enterprise platforms often suffer from cognitive overload. When you introduce machine learning, automated recommendations, and real-time data feeds, that complexity multiplies.

One of the most rewarding challenges of my work is translating dense technical architecture into clean, decisive user experiences.

During my graduate research at UW—designing building information interfaces and asset-tracking workflows for campus facilities leads—the goal was simple: give professionals immediate, dependable answers without forcing them to wade through technical clutter.

That exact discipline translated directly to my work at Amazon:

  • Focusing on decision velocity: Surfacing the right insight at the right moment so users can act quickly and confidently.

  • Demystifying machine intelligence: Designing explainable UI patterns that clarify why a recommendation was made.

  • Architecting for scale: Creating extensible design frameworks that adapt gracefully as engineering capabilities expand.

3. Serving as a Cross-Disciplinary Strategic Partner

Great products aren't built in design isolation. They are built at the intersection of user empathy, technical reality, and commercial viability.

Because my background bridges technical, operational, and design disciplines, I view cross-functional collaboration as core to the design craft:

  • Partnering with Product: Grounding business objectives in validated customer research and clear success metrics.

  • Partnering with Engineering: Understanding API limits, system latency, and data pipelines early to prevent expensive rework before code is written.

  • Partnering with Executive Leadership: Framing design decisions around customer retention, operational efficiency, and tangible business ROI.

When design leads with a deep respect for technical and business constraints, teams ship faster, communicate better, and deliver cohesive products that customers love.

Looking Ahead

The emergence of AI isn’t diminishing the value of design—it is elevating it. It removes repetitive drafting tasks so we can focus on the work that matters most: strategy, systems architecture, customer trust, and meaningful innovation.

As tech organizations build the next generation of intelligent enterprise tools, the teams that succeed will be guided by leaders who thrive in complexity, lead with empathy, and design for the whole system.

That is the work I love doing, and there has never been a more exciting time to build.

Let’s Connect

I’m always open to discussing design leadership, complex enterprise product challenges, and future collaborations.

Previous
Previous

Designing for High-Stakes Decision Making: What I Learned from Researching 30 Fraud Investigators

Next
Next

Alpine climbing and design