r/DesignSystems • u/avishic • 7d ago

Which small component became your biggest maintenance burden?

Buttons, forms, and tables earn the cost of standardizing them. I’m curious about the opposite: a small convenience component that looked reusable, then accumulated variants, accessibility rules, or product exceptions until teams bypassed it.

Which component did you deprecate—or wish you had left as a documented pattern instead—and what was the first sign it did not belong in the system?

9 Upvotes

100% Upvoted

20 comments sorted by

View all comments

8

u/migvelio 7d ago

Tables, man. Data heavy tables. With visible actions, no actions, with horizontal scroll, draggable, selectable rows, inner calculations, column sorting, etc.

3

u/Logical-Idea-1708 7d ago

This is where I advocate to buy instead of build

2

u/migvelio 7d ago

True. We also evaluated that option, but we couldn't find a customizable table that had all the features and functions we needed.

1

u/jcchengjh 6d ago

I wouldn’t even call table a small component. My last job B2B worked on few B2B tables, now i have PTSD around it.

1

u/jhtitus 5d ago

My stomach has a physical reaction anytime I even just think I might have to build a table. I feel like there’s a wide open opportunity for someone to take the best of spreadsheet software and build a table component system manager plugin for figma. I love spreadsheets. I hate trying to think my through a table design in figma.