Every RevOps leader I talk to is fighting the same war, and describing it in the same tired voice: the forecast is built on pipeline data, the pipeline data is maintained by reps, and the reps treat the CRM as a tax to be evaded. Close dates that roll forward every Monday. Deals stuck in "Negotiation" since March. The Notes field carrying information that belongs in six different structured fields, where reporting could actually see it.
The standard arsenal is escalation: more mandatory fields, more validation rules, dashboards of shame in the Monday meeting, the occasional executive email about "data discipline." I want to make the case that this arsenal fails because the diagnosis is wrong — and that this is, at root, a training problem, just not the kind that gets fixed with a training session.
Why reps don't update the CRM
Three reasons, and "laziness" isn't one of them.
They don't know how — specifically, not generally. Ask a rep to update a close date and they'll do it. Ask them to log an objection so it lands in the field your win-loss reporting reads, split a renewal from an expansion, or re-map contacts after a champion changes companies, and a large fraction quietly don't know the click-path. They learned the CRM in a two-hour session during onboarding, months before they had deals, and they retained what everyone retains from a tour of someone else's screen: approximately nothing. Nobody asks, because "how do I split a renewal?" feels like a confession at pipeline review.
The right way is invisible. CRMs are configured, not learned once. Your Salesforce has custom fields, validation rules, and a picklist philosophy some admin chose years ago. What "Stage 3" means at your company is tribal knowledge, and the rep's version of it came from whichever colleague trained them — hygiene folklore, mutating with each retelling. When ops says "the data is wrong," what's often true is that three cohorts of reps were taught three different definitions of right.
The cost-benefit is upside down at the moment of entry. Updating a deal properly costs the rep ninety seconds now; the cost of not doing it lands on someone else, later, diffusely. No dashboard of shame changes that math at 6:40pm after the fourth call. The only thing that changes it is dropping the ninety seconds toward ten.
Look at what escalation does to each of these: mandatory fields punish the person who doesn't know the click-path, making them slower and more resentful. It doesn't touch cause one or two at all, and it worsens cause three. That's why every RevOps team that has gone down the validation-rules road ends up with reps typing "." into required fields — the data theater equilibrium.
The fix is at the moment of entry, not in a session
If the causes are "doesn't know the specific path," "was taught folklore," and "friction beats diffuse future benefit," then the fix has one shape: authoritative, specific guidance available at the exact moment a rep is touching the record — cheaper to follow than to dodge.
Practically, for a RevOps team, that means three moves:
- Write the canon. Pick the ten highest-leverage hygiene motions (close-date changes, stage criteria, objection logging, renewal vs. expansion, contact re-mapping…) and define the one right click-path for each, in your instance, with your fields. This is the same ten-tasks exercise from the onboarding playbook, but for the whole team, not just new hires — because folklore, unlike ignorance, doesn't cluster in new hires.
- Put the canon inside the CRM. Not in Confluence. A rep mid-deal-update will not go read a wiki page — the distance between question and answer decides whether the canon gets used, and a wiki loses to guessing every time. Guidance has to show up on the record, pointing at the actual fields.
- Retire folklore transfer. New reps learn the canon by doing it guided, in their first week, on real records. Existing reps get the canon at the moment they touch a motion they learned wrong. Nobody sits through a re-training session, because re-training sessions are where hygiene initiatives go to die.
Disclosure, as always on this blog: step two is literally what Guidely does — a rep asks "how do I log this objection properly?" in the side panel and gets walked through it on the live page, or plays a guide your RevOps team built once for exactly that motion. And the flip side of the same install: your team's ask-log doubles as a hygiene diagnostic. When "how do I change a close date without triggering the approval flow?" is the most-asked question, you've learned something about your validation rules that no data-quality dashboard would have told you.
But the argument doesn't require my product. A team that does steps one and three with laminated cards taped to monitors will beat a team with perfect validation rules and no canon.
How you'll know it's working
Not by field-completion rates — those are gameable and get gamed (see: "."). Watch second-order signals instead: forecast revisions shrinking week over week, win-loss reports that cite structured fields instead of anecdote, pipeline reviews that spend their time on deals instead of on interrogating data. And one leading indicator that sounds soft but isn't: reps asking how questions openly. A team that asks "what's the right way to log this?" is a team that believes a right way exists — which is the actual, load-bearing difference between hygiene as a policy and hygiene as a habit.
There's a dedicated page on Guidely for ops teams at /for/ops.