Standard Business Analysis recommendations are usually quite clear-cut: every element should have documentation, fields without descriptions are technical debt, and unused processes must be removed. However, in the day-to-day reality of working with a mature system, sticking to these rules blindly rarely works. When entering an organization that has used Salesforce for years, we seldom face a clean slate—more often, we encounter a structure that has evolved alongside the business.
In such cases, analysis becomes system archeology. Instead of criticizing the lack of standards from years ago, we learn to read the layers we’ve inherited. This approach is rooted in respect for the logic and decisions that allowed the organization to grow into what it is today.
The System as a Record of Growth
A mature org is not a mess—it is a record of dynamic development. Stepping into an environment that has lived for years means encountering traces of different stages in the company’s life. What might seem redundant at first glance often has a deep-seated justification:
- Technical fields without visible documentation: Often ignored, but in practice, they may be critical for external integrations or specific reporting that isn’t visible on standard record views.
- Complex validation rules: These may seem like a barrier, but they are often the result of security procedures that protected the company from critical data errors in the past.
- Intricate automations (Flows): These often handle hundreds of exceptions and specific processes that the business has forgotten about because the system has been handling them invisibly for years.
A good example is a technical field that, according to usage reports, was populated in less than 3% of records. At first glance, it was an obvious candidate for deletion. Only a conversation with the finance team revealed that the field was used exclusively once a year during the audit closure as a marker for a specific regulatory report. Its removal would have forced manual workarounds during a critical time of the year.
Understanding this intent is key. At the same time, let’s be clear: not every element of a mature system deserves permanent protection just because it has a history. Some configurations were quick reactions to time pressure, organizational shifts, or technological limitations that no longer exist. System archeology is not about preserving everything we find, but about consciously separating the elements that still support the business from those that have become mere ballast.
Today, as we prepare systems for solutions like autonomous agents, this knowledge becomes critical. For such tools to truly support us, they must rely on rules consistent with how the company actually operates.
The System Archeologist’s Toolkit: 5 Rules for Safe Analysis
- Analyze footprints, not just figures Field usage analysis tools are useful, but they can be deceptive. A field populated at 5% might seem redundant until it turns out to be a key marker for audits or periodic reports. Deletion decisions should always consider the business context.
- Consult the Guardians of Historical Knowledge In every organization, there are people who remember the key moments of system and business transformation. They are the guardians of history, often involved in the configuration decisions that shaped the current org. Their perspective helps clarify past risks, though it should always be cross-referenced with current data.
- Respect the “load-bearing walls” of the architecture Validation rules and complex Flows are often the foundation of data integrity. Before they are simplified or removed, they require a thorough impact analysis. Elements perceived today as limitations may have served as crucial protective mechanisms in the past.
- Practice “safe excavations” If you suspect an element is dead weight, the safer approach is a “soft decommission.” Labeling a field as
[DEPRECATED], hiding it from page layouts, and observing the organization’s reaction allows you to avoid uncontrolled side effects. - Document findings for future generations Proper descriptions of fields and automations are among the most valuable artifacts of analysis. In a world of autonomous agents, these become operational instructions for systems that rely on metadata. Today’s documentation is the foundation for tomorrow’s automation.
Thorough analysis in a mature environment is, above all, about ensuring business continuity. Clients appreciate an approach that proposes a thoughtful evolution rather than a violent revolution. Understanding that every checkbox and every Flow has a story allows us to design solutions that are durable and truly aligned with the organization’s DNA.
