The UX Double Diamond is dead, and in AI only one survives for softwareUX Collective
DesignProduct
The classic double-diamond design process no longer fits AI-compressed software development.
- The claim: Traditional discover-define-develop-deliver framing collapses when AI can generate and iterate designs almost instantly.
- What survives: Only one 'diamond' — the problem-framing phase — remains genuinely relevant in AI-era software design.
- Why it matters: Design process frameworks built for slower, human-only iteration need rethinking now that AI compresses execution time to near-zero.
- Bottom line: Design leaders should question which parts of their process are ceremony versus genuinely useful thinking.
For design
Worth an internal audit of which double-diamond rituals your team still runs out of habit versus actual necessity, now that AI collapses the 'develop' phase.
The death of the deliverableAI didn't kill the wireframe — it revealed deliverables were always just a proxy for design thinking.
- The argument: Wireframes, comps, and specs were always stand-ins for decisions, not the actual value designers create.
- AI's effect: When AI can produce polished deliverables instantly, it exposes that the artifact was never the real point — the judgment behind it was.
- Why it matters: Design teams need to redefine what they're actually measured and paid for if not the deliverable itself.
- Bottom line: This reframes designer value around decision-making and taste rather than production speed.
For design
If your team's velocity metrics are still tied to deliverable output, this is a good prompt to shift them toward decision quality and outcomes instead.
Planning with agentsCollaborative planning with AI agents needs richer interfaces than today's chat-based tools provide.
- The problem: Current agent interfaces are too thin to support real collaborative planning between humans and AI.
- The proposal: We need 'thicker' interfaces and better shared reference points (boundary objects) for humans and agents to plan together.
- Why it matters: As agentic workflows spread, interface design — not just model capability — becomes the real bottleneck for useful collaboration.
- Design opportunity: This is a wide-open space for design teams to define new interaction patterns beyond chat.
For design
Start prototyping richer agent-planning interfaces now rather than waiting for chat UI to harden into the default pattern by default.