Maggie Appleton argues that as the capability gap between what agents can do and what designers know how to shape closes, design itself becomes the binding constraint — not model capability or engineering. The piece surfaces a set of recurring orchestration patterns she's observed across agentic products, naming the structural moves that show up again and again: delegation with scoped context, planning steps surfaced for review, and the handoff of finished or blocked work back to humans with enough legibility to act on.
Appleton also takes on vibecoding at scale — the informal, prompt-driven way many teams are now building agent workflows — and asks what happens when that approach meets real production complexity. Her concern is that without deliberate design of the human-agent interaction layer, teams end up with capable but opaque systems that users can't inspect, correct, or trust. The orchestration layer isn't just an engineering problem; it's a design surface that currently has almost no established vocabulary or tooling.
For UX leadership, the provocation is direct: the patterns that make agentic systems legible — who is doing what, what is about to happen, what just changed — are design decisions that are being made by default right now, not by intention. Appleton's pattern framing offers a way to start naming and debating those decisions before they calcify into the wrong defaults.