The Short Answer
A system needs an upgrade when the effort spent working around it exceeds the effort spent working within it. The eight signs below are different expressions of this same phenomenon, but each points to a different root cause—making accurate identification more crucial than a simple headcount.
The Eight Signs
| # | Sign | What It Reveals |
|---|---|---|
| 1 | Parallel spreadsheets for managing forecasts or queues | The system isn't the single source of truth |
| 2 | Reports displaying conflicting numbers | Unharmonized metric definitions or data duplication |
| 3 | Every change request takes weeks | Automation debt, no proper testing environment |
| 4 | Screens with dozens of fields nobody fills out | Accumulation of requirements without cleanup |
| 5 | Noticeably slow record loading | Duplicate Triggers, cascaded Flows, inefficient queries |
| 6 | Daily recurring manual operations | A process that was documented, not implemented |
| 7 | Permissions granted "to make it work" | A visibility model that has lost its logic |
| 8 | Knowledge held by only one person | Lack of documentation and governance |
How to Read the Picture
The signs fall into four families, which determine the type of work required:
Process (1, 6) - The system is built around a process that isn't the actual process. The fix is re-mapping, not development.
Data (2) - The problem lies in definitions and quality, not in the reporting tool. Expand on this in Salesforce Data Quality Metrics.
Architecture (3, 5) - Accumulated debt in automations and code. Expand on this in Salesforce Performance Optimization.
Governance (4, 7, 8) - There's nobody deciding what gets in, who sees what, and who documents it. This is the family where, if left unaddressed, other fixes will unravel.
The Strongest Indicator
Among the eight, a parallel spreadsheet used by a senior manager for decision-making is the most unambiguous sign. It's not a complaint; it's a quiet declaration by the organization that the system is insufficient. As long as it exists, any improvements to reports are just working on a display that nobody relies on.
What to Do Before Fixing
The temptation is to start with the loudest sign. The effective order is different: two weeks of measurement on the three strongest signs to establish a baseline. Without it, even a successful fix can't prove itself, and funding for the next phase won't be approved.
After measurement comes the decision between a targeted fix and structural work, detailed in Salesforce Rebuild vs. Refactor.
Summary
The signs are not a list of complaints but a diagnostic tool: each points to a different root cause family, and treating a symptom from the wrong family wastes an entire cycle. Three active signs warrant a structured review; a parallel spreadsheet in leadership alone warrants it.