Most Salesforce orgs do not fail all at once. They accumulate small decisions — a quick field here, a workflow rule there — until everyday work feels slower and riskier than it should. A structured health check helps you see what has built up, and what to do about it.
Symptoms worth paying attention to
- Pages and saves feel slow. Often a sign of overlapping automation running on the same object.
- Nobody is sure what happens when a record changes. Process Builder, legacy workflow rules, Flows and Apex triggers may all be firing.
- Reports disagree with each other. Usually a data quality or definition problem, not a reporting problem.
- Admins are nervous about releases. A sign that test coverage, sandbox strategy or documentation needs attention.
- Users keep side spreadsheets. The org no longer matches how people actually work.
What a health check should cover
A useful assessment looks at the whole platform rather than one feature:
- Automation inventory. List every trigger, Flow, workflow rule and process per object, and identify overlaps and order-of-execution risks.
- Code quality. Review Apex for bulkification, trigger frameworks, test quality and hard-coded IDs.
- Security and sharing. Check profiles, permission sets, sharing rules and field-level security against the principle of least privilege.
- Data quality. Look for duplicates, unused fields, inconsistent picklist values and missing required data.
- Technical debt and limits. Note retired features still in use and anything approaching platform limits.
- Release process. Understand how changes move from idea to production.
Turning findings into a plan
Findings only matter if they lead to action. Group them by risk and effort, fix the high-risk items first, and schedule the rest into regular releases. Consolidating automation per object — for example, moving to one record-triggered Flow strategy or a single trigger framework — usually pays back quickly in stability.
A good rule of thumb
Before adding a major new capability, understand the foundation it will sit on. A few weeks of assessment can prevent months of rework.
This article is a draft for review.