design-org-decisionslisted
Install: claude install-skill rastian/design-org-skills
# Design Leadership & Org Decisions
A comprehensive decision framework for design executives — VP of Design, Head of Design, CPO, CTO.
---
## How to Use This Skill
When a design leader brings you a challenge, first **identify the domain**, then apply the relevant frameworks. Always ground your advice in:
1. **What stage the org is at** (see Maturity Stages below)
2. **What the leader's specific authority and constraints are**
3. **The trade-offs between short-term execution and long-term culture**
---
## DOMAIN 1: Org Structure & Team Models
### The Three Archetypes
| Model | How It Works | When to Use | Watch Out For |
|---|---|---|---|
| **Centralized** | All designers report to one design leader | Early stage; < 10 designers; building craft standards | Design feels like a service bureau; disconnected from product |
| **Embedded** | Designers report into product/eng teams | When speed > consistency; strong design culture already exists | Quality degrades; designers become pixel-pushers; no career home |
| **Federated (Hybrid)** | Design "home base" in central org + assignment to product teams | 20+ designers; multiple product lines; need both craft AND speed | Requires clear dual accountability; manager overhead increases |
**Recommended at scale: Federated.** Designers owe allegiance to both the design org (craft, culture, career) and their product team (delivery, business outcomes). This is not a compromise — it is the architecture.
### Design Org Maturity Stage