The Short Answer
An extra five seconds per data entry, multiplied by thirty entries per day, then by one hundred users—that's a full workday lost daily to an overloaded interface. UX simplification is typically the highest-ROI action you can take on an existing system, and it almost always involves deletion, not construction.
Three tools are sufficient: a field usage audit, a three-click test for each key task, and layout customization by role and stage.
Why Screens Get Bloated
No one designs a screen with 80 fields. It originates from seven years of ad-hoc requests, each seemingly reasonable at the time. Three recurring mechanisms:
- The "just one field" request — seemingly negligible marginal cost, but a huge cumulative cost.
- A field remaining after a process changes — no one is responsible for its removal.
- The "just in case" field — "we might need this for a report in the future."
Therefore, simplification isn't a one-off project but an ongoing practice: every new field request requires specifying a field to be removed, or a clear justification.
Step 1 — Field Usage Audit
For each core object, create a table with four columns: percentage full over the last 12 months, usage in reports, usage in automations and integrations, and the declared process owner.
| Finding | Interpretation | Decision |
|---|---|---|
| Less than 10% populated, no report usage | Abandoned field | Remove from Layout |
| High population, no report usage | Work no one uses | Consult process owner |
| Low population, required field | Users enter arbitrary values | Remove requirement or change to Picklist |
| High population and report usage | Active field | Keep, perhaps move to front |
The third row is the most dangerous: a required field filled with dummy data pollutes your data and erodes trust.
Step 2 — The Three-Click Test
For each key task—updating a stage, logging a call, closing a Case—count the number of clicks and screens from the initial intent to completion. More than three clicks for a daily task warrants a fix.
Available tools include: Quick Actions instead of opening a full record, editing from a list, Path with guiding fields for each stage, and components that appear only in relevant contexts. The guiding question is always the same: What is the user here to do, and what's in their way?
Step 3 — Layout by Role, Not by Object
A uniform screen for all roles is a consolidation of all needs, meaning it's bad for everyone. A sales representative needs eight fields; an operations manager needs five different ones; Back Office needs approval fields that have no place for the first two.
Separation by Record Type and Profile, combined with Dynamic Forms for conditional display by stage, can shrink a 60-field screen to a 12-field relevant screen. Important: conditional display is not a substitute for a business decision about what is needed at all.
Step 4 — The Home Page as a Work List
The first screen a user sees should answer "What do I need to do now," not display general graphs. A prioritized task list, stuck items, and anomalies requiring attention. This is the daily return that justifies the input, and it's the main factor in restoring adoption—see Improve Salesforce User Adoption.
Measurement: Before and After
Before the fix, measure the average completion time for three core tasks, by five actual users, with a stopwatch. After the fix, re-measure using the same method. A 30% or more decrease in task time is an acceptable result for a first wave of simplification.
Alongside this, track data quality and the completion rate of core actions, according to Salesforce Adoption Metrics. True simplification improves both; if time decreased but quality suffered, a necessary field was removed.
Objections and How to Address Them
"But the field is needed for a report"—Who produced that report in the last year? "Manager X requested it"—Does the process that justified it still exist? "We might need it in the future"—It can be restored within an hour, and historical data is retained even after removal from the Layout.
These objections are managed within the organizational change process, not as a technical discussion—see Salesforce Change Management.
Summary
Conduct a field usage audit, remove abandoned fields, reduce required fields to two per stage, build layouts by role, and convert the home page into a work list. Measure task time before and after—this is the evidence that justifies the next wave.