Nobody's opened a support ticket. The system technically works. There's no burning platform forcing anyone to act. This is exactly the environment where optimization opportunities go unaddressed for years — not because they're invisible, but because "working, just not great" never creates the urgency that "broken" does. Here are five specific signs worth checking for, even when everything looks fine on the surface.
1. Your Team Has Quietly Built Workarounds
If specific tasks routinely get done in a spreadsheet, in email, or through a manual process that exists "because the system is annoying for this," that's a real optimization signal — even if nobody's complained loudly about it. Workarounds are usually invisible in a system health review precisely because they happen outside the system. Ask your team directly what they do outside Business Central to get their job done; the answers are usually more revealing than any usage report.
2. Reports Take Noticeably Longer Than They Used To
A report that took ten seconds two years ago and takes forty-five seconds today, with nobody able to explain why, is a symptom worth investigating — usually tied to data volume growth interacting with a Dimension or SIFT index setup that was never revisited as the business scaled. Slow-but-tolerable is exactly the zone where problems compound quietly for years before anyone treats them as urgent.
3. New Employees Take a Long Time to Get Productive
If onboarding a new user into Business Central involves a lot of "let me show you the workaround for this" rather than the system behaving intuitively for standard tasks, that's a sign the setup has accumulated complexity that's become normalized for existing staff but genuinely confusing for anyone new. Long onboarding ramps are an optimization signal hiding in plain sight.
4. Nobody Can Confidently Explain Certain Configuration Choices
Every environment accumulates decisions nobody currently on staff can explain — a dimension that exists for reasons lost to history, a workflow step nobody remembers the purpose of, a posting group setup that predates everyone currently using it. This kind of institutional memory gap is a strong, specific signal that a fresh diagnostic look would surface real, fixable clutter.
5. It's Been Years Since Anyone Looked at the Whole System Deliberately
Most Business Central environments get attention reactively — something breaks, someone fixes that specific thing, and the review ends there. A deliberate, comprehensive look at the whole environment — Dimensions, posting setup, permissions, reporting — is different from reactive firefighting, and if it's never happened since your original implementation, the environment has likely drifted further from optimal than anyone realizes, simply because nobody's looked at it as a whole.
What to Do With This List
None of these five signs are dramatic on their own — that's exactly why they go unaddressed. Recognizing two or more of them is a reasonable, low-drama trigger to have an actual diagnostic conversation, rather than waiting for something to break loudly enough to force the issue.