Many employees are having difficulty adopting AI in their work.
It’s not due to a lack of capability or tool complexity.
Not because the tools are too complicated.
The main reason is habit— the pull of the old, familiar way of working.
“Nakasanayan na.”
And that’s understandable.
The old way feels safe.
When you’ve done a task the same way for years, the process carries invisible weight. You know where to click, the sequence, and what the output looks like even before you start. The workflow lives in muscle memory.
You do not have to think too much.
That sense of flow is real. It is not laziness, and it is not resistance for its own sake. It is competence built through repetition, and it is something most people have been rewarded for their entire careers. Doing something well and doing it efficiently have always meant the same thing.
So when a new tool disrupts that flow, the natural instinct is to return to what works. This is not a character flaw. It is how humans work.
Why is the comparison unfair?
Using AI requires a different kind of effort.
You pause, think about the task, write a prompt, review the output, adjust, and repeat.
At first, it feels slower. If you compare it to a process you’ve repeated hundreds of times, it is slower because you’re measuring years of practice against day one of something new.
Most organizations get trapped by measuring early AI adoption against habitual workflows, misunderstanding the real barrier.
The old way feels faster because it is familiar; AI feels slower because it is new. But this difference is about comfort, not actual speed. The first is competence earned over the years; the second is the friction of learning.
We often confuse the two. Using the wrong metric, teams dismiss the tool as useless. Leaders see low engagement and doubt the technology. Adoption stalls, not from the tool, but from flawed measurement.
What the comparison looks like after the friction passes
The picture looks very different on the other side of that learning curve.
A report that used to take hours can be drafted in minutes. A document that used to start from scratch can now start from a strong first version. An analysis that used to require manual checking can now be explored faster and to a depth that was simply not possible before, within normal working hours.
In the programs we run through PAIBA and Olern, we consistently see this pattern. Employees who push through initial friction and build real AI workflows don’t just work faster; they work differently. They ask questions they never had time for before and take on problems that used to require escalation.
And that is still worth paying attention to: the ceiling does not just go up. The nature of the work shifts.
The challenge is that most employees never reach that point, halting during the uncomfortable middle stage when habit resists AI’s unfamiliarity.
AI adoption is a habit problem, not a training problem.
This is the part most AI adoption programs miss.
You can teach someone how to write a prompt. You can demonstrate the features, run a half-day workshop, and show them what the outputs look like for different tasks. And if you stop there, you have addressed the surface while leaving the real problem untouched.
The central issue is that people must first unlearn old workflows before mastering new ones. Training sessions alone cannot solve this. Success demands time, repetition, and a work environment that supports the initial slow adjustment period.
The biggest barrier to AI adoption is not access to tools.
It’s a matter of HABIT.
The companies making real AI progress are not those with the best models or largest budgets. They’re the ones actively helping their people confront discomfort, not avoid it.
What to actually do about it
If you are a leader who wants to move your team past “nakasanayan na,” three approaches have worked consistently in deployments we have run:
Start with tasks that have an obvious before-and-after. Pick a specific task your team does regularly and ask them to try it with AI once. Not to replace their process, just to compare. When someone sees a first draft of a report in front of them within two minutes instead of two hours, the gap becomes concrete. Abstract arguments about AI productivity do not move people. Seeing the difference with their own actual work does. Pick a task with a clear, observable output so the comparison is undeniable.
Give people permission to be slow during the learning period. One of the main reasons employees revert to old habits is that the working environment does not tolerate the learning curve. If your team feels pressure to maintain the same output speed while adopting something new, they will default to whatever is fastest right now. That will always be the old way, at least at first. Make it safe to be slower while the new habit is forming. This means being explicit, not just implicit.
Celebrate the first real win loudly. When someone on your team produces something meaningfully better or faster because of AI, name it in front of the group. Share the example. Make it visible. That single moment does more for adoption than any training module, because it makes the outcome feel achievable rather than theoretical. Early wins need to be celebrated publicly to signal that this is a direction worth investing in.
Where to start this week
Pick one person on your team who is already curious about AI, even slightly. Ask them to try using an AI tool for one task they do this week. Not a new task. The same task they would have done anyway.
Sit with them while they do it, or ask them to share the output afterward. Use that conversation as the foundation for the next step.
Shifting habit starts with one person and one task, not a company-wide AI plan. The rest follows from small changes.
FAQs:
What does “nakasanayan na” mean in the context of AI adoption?
“Nakasanayan na” is a Filipino phrase meaning “we are already used to it” or “that is the way it has always been done.” In the context of AI adoption, it describes employees defaulting to familiar old workflows because those workflows feel safe and efficient, even when a faster AI-assisted alternative is available.
Why does AI feel slower than existing workflows at first?
AI feels slower in early adoption because the employee is comparing a new, unfamiliar tool to years of practiced routine. The old workflow is fast because it has been repeated hundreds of times. Once an AI workflow is practiced with the same regularity, the speed and quality advantage becomes measurable. The slowness is a learning curve, not a ceiling.
Is the barrier to AI adoption really a training problem?
Training helps employees understand tools, but it does not address the habit layer. Most adoption stalls not because people cannot learn the tool, but because their environment still rewards and tolerates old workflows. Lasting adoption requires changing the workflow environment alongside the training.
How long does it take for employees to shift from old workflows to AI-assisted ones?
The timeline varies by task complexity and frequency of use, but in programs run through PAIBA and Olern, employees who use AI tools daily for a specific task typically see a habit shift within 2 to 4 weeks. The factor is not calendar time but the number of repetitions and whether early wins are made visible.
What kinds of tasks work best for introducing AI to a skeptical team?
Tasks with a clear, observable output work best: report drafts, document summaries, email responses, and meeting notes. These give employees an immediate before-and-after comparison. Avoid starting with highly creative or judgment-heavy tasks, which require more prompt sophistication and are harder to evaluate quickly.
What role do leaders play in AI habit adoption?
Leaders set the environment. If a leader visibly uses AI tools in front of their team, tolerates the slower early phase, and publicly celebrates the first wins, adoption accelerates. If leaders only talk about AI without modeling it, or implicitly signal that productivity cannot drop during the transition, teams will default to the old way.
Are you seeing this pattern in your own teams? Share your experiences or strategies that have helped you address “nakasanayan na.” Your insights can help others make real progress. I would be curious to hear what has worked for you. Send me a message if you have a success story, a question, or an idea.
