Three things Users feel every day.
Phase 1 only cleans what Users touch: the pages, the Bugs and the old data behind them. We sat with six Users, Field by Field. No new Fields, no new features.
Deep dive 1 · Page Layouts and List Views
One page per role, the important Fields on top.
What we found
The Event Opportunity page had grown with every freelancer: sections across nine tabs, Fields nobody could explain, and many layouts behind six Record Types. Account and Order looked the same. Every User had built private List Views because the shared ones were useless.
What we did
- Sat with two Key Account Managers, a Sales Manager, two Sales Ops Specialists and an Event Service Manager
- Moved the Fields each role uses daily into the first section, everything else into one place or off the page
- Deleted the unused layouts behind the three Objects
- Deleted, merged and renamed List Views, one clear default per role
Opportunity page
Fields on the layout
−71%Fields
Account page
Fields on the layout
−52%Fields
Order page
Fields on the layout
−73%Fields
List Views
Opportunity, Account and Order
−84%List Views
Unused Page Layouts
On the three Objects
16deleted
Deep dive 2 · Bugs and Errors
27 Bugs fixed, the ones Users hit every day.
What we found
Mostly simple automation errors: Flows without null checks, two automations writing the same Field, hard-coded Ids. A few smaller Apex problems and Sharing gaps. Users had learned to work around them.
What we did
- Took the 27 Bugs that annoyed Users most
- Fixed each Bug where it happened, without rebuilding the automation around it
- Tested every fix with the Users who reported it
12 Flow errors
7 Sharing
4 Apex and limits
3 Validation Rules
1 Page Layout
Opportunity
Error on save when setting an event to Closed Won.
- Why
- A Flow set the Venue Status. The Flow failed on online events without a venue.
- Fix
- Added the missing check for events without a venue.
- Who felt it
- All Sales Users, several times a week.
Order
Event Service could not see some of the Orders of their own customers.
- Why
- The Sharing Rule still pointed to a Role that is not used anymore.
- Fix
- Sharing Rule rebuilt on a Public Group.
- Who felt it
- The whole Event Service team, on some events.
Order
"Too many SOQL queries: 101" when saving a large conference Order.
- Why
- The Order Product trigger ran one query per line item. Big events have over a hundred lines.
- Fix
- Bulkified the trigger, one query per save, tested with 200 lines.
- Who felt it
- Sales Ops, on every large event.
Deep dive 3 · Old data
Years of old data cleared, with a full backup first.
What we found
Data Storage almost full. Most of it was Emails and Tasks from events long finished, and an integration log nobody reads. More clutter for Users and AI, and a storage upgrade on the horizon.
What we did
- Agreed a retention rule with the Head of Sales Operations: Emails and Tasks older than 4 years, sync logs older than 6 months
- Took a full backup and archived it in the customer's own storage before every delete
- Deleted in batches, Object by Object
ObjectRecords deleted
Email Message98,640
Task49,820
ERP Sync Log81,200
Total229,660
Data Storage used
Before and after the cleanup
−13percentage points