Compose a design onboarding bootcamp covering history, rituals, component philosophy,…
- User
Compose a design onboarding bootcamp covering history, rituals, component philosophy, and tooling walkthroughs.
Assistant
The question/task: Compose a design onboarding bootcamp covering history, rituals, component philosophy, and tooling walkthroughs.
My reasoning: Design Onboarding Bootcamp
Thinking & Reasoning
This bootcamp is structured to progressively build context and capability for new designers joining a team. The sequence moves from foundational knowledge (history and context) to practical workflows (rituals), then to craft philosophy (components), and finally to hands-on tooling. competitors
- Signature visual/interaction patterns
- Market differentiation through design
Deliverable: Reflective essay on how past decisions shape current constraints
Module 2: Rituals & Collaboration (Days 3-4) Objective: Integrate designers into team cadence
2.1 Ceremonies Overview
| Ritual | Frequency | Purpose | Designer Role | Design Crit | Weekly | Feedback on in-progress work | Present or give feedback | | Sprint Planning | Bi-weekly | Scope upcoming work | Estimate design effort | | Design Sync | Weekly | Cross-team alignment | Share updates, flag blockers | | Portfolio Review | Quarterly | Career growth | Present impact |
2.2 Handoff Rituals
- Design-to-engineering spec template
- QA review protocol
- Post-launch retrospective participation
2.3 Stakeholder Engagement
- Request intake process
- Presentation norms (audience-specific)
- Documentation expectations
Deliverable: Shadow a crit and submit one piece of constructive feedback
Module 3: Component Philosophy (Days 5-7) Objective: Internalize systematic design thinking
3.1 Core Principles
- Composition over inheritance: Build from primitives
- Deterministic behavior: Same input = same output
- Progressive enhancement: Works at base, delights at peak
- Accessibility-first: No retrofits
3.2 Component Taxonomy
├── Tokens (foundational variables) │ ├── Color │ ├── Spacing │ ├── Typography │ └── Motion ├── Primitives (atomic elements) │ ├── Buttons │ ├── Inputs │ ├── Icons │ └── Typography components ├── Composites (molecules) │ ├── Form fields │ ├── Cards │ └── Navigation items └── Patterns (organisms) ├── Headers ├── Forms └── Data tables3.3 Contribution Model
- When to extend vs. when to create new
- Naming conventions and documentation standards
- PR review process for component additions
3.4 Anti-patterns Gallery
- Inconsistent padding examples
- Color misuse cases
- Accessibility failures
Deliverable: Build a simple UI using only existing components; document gaps
Module 4: Tooling Walkthroughs (Days 8-10) Objective: Achieve operational fluency
4.1 Design Tools
Figma
- Team library structure and publishing
- Variants and component properties
- Auto-layout deep dive
- Dev Mode handoff
- Branching for exploratory work
4.2 Collaboration Tools
| Tool | Use Case | Onboarding Task | Notion | Documentation, specs | Create a spec page | | Lottie/Motion | Animation handoff | Export a simple animation | | Storybook | Component documentation | Navigate to 3 components |
4.3 Development Adjacent Tools
- Git basics for designers (viewing branches, reading diffs)
- Browser DevTools for design QA
- Accessibility audit tools (Axe, WAVE)
4.4 Internal Tools
- Design token pipeline (how changes propagate)
- Icon submission workflow
- Illustration request process
Deliverable: Complete a mock feature handoff using proper tooling
Capstone Project (Days 11-14) Objective: Synthesize all learning
Brief: Design a small feature end-to-end
- Research existing patterns
- Use component library appropriately
- Document decisions with historical context
- Present in design crit format
- Hand off to "engineering" (facilitator)
Evaluation Criteria:
- Appropriate component usage
- Clear rationale rooted in system philosophy
- Proper ritual participation
- Clean handoff documentation
Verification Checkpoint
The bootcamp is successful if the new designer can:
- Complete a handoff that meets team standards
Feedback Loop: 30-day check-in to assess gaps and iterate on bootcamp content.
Design Onboarding Bootcamp
Thinking & Reasoning
This bootcamp is structured to progressively build context and capability for new designers joining a team. The sequence moves from foundational knowledge (history and context) to practical workflows (rituals), then to craft philosophy (components), and finally to hands-on tooling. This mirrors how humans learn: understand why before how, build mental models before skills, and apply skills with supervision before independence.
Final Bootcamp Design
Module 1: History & Context (Days 1-2)
Objective: Ground new designers in organizational DNA
1.1 Company Design Legacy
- Founding story and original design vision
- Key inflection points in brand evolution
- Major product redesigns and lessons learned
- Archive walkthrough: past campaigns, discarded directions, pivots
1.2 Design System Origin Story
- Why the system was created (problems it solved)
- Original architects and maintainers
- Version history and breaking changes
- Current state vs. future roadmap
1.3 Competitive Landscape
- Design positioning vs. competitors
- Signature visual/interaction patterns
- Market differentiation through design
Deliverable: Reflective essay on how past decisions shape current constraints
Module 2: Rituals & Collaboration (Days 3-4)
Objective: Integrate designers into team cadence
2.1 Ceremonies Overview
Ritual Frequency Purpose Designer Role Design Crit Weekly Feedback on in-progress work Present or give feedback Sprint Planning Bi-weekly Scope upcoming work Estimate design effort Design Sync Weekly Cross-team alignment Share updates, flag blockers Portfolio Review Quarterly Career growth Present impact 2.2 Handoff Rituals
- Design-to-engineering spec template
- QA review protocol
- Post-launch retrospective participation
2.3 Stakeholder Engagement
- Request intake process
- Presentation norms (audience-specific)
- Documentation expectations
Deliverable: Shadow a crit and submit one piece of constructive feedback
Module 3: Component Philosophy (Days 5-7)
Objective: Internalize systematic design thinking
3.1 Core Principles
- Composition over inheritance: Build from primitives
- Deterministic behavior: Same input = same output
- Progressive enhancement: Works at base, delights at peak
- Accessibility-first: No retrofits
3.2 Component Taxonomy
├── Tokens (foundational variables) │ ├── Color │ ├── Spacing │ ├── Typography │ └── Motion ├── Primitives (atomic elements) │ ├── Buttons │ ├── Inputs │ ├── Icons │ └── Typography components ├── Composites (molecules) │ ├── Form fields │ ├── Cards │ └── Navigation items └── Patterns (organisms) ├── Headers ├── Forms └── Data tables3.3 Contribution Model
- When to extend vs. when to create new
- Naming conventions and documentation standards
- PR review process for component additions
3.4 Anti-patterns Gallery
- Inconsistent padding examples
- Color misuse cases
- Accessibility failures
Deliverable: Build a simple UI using only existing components; document gaps
Module 4: Tooling Walkthroughs (Days 8-10)
Objective: Achieve operational fluency
4.1 Design Tools
Figma
- Team library structure and publishing
- Variants and component properties
- Auto-layout deep dive
- Dev Mode handoff
- Branching for exploratory work
4.2 Collaboration Tools
Tool Use Case Onboarding Task Notion Documentation, specs Create a spec page Lottie/Motion Animation handoff Export a simple animation Storybook Component documentation Navigate to 3 components 4.3 Development Adjacent Tools
- Git basics for designers (viewing branches, reading diffs)
- Browser DevTools for design QA
- Accessibility audit tools (Axe, WAVE)
4.4 Internal Tools
- Design token pipeline (how changes propagate)
- Icon submission workflow
- Illustration request process
Deliverable: Complete a mock feature handoff using proper tooling
Capstone Project (Days 11-14)
Objective: Synthesize all learning
Brief: Design a small feature end-to-end
- Research existing patterns
- Use component library appropriately
- Document decisions with historical context
- Present in design crit format
- Hand off to "engineering" (facilitator)
Evaluation Criteria:
- Appropriate component usage
- Clear rationale rooted in system philosophy
- Proper ritual participation
- Clean handoff documentation
Verification Checkpoint
The bootcamp is successful if the new designer can:
- Explain why the design system exists and evolved
- Participate autonomously in team rituals
- Make component decisions aligned with system philosophy
- Navigate all tooling without assistance
- Complete a handoff that meets team standards
Feedback Loop: 30-day check-in to assess gaps and iterate on bootcamp content.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.