Adoption Isn't Training. It's Deleting Something From Their Day in Week One.
Staff adopt tools that make today easier for them individually and resist tools that only pay off if everyone else cooperates — regardless of how the change is communicated.
Fabien DarollesOperations ExpertThe trade rule
Every automation you introduce must visibly remove a task from somebody's day within the first week, or it is experienced as additional work no matter what the business case says.
Give before you take. Send the agent's output to the team before asking them to feed it anything. A daily list of eight calls with reasons and account context attached — built from data they never had to enter — buys more CRM discipline than any policy.
Design constraints people ignore
Phone-first is a hard requirement for sales, field and property teams. If it needs a laptop and a login it will not be used in the car, on site, or between viewings. Design for a thumb.
Zero-training bar: if a tool requires a session to explain, it needs redesigning rather than documenting. Mid-market teams have no training capacity and the benefit of the session decays within two weeks. Address fear explicitly — state what the automation decides, what it does not decide, and who reviews its output. Vague reassurance increases anxiety; specificity reduces it.
Why mandates backfire
Mandating usage is the fastest route to bad data. You get compliance theatre — fields filled with junk to clear validation — which is worse than empty fields because it looks like signal.
If a tool needs a mandate, it is not finished. Measure daily active use of the output rather than seats provisioned, and measure by individual.
Ask the three people closest to the process which single task they would most like deleted from their day. Build that first, even if it ranks third on your return-on-investment list.
Has run organisations above €100 million in revenue with teams exceeding 10,000 people.
Meet the team →Questions we get asked
How do I get staff to actually use a new automation?
Delete something from their day in week one. Give the tool's output before asking for input, design for a phone rather than a laptop, and require no training session — if it needs one, it needs redesigning.
Should we mandate use of a new system?
No. Mandates produce compliance theatre — junk data entered to clear validation — which is worse than empty fields because it looks like signal. A tool that needs a mandate is not finished.
What is the right adoption metric?
Daily active use of the output, measured per individual. One person using it every day tells you more than 60% weekly usage across a team.
Related insight
The AI Assistant That Does Everything Does Nothing
An agent's reliability collapses as you add systems it must be simultaneously correct about. The only agents that reach production…
AutomationYour Software Is Fine. The Gaps Between It Cost You Forty Hours a Week.
The recoverable waste in most operating companies sits in the transfers between systems, not inside any one of them. No vendor is …
AutomationAutomate a Broken Process and You Buy a Faster Broken Process
Automation makes a process permanent. Any step you encode without questioning becomes structurally harder to remove than it was th…
Where is your business still running manually?
We review your processes, identify the highest-impact automation opportunities and estimate their financial impact — before anything is built.