Component Classification Decision Framework

How Intuit's simple three-question framework revolutionized their component vs pattern decision-making process.

Event Context

Session: Craft Across: Documentation in Design Systems
Date: August 7, 2025
Key Contributor: Kristen Singh (Intuit)

This framework emerged from Intuit's struggle with component classification debates that were slowing down their design system contribution process.

Core Insight

"I built a decision flowchart that eliminated 80% of classification questions" - Kristen Singh

A simple three-question framework can eliminate subjective debates about whether something qualifies as a component, pattern, or experimental element.

The Decision Framework

Three questions that cut through classification debates:

1. Is it reusable?

Question: Can this be used in multiple contexts across different products or features?

2. Does it solve user problems?

Question: Does this address real user needs rather than just aesthetic preferences?

3. Experimental or ready?

Question: Is this proven in production or still being validated?

Real Impact at Intuit

Before the framework:

Teams spent hours in meetings debating component classification
Inconsistent decisions across different contributors
Bottlenecks in the contribution process
Subjective arguments based on personal preferences

After implementation:

80% reduction in classification questions
Faster decision-making process
Self-service capability for contributors
Consistent standards across teams

Why This Framework Works

✓ Eliminates subjective debates - Clear criteria removes personal opinions from decisions
✓ Scales across teams - Same framework works for all contributors regardless of experience
✓ Speeds up decision-making - No more endless meetings about classification
✓ Enables self-service - Teams can classify without constant design system team approval

Key Speaker Insight

Kristen Singh (Intuit): "I built a decision flowchart that helped our team determine if something is a component, pattern, experimental, or ready for production. It eliminated 80% of the questions we were getting."

When to Apply This Framework

Teams struggling with component vs pattern classification
Design system teams receiving frequent classification questions
Organizations with multiple contributors creating system elements
Large teams where classification decisions are slowing down work
Teams wanting to enable self-service contribution workflows

Framework in Action

Example: Search suggestions dropdown

❓ Is it reusable? → YES (used in search, filters, navigation)
❓ Does it solve user problems? → YES (helps users find content faster)
❓ Experimental or ready? → READY (proven in multiple products)

🎯 RESULT: COMPONENT

Alternative Approaches

Centralized Approval Process

Provides quality control and consistency
Creates bottlenecks and slows down contribution velocity

Subjective Judgment Calls

Fast decision-making in the moment
Inconsistent results across different team members and time periods

No Classification Guidelines

Maximum flexibility for contributors
Maximum confusion and inconsistent system architecture

Implementation Tips

Document the framework clearly - Make the questions and criteria easily accessible
Train contributors - Ensure everyone understands how to apply the framework
Provide examples - Show the framework applied to real scenarios
Iterate based on feedback - Refine questions if edge cases emerge

Component Tagging Strategies - Methods for organizing and tracking components in production
Props vs. Slots - Technical decisions about component flexibility and architecture

Takeaway: Clear decision frameworks aren't about restricting creativity—they're about enabling teams to move faster with confidence by removing subjective debates from the contribution process.

Source: Craft Across: Documentation in Design Systems • August 7, 2025