Salesforce Picklist Hygiene: Why 'Other' Is Eating Your Data Quality

Open any mid-market Salesforce org and pull a report on Lead Source, Loss Reason, or Industry. In most cases, you will find that "Other" is the second or third most common value. Sometimes it is the most common value. When 30% or more of your records say "Other," your CRM is not capturing data. It is capturing the absence of data.

This matters for two reasons that go beyond reporting. First, any AI tool that reads picklist data will treat "Other" as a meaningful category. A lead scoring model that sees 35% of closed-won deals tagged as Lead Source: Other will learn that "Other" is a strong predictor of success, which is nonsensical. Second, downstream routing, assignment, and segmentation logic that depends on picklist values breaks silently when the dominant value is "Other."

Why "Other" takes over

Picklist sprawl happens for predictable reasons. The original values were defined years ago by someone who is no longer at the company. The business has changed, but the picklist has not. Reps encounter scenarios that do not fit any existing value, so they pick "Other" because it is faster than requesting a new value through an admin ticket.

There is also a design problem. Many picklists are built with too few values (forcing legitimate answers into "Other") or too many values (making reps scroll through 40 options until they give up and pick "Other"). Both extremes produce the same result: unreliable data.

How to audit your picklist health

Run a distribution report on every picklist field that matters to your reporting or AI tools. For each field, calculate the percentage of records in each value. Flag any picklist where "Other" exceeds 10% and any picklist where more than 30% of values are used by fewer than 1% of records (these are zombie values that add clutter without capturing meaningful data).

For fields with a free-text "Other" description field, export those descriptions and cluster them. You will almost always find that 60-80% of "Other" entries map to three or four patterns that should be their own picklist values. This clustering exercise is the fastest way to fix a broken picklist.

Fixing the picklist: a practical process

Start with your highest-impact fields: Lead Source, Loss Reason, Industry, and any field that feeds routing, scoring, or AI models. For each field, pull the current value distribution and the free-text Other descriptions.

Propose a new value set based on what you find: merge rarely-used values into broader categories, promote common "Other" descriptions to named values, and retire values that represent fewer than 1% of records. Then validate the new set with three to five reps and one sales manager. If they can categorize ten recent records using the new values without hesitation, the set works.

Once you update the picklist, backfill historical records where possible. A simple data update that recategorizes old "Other" records into the new values improves your historical reporting and gives AI models a richer training set.

Governance: keeping picklists clean

Set a quarterly review cadence for high-impact picklists. Check the "Other" rate, check for new patterns in free-text descriptions, and update values accordingly. Assign a named owner for each critical picklist so that requests for new values have a clear path instead of dying in a backlog.

Consider dependent picklists where appropriate. If your Industry field is broad, a dependent Sub-Industry field can capture specificity without bloating the primary field. But be cautious: every layer of dependency adds complexity for reps and admins.

The AI connection

Picklist quality is one of four criteria in the Data Foundation dimension of the AI-Ready RevOps Framework. When picklist data is clean, AI tools can segment, score, and route with precision. When 30% of records say "Other," every model built on that field inherits the ambiguity. Clean picklists are not a nice-to-have. They are a prerequisite for any AI tool that reads from your CRM.

Try it free →CRM Data Quality Scorecard

Frequently asked questions

What is a healthy 'Other' rate for Salesforce picklists?

Below 5% is strong. Between 5% and 15% suggests the picklist values need updating. Above 15% means the picklist is failing as a data capture mechanism and your reporting on that field is unreliable.

Should I remove the Other option from picklists?

Not necessarily. Other serves a purpose as a catch-all for genuinely rare cases. The problem is when it becomes the default because your picklist values do not reflect how reps actually describe deals, leads, or accounts. Fix the values first, then monitor the Other rate.

---

← All articles