What 32 design leaders do when told to move fasterA survey of design leaders on handling the perpetual 'move faster' mandate — and why the Greeks solved this problem first.
- The pattern: Most design leaders don't respond to speed pressure by cutting process — they respond by clarifying priorities and renegotiating scope.
- The classical framing: The piece draws on ancient Greek ideas about tempo and craft to argue that 'faster' and 'better' aren't opposites if you're honest about tradeoffs.
- Why it's useful: Practical, real-world tactics from peers facing the exact pressure DesignOps leaders deal with daily — especially as AI tooling raises expectations for velocity.
For design
Good source material for your own 'how do we go faster without breaking things' conversations with leadership — worth pulling specific tactics from this for your next planning cycle.
AX is just the orchestration layerUX Collective
DesignProduct
Agent experience (AX) doesn't eliminate design work — it just pushes it down a layer, into orchestration and system logic.
- The argument: As interfaces shift from screens to agents, the craft of design moves from visual composition to defining how agents coordinate, hand off, and fail gracefully.
- Why it matters: Teams treating 'AX' as a lightweight replacement for UX are missing that the complexity didn't disappear — it moved somewhere less visible.
- For DesignOps: This has real implications for how design teams are staffed and what skills matter — orchestration design is a different discipline than screen design.
For design
If your team is being asked to 'design for agents,' push back on treating it as a simplification — budget for the orchestration and failure-state work the same way you'd budget for a complex multi-step flow.
When design becomes the organisation, and AI becomes the designA provocative look at what happens when AI systems start shaping the organization that's supposed to be designing them.
- The loop: As AI tools increasingly define workflows, org structure, and decision-making, the line between 'designed system' and 'designer' blurs.
- Why it's relevant: This isn't abstract philosophy — it's already happening in how AI tools shape meeting cadences, review processes, and team structures.
- The risk: Organizations that adopt AI tools without examining how those tools reshape their own operating model may end up designed by default, not intention.
The people who will thrive in the AI ageWhat separates future high performers isn't raw intelligence — it's a healthy relationship with mental effort itself.
- The core idea: As AI removes friction from thinking, the people who deliberately keep doing hard cognitive work will pull ahead of those who default to AI shortcuts.
- Why it matters for teams: This has direct implications for how you develop junior talent — over-reliance on AI for early-career reps may quietly erode the skill-building that senior judgment depends on.
- Practical angle: Worth thinking about as a hiring and development signal, not just a personal productivity tip.
For design
Consider building 'effort checkpoints' into junior designers' workflows — moments where they must work a problem before reaching for AI assistance, so foundational judgment still develops.