Symptom · one of six
People avoid the system
A page layout that asks for more than it gives back. Below: what that means underneath, a check you can run yourself in about ten minutes, and what it costs to put right if the check confirms it.
Nothing on this page is sent anywhere. The check runs in your own org.
What it is
A page layout that asks for more than it gives back
Sixty fields of which nine matter, no answer to what the rep gets out of filling them in, and reporting built on data nobody enters. Adoption problems are almost never solved by training, because the training is not the reason people stopped. Fields have to earn their place by being used in a report, an automation or a conversation.
Confirm it yourself
How do you confirm this yourself?
Pick your five most recently created opportunities and count how many fields are populated beyond the required ones. Under a third means the layout is asking for work with no return.
You have this if under a third of the optional fields are filled in. If your org comes back the other side of that line, this is not your problem, and nothing on this page is worth buying to you. Finding that out costs nothing and takes ten minutes.
If the check confirms it
Layout and process rebuild around what the team actually does
Fixed price on a written scope, 60 hours at fifty euro an hour, about 3 weeks elapsed. Documentation and sixty days of support after handover are in the price rather than an addition.
€3,000 · 60 hours · 3 weeks
When it is bigger than a repair
When is this the org rather than one fault?
This one travels with changes breaking other things: layouts grow because automation demands fields, and nobody removes either. If more than two of the six match at once, the pattern is usually one org that was never configured for how the company sells now, rather than several separate faults. That is an implementation, not a repair, and it is priced the same way: hours multiplied by fifty.
Asked often enough to answer here
Questions
Would more training not fix this?
Training is the apology for skipping the design. People who stopped entering data did not forget how; they concluded it was not worth the time. Training repeats the instruction without changing the trade.
What happens to the fields nobody fills in?
Each one has to justify itself by appearing in a report, an automation or a conversation. The ones that cannot are removed from the layout, which is usually most of them.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018. Reviewed 22 August 2026.