Five eras of UX design and the lessons to keep in the AI eraA look back at UX's past disruptions offers grounded lessons for navigating the current AI shift.
- The framing: Traces UX design's evolution through distinct eras to extract patterns for how the field adapts to major disruption.
- Why it matters now: Useful historical grounding for design leaders anxious about AI's impact — this isn't the discipline's first existential threat.
- Takeaway: Past eras suggest the field survives by redefining its value proposition, not by resisting the new tools outright.
AI is making us build too muchAI made code, docs, and policy nearly free to produce — but not free to own or maintain.
- The core argument: Generation is now cheap; the real bottleneck has shifted entirely to ownership, maintenance, and organizational judgment about what's worth keeping.
- Why it matters: Teams flooded with AI-generated specs, tests, and docs risk drowning in low-quality volume that someone still has to review and be accountable for.
- For DesignOps: Directly relevant to design systems and documentation sprawl — more output isn't more value if nobody owns pruning it.
For design
Before rolling out more AI generation into your design system or documentation workflows, make sure someone is explicitly assigned to review and prune the output — that's the actual bottleneck now, not creation speed.
How authentication friction frustrates users — and how to stop itUX Collective
DesignProduct
A breakdown of what's actually broken in login flows and how to fix it without sacrificing security.
- The problem: Common auth patterns — forced re-verification, clunky MFA, password resets — frustrate users far more than the security gain justifies.
- The fix: Lays out concrete patterns like smarter defaults, passkeys, and progressive trust to cut friction without weakening protection.
- Why it matters: Authentication is one of the few UX touchpoints nearly every product shares, yet it's rarely prioritized for redesign.