In a LinkedIn post, Gess Puglielli argues that the recent wave of “prompt in, UI out” tools is not primarily a story about AI replacing designers, but about companies revealing what they thought Design was all along: interface production. If a 12‑second mockup feels like a substitute for a design team, the uncomfortable question is not what AI can do, but what organisations have been asking designers to do.
The core claim is simple: interfaces are artefacts, not the value. Puglielli frames Design as a deeper practice that shapes behaviour, systems, and meaning—drawing examples from Apple’s focus on making technology feel understandable and human, to automotive and architectural history where breakthroughs came from rethinking mobility and inhabiting space rather than “making it look nice.” Good Design often becomes invisible because it removes friction so effectively that people only notice it when it fails: the confusing airport, the dangerous junction, the door that invites the wrong action.
From that perspective, generative AI is best understood as an accelerant for production work: variations, rapid prototyping, visual systems, repetitive tasks. That is real power, and it will compress timelines and change job descriptions. But it also sharpens a boundary that many organisations have blurred for years. If product defines requirements, leadership defines strategy, engineering defines constraints, and Design is invited in at the end to “make it look good,” then the designer has already been pushed out of designing. Replacing that late-stage decoration with a model is not a triumph of automation; it is a diagnosis of a broken design function.
The more interesting implication is economic and organisational: as execution becomes abundant, polish stops being differentiation. Intent, clarity, originality, taste, and human understanding become the scarce resources. AI will likely raise the value of designers who can frame problems, surface latent needs, navigate politics and ethics, and translate between human lives and technical complexity—work that depends less on output volume and more on judgement and care. For design education and leadership, the task is not to defend “screens” as a craft, but to rebuild the conditions under which designers can actually shape decisions early enough to matter.
If this shift feels threatening, it is also an opportunity to stop treating Design as a service layer and start treating it as a capability: a way organisations learn, choose, and take responsibility. The companies that win will not be the ones generating generic interfaces faster; they will be the ones using abundant execution to explore more options, then making better calls about which futures are worth building.