Every RevOps leader has heard some version of this:

“The system slows me down.”

And every time, the instinct is to push back.

But here’s the uncomfortable truth: When top reps avoid systems, they’re often telling you something important.

Most reps don’t resist structure. They resist friction without payoff.

If a system:

• asks for data but gives nothing back
• adds steps without clarity
• forces judgment calls without context

They’ll bypass it, not out of laziness, but survival.

This is where GTM engineering complements RevOps beautifully.

RevOps ensures:

• clean data
• reliable systems
• operational consistency

GTM engineering focuses on:

• encoding decision logic
• reducing manual choices
• making “the right next step” obvious

Together, they answer:

“How do we make the system help the rep?”

In practice, the fastest adoption happens when:

• systems surface priority automatically
• research appears before reps ask for it
• routing reflects real-world urgency
• CRM updates themselves

At that point, resistance disappears, because the system is doing real work.

A useful diagnostic: Where do your best reps still operate “outside the system”?

That’s not rebellion. That’s a design brief.

Next edition: why the CRO’s real job isn’t revenue, it’s decision quality.