March is a good moment to look at the component library with fresh patience. Some patterns still feel useful. Others feel like decisions the team forgot to revisit.

I start by looking for components with low usage, unclear ownership, or too many variants. Those are usually the places where the system is carrying extra weight.

Pruning is not only deletion. Sometimes the right move is combining two patterns, renaming one, or documenting the reason it exists.

A component library should feel maintained. When teams can see that old decisions get revisited, they trust the system more.