Design owns coherenceAs AI fragments product experiences, design is best positioned to own cross-system coherence — if it claims it.
- The gap: Leadership now openly acknowledges a coherence problem — fragmented AI features, inconsistent experiences — but no function has formally claimed ownership.
- The opportunity: This is a rare moment where a C-suite-acknowledged problem is up for grabs, and design has the strongest natural claim to it.
- Why it matters: Coherence has always been design's implicit job; AI's rapid feature sprawl just made it an explicit, visible business problem.
- The risk: If design doesn't step up, another function — product ops, platform engineering — will define 'coherence' on its own terms, without design input.
For design
This is a genuine opening to pitch design systems and DesignOps as owners of AI-era coherence — bring fragmentation-cost data to your next leadership conversation before someone else frames the problem first.
The AI experience doesn't care about your org chartUX Collective
DesignProduct
Users feel every internal team silo when AI features don't line up into one coherent experience.
- The friction: When different teams own different AI features or agents, users feel the seams — inconsistent tone, logic, and handoffs.
- Why it matters: AI's conversational, continuous nature makes org-chart seams far more visible than they ever were in traditional multi-screen products.
- DesignOps angle: This is a structural argument for cross-functional governance of AI experiences, not just more design reviews.
- Bottom line: The fix isn't better documentation — it's rethinking how teams coordinate when the 'product' is one ongoing conversation.
For design
Audit whether your current design review process actually catches cross-agent, cross-team inconsistency, or just reviews features in isolation — AI exposes that gap fast.
Pure UI in the Agentic EraAgentic AI is forcing a rethink of UI as a snapshot of state, not just a response to user clicks.
- The shift: Moving from 'UI reacts to events' to 'UI reflects state at a point in time' — driven by agents that can change things without a user click.
- Why it matters: If agents act independently of user input, interfaces need new mental models beyond click-triggered updates.
- For design systems: Components built around user-triggered events may not gracefully handle agent-triggered changes — a real design and tech debt risk.
- Bottom line: Early-stage thinking, but worth tracking as more products let AI agents act autonomously inside existing interfaces.
Nobody feels heard by a reportUX Collective
DesignProduct
The rise of forward-deployed engineers shows customer insight often stalls before reaching the people who need it.
- The pattern: Companies increasingly embed engineers directly with customers to solve problems fast, bypassing the traditional research-to-report pipeline.
- Why it matters: If forward-deployed engineers are trusted more than research reports, that's a real signal about how customer insight actually moves — or doesn't — inside orgs.
- DesignOps angle: Raises hard questions about whether research and insights teams are structured to influence decisions, or just to produce documentation nobody reads.
- Bottom line: The fix might not be 'better reports' — it might be embedding researchers the way forward-deployed engineers are embedded.
For design
If your research org still measures success by reports shipped rather than decisions changed, this is a good prompt to rethink the embedding model — proximity to the work seems to beat documentation polish.
The "disability dongle": Why Silicon Valley hates me and youA sharp critique of flashy, expensive assistive tech built without real input from disabled users.
- The term: 'Disability dongle' describes well-intentioned but poorly-informed assistive tech designed without meaningful input from disabled users themselves.
- Why it matters: It's a pointed inclusive-design lesson that applies well beyond disability tech — design-by-assumption produces expensive, unused solutions.
- For design teams: A reminder that accessibility requires including real users in the design process, not just user-testing a finished prototype on them.
For design
A useful gut-check for any 'innovative' accessibility initiative in your pipeline — ask whether disabled users were in the room designing it, not just validating it afterward.