Great design at scale comes from frameworks, principles, and foresight. Solve for patterns, not just pixels, so teams can deliver quality consistently.
I’ve always called myself an Experience Designer. It can sound precious, I know. But the distinction matters more than ever as products get shipped faster and with less consideration for what they add up to.
The difference isn’t really in the title—it’s about orientation and how we’re actually able to influence work. Product design tends to be vertical: scoped, focused, accountable to a specific feature or pillar. Experience design is horizontal: concerned with how everything connects, what happens at the seams, and what the full arc of someone’s interaction actually feels like.
The limitation of purely vertical thinking is that it usually stops at the edges of a mandate—especially in large organizations. You can design an elegant transaction flow and have zero influence over the failure state, the support experience, or the three other touchpoints a user hits before they get there. The work looks complete on a canvas and falls apart in the real world. And when the only way to close that gap is to lobby a director or navigate inter-team politics, the seams in the org become the seams in the product.
And when you ship the org, not only do users feel every one of them, but they’re difficult to defend in a case study or portfolio review. The hardest thing I’ve seen people try to do is establish cross-team influence as a designer, because the fact of the matter is that in most organizations (especially large ones), you simply don’t have that level of authority.
What prevents this limitation is investing in the connective tissue: creating shared frameworks, radiating consistent visibility into work happening across teams, socializing consistent patterns, and aligning the team to design principles that give people a common language and a stable foundation to build from. When those exist, designers can move faster, collaborate across scopes more easily, and make decisions that compound well over time instead of creating debt.
The best work I’ve seen comes from designers who can hold both: the specific problem in front of them and the broader system it lives inside. Who ask not just “does this work?” but “what does this make possible, and what does it make harder?” Architects don’t design for how a building looks on a clear day. They design for load, stress, and the conditions most likely to test the structure. Design at scale requires exactly the same foresight.