The smallest decision that changed the system
Most of the time, the work that improves a system is not a rewrite. It is one well-placed decision, repeated consistently.
There is a pattern I keep seeing in systems that have grown quietly over years. They are not the product of one brilliant re-architecture. They are the product of one or two small decisions — usually naming, usually a contract between modules — that someone made carefully and the rest of the team respected.
A consistent way to name records. A single source of truth for the date a thing happened. A rule about who can edit what and when. These decisions are not exciting, but they are the ones that decide whether a system grows or rots.
If you cannot point to the small decision that holds your system together, that is probably the place to start the next round of work. Not a new feature. Not a rewrite. Just the next decision, made carefully, and shared.