dragoon0x/everything-design-taste

design-org-structure

Scaling design teams, reporting structures, hiring strategies, design culture, and operating models for design organizations.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill design-org-structure

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,947 B
  • docs SUMMARY.md 153 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Design Org Structure

Team Models

Centralized

All designers report to a design lead. They're assigned to product teams but their career and craft development lives in the design org.

Pros: Consistent quality, strong design culture, clear career paths Cons: Potential disconnect from product teams, resource allocation friction Best for: Companies where design consistency matters more than speed

Embedded

Each designer reports directly to a product team lead. No central design org.

Pros: Fast, tight product alignment, designers have full context Cons: Quality drift, isolation, no design mentorship, career path unclear Best for: Early-stage startups where speed is everything

Hybrid (most common at scale)

Designers are embedded in product teams but have a dotted line to a central design leader. Regular design org rituals (critique, design system work) keep quality aligned.

Pros: Speed of embedded + quality of centralized Cons: Complex management, potential conflicting priorities Best for: Growth-stage companies (50-500 employees)

Designer-to-Engineer Ratio

Benchmarks

  • Early startup: 1 designer per 8-10 engineers
  • Growth stage: 1 designer per 5-7 engineers
  • Mature product: 1 designer per 3-5 engineers
  • Design-led products: 1 designer per 2-3 engineers

When to Hire

  • Designers are consistently the bottleneck
  • Quality is dropping because designers are spread too thin
  • You're entering a new market/product area
  • Design debt is accumulating faster than you can address it

Roles and Levels

IC Track

  1. Junior Designer — Executes defined tasks, learning the craft
  2. Designer — Owns features end-to-end, works independently
  3. Senior Designer — Drives strategy for product areas, mentors juniors
  4. Staff Designer — Cross-product impact, defines systems and standards
  5. Principal Designer — Company-wide influence, sets design direction

Management Track

  1. Design Lead — Player-coach, manages 3-5 designers
  2. Design Manager — Full-time people management, 5-8 reports
  3. Director of Design — Org strategy, cross-functional leadership
  4. VP of Design — Executive team, company strategy, org building
  5. CDO/Head of Design — Board-level, brand and product vision

Design Culture Essentials

  • Weekly design critique (skill-based, not approval-based)
  • Shared design system with active governance
  • Design principles documented and referenced in decisions
  • Regular user research exposure for all designers
  • Portfolio reviews for career development
  • Design all-hands with show-and-tell