I used to think a simple equation held true:
New system + New workflow + a bit of AI = Guaranteed Efficiency.
Better tools should lead to better results. It seemed obvious.
However, working with clients changed my perspective.
Some people don't just hesitate to adopt new systems; they outright reject them. Itâs not that the new system is worse. Often, it is faster, cleaner, and more automated. But adoption isnât just a logical decision; it involves habits.
The Client Who Said "Put It Back"
I had a client who was excited about the idea even before I finished explaining it. With one click, the entire process would run: the document would be scanned, saved to his desktop, and emailed straight to his customers. He would no longer have to manually initiate a scan, dig through folders, or type the same email every time.
He loved it. After testing it and seeing it work as promised, he gave the green light for full implementation.
A few days later, he called me. He wanted to revert everything to the old method.
Nothing was broken.
The automation worked perfectly; that wasnât the issue. What I underestimated was that the old, âinefficientâ process wasn't just a series of steps for him. The manual scanning, saving, and sending provided small checkpoints. These were the moments when he could glance at the document, notice if something seemed off, or feel he had to double-check his work before it left his hands.
The automation removed those checkpoints along with the busywork. It turns out that busywork served a purpose for him that âefficiencyâ couldnât replace: it gave him a sense of confidence.
Why "better" Doesn't Win
People build workflows as water flows downhill, through friction, trial, and repetition, until a groove forms that feels effortless. This groove is invisible to an outsider. You may see a cumbersome manual process, but they see a system they built that they could understand every step and its meaning. Replacing it changes their tools, but also erases the muscle memory and sometimes the trust they spent months or years developing.
This is why "this new tool is three times faster" often loses out to "I already know where everything is, and I know itâs correct."
Three Things I've Started Doing Differently
1. Diagnose before I prescribe. Before I recommend automation, I ask what the current workflow is actually protecting: speed, control, a mental model, or just peace of mind. My clientâs manual scan-and-send wasnât protecting speed; it was safeguarding his confidence that nothing was overlooked.
2. Reduce switching cost, not just task cost. A tool can save hours each month but still fail if the first week of using it disrupts someoneâs sense of control. I now consider adoption friction as a separate factor from increased efficiency.
3. Let people keep one thing. Major workflow overhauls are often met with the most resistance. Partial automation, where someone retains a familiar piece, like a final visual check before sending something, is adopted much more frequently, even if it is technically âless efficientâ on paper. If I had left my client a checkpoint, even a small one, he might have kept the automation.
The Takeaway
Efficiency isnât just about the system. Itâs about how the person using it interacts with that system. A brilliant automation that no one trusts to use leads to zero efficiency. The best workflow design considers adoption just as seriously as it considers speed. Sometimes, the âinefficientâ step you want to eliminate is the one that does the most important job.
Where Kazeniq Cadence Comes In
This is exactly the issue Iâm addressing with Cadence. Most project and task tools expect you to abandon your process and adopt theirs. Cadence is built on a different approach: your tools should evolve to fit how you already work rather than forcing you to start from scratch.
A few features that illustrate this include:
- Track progress without hiding details. Instead of a single âclick, and itâs doneâ action, Cadence provides task status, completion timestamps, dependencies, and acceptance criteria. This way, you can see where things stand rather than just whether theyâre finished.
- Goals adjust as you near completion. When a goal reaches 80% complete or you're down to your last task, Cadence shifts into a âFinish Modeâ view, acknowledging that the final push deserves more attention than earlier project phases.
- Shape your calendar around your process. You can customize calendars by name, description, and colour while organizing goals by year, quarter, or month. This ensures the calendar mirrors how you actually plan, not a generic default.
- Stay up-to-date about collaborative work. Calendar sharing includes built-in notifications, so collaborators are aware of changes without you having to manually track them.
If any of this sounds like the workflow you've been trying to build for yourself, [try Cadence free â] https://cadence.kazeniq.com/
On the roadmap: stage-by-stage automation with manual approval checkpoints, standalone recurring automations for reminders and hand-offs, and a full activity/audit trail, creating the deeper âkeep your checkpoint, automate the restâ experience I want Cadence to offer.
If you're creating workflows for yourself or your team, I'd love to hear where automation has helped and where it has backfired. Reply and share your version of "put it back."
Henry, Kazeniq