Every system (or interface) breaks with its growth.
It is impossible to design a system for every case. The more diverse the cases or entries, the more likely it is that some will not align with the system's original design.
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. Foundation paralysis effect 🎨 makes it hard to improve system later on. That's why often one software will die and another will emerge.
When adding entries to a system eventually it will bloat and it will be harder to use it. 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 as a user of the system one need to agree that it won't be ideal and some things won't be adjusted correctly or will not work.