Book a call

WritingBuilding a systemPart 3 of 4 in Components in depth

Component complexity: how to estimate design system work

A badge and a data table are both "one component", and planning them the same way guarantees missed dates. Four levels of complexity, an eight-question scoring method, and how to match the process to each level.

On this pageWhy "ten components this quarter" misleads
  1. Why "ten components this quarter" misleads
  2. Four levels of complexity
  3. Scoring complexity: eight questions
  4. Four components, scored
  5. Match the process to the level
  6. Plan by points, not by count
  7. Choose the simplest component that works
  8. The short version
  9. Frequently asked questions
  10. Further reading

The short answer

Not all components are equal: a badge takes days, a data table can take months. Sort components into four levels: elements (show something), controls (one clear interaction), composites (several parts that coordinate) and systems (data, logic and performance). For planning, score each one 0–3 on eight questions (options, states, interaction, keyboard and screen reader, data, screen sizes, composition, platforms) and add them up. Then match the process (people, research, testing, beta length) to the level, and plan by points rather than by component count.

  • 0–6 points is level 1, 7–12 level 2, 13–18 level 3, 19–24 level 4.
  • A date picker scores like a composite, not a select menu: dates are data, and the calendar grid has demanding keyboard behaviour.
  • Each extra platform adds roughly the same effort again.

Why "ten components this quarter" misleads

Plans that count components treat a divider and a data table as the same unit of work. They're not, and the result is predictable: the quarter's plan looks on track until the one complex component swallows two months. Leadership loses confidence, and the team gets blamed for a planning model that was wrong from the start.

Complexity also matters for process. Running a heavyweight process for a badge wastes everyone's time; running a lightweight one for a data table guarantees bugs in production.

Four levels of complexity

These loosely echo Brad Frost's idea of building from small parts to large ones, but they're organised by how hard something is to get right, not by how big it is.

1ElementsShow something. Little interaction, few states. Badge, avatar, divider, icon, tag, spinner.
2ControlsOne clear interaction. Full set of states; standard keyboard use. Button, text field, checkbox, radio, switch, link.
3CompositesSeveral parts that coordinate. Complex focus rules; open/close; selection. Select, menu, tabs, dialog, combobox, date picker.
4SystemsData and logic; performance matters. Data table, rich text editor, file uploader, charts, multi-step form, app frame.
Each level adds a new kind of difficulty: interaction at level 2, coordination between parts at level 3, and data, logic and performance at level 4. Practitioner view

Level 3 is where accessibility gets genuinely hard: a menu has a trigger and a list, tabs have a tab list and panels, a dialog manages focus for everything inside it, and people expect established keyboard patterns. Level 4 components are small applications in their own right and often take longer than everything else in the library combined.

Scoring complexity: eight questions

Levels are a good first guess. For planning, rate each component 0–3 on eight questions and add them up. You don't need precision; the point is to have the conversation as a team before committing to dates.

Question0 · none1 · a little2 · quite a lot3 · a lot
OptionsOne version2–3 variantsVariants × sizesMany combinations
StatesStaticHover, focusFull interactive setPlus loading, empty, error
InteractionNoneClickTyping, selectionDrag, resize, multi-select
Keyboard & screen readerNothing specialTab and EnterArrow keys, announcementsComplex focus, live updates
DataNoneA simple valueLists, formattingLarge data, async loading
Screen sizesSame everywhereMinor adjustmentsDifferent layout on mobileDifferent behaviour on mobile
CompositionSingle partFixed sub-partsSlots or childrenNested, coordinated components
PlatformsWeb onlyWeb, one frameworkWeb plus one nativeWeb, iOS and Android
The eight-question rubric. Total 0–6 → level 1 · 7–12 → level 2 · 13–18 → level 3 · 19–24 → level 4.

Four components, scored

ComponentOpt.StatesInter.KeysDataScreensComp.Plat.TotalLevel
Badge1000000121 · Element
Button2211011192 · Control
Date picker23232221173 · Composite
Data table33333331224 · System
Notice the date picker. Most people would guess it's like a select menu. It isn't: dates are data (time zones, locales, ranges, disabled days), and a calendar grid has some of the most demanding keyboard behaviour of any common component.

Match the process to the level

1 · Elements2 · Controls3 · Composites4 · Systems
Who's involvedOne designer, one engineerPair, plus an accessibility checkPair, accessibility specialist, a pilot teamA small squad, several pilots, product managers
ResearchInventory onlyInventory and real contentUsage research across teamsRequirements gathering, like a product feature
AccessibilityContrast, labelsKeyboard and screen reader basicsFull ARIA pattern; manual testingExpert review; testing with assistive technology users
TestingVisualVisual and behaviourPlus manual keyboard and screen readerPlus performance with real data volumes
Beta periodNoneA week or twoA month, with a pilotA quarter, with several pilots
DocumentationShort pageFull templateTemplate plus behaviour notesGuides, recipes and examples
Typical effortDays1–2 weeks3–6 weeks1–3 months or more
Effort ranges are practitioner estimates for one web framework, with foundations in place. Each extra platform adds roughly the same again.

For level 3 and 4 components, start with a kick-off workshop with every team that will use the component: walk through every existing version, agree must-haves and out-of-scope items, and name the pilot team. People support what they helped shape.

Plan by points, not by count

Instead of "ten components this quarter", plan with the totals: "about 90 points this quarter". A badge is 2 points; a data table is 22. It sounds a little nerdy, but it makes plans honest overnight, and it gives leadership a much better picture of progress than a count of finished components.

The same scores help with request prioritisation: complexity is the "effort" that divides a request's value score.

Choose the simplest component that works

Complexity is also a design decision for product teams. Every time a designer picks a component, they pick a level of complexity for users and for the engineers who'll build the screen. The simplest component that does the job is almost always right.

If people need to…PreferOverUnless…
Choose one of 2–5 optionsRadio buttonsA dropdown selectSpace is very tight
Choose one of 6–15 optionsA selectA searchable comboboxOptions are unfamiliar or long
Choose from hundreds of optionsA combobox with searchA custom picker dialogOptions need images or grouping
Enter a date they know (a birthday)Simple text fieldsA calendar date pickerThey need to see days of the week
Show extra informationText on the pageA tooltipIt's genuinely secondary

The short version

  • Four levels: elements, controls, composites, systems.
  • Score components 0–3 on eight questions to place them and estimate effort.
  • Match people, research, testing and beta length to the level.
  • Plan by points, not by number of components.
  • For product teams: choose the simplest component that does the job.

Frequently asked questions

How long does it take to build a design system component?

From days for a simple element to one to three months or more for a data table, on one platform. Score the component to estimate it.

Why are date pickers so hard?

Because they combine data (locales, time zones, ranges, disabled days) with a calendar grid that needs complex keyboard and screen reader behaviour.

Should the whole team score components together?

Yes, briefly. The value is in the conversation: designers, engineers and accessibility specialists notice different sources of complexity.

How do we re-score as we learn more?

Re-score yearly, or when a component's scope changes. Scores also help explain to leadership why one component took a quarter.

Further reading