Most design is “Little Design"

When I started in UX 20ish years ago, systems were small. Google was a search engine. Amazon was an e-commerce website. Meta was a Facebook. There were two sides to these systems: the frontend and the backend—logically divided, and a designer or small team of designers could work on these systems and mostly maintain a sense of cohesion.

Systems have grown larger. Like HUGE. To the point where people working on them really don’t know all the nooks and crannies of the system. Things have been built over years, code bases are divided up, and the user experience feels like a labyrinth.

When a system becomes so large such that no one can quite wrap their head around it all this generally means that you need teams working on each component part. One team might own the overarching structure of it, for example, the global navigation of a large software product. But the others own pieces that stem from that structure, namely pages and features. Sometimes these are standalone (like a page for spinning up and managing databases in a cloud provider), or sometimes they’re threaded through the entire site (like ad widgets on a sprawling information portal). And of course, each team brings its own business objectives, and therefore desires to cut through ambiguity and understand the bounds of its ownership so it can claim success and prove its worth. The end result: a company ships its org chart.

Outside of very early startups or within mature, quality-focused companies, designers today mostly work on these types of teams. I call this “Little Design” because it means a designer stays in their boxed-off area, focusing on the minute details of their feature (too often erroneously called a “product”), often at the exclusion of how it fits broadly into the larger whole.

They know their box well. The run evaluative studies to “validate” their designs. They get excited to work with their product managers and hit their metrics and celebrate their wins. They use the design system, but routinely override the components because their use case is a special snowflake that “needs“ it. They’re proud of the quality of the internals of their feature, but not how it fits into a broader system.

In short, they contribute to the entropy of the system.

“Big design” tries to reduce that entropy by working on initiatives that help users make sense of an organization’s ever-growing and complex set of offers. They do so by creating systems that scale user experience in an ordered way (design systems, UX measurement and success frameworks, well-researched Jobs to Be Done frameworks, and other similar strategic artifacts) and by using these to redesign sub-optimal systems to harmonize the feature sprawl. The goal ultimately is to effect change in the overall system, making the entirety of it more attractive to users, easier to use, or whatever positive indicator suffices.

Big design is hard. Like super hard. It first of all requires an organization to recognize the need for someone to sit above the feature factory and think hard about what a product, platform, or service ought to be in the future, regardless of what is now. In many organizations that feels like an extravagance. It also requires someone who is able to gather and synthesize a large number of inputs (business needs, user needs, technical constraints) across business lines and translate them into designs that users can use easily with minimal guidance. It’s cognitively taxing, highly abstract work. It also requires an extraordinary amount of political will to get teams and leaders on board with new concepts, to disrupt their roadmaps, and to set aside short term metrics. In most cases, someone undertaking a Big Design project is either an exceptional storyteller, or has an avenue for appealing to someone high enough up in the org chart (often an SVP or C-suite member) who can make the decision for their entire organization.

Many big design projects never see the light of day. This is almost always because of political failings—for example, an empire building exec refused to cooperate—or because the cost is too high—the cost to build (4000 man years!) or the short-term economic hit to the business. The designers who are able to pull these types of projects off are handsomely rewarded with money and fancy job titles like “Sr. Principal UX Designer” or “Distinguished Designer.” Lofty.

As most big design projects fail or are never attempted to begin with, most big companies don’t do design well. I would argue that even companies known for good design (Apple, for instance) mostly don’t. All one has to do is look at connected services like iCloud or Parental Settings, or the bolting of Siri onto everything, before you collapse in a state of confusion. This isn’t, of course, because the designers are bad. It’s because the organization is too large to get its arms around everything its trying to do, the function of design is dispersed across teams, and no one is responsible for wrangling all of it OR that person is thwarted by an army of naysayers.

So, is Little Design bad? Is Big Design good? As a former UX Director at Amazon, I wanted all my designers to grow into Big Designers. I wanted them all to think strategically, in systems, to always consider the effects on the broader system, and to make courageous choices in their designs. But I was also responsible for shipping features that were on real deadlines (the holidays don’t move!), and in some cases, getting something out was better than getting nothing. So it’s not as simple as good or bad. As is always the answer with UX, it depends.

Recent articles