Five eras of UX design and the lessons to keep in the AI eraUX design has reinvented itself every decade since Bell Labs — AI is just the next cycle, not an ending.
- The thesis: Human factors research has weathered multiple paradigm shifts before, and the same foundational lessons still apply.
- Why it matters: It's a useful counter to AI-era doom framing — reframes the moment as a familiar pattern rather than an existential break for the discipline.
- Practical takeaway: Looking at how UX adapted through past tech transitions (mainframes, GUI, mobile, web) offers concrete playbooks for now.
The most important product decision is what you don't buildTeams love listing what they shipped — the harder, more telling question is what they deliberately killed.
- The insight: Ask a team what they shipped this year and you'll get a confident list; ask what they killed and the room goes quiet.
- Why it matters: Saying no is harder to measure than shipping velocity, but it's often the higher-leverage decision.
- For DesignOps: This argues for tracking 'kills' as a formal metric alongside roadmap output, not just an informal war story.
For product
Consider adding a 'features not built' section to quarterly reviews — it surfaces prioritization discipline that ship-count metrics hide entirely.
Seats and sunsetsA sharp look at the brutal unit economics behind AI agent products — token burn, thresholds, and failure modes.
- The topic: Explains why agent-based products have fundamentally different cost and capability curves than traditional per-seat SaaS.
- Key concept: Capability thresholds mean small model improvements can suddenly unlock — or break — an entire workflow overnight.
- Why it matters: Teams building agentic features need to understand these economics before committing pricing or roadmap decisions to them.
For product
Before greenlighting an agent-based feature, model out the token-cost curve at scale — pricing that works in a demo can quietly become unviable once usage crosses a capability threshold.