Every fork looks like adoptionDesign system 'adoption' metrics are often misleading — forks and copies inflate numbers without real usage.
- The problem: Common ways of measuring design system adoption, like counting forks, keep trending up even when real usage doesn't reflect it.
- Why it matters: DesignOps teams reporting adoption metrics to leadership may be overstating impact without realizing it.
- What to check: Distinguish 'someone copied our components once' from 'teams are actively maintaining and updating with our system.'
- Bottom line: Adoption should be measured by sustained integration, not surface metrics that always go up regardless of health.
For design
If your team reports design system adoption via repo or fork counts, this is worth a gut-check before your next leadership review — you may be reporting vanity metrics.
Is AgenticA new tool scores how ready your website is for AI agents to browse and act on.
- What it does: Evaluates how well AI agents can parse, navigate, and act on a site, then provides recommendations to improve it.
- Why it matters: As agentic browsing grows, sites optimized only for human eyes risk becoming invisible or unusable to AI agents.
- The next SEO: This is shaping up as a new discipline — designing for machine visitors, not just human ones.
- What's missing: Standards here are still nascent, so today's score is more diagnostic than authoritative.
For product
Worth running your core flows through a tool like this — agent-readability could become a real acquisition channel as more users delegate browsing and shopping to AI agents.
Vibe coding and qualityA year after being dismissed as a toy, vibe coding is now argued to be the path to genuinely high-quality software.
- The shift: What was mocked as 'vibe coding' last year is now claimed to be the only route to genuinely high production quality.
- Why now: Better models and tooling have closed the gap between fast prototyping and shippable, maintainable code.
- Implication for teams: Design/engineering norms built around 'AI-generated code needs heavy rework' may already be outdated.
- Caveat: This is one strong opinion — worth testing against your own team's actual output before changing workflows.
What luxury bags can teach designers about how to adapt to a changing dealDesign's value is shifting away from screens — luxury brands show designers how to adapt.
- The argument: As AI generates competent screens for free, differentiation moves to craft, story, and brand — the same levers luxury goods pull.
- Why it matters: Design isn't becoming irrelevant, but what designers are valued for is changing — polishing interfaces alone won't cut it.
- Lesson from luxury: Luxury brands sell meaning and scarcity, not just flawless execution — a useful model for rethinking design's value proposition.
- Bottom line: Designers who tie their worth purely to interface craft should start building adjacent skills — strategy, narrative, brand.
For design
Use this as a prompt for a team conversation: if AI can generate most routine screen work, what's the remaining slice — craft, judgment, narrative — your team should double down on?