Creative Duel: Scale versus Craft
The first Creative Duel of Nivan Live 2026 put Noel Childs of Digitas on the side of scale and David Kazaryan of United Airlines on the side of craft, moderated by Alex of NVISIA under one rule. No compromise. It is scale or it is craft. What followed was less a contest than an exposure of the assumptions the design profession has stopped examining.
Noel Childs and David Kazaryan at Nivan 2026
Why this argument was worth staging
Roughly half the room raised a hand as designers by trade, which made the question personal rather than theoretical. Every practitioner in that hall has been asked to produce more, faster, across more surfaces, while also being told that quality is the differentiator. The duel format forced two leaders to stop reconciling those demands and defend one of them properly.
The tension is real and partly manufactured
Both debaters agreed on something the format tried to prevent. The tension between scale and craft exists because organisations created it, through deadlines, measurement systems and briefs that arrive incomplete. Noel put it plainly. The tension is only there because we made the tension. That does not dissolve the disagreement, it relocates it. The question is not whether to choose, it is who benefits from the way the choice is currently framed.
What is easy to measure wins by default
David identified the structural asymmetry underneath everything else. Scale is trivially quantifiable, so it can be taken into a conversation with executives and pointed directly at revenue. Craft resists that translation. It therefore loses arguments it should win, not because it is worth less but because it arrives without a number attached. Any practitioner who has watched a quality argument fail in a planning meeting has watched this asymmetry operate.
The case for scale, argued by Noel Childs
Noel refused the premise before defending it. His claim is that the profession has scale wrong, that it hears speed and volume when it should hear reach and system. Craft cannot scale by itself and never will, but craft can be amplified through scale, which reverses the usual relationship between the two. Craft should be a given, held to the highest standard possible, and then removed from the centre of the conversation, because the design community talks about almost nothing else. His evidence was a design system built for Goodyear four or five years ago that now powers hundreds of sites and digital experiences, made possible by flexibility and diverse users designed in from the beginning, and sustained by constant work rather than by being finished.
What scale actually requires
The strongest part of Noel's argument was operational. Designers need help, and the profession has never built the apparatus that lets talented people concentrate on the work. He pointed to design operations, a discipline he believes arrived, receded and is now barely discussed, and asked the room to look at it again. Film production, architecture, gaming and professional sport all treat that operational function as equal in importance to the craft itself. Design improvises, rewrites briefs that arrived wrong, and figures things out in flight. He also called for the era of moving fast and breaking things to end, arguing that failures blamed on scale are usually failures of effort or of who was invited into the room.
The case for craft, argued by David Kazaryan
David's argument was about attachment rather than polish. Customers do not care about your organisational structure, your technology stack or how quickly you ship. They care about using something they feel connected to, and that connection is produced by tone, voice and finish. Craft is therefore the mechanism, not the decoration. His evidence was a project he declined to name, where deadline pressure led a team to prioritise componentry that would optimise testing. When multivariate testing ran across customer segments, the expected lift never appeared. The failure was not the design system. It was that nobody had taken the time to ask customers the questions that would have revealed the testing strategy was the real priority.
What a leader owes the team
Asked how he protects craft while his organisation infuses AI workflows everywhere, David's answer was about authority rather than method. Give your team explicit permission to ask difficult questions in meetings, to say a brief is not clear enough, and to challenge the status quo in service of a better experience. Designers are a line of defence between quality and business output and cannot hold that line without being told they are allowed to. He was candid that this comes down to repeated difficult conversations rather than any framework.
Where they converged, and what it revealed
On generative design tools the two positions nearly met. David observed that these tools were not built for designers but for people who need to launch something quickly, which explains why so much output shares a format. Noel called them a prototyping instrument worth learning rather than fearing, and named curation as the future proofing skill, because a tool can produce a design and someone still has to decide what it means. Both agreed research does not get replaced, though David drew a line, saying reliance on synthesis alone does not qualify someone as a human centred designer.
What the room decided
The audience vote produced a tie, and the moderator declined to break it. That result is more interesting than a verdict would have been. A room of practitioners, asked to pick between the argument that scale is misdefined and the argument that quality is the mechanism of connection, split evenly. Both propositions were recognised as true by the same people, which suggests the profession holds them simultaneously and has simply never been asked to say so out loud.
Questions this leaves open
If craft is a given, who in your organisation is actually enforcing it, and what happens to it the first time a deadline moves. If design operations is genuinely the missing half of the profession, why did it recede, and is anyone in this room positioned to build the company that supplies it. When your quality argument last failed in a planning meeting, did it fail because it was wrong or because it arrived without a number. And if generative tools have taken speed and options off your plate, as Noel argued, what precisely are you doing with the capacity that returned to you.
The question underneath both positions
Noel closed on something larger than the debate, saying he wants the design industry to succeed and exceed, and that more practitioners should aim at the world's problems, which requires scale, the right rooms and some bravery. David closed on fundamentals, on asking the right questions and getting clarity about the problem being solved. Together they describe one instruction. Get clear about the problem, then build something large enough to matter.
