Problems

01 How do you make design answer to business economics, not aesthetics?

Capital One, 2022 to 2025. A partnerships design organization spanning consumer and business experiences for some of the largest retail brands in America.

Design organizations measure themselves in craft. Businesses buy outcomes. The moment design can't explain where it moves money, it becomes production support with good taste.

I stopped assigning designers to roadmaps and started allocating design like capital. I looked horizontally across the portfolio, asked where experience investment created the greatest customer and business leverage, and moved capacity, ownership, and senior talent to match. My designers were expected to understand the business mechanics of what they built, and to shape problems early instead of receiving requirements late.

Design became an input to planning rather than a recipient of it. The question in the room changed from "can design support this" to "what does design think we should do."

02 How do you move millions of customers to a new product without losing their trust?

The end of one of the largest retail card partnerships in the country. Millions of customers converting to a new product, whether they asked to or not.

A forced migration reads like a breakup letter. Customers don't ask what product they have now. They ask whether they were dropped. Confusion at that moment converts directly into attrition.

I reframed the conversion from a compliance exercise into a retention event. The experience had to earn the customer's confidence at the moment of transition, and keep earning it afterward, when most programs go silent.

Attrition risk became an experience problem with a design owner, not an operational footnote. Experience decisions entered the portfolio economics conversation, which is where they belonged all along.

03 How do you create one coherent experience when five companies share the customer?

Partnership experiences where the user, the purchaser, the account holder, and the brand were often four different parties, across acquisition, servicing, rewards, business portals, and trade credit.

Every partner wants their own version of everything. Solve each brand separately and you build the same thing five times, a little worse each time, at five times the cost.

I pushed the organization from partner-specific design toward horizontal capability. When the same problem appeared across brands, we built it once as a platform behavior and let partners inherit it. That meant managing external brand stakeholders with the same rigor as internal ones, because the partner's name was on the experience too.

Reusable capability replaced bespoke repetition. One design organization served radically different experience archetypes as a coherent system instead of five teams solving the same problem apart.

04 How do you decide where design talent creates the most leverage?

A scope expansion that merged previously separate design areas into one organization.

Most org charts are inherited, not designed. Talent sits where history put it, not where the opportunity is, and everyone quietly works around the mismatch.

I treated the organization itself as the design problem. Which problems deserve persistent ownership. Where senior talent compounds. What can be shared support without becoming no one's job. I unified the operating model without adding process, because process is what leaders reach for when they haven't decided anything.

Structure followed opportunity. People grew by taking on more ambiguous problems, not more screens.

05 How do you rebuild a design organization for the AI era?

Epicor, now. A global enterprise software company, and a design organization meeting the AI era.

AI doesn't make the old design job faster. It replaces the job. When software can be generated on demand and agents operate interfaces alongside people, a design organization that only produces screens is already obsolete.

I'm rebuilding the operating model rather than bolting AI onto the old one. Design infrastructure that machines can consume as reliably as people. Research and decision practices rebuilt around AI leverage. Designers accountable for judgment and outcomes, not artifact volume.

The organization's output is shifting from deliverables to decisions. That's the difference between a design team that survives this era and one that gets automated by it.

06 What happens when a leader's judgment can scale past their calendar?

My own practice.

Every leader is a bottleneck shaped like their own judgment. Most accept the bottleneck. I decided to engineer it.

I codified how I frame problems, make decisions, communicate, and lead people into a working AI system. Not notes. Not prompts. An operating system I run daily, and that improves every time I use it.

context → framing → perspectives → judgment → output → feedback

My judgment now scales past my calendar.

This site was researched, written, and structured with that system. The colophon is the case study.