Why the best resume may be the wrong resume for a design teamDesign leadership often hires for polished portfolios instead of the specific expertise a team actually needs.
- The critique: Hiring managers default to the 'best' portfolio rather than asking what gap or diversity of thinking the team actually needs.
- The risk: Optimizing for pedigree creates homogenous teams that struggle with genuinely novel problems.
- Practical fix: Define the specific expertise gap before opening a req, instead of benchmarking candidates against an abstract 'great designer' ideal.
Designers lost their unit of measurement. That's why we're struggling.As screens stop being the default canvas, designers are losing the basic unit they use to think and communicate.
- The problem: Pixels and screens gave design a shared unit of measurement; voice, agents, and ambient interfaces don't have an equivalent yet.
- Why it matters: Without a stable unit, critique, handoff, and specs all get harder — teams lose a common language for 'done.'
- Open question: The piece names the gap clearly but doesn't fully answer what replaces the screen — flows, outcomes, tokens?
For design
Worth a team discussion now: as more of your product surface goes agentic or voice-based, what's your team's replacement for 'screens' as the unit design reviews are organized around?
The variance problem in AI productsUX Collective
DesignProduct
AI products behave differently every time, which breaks the consistency assumptions traditional UX design relies on.
- The core issue: Deterministic software gives the same output for the same input; generative AI products don't, undermining standard usability testing and QA.
- Why it matters: Design systems and heuristics built for consistency don't map cleanly onto probabilistic outputs.
- What's needed: Teams need new methods for testing and communicating acceptable ranges of variance, not just 'correct' vs. 'broken.'
For product
If your QA and design review processes still assume deterministic behavior, they'll keep flagging 'bugs' that are actually just model variance — separate the two categories explicitly in your process.
The 3 roles of context for AI agentsPower users of AI agents manage three distinct context types — global, local, and ambient — to get good results.
- The framework: Global context persists across tasks, local context is task-specific, and ambient context is raw streams like email or Slack.
- Why it matters: Most agent tools conflate these layers, leading to context bloat or missing the right information at the right moment.
- Design implication: Interfaces that let users explicitly manage which context layer an agent draws from will beat ones that dump everything into one bucket.