Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why won't the sales team use what I built for them?

You say you can enable sales now. That part is within your power — the building, the training, the rollout. What happens after is not fully yours to control. Adoption depends on their judgment, their habits, their trust. You keep treating it like a feature you forgot to ship. Ask yourself plainly: did the team help shape this, or did it arrive finished, asking only for their agreement? People resist what is done to them. They use what they helped make. Stop asking why they won't change. Ask what you are still doing alone that should be done with them.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The pattern behind low adoption is simple to name; the real work is specific action the pod must take together, so guidance leads.
How the two dials adapt to you →
What’s really going on

The tool is not the problem. You built it alone, then asked others to change their habits for it. You cannot make anyone adopt anything. You can only build with them from the start, remove the old habit you're asking them to drop, and make the new way the easier way.

🔒 What you’ll build togetherUnlock by starting
A moveBring actual users into the next decision about the tool this week, before you build further.
A moveName the one old habit your tool is meant to replace. Remove it. Do not let both exist side by side.
A moveAsk each person directly what stops them from using it. Fix the first true answer, not the comfortable one.
A moveReview adoption numbers with the team in the open, weekly. Do not study them alone.
A moveGive users one real win in the first week. Do not promise value later — show it now.
PractiseThe Missing Builder · a Pod of 4 · 30 min

What changes unlock by starting

  • You stop confusing 'built' with 'done.'
  • You find the small group whose resistance speaks for the whole team.
  • The tool changes because the team changed it, not because you defended it.
  • Adoption moves because the habit moved, not because you asked again.

Related problems

The same struggle, seen by other coaches
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.