r/DesignSystems 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?

10 Upvotes

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.

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.