For years, learning a new tool at work meant a course. Someone booked a session, a link arrived, and the plan was to sit through the modules and then, eventually, start using what we had learned. The assumption underneath was simple: knowledge comes first, practice comes second. With AI, that order seems to be flipping. In a study of 767 knowledge workers, people who knew at least one person using AI were about three times more likely to have used it themselves in the past week than people who knew no one. Nearly nine in ten participants did know someone. The strongest signal for starting was not a course, a licence or a policy. It was being close to somebody already doing it. That is a time issue, and a bigger one than it looks. The gap between "I should try this" and "I just finished something real with it" is where hours quietly disappear. A month of good intentions is a month of saved time that never started. Ten minutes beside a colleague can close that gap on an ordinary Tuesday afternoon. ------------- Context ------------- Most teams still treat AI adoption as a training problem. Budget goes to courses, prompt libraries and lunch-and-learn sessions. The thinking is reasonable: if we can get everyone through the material, the use will follow. Completion rates become the scorecard, and a high completion rate feels like progress. But courses carry a hidden timing problem. They ask for hours up front and return the payoff later, if at all. Picture a three-hour course spread over two weeks, followed by a gap while the learner hunts for a real task to apply it to. At the end, that person has spent three hours and saved none. Plenty of us have been that learner, and plenty of us never opened the second half. This is where it helps to name a different measure. Call it time-to-first-use: the number of days and minutes between deciding to try something and finishing a real piece of work with it. Courses tend to stretch that distance. Watching a peer shrinks it, because the learner sees the tool working on a real task before they have to figure out the task themselves.

Picture two colleagues in the same team, with the same licence for the same AI tool. One opens it when she remembers, perhaps twice a week, usually when she is stuck. The other opens it first thing every morning, for small things, almost without deciding to. Six months on, they are not slightly different. They are working in different ways. One has a handful of saved instructions, a feel for what the tool does well, and a short list of jobs she no longer does by hand. The other still starts from a blank box each time. That gap is a time gap, and it is the one most worth understanding right now. A new global workforce survey of nearly 50,000 people shows where we are. Around 64 percent of workers used AI at work in the past year, up ten points. But daily use of generative AI sits at 22 percent, up from 14. Most of us have tried it. Far fewer of us have made it a habit. ------------- Context ------------- When we talk about AI adoption, we tend to count who has used it. Did you try it? Do you have access? Have you been trained? Those are fair questions, and the answers are improving. But they measure whether someone has touched the tool, not whether the tool has changed how their week runs. That distinction hides a cost. A tool you use twice a week never quite becomes familiar. Each session starts with a small tax: remembering what it is good at, rewriting the context, working out how to phrase the request, deciding whether the answer is any good. Those few minutes do not feel like much. They are also exactly the minutes that make people conclude the tool is not worth the bother. So we end up with a quiet two-speed pattern. Daily users pay the setup tax once and then keep the benefit. Occasional users pay it again every time, and often decide the saving is too small to chase. The survey describes a widening divide between a small group of front-runners and a much larger group in the middle. Part of what separates them is simply frequency. For a Save Time post, the point is plain. The hours are not in the tool. They are in the repetition. Our job is to make repetition cheap enough that the habit forms.

Eight points. That is how far access to learning resources fell in a single year, from 59 percent of workers to 51 percent, according to a new global survey of nearly 50,000 people. What makes that number strange is the one sitting next to it. Over the same twelve months, daily use of generative AI at work rose from 14 percent to 22 percent. More of us are using these tools every single day, and fewer of us are being given the courses, the guidance or the working hours to learn how to use them well. Those two lines are moving in opposite directions, and somebody has to close the gap between them. That somebody is usually the individual, in their own time. It is a time issue, and an unusually hidden one, because those hours never appear on a timesheet, a project plan or a training budget. They get spent on Tuesday evenings and Sunday mornings, which is why so many of us feel that AI saves time at work while quietly costing time outside it. ------------- Context ------------- Most of us were told that AI would be easy to pick up. Open a chat window, type a sentence, get something useful back. For the first week that is largely true, and the speed of that first result feels like proof that nobody needs any training at all. The trap arrives after the first week. A useful first answer is easy. A reliable answer, on a real task, with real context, in a way that fits how a team already works, is a different skill altogether. Nobody calls it training because it mostly happens as tinkering: a tutorial video at 9pm, a prompt copied from a post, three attempts at the same task until one comes out right. This is where we think the more meaningful shift sits. Learning to work with AI has become part of the job without becoming part of the schedule. Organisations are counting the time the tools save while ignoring the time people spend becoming good enough for the tools to save anything. Both sides of that ledger are real, but only one side is being recorded. That matters because a time saving that depends on unpaid evening study is not really a saving. It is a transfer. The hours move out of the working day and into the margins of our lives, and the margins are where we have the least left to give. Counting the learning hours is the first step towards making the time gain real.

See how ChatGPT Dots work, how to talk to your Dot by voice, and how I use them to help me find a house in Phoenix. Get the FREE Dots PDF

You have an idea worth posting, and you want it to look good, so you decide to make it a set of images. You open a design tool, click through a few templates, drag in a photo, and start nudging text boxes around. Two hours later you've got five images that look amateur, and you can't even say why. Here's what actually happened in those two hours. You sat down to share an idea, which is a writing job. But the moment you opened the design tool, you were suddenly also doing a design job: picking fonts, choosing colors, deciding spacing, judging whether text is big enough to read on a phone. One image took forty minutes. One had too much on it and you couldn't tell what to cut. The whole thing looked off, and you had no idea how to fix it. You walked away thinking you're bad at this. You're not. You were just asked to be a writer and a designer in the same sitting, and almost nobody is both. ---------- THE REAL PROBLEM ---------- The problem is not "I'm bad at design." The problem is "posting good-looking images forces me to write and design at the same time, and those are two different jobs." Having something to say and knowing how to lay it out visually are separate skills. You have the first one. The idea is yours, and it's good. What trips you up is the second: the grid, the hierarchy, the color palette, the hundred small visual decisions that make something look professional instead of homemade. When you try to do both at once, the design half drags the whole thing down, and the time disappears. That's not a talent problem. It's a job-mixing problem. You're being a designer when your actual job was to be the person with something to say. ---------- WHY THIS MATTERS ---------- When every good-looking post means doing two jobs, posting becomes something you dread. The writing you could do quickly. It's the design half that balloons into hours, so each post costs far more than it should, and most of that cost buys you something that still looks amateur. After a few rounds of that, you quietly stop. Not because you ran out of ideas, but because the effort to make them look decent isn't worth it.