The short version
Ask any RevOps lead which field has the worst completion rate and most will say “next step” or “close reason.” These are the fields that actually predict whether a deal moves or dies, and they’re the ones reps skip under time pressure.
The fix isn’t more training, it’s fewer mandatory fields overall. Cut the CRM down to the 6–8 fields that genuinely drive a forecasting or handoff decision, make those required at stage change, and delete the rest. A CRM with 40 optional fields gets 40 badly-filled fields. A CRM with seven required ones gets seven well-filled ones, and a forecast you can trust.
Making “next step” a real field
Free-text next steps rot because they are easy to write and impossible to report on. Split it in two: a short text field and a mandatory next-step date. A deal with a past-due or empty date is automatically flagged, and a weekly view of “deals with no dated next step” becomes the most useful list in the CRM.
Set the wording convention by example: “Send security questionnaire to Sara, Thu 14 Nov” beats “follow up”. The test is whether a colleague covering the account could act on it without messaging the rep. Reps adopt this quickly when they see the manager reading the field rather than ignoring it.
Close reasons that can be analysed
Close-lost reasons are usually a free-text dumping ground. Replace them with a picklist of six to eight options: no budget, no decision, chose competitor, chose status quo, bad timing, poor fit, went silent. Add one optional text field for nuance. A short list is something you can count; a long one just gets “other” selected every time.
Make the field required at the moment of closing, not afterwards. Review the distribution monthly. If “went silent” exceeds roughly a third of losses, the real problem sits upstream in qualification or multi-threading, and no amount of late-stage coaching will fix it. The field earns its place when it changes what you do next.
Pruning the form without losing data
Deleting fields frightens people, so do it in stages. First hide the field from rep views and keep it in the database. Set a calendar reminder at 60 days and ask whether anyone noticed. If nobody asked, archive it. Fields tied to an integration or a report should be listed before you start, so you do not break a dashboard in Power BI.
Also check for duplicates in meaning. Teams often hold “lead source”, “original source” and “campaign source” that all try to answer one question. Choose one definition, map the old values into it, and write that definition in the field’s help text. One clearly defined field beats three vague ones in every attribution report.
Worked example (illustrative)
A hypothetical sales team of eight reps cuts a deal form from 38 fields to 8 required ones, with the rest hidden.
What changed: Completion rose because the form became short enough to finish on the way out of a call. The stale-deal list only exists because next-step dates are now reliable.
Do it: the steps
Tick them off as you go. Your progress stays on this device.
Traps to avoid
- ×
Adding fields every time a manager asks a new question. Answer new questions from existing data first.
- ×
Making a field required but leaving it unused in any report. Reps notice within a week and fill it with filler.
- ×
Letting every manager own a custom field. Assign a single field owner, usually RevOps, who approves additions against a named decision.
What to track
- Required-field completion rate
- populated records divided by total records at each stage change; target above 95%
- Next-step hygiene
- open deals with a future-dated next step divided by all open deals; a common goal is above 90%
- Time to update
- median seconds from call end to CRM update, sampled from activity logs or a rep survey; under 30 seconds is the aim
Benchmarks are typical planning ranges, not guarantees. Calibrate to your own data.
Questions people ask
Which fields should be required at creation versus later?
Keep creation light: company, owner, source and a contact. Require amount, close date and primary stakeholder when the deal reaches a qualified stage, and next step with date at every stage change. Requiring everything up front just makes reps enter junk values to get past the form.
How do I stop reps entering placeholder data?
Use validation rules: close date must be in the future, amount must be above zero, next-step date cannot be blank. Then audit a sample each month. Placeholder values like 1 or 01/01 are easy to spot with a simple report, and naming the pattern in a team meeting usually ends it.