Rethinking design leadership with swarms and flocksA fresh take on design leadership borrowing coordination patterns from swarms instead of rigid hierarchies.
- Core idea: Applies biological swarm/flock coordination as a metaphor for how design teams could organize and make decisions collectively.
- Why it matters for DesignOps: Challenges the standard top-down design leadership model as teams flatten and increasingly work alongside AI agents doing execution.
- Bottom line: Worth a skim if you're rethinking team structure as more execution work shifts to AI and human leadership shifts toward orchestration.
You don't have a design systemA pointed argument that most 'design systems' are component libraries missing the logic that makes them systems.
- The claim: Many teams conflate a component library with an actual design system — the difference is documented implementation logic and decision rationale.
- Why it matters: Without that documentation, systems don't scale consistency as products and teams grow.
- The AI angle: As AI coding/design agents start reading design systems directly to generate UI, undocumented 'tribal knowledge' systems will break down fast.
For design
If you're prepping your design system for AI-agent consumption (Claude Code, Copilot, etc.), this documentation gap is exactly where things will break. Worth an audit now, before an agent starts 'reading' your system and getting it wrong.
Claude Code 101, for designersA plain-language primer decoding Claude Code jargon — models, tokens, agents, MCP — for designers.
- What it is: Breaks down what Claude Code actually does and demystifies vocabulary (agents, MCP, tokens) that's increasingly part of design conversations.
- Why it matters: Designers are getting pulled into AI-agent workflows without a shared vocabulary with engineering — this closes that gap.
- Bottom line: Good onboarding material if your design team is starting to touch code-generation tools directly.
AI is removing the middle class of software engineeringAI coding tools are collapsing the mid-tier of engineering, rewarding judgment over execution speed.
- The shift: As AI handles routine implementation, economic value is consolidating around senior architects who direct AI, hollowing out the mid-level execution roles.
- Why it matters: Mirrors what's already starting in design — execution-heavy roles get automated while judgment and strategy roles hold their value.
- For Ops leaders: Team structures and career ladders built around mid-level execution may need rethinking across both engineering and design orgs.
For design
This same 'hollowing of the middle' is likely coming for design teams — start thinking now about how junior design roles evolve when AI absorbs routine execution work.