Every system (or interface) breaks with its growth.
It is impossible to design a system for every case. The more entries in the system, the more different cases, the more things that doesn't work with how the system was designed.
Every entry demands a little bit different treatment. So never redesign a system because one entry needs it. Redesign the system based what most entries need or what highest priority entries need.
It's computationally almost impossible to oversee what users will need from an interface two steps ahead In your product development.
When adding entries to a system eventually it will bloat and it will be harder to navigate because of a lot out of date entries. That's why one should regularly restart the system from scratch. A good tool for it is loss aversion deleting method.
In order to take a value from the system one need to agree that it won't be ideal and some things won't be adjusted correctly or will not work.
Organization systems are in a constant temporal state. Maybe it's better to think about the systems that they are by broken default and they can fulfill a function in a rare state of the specific time and context.