Three short essays, each written as a proper 2-minute read, on breadth, AI-enabled judgement and quality as an operating model.
Breadth gets misunderstood because people often use it as a softer word for being unfocused. That is not the useful version. The useful version is transfer: the ability to carry judgement from one material, medium or organisation into another without pretending the contexts are identical.
The easy AI story is speed. Faster drafts, faster prototypes, faster research synthesis, faster copy, faster code. All of that is real, and any serious design leader should be paying attention. But speed is not the most interesting shift. The deeper change is that production is becoming less scarce while judgement becomes more exposed.
Organisations often talk about quality as if it is a personal preference. Someone has taste, someone else does not. One team cares about craft, another does not. That framing is too small. In practice, quality is usually the output of a system. It is shaped by who makes decisions, what evidence matters, how feedback happens, how teams learn, what leaders reward and how much time is reserved for thinking before delivery pressure takes over.
Essay 01 / 2-minute read
Breadth gets misunderstood because people often use it as a softer word for being unfocused. That is not the useful version. The useful version is transfer: the ability to carry judgement from one material, medium or organisation into another without pretending the contexts are identical.
A designer who has moved through 3D, games, mobile, brand, SaaS, fintech and enterprise products has met different kinds of constraint. In games, timing and feedback matter because a tiny delay can break the feeling of control. In mobile, hierarchy has to survive a small screen, an impatient user and a distracted moment. In enterprise products, the visible interface is often the tip of a much larger system of roles, permissions, data quality, adoption, risk and internal politics. In design leadership, the work is not only the product. It is the organisation that keeps producing the product.
That range matters more now because AI is blurring old production boundaries. A team can generate interface options, drafts, flows, research summaries and code-shaped prototypes at a pace that would have seemed absurd a few years ago. But faster production does not create better product judgement by itself. The person leading the work needs to understand what kind of problem is in front of the team. Is the issue visual? Behavioural? Organisational? Commercial? Ethical? Technical? Is the interface confusing because the screen is badly designed, or because the business model behind it is incoherent?
The value of breadth is not that one person can do every task. It is that they can recognise the nature of the task before the team wastes weeks solving the wrong version of it. They can tell when craft is being used to hide weak strategy, when strategy is too abstract to survive contact with users, when research is becoming theatre, and when a team has enough information but not enough courage to make a decision.
That is the through-line of this site. Paper Design is not trying to present a tidy linear career. It is showing how a long body of work creates pattern recognition. The modern design leader has to connect interface detail to product strategy, product strategy to team behaviour, team behaviour to business consequence, and business consequence back to the human experience. Breadth only matters when it makes those connections stronger.
Essay 02 / 2-minute read
The easy AI story is speed. Faster drafts, faster prototypes, faster research synthesis, faster copy, faster code. All of that is real, and any serious design leader should be paying attention. But speed is not the most interesting shift. The deeper change is that production is becoming less scarce while judgement becomes more exposed.
When a team could only make a small number of options, the cost of production forced selectivity. Now teams can create dozens of plausible directions very quickly. That sounds liberating until the organisation has to decide which of those directions is true, useful, ethical, on-brand, technically realistic and worth learning from. AI does not remove the need for taste. It increases the volume of material that taste has to evaluate.
This changes the role of design leadership. Leaders cannot simply encourage teams to use tools and hope quality follows. They need to design the conditions around tool use. What counts as a good prompt? What source material is allowed? How are claims checked? How does the team distinguish a persuasive-looking output from a valid one? When does AI help divergent thinking, and when does it create false confidence? How are user needs, business goals, accessibility, brand, data privacy and product architecture held in the same conversation?
The better teams will not be the ones that outsource judgement to machines. They will be the ones that use machines to widen the field of exploration, then use human judgement to choose, test and improve. That judgement has to be made visible. Principles, critique rituals, decision records, examples of good work, evidence standards and review loops become more important, not less.
This is also why senior designers need to stay close to the tools. If leadership retreats into abstract strategy, the actual practice of AI-enabled design will be shaped by convenience, speed and whatever the tool makes easiest. That is dangerous. The defaults of a tool are not the same as the standards of a product. Leaders need enough hands-on fluency to know what the tools are good at, where they distort thinking, and how to build workflows that improve the work rather than merely accelerate it.
AI makes average production cheaper. It does not make good judgement cheaper. In many businesses, judgement will become the differentiator: the ability to frame the right problem, recognise quality, challenge weak assumptions, connect evidence to decisions and keep responsibility with the humans who choose what ships.
Essay 03 / 2-minute read
Organisations often talk about quality as if it is a personal preference. Someone has taste, someone else does not. One team cares about craft, another does not. That framing is too small. In practice, quality is usually the output of a system. It is shaped by who makes decisions, what evidence matters, how feedback happens, how teams learn, what leaders reward and how much time is reserved for thinking before delivery pressure takes over.
This becomes clearer as organisations scale. A small team can rely on a few strong individuals to hold the standard together. Everyone knows who to ask, what good looks like and where the important trade-offs live. But as products multiply, teams split, markets diverge and leadership layers appear, quality becomes harder to keep coherent. Without an operating model, every product team invents its own version of good. Some will do that well. Others will optimise for speed, local preference or the loudest stakeholder in the room.
AI increases both the opportunity and the risk. It can help teams explore faster, summarise evidence, produce variants, test language, inspect interfaces and make prototypes feel more real earlier. But it can also create a flood of plausible mediocrity. If the organisation lacks a shared view of quality, AI will not fix that gap. It may simply make the gap more productive.
A quality operating model does not mean bureaucracy. It means useful structure. Teams need principles that are specific enough to guide decisions. They need review rituals that improve the work rather than perform authority. They need examples that show the standard in context. They need evidence loops that connect design decisions to behaviour, adoption, trust, confidence and business value. They need leaders who know when to centralise a standard and when to let local teams adapt it.
The aim is not to slow teams down. It is to reduce the cost of confusion. When teams know what good means, they can move faster because they spend less time renegotiating fundamentals. When critique is normal, feedback becomes less personal and more useful. When decisions are recorded, the organisation builds memory. When AI-generated work is judged against clear standards, the tool becomes part of a learning system rather than a shortcut around accountability.
Quality is not a polish phase. It is the way an organisation thinks, decides and learns. Design leadership earns its keep when it makes good work easier to produce, weak work harder to justify, and future work smarter because of what the organisation has already learned.