A regional sales team was burning out on the very tool meant to help them close. We rebuilt the workflow around what salespeople actually do in a day — not around the data the system wanted to collect.
The CRM had been built up over five years of feature requests. Sales reps were spending more time logging activity than doing it. Leadership read this as "low adoption" and asked for training. The team read it as "tool fatigue" and asked for a redesign.
Both were partially right. The deeper issue was that the interface mirrored the org chart instead of the salesperson's day.
Three patterns came up in every interview:
The cost wasn't just time. It was the steady drip of micro-stress that turned a good salesperson into a tired one by Wednesday.
We worked in three short cycles instead of one big rebuild.
Cycle 1 — Observation. Two weeks shadowing four reps and three managers. We measured "decision moments" — times the rep had to think, not just click.
Cycle 2 — Pattern reduction. We reframed the system around five core actions a rep takes daily, demoting everything else.
Cycle 3 — Calmer surfaces. The interface became quieter on purpose. Tertiary information moved into expandable panels. Required actions got space; optional ones got translucent.
The biggest decision was a small one: a single "What's next?" element on every screen. It carried the rep through the day without forcing them to remember a flow.
We also added a deliberate pause step before any action that was hard to reverse — a one-second moment of structured doubt that, counterintuitively, sped people up because they no longer feared the system.
"It used to feel like the CRM was watching me. Now it feels like it's working with me."— Senior Sales Rep, post-launch
By the end of the second quarter, weekly logged activity rose by 22% with zero new training. Onboarding for new reps dropped from 21 days to 13. Most importantly, the team stopped describing the tool as "another job" — and started describing it as a habit.
The lesson I keep with me: clarity is a leverage point. You almost never need new features. You need to demote the ones already there.
Keep reading