Over the past few years we have published sixty-four long conversations with people who run design and product organisations. Apple, Google, Amazon, Microsoft, PlayStation, Bloomberg, IKEA, Jaguar Land Rover, Mercari, PayPay. Different industries, different continents, no shared script.
We went back and read all of them in one sitting. Not for quotes. For what the questions had quietly stopped being about.
The craft questions went first
The early conversations are full of craft. How to run research inside an organisation that does not want it. How to build a design system that survives its second year. How to move from interface work into industrial design and back. Concrete problems with concrete answers, the kind a senior individual contributor takes back to their team on Monday.
Those questions have not disappeared, but they have moved down the agenda. When we ask the same people today what is hard, almost nobody says the work itself. They say the deciding.
What replaced them
Three themes come up again and again, and they are all organisational rather than technical.
Who decides, and how fast. Teams can now produce more options than they can evaluate. The bottleneck moved from making to choosing. Several of our speakers describe the same symptom from different angles: a team that ships weekly but cannot say which of the last ten decisions mattered. The craft is no longer the constraint. The judgement is.
Where design sits when the work is distributed. A striking number of conversations are about growing design inside organisations rather than designing anything in particular β intrapreneurship, enterprise capability, scaling teams, the awkward middle years when a function stops being a service desk and starts being accountable for outcomes. The question is not whether design has a seat. It is what the seat obliges you to be responsible for.
Consequences nobody asked you to own. Sustainable service design, speculative futures, behaviour outcomes, design and biology, inclusive research. These were edge topics five years ago. They now sit in the middle of the programme, because the people doing the work discovered that a shipped product has effects they are the only ones positioned to see early.
The uncomfortable part
There is a version of this story that flatters designers: the craft got automated, so we all became strategists. That is not what the conversations say.
What they say is harder. The people who moved up did not do it by abandoning the craft. They did it by keeping enough of it to know when an answer is wrong. Every leader we spoke to who sounded credible on strategy could still tell you, specifically, why a particular flow failed. The ones who had let go of the detail entirely were the ones describing their own teams in abstractions.
Judgement is not the opposite of craft. It is what craft turns into when you have done it long enough to recognise the shape of a mistake before it is finished.
Why this matters for the next two years
If the scarce resource is judgement rather than output, then the things that develop judgement become the investments worth making. Not more tooling. More exposure to decisions that went badly and the reasoning behind them.
That is an uncomfortable conclusion for an industry that has spent a decade optimising for throughput. It is also why our conversations keep returning to the same format: not a talk about a success, but a room where someone walks through the decision they would make differently.
It is the reason the programme at every DDX edition is built around rooms small enough to argue in, and why the interviews keep running between the editions. Sixty-four is not a large sample. But it is sixty-four more than most people have read in a row, and the pattern in them is consistent enough to plan against.
What we are watching next
Three questions we do not have good answers to yet, and intend to keep asking:
Does design leadership survive contact with teams where most production is automated, or does it dissolve into product management? The conversations split roughly evenly, which usually means the question is badly framed.
What does a design organisation owe a user it will never meet, in a market it does not operate in? The sustainability and inclusion conversations circle this without landing.
And the one nobody enjoys: how do you develop judgement in people who have never had to make an expensive mistake, when the tooling now prevents most cheap ones?
We will keep publishing what we find. If you work on any of these, the conversations are open.
