The Weak Links in Design

AI makes parts of design faster. The harder question is what still prevents design from changing the system.

A recent talk by economist Chad Jones helped me think more clearly about something I had been trying to articulate about AI and design. Jones was not talking about design specifically. He was talking about AI, economic growth, and why transformative technologies do not always transform the world as quickly or as evenly as their technical capabilities suggest. But one of his central ideas, the idea of weak links, applies surprisingly well to design work.

The basic point is that complex systems depend on many connected tasks. If a chain has twenty links and seventeen of them become much stronger, the chain may still be constrained by the three that remain weak. The improvement is real, but the full value of the system depends on the links that still limit it. Jones uses this to explain why AI could be extraordinarily powerful while its economic effects still unfold unevenly across industries, occupations, and institutions.

This is a useful way to think about design because design is often discussed as if it were a single kind of work. This is especially true in conversations about AI, where the question is often reduced to whether AI can "do design" or whether it will eventually replace designers. The problem with that framing is that design is not one activity. It is a bundle of different tasks that happen to sit under the same professional label.

A designer might spend part of a day synthesizing research, part of it exploring interface patterns, part of it writing product documentation, part of it facilitating a stakeholder discussion, and part of it trying to understand why the organization is solving the wrong problem in the first place. Some of this work is analytical, while other parts are creative. Some of it is communicative and social. Some is strategic, while other parts are operational and deeply connected to delivery. All of it gets called design, but AI does not affect each part of that bundle in the same way.

AI is already useful for many parts of design work. It can summarize interviews and workshop notes, find patterns across messy inputs, generate alternative concepts, draft documentation, compare options, rewrite complex material into clearer language, and help move from an ambiguous starting point to a usable first version of something. These are not trivial improvements. They can change the speed, cost, and rhythm of design work. They reduce the friction of starting, make rough thinking visible earlier, and allow teams to explore more options before narrowing too quickly.

But faster production of design artifacts is not the same as better design impact.

This is where the weak-link idea becomes important. Design work creates value only when several connected links hold together. Research needs to become insight. Insight needs to become framing. Framing needs to become product direction. Product direction needs to become alignment. Alignment needs to become delivery. Delivery needs to become adoption. Adoption needs to become some form of measurable value for users, customers, employees, or the business.

If one of those links breaks, much of the value is lost.

A team may have better research summaries but still lack agreement on what problem matters most. It may have stronger concepts but no clear product owner with authority to act. It may have better prototypes but no engineering capacity, no trusted data, or no realistic path through governance and security. It may have sharper documentation but incentives that reward local optimization over end-to-end user value. It may have more polished presentations but low trust between the teams that need to make a decision together.

In enterprise UX, these weak links are often the real bottleneck. The problem is rarely that the organization simply needs more screens. More often, the organization struggles to decide what should exist, why it matters, who owns it, how it fits into the wider system, and which trade-offs are acceptable. AI can help with parts of that work, but it does not automatically resolve the conditions around the work.

This is why AI demos can feel both impressive and incomplete. A tool that generates a prototype from a prompt can be genuinely useful. But in an enterprise setting, the hard part is rarely only the prototype. The hard part is knowing whether the prototype represents the right problem, the right workflow, the right policy constraint, the right data model, the right operational reality, and the right level of risk. The artifact matters, but the artifact is only one link in the chain.

As AI strengthens some links in the design process, it also exposes the others. When synthesis becomes faster, weak problem framing becomes more visible. When interface generation becomes faster, weak product strategy becomes more visible. When documentation becomes faster, weak decision-making becomes more visible. When communication becomes faster, weak alignment becomes more visible. The organization may feel more productive, but it may also become clearer that the real constraint was never only production capacity.

This changes the shape of design work.

Some tasks that used to consume a lot of design time will become less central. First drafts, research summaries, interface variations, documentation scaffolds, and even certain kinds of prototyping will increasingly be assisted by AI. Designers who define their value mainly through producing these artifacts will feel pressure, and that pressure should not be dismissed. Some parts of design work will be automated, some will be compressed, and some roles may become less viable if they are built primarily around tasks that AI can perform well enough at lower cost.

But the more interesting question is not which tasks disappear. It is where value moves.

Jones makes the point that jobs are bundles of tasks. When AI automates some tasks in a job, the remaining tasks can become more important because they are now the scarce links. In design, that means the value may shift toward framing, judgment, context, facilitation, trust, and the ability to connect design work to decisions that actually change what gets built.

If generating a reasonable prototype becomes cheap, the scarce work becomes knowing what should be prototyped and why. If summarizing research becomes cheap, the scarce work becomes knowing whether the research was asking the right question in the first place. If documentation becomes cheap, the scarce work becomes ensuring that documentation clarifies accountability, trade-offs, and delivery implications rather than simply producing more polished words.

This does not mean the remaining human work is automatically noble or safe from automation. Humans are also weak links. Human judgment can be biased, slow, political, territorial, or poorly informed. Designers can mistake taste for quality, process for progress, or alignment theater for genuine shared understanding. The point is not that human work is inherently better. The point is that some parts of design are more entangled with context, authority, accountability, and trust, and those parts are harder to automate cleanly because they are not just tasks. They are relationships inside a system.

This matters especially in large organizations. Enterprise design is not only a matter of understanding users and producing better interfaces. It is also about working inside complex systems of ownership, architecture, compliance, legacy platforms, procurement, security, delivery models, and incentives. The work often involves translating between worlds that do not naturally understand each other: business strategy, technical feasibility, operational reality, user needs, and organizational politics.

AI can support that translation, but it does not remove the need for it. In many cases, it may make the translation work more important because teams will be able to generate more material, more quickly, with less confidence that the surrounding context has been properly understood. More output can easily become more noise unless the design process has stronger ways to decide what matters.

This is where I think design leaders need to be careful. The most obvious use of AI is to make existing design tasks faster. That is useful, and it should happen. But if AI is added to a weak design process, the result may simply be a faster weak process. More summaries, more concepts, more decks, more prototypes, more apparent progress, but not necessarily better decisions or better outcomes.

The better opportunity is to use AI to examine the design process itself.

Which parts of the work are slow because they are manually intensive? Which parts are slow because context is missing? Which parts are weak because decision rights are unclear, incentives are misaligned, or trust is low? Those are different problems. They should not all be treated as productivity problems.

This is also why speed is an incomplete measure of AI adoption in design. Speed matters, especially in organizations where producing and maintaining design artifacts has become unnecessarily expensive. But a team can become faster without becoming meaningfully better at design. The better measures are closer to the actual work of design: whether the team frames the problem more clearly, brings the right context into the conversation earlier, or makes a difficult trade-off easier to discuss. A useful AI-enabled design process should reduce ambiguity for engineering, improve the quality of product decisions, and help stakeholders see the system more clearly.

Those measures are less dramatic than output volume, but they are closer to the conditions under which design creates value.

The weak-link view also helps explain why the effect of AI on design will be uneven. In some contexts, AI will feel like a major productivity gain because the existing bottleneck really is production capacity. In other contexts, it will feel underwhelming because the weak links sit elsewhere. A team that already has clear strategy, strong product ownership, good data, trusted research, and mature delivery practices may benefit quickly from AI. A team without those things may generate more artifacts while still struggling to move the organization.

This is not an argument against AI in design. Quite the opposite. It is an argument for using AI more seriously. If design is a bundle of tasks, then AI adoption should begin by understanding the bundle. Not in an abstract way, but in the actual flow of work: how problems are framed, how evidence is gathered, how options are explored, how decisions are made, how teams align, how delivery happens, and how outcomes are evaluated.

The future of design will not be shaped only by whether AI can generate interfaces. It will be shaped by which parts of design become cheap, which parts remain scarce, and which weak links determine whether the work changes anything in the real system.

References

[1] Chad Jones, "A.I. and Our Economic Future," Stanford University, 2026.

[2] Philippe Aghion, Benjamin F. Jones, and Charles I. Jones, "Artificial Intelligence and Economic Growth," Stanford University/NBER working paper.

[3] Chad Jones and Christopher Tonetti, "Past Automation and Future A.I.: How Weak Links Tame Growth," Stanford University/NBER working paper.