One morning, he got a Slack notification. "Starting today, AI writing tool accounts are active for everyone on the team. Please make full use of them to improve work efficiency." There were no usage guidelines and no explanation of which tasks to try first. Two months later, he said he could count on one hand the number of times he had logged in. He didn't know how to use it—or more precisely, he didn't know what "how" was even supposed to mean.
The scene maps precisely onto a phenomenon BBC Business recently spotlighted: a growing number of companies are encouraging—or requiring—employees to use AI while skipping any preparation for how they should actually use it. The tools arrived, but there was no path for working them into the daily flow. Organizations wanted speed, and employees lost their bearings.
The Account Arrived. The Plan Never Did.
There is a striking difference in how companies roll out AI. Some buy licenses, hand out accounts, and wrap things up with a memo—"AI use is encouraged going forward"—while others first map out which tasks the tool will support, what outputs it should produce, and at what level it will be used, and only then bring it in. Most organizations struggling right now fall into the first camp.
The gap is not simply a lack of training. It's less that people don't know how to operate the tool and more that they don't know what to do with it. When a marketer receives an AI copywriting tool and has to decide on her own where it fits into her current workload, that isn't efficiency—it's a new cognitive burden. Few people have room in their workday to make that call.
Surveys of UK companies show the same pattern repeating. A majority of managers at organizations that have adopted AI tools say their teams aren't using them effectively, yet only a small minority have formal usage guidelines or a plan for integrating the tools into workflows. The investment was made; the design work that would convert it into actual performance was skipped.
We already know how decisive the first few weeks are when a new person joins an organization. Six months in, there is a clear divide between someone who was walked through, in a structured way, what work they would own, who they would collaborate with and how, and what standards they would be judged by—and someone who wasn't. A new hire handed nothing but a desk on day one rarely figures out their role alone. There is no reason tool adoption should be any different. Onboarding begins the day the account is created, and how people relate to the tool in those first few weeks determines whether it ever makes its way into their work.
How Pressure Produces Performative Use
The word that stands out in the BBC's reporting is "confused." Employees aren't resisting or refusing; they don't know which way to go. That distinction is not small. Many executives read failed AI rollouts as employee resistance to change, but on the ground the situation more often looks like an absence of direction.
When there is a goal but no path, people make the safest choice. Rather than turning their backs on the AI tool entirely, they often settle into performative use: having AI draft a report and then rewriting it from scratch, submitting the output unreviewed, or dabbling only in areas unrelated to their actual work. None of these lead to the productivity gains the organization expected.
The pattern sharpens in environments with heavy short-term performance pressure. When AI usage lands on the evaluation sheet in a setting that leaves no time to learn while doing, employees prioritize the deadline in front of them over learning the tool. Usage numbers go up, but the actual work doesn't change.
The counterargument deserves a hearing, too. Today's AI tools are far more intuitive than previous generations of enterprise software, and YouTube and online communities offer vast free learning resources. Some argue that an overly structured rollout program can actually stifle employees' self-directed exploration and shut down creative uses the organization never anticipated. There is no shortage of cases where people who learned by trial and error came to understand a tool more deeply than those who simply followed the guidelines. The observation that exploration teaches more than any manual is not wrong.
But for that argument to hold, certain conditions must be met. There has to be time to explore, a culture in which mistakes are acceptable, and a structure through which what's learned can flow back into the work. Pressure poured on without those three things doesn't invite self-directed exploration—it produces something closer to abandonment.
What Korea's Solo Planners and Middle Managers Should Be Asking Now
In Korea, another layer of pressure sits on top of all this. The decision to adopt AI comes down from the top of the organization, but the responsibility for actually making it work lands on frontline managers and solo planners—the one-person strategists common in Korean companies who handle planning work on their own. They end up in the position of having to design "how should our team use this?" by themselves.
The first thing to check from that position is whether the team's purpose for using AI is actually concrete. "Efficiency" and "encouraged use" are not purposes. The goal needs to connect to a measurable outcome: "cut the time to draft a proposal to under 30 minutes," or "automate the data-collection stage of the weekly report." Adoption without a purpose leaves nothing behind but the license fee.
Next comes checking whether you have actually mapped, together, where the tool can slot into each team member's workflow. If you work alone, it's worth experimenting directly with which step of your daily or weekly routine AI assistance genuinely improves. Even without a company-wide rollout, small individual integration experiments can start right now.
It also helps to set a failure tolerance in advance. When AI output gets used as-is and the result disappoints, the only way to keep that from hardening into "this thing is useless" is to adjust expectations first. The first few attempts should be treated as the cost of learning the tool. Creating that breathing room is a manager's job—and if you're a solo planner, you have to grant it to yourself.
The gap between the day the account is issued and the day the tool is actually woven into the work: organizations that designed in advance how to fill that interval and those that didn't will be standing in entirely different places six months later, having paid the same license fees. How you design the first few weeks is what decides whether adoption succeeds or fails. I would argue this is not a technology problem—it's a design problem.
