Richard Alvarez

Hi, I'm Richard.

I help design teams get faster without getting careless.

I've spent 25+ years in UX, from Windows 3.1 to agentic AI. Today I lead the AUX Strategy & Design practice at Apexon, where I'm figuring out, in real client work, what good design looks like when AI agents are part of the team.

25+ yearsin UX and digital
~30 peoplein the practice I lead
3 countriesU.S., India, and the UK
Illustrated portrait of Richard, chin in hand, behind a row of hot sauce bottles
Still thinking about what to put hot sauce on next.

AI made design faster. Judgment is what makes it good.

AI can now produce a dozen good-looking options in minutes. That doesn't make designers less important. It moves the work. The hard parts are still understanding the problem, hearing what people struggle to say, noticing who got left out, and knowing which option actually fits. I spend my time building teams and systems that keep that judgment intact while everything else speeds up.

Agentic Experience (AX)

When software acts on someone's behalf, people need to see what it did, understand why, and step in when they should. I design that oversight and trust in from the start.

Intelligent Design Systems

A design system only people can read is half a system. I push for components, tokens, and written rules that designers and AI agents both follow.

Human-centered strategy

Speed only helps when it's aimed at the right problem. Research, workshops, and honest framing keep the work tied to real people and real outcomes.

Case studies

Three pieces of work that shaped how I think about design, AI, and leading teams. Each one notes the steps it leaned on most, and where it makes sense, what's still open.

Before
After
Just over 1 week

One product design cycle, before and after an AI-ready design system and a multi-agent workflow.

Global pharmaceutical company, clinical supply

  • Frame
  • Give AI context
  • Prototype
  • Check
  • Hand off
  • Show the impact

A control tower designed with humans and agents together

The people who keep medicines moving to clinical trials were juggling several separate supply chain tools. The goal was one platform and one view. I led the engagement and the UX team. We started with ordinary UX deliverables and ended with something bigger: a design system built in React that both people and AI agents could use, and a new way of working that cut a design cycle from four weeks to just over one.

My roleEngagement and UX lead
TeamSeven UX and design system practitioners
ResultFirst release launched; 4 weeks to just over 1
Read the full story

What we built

A unified design system with components, tokens, and written rules that agents could read, so creating and checking designs became repeatable. A workflow where specialized AI agents handled parts of the work alongside our designers. A direct path from prototype into the client's React code, with new components flowing back into Figma so design and engineering worked from one shared library. Plus full-day workshops, executive materials, and the screen naming conventions the client's training team now uses.

What speed taught me

  • Structure keeps AI honest. Where the design system was thin, AI misread intent or made things up. Where approved components and clear rules existed, the output stayed accurate.
  • The round trip still has friction. Early tool limits pushed us straight into React. That kept us moving, but bringing new components back into Figma still takes extra steps.
  • Speed exposes the human bottlenecks. Once design got fast, the slow parts were data access, decisions, and expert time. AI can't sprint through those.
  • Evaluation never ends. The tools change monthly. I treat tool choices as ongoing experiments and judge every engagement by its outcomes.
Named gapAgents lost context between separate conversations. There was no shared memory across the workflow.
Next stepA shared context file my team is building now, so every agent starts from the same understanding.

The team: Inez Yuen, Tharun, Pravin, Chetan, Yilmaz, Tony Knaff, and Umang. This story is theirs as much as mine.

The design system sits underneath every step, so each agent works from the same rules.

Inside Apexon

  • Give AI context
  • Prototype
  • Check
  • Hand off

Practicing what we preach: an AI design workflow for our own products

It's hard to advise clients on AI-first design if you don't do it yourself. So my team turned the approach on Apexon's own internal applications. We built a plugin that brings an intelligent design system into an agentic design flow, taking work from discovery and ideation all the way to near production-ready code.

My rolePractice lead and sponsor
ScopeApexon design system and internal apps
ResultAdopted beyond the team, starting with a client
Read the full story

We aligned with Apexon's Agentic AI and engineering leaders to dedicate the team to internal tools, including audits and improvements to four internal applications. The plugin grew out of lessons from the control tower work, especially the need for agents to share context instead of starting each conversation from scratch. We previewed it for Apexon's president and senior leaders, who asked for a deeper session, and a financial services client has started adopting the same approach.

Named gapIt's still a work in progress, and the Figma round trip takes extra steps.
Next stepA deeper session with Apexon leadership on rolling it out more widely.

The team: Tharun and the AUX design team built it, and keep improving it for internal teams and clients.

One relationship, grown one practitioner at a time.

Global payments company

  • Frame
  • Explore
  • Check
  • Show the impact

Growing a ten-year UX partnership from one person to eleven

In 2016, at Saggezza, I started a UX engagement with one of the world's largest payments companies. Over the following decade it became one of the defining relationships of my career, growing into an 11-person UX team.

My roleStarted the engagement; practice lead
Span2016 to 2026
TeamGrew to 11 practitioners
Read the full story

Long engagements are earned one project at a time. The lesson I took from this one is that trust compounds when the team is consistent, the work is visible, and the people on it are treated as partners rather than extra hands. Maria Theron led the team day to day for much of that run.

How I work

AI has changed how fast my teams can move, but not who's responsible for the result. This is the path most of our work follows, and what each step leaves behind.

  1. FrameGet clear on the problem and who it affects before anyone opens a design tool.Workshops, problem framing, journey maps
  2. ExploreLay out real options and write down why we chose one.Design principles, options, decision log
  3. Give AI contextTeach the agents our rules so they don't guess.Design system rules, a shared context file, UI states
  4. PrototypeAgents draft fast. Designers shape what's worth keeping.Prototype brief, clickable prototypes
  5. CheckHold the work to a quality bar before anyone else sees it.Quality checks, accessibility review, self-critique
  6. Test with peoplePut it in front of real users and listen.Critique sessions, usability tests, findings
  7. Hand offMove approved work into code without losing the design.Specs, React components, sync back to Figma
  8. Show the impactClose the loop with what changed and what we learned.Design reviews, feedback, case studies

Who decides

The evidence, the people who'll use the product, and the designers on my team. AI drafts and checks along the way. It doesn't make the call.

How I keep the work honest

Every claim has evidence behind it, or we say plainly that it doesn't yet. Prototypes are called prototypes. Nothing is presented as tested unless real people tested it. And every decision ends with a named next step.

Watch: agents building alongside us

A short walkthrough of my team's agentic design flow, from first idea to near production-ready code.

Faster Together

My five-part series on what an AI-accelerated design engagement actually taught us, including the uncomfortable parts.

  1. What AI-accelerated product design actually taught usWhat changed, what didn't, and why judgment matters more now.
  2. From four weeks to just over oneWhere the time went before, and where it went after.
  3. A design system for humans and machinesMaking documentation readable for AI without losing people.
  4. The five AI agents beside our designersInside the multi-agent workflow and what each agent does.
  5. AI can't sprint through dataThe human bottlenecks that show up once design gets fast.

I've been writing about this stuff for a long time. My first book was the first on dynamic Flash web development with Macromedia Generator (New Riders). More recent pieces, like The Irreplaceable Human: 4 UI/UX Processes that Should Never be Automated, are on the Apexon blog.

My journey

Corporate, agency, startup, and classroom. I've been asking "why" more than "how" since my first job.

  1. What's next

    Here's where you join my journey

    Want to figure out what AI-first design means for your team? Let's talk.

  2. 2022 to now

    UX Service Line Director

    Leading the AUX Strategy & Design practice after Apexon acquired Saggezza, and steering it toward AI-first delivery.

  3. Jan 2017

    UX Practice Lead

    I formed the Saggezza UX team to focus on user research and design, using design thinking to understand what people need. We focus on building the right thing, not just anything.

  4. Mar 2015

    Senior Front-end Developer

    If today feels like yesterday, you're doing something wrong. So I mixed it up and joined Saggezza to collaborate with peers I could learn from and grow with.

  5. Feb 2013

    Co-founder

    Is it too much to say Zoom was my idea? Our startup for bringing people to museums and cultural events in a virtual world was, maybe, just a little ahead of its time.

  6. May 2003

    UX Director

    My two-person company joined another two-person firm so we could go after larger accounts together. Working with Thermos was great, but the highlight was the digital creative we produced for Lincoln Center's 50th anniversary celebration.

  7. Sep 2000

    Principal and Interactive Developer

    The success of my book forced me to incorporate. Apparently, Intel didn't want to contract a guy in his garage.

  8. Sep 1999

    Lecturer, then faculty

    A guest speaker opportunity turned into a class, which turned into an adjunct position, which turned into a full-time faculty position. It was just supposed to be one lecture about the web.

  9. May 1999

    Interactive Developer

    New skill: Macromedia Flash. I devised a way to make Flash dynamic, before it was built in, so editors, designers, and developers could work at the same time. My documentation became the first book on Generator and Flash web development, published by New Riders. I was told it sold well in Brazil!

  10. Aug 1997

    Interactive Developer

    Taking my interactive skills to the World Wide Web, while still creating a ton of CD-ROM and desktop content.

  11. Sep 1996

    Design Access

    Interactive Developer

    New skill: Macromedia Authorware, creating corporate eLearning content.

  12. Aug 1995

    Interactive Consultant

    Jenn didn't want to date someone she worked with, so I made it easy for her and got a new job.

  13. Sep 1993

    CD-ROM Interactive Developer

    Working in Macromedia Director, our team created interactive storybooks on CD-ROM that taught reading skills to kids with special needs. The best part: I met Jenn, who I would one day marry.

  14. Jun 1992

    Volunteer Technology Instructor

    Teaching computer skills like Word, Excel, email, and Windows in Little Village to people rejoining the workforce.

  15. Sep 1991

    Master's candidate

    The bad news: I didn't finish my master's. The good news: to pay for school, I taught myself HTML and started freelancing, building websites.

  16. May 1991

    Associate Developer

    Working on Windows 3.1, I got my first taste of software product development. Even then, I remember asking "why" more than "how."

  17. May 1991

    Bachelor of Arts, English

    I majored in English with a minor in Spanish literature. My older sister studied computer science, and with her help, I learned to program in C.

Let's connect.

I'm always glad to talk with product and technology leaders, fellow practice leaders, and anyone looking for a speaker or workshop facilitator on AI and design. When I'm not working, I'm running, following the Chicago Cubs, or hunting for my next hot sauce.