Most Orgs are carrying 50-70% more clutter on their Page Layouts than anyone actually needs, and the fix is an average User and a stopwatch. Ask a user "what's this for, when did you last use it?" If they can't answer in 5 seconds, the element goes.
The Classic Approach Log in as a Power User or sit down with your PO/BA. Go Layout by Layout Cross-reference against documented processes, maybe check fill rate. Methodical, defensible, thorough.
It's also slow and it has a blind spot. Documented process and lived process diverge fast. The person who wrote the requirements two years ago isn't the person filling out the form today.
The Johann Way: the 5-Second Method
Grab an AVERAGE User. Ask them to walk you through their daily tasks. Be methodical about it, everything on the screen, not just the things that look important. Don't skip a Field, Button, Tab, or Component just because you think its purpose is obvious. Top left to bottom right. EVERY ELEMENT!
For every single element they encounter:
- "What do you need that for?" → "When did you last use it?"
If they can't answer in 5 seconds, it goes. Repeat with a second User. Maybe a third.
(Sidenote: I once spent months building and optimizing a "Send Email" Button, fully convinced it was essential turned out average Users never touched it.)
In my experience, the 5 second method beats the classic method almost every time. It's faster, and more importantly it's user-centric instead of documentation-centric. You're testing real recall under real conditions, not justification after the fact. The hesitation itself is the signal.
Who Should Run This Not the PO, BA, or Power User who was responsible for adding all those Fields and Buttons in the first place, they're emotionally invested in their own decisions. Bring in a neutral third party. Ideally one who likes to be radical.
Guardrails
Don't remove everything, give the Field, Button, Component a chance, maybe a little Change Management or Training can save it! (Thanks for the hint Vanessa Gröschner)
"Average" is the operative word. Not your Power User, trainer, or local champion, they know too much and will rationalize Fields an average user never touches.
Add fast if you removed something important: Remove it on a Tuesday morning. Pull it from the Page Layout, sit there, and watch. If users start complaining, add it right back. This is the one time changing directly in Production is the right call fast feedback beats a Sandbox simulation nobody will test properly anyway.
What You Will Gain At least 50%, realistically more like 70%, reduction in Page Layout clutter. Most Orgs are carrying that much dead weight without knowing it.
If you ever need a 5-second executioner, I'm your person!
Book a free 60-minute Org Technical Debt Audit: a score for Usability and Build Quality, and your top cleanup priorities.