Stop reporting UX activity and report business outcomesUX teams should tie their reporting to revenue, cost, risk, and retention — not just activity counts.
- The shift: Move from 'we ran 12 usability tests' to 'we cut support costs by X%.'
- Why it matters: Outcome framing is what actually secures budget, headcount, and exec buy-in for design orgs.
- Practical step: Map every UX initiative to a specific business metric before presenting it upward.
For design
Audit your team's next quarterly report — if it's full of activity counts rather than dollar or risk impact, fix that before your next budget conversation.
Most AI work can waitMost AI workloads run fine on cheap local models — routing matters more than model choice.
- Key insight: Smart routing logic saves cost without sacrificing quality for the majority of AI tasks.
- Why it matters: Teams fixating on 'which frontier model to use' may be optimizing the wrong lever entirely.
- Practical takeaway: Ask your AI vendor about routing architecture — cheap models for simple tasks, escalation only when needed.
98% isn't very muchA 98% browser-support figure still quietly excludes millions of real users.
- The math: At internet scale, even a 'high' support percentage translates into millions of excluded people.
- Why it matters: A reminder that aggregate metrics can mask real accessibility and inclusion gaps.
- For design teams: Worth re-checking what your own 'good enough' coverage numbers actually mean for underserved segments.