Article Preview: Where does design reside now? by Paul Melcher

Where does design reside now?

Originally featured on Design Week, this new article called Where does design reside now? by Paul Melcher explores a critical shift: as generative AI and automated templates decentralize production, the traditional design department is actively dismantling. In an enterprise landscape where sales, marketing, and AI models generate their own assets, where does the design function actually live today—and how can designers secure their survival?

This piece offers a compelling look at the rise of DesignOps, the quiet erosion of the bottom of the agency market, and why governance at the infrastructure layer is the only thing preventing total brand-communication chaos. As AI continues to democratize content creation, the designers who thrive will be the ones who build the system constraints that safeguard brand equity.

Below is an excerpt from the article by Paul Melcher:

For most of the last forty years, the answer was simple. Design resided in a department. It had a door, a headcount, a queue, and a budget line. Marketing wrote a brief, the design team produced the asset, and the asset came back through a review cycle that everyone, on some level, resented.

That department still exists in many organisations. But the work it once did has been quietly migrating elsewhere for at least a decade, first into marketing operations, then into individual contributors across sales, HR, and product, and most recently into the prompt box of a generative model. The question worth asking now is not whether design has been decentralised. That argument is over. The question is where the function actually lives today, and whether it will continue to exist as a recognisable role at all.

Two futures, both live

There are two coherent readings of what happens next, and they point in opposite directions.

In the first reading, the design function continues to shrink. If a marketing manager can describe a campaign in natural language and receive a coherent set of cross-format assets, the head designer’s template library becomes redundant. The brand book becomes a prompt. The role compresses into a quality-control function, then thins further, then dissolves into the same fate that overtook in-house typesetters in the 1990s. The work does not disappear, but the job does.

In the second reading, the opposite happens. Generative models without constraints produce drift – not catastrophic drift, but the steady erosion of what makes a brand legible across thousands of touchpoints. The more powerful the generator, the more valuable the constraint layer that sits above it. Someone has to decide what the model is allowed to do, what it must never do, and how its output is measured against a standard. That work is not prompt engineering. It is a design system architecture, applied to a generative substrate rather than a static template library. In this reading, the head designer is elevated, not eliminated, moved from rule-writer to systems architect, responsible for the operating environment in which non-designers and machines both produce work.

Read the full article on Design Week to explore the complete perspective.

Read the full article here