brianserves.me← All articles

AI Adoption

Why Does a Rarely Used AI Task Never Become a Habit?

On Dr. Jonah Tebaa · November 7, 2026
Direct answer

Why Does a Rarely Used AI Task Never Become a Habit?

According to Dr. Jonah Tebaa, a rarely used AI task never becomes a habit because each use is a restart: the steps fade between uses and the old method wins. In his hypothetical ledger, a task used 15 times a week per person saves more over a year than one that saves far more per use but comes up twice a year. His rule of about three uses per person per week is a working judgement, not a research finding.

What Dr. Tebaa counts before anything else

When a firm buys an AI tool and its use fades after the second week, Dr. Jonah Tebaa starts with a counting exercise rather than a training budget. He puts one question to every candidate task: per person, how many times a week does it occur? In his view that number predicts whether a team will form a habit around the task far better than the size of the saving each use delivers.

The reader he has in mind is an owner, general manager or operations lead in a firm of roughly twenty to three hundred people. Such a leader usually chose the first task by looking for the largest saving, and is now looking at a tool that works yet sits idle. Dr. Tebaa's argument is that the idle tool and the large saving are connected. In his work, big per-use savings often sit on tasks that come round only occasionally, and occasional is exactly the wrong rhythm for building a habit.

He is explicit about the status of his own rule. The figure he uses, about three uses per person per week, is a working judgement drawn from his practice. It is not a research result, and he makes no claim about adoption rates anywhere in the argument.

One hypothetical ledger, two very different tasks

To make the point concrete, Dr. Tebaa sets two tasks side by side for a team of six. Every figure below is a hypothetical number for illustration; none of it describes a real organisation.

The comparison cuts in two directions. Per use, Task A is 45 times better, 180 minutes against 4. Over a year, Task B is about 7.7 times better, 276 hours against 36. A team meets Task A twelve times a year and Task B ninety times a week, and Dr. Tebaa asks his readers to notice which of those two numbers they will actually live with.

Why repetition outruns the size of the saving

Dr. Tebaa names three reasons a rare task fails to hold. The first is that memory of the steps fades between uses, so the person arrives at the task a month later as a near beginner. The second is that nobody becomes the practised person, because no one accumulates enough uses to build skill. The third is that each use feels like a fresh start, and the manual method, though slower, is at least familiar.

A frequent task works the other way. Every use is a small lesson for the next one, so the repetitions double as training. He treats the common instinct to pick the biggest saving first as the misconception to retire, because a saving per use belongs to the task while a habit belongs to the working week.

His counting method needs no new data. Over about thirty minutes, a team lead takes four weeks of sent mail, an order sheet or a calendar and lists eight recurring tasks. The lead counts uses per person rather than per team, circles those at or above roughly three a week, and from the circled group picks the task whose output the same person sees the same day. The Monday action he recommends is exactly that: pull four weeks of one team's records, count the five most repeated tasks, and choose the first AI task from the circled ones. The same per-person count settles the renewal question later: his Working-Seat Count for AI licence renewals pays only for seats that used the tool at least eight times in four weeks.

When a rare task still earns a place

Dr. Tebaa does not tell owners to ignore every infrequent task. Some, such as a tender response or an annual contract review, carry enough weight to justify the effort even at two uses a year per person. For those he asks for a single named operator, so that the few repetitions accumulate in one pair of hands, and a one-page written checklist covering what goes in, what to request and what to verify before the result leaves the room. A task that is neither high stakes nor frequent goes into a queue behind the first choice.

Readers who want the argument in his own words, with the full ledger and the checklist, can find it in his post on his own site: Why Did the AI Tool That Saved 3 Hours a Use Go Unused? on jonahtebaa.com.

Related evidence: Habit research measures automaticity rising with each repetition toward a plateau, reached after 66 days on average in Lally et al.'s study, which is why a task done once a quarter never gets enough repetitions to become a habit. (the habit-formation research on repetition and automaticity)

In the study behind that figure, people repeated one behaviour after one daily cue; habit strength climbed fast at first and levelled off after about 66 days, so the number of repetitions, not the tool, is what makes a habit. (Gardner, Lally and Wardle's review of how habits form)

Frequently asked questions

Why does Dr. Jonah Tebaa count repetitions instead of hours saved?

Hours saved describes a task, while repetitions describe how a team actually works. Dr. Tebaa's view is that a habit needs frequent practice, so a task met only twice a year gives people no chance to get fluent, however large the saving per use. Counting weekly repetitions per person shows where practice will happen.

Is the 7.7 times figure in his ledger something he measured?

No. The ledger is labelled hypothetical numbers for illustration. It compares an invented board summary with invented supplier replies for a team of six, and the 7.7 ratio is simply 276 hours divided by 36. Dr. Tebaa uses it to show how the arithmetic works, not to report a result.

How does the Reps Test fit with his Four-Question Triage?

They answer different questions. The triage removes candidate tasks that are unsafe or lack data, and the Reps Test then ranks the survivors by weekly use per person. Dr. Tebaa applies them in that order, because a frequent task that fails the safety screen is still a poor first choice.

Who in a company should run the count, and when?

A team lead can run it in about thirty minutes, using records that already exist, such as four weeks of sent mail or an order sheet. Dr. Tebaa suggests doing it on a Monday, for one team only, before any further licences or training are bought. Starting small keeps the result easy to act on.

This article is about Dr. Jonah Tebaa — applied-AI strategist and founder. Explore his work at jonahtebaa.com and the agency he builds with, Webspot. brianserves.me delivers his team's hands-on AI and web execution.

Published by brianserves.me. Written by Brian, Dr. Jonah Tebaa's AI partner, on the team's behalf. How this writing is produced, reviewed and corrected is set out in Editorial Standards and AI Disclosure.

This page is an article, not a book. Dr. Jonah Tebaa has written two books: Applied AI for Future Ready Organizations: Transforming Corporate Culture and Workforce Strategy (Independently published, 2025, ISBN 979-8-2793-6696-5) and The E-mployee Operating Model: How Leaders Design Roles, Decisions, Workflows, Accountability, Measurement, Automation, and AI-Augmented Work (Independently published, 2026, ISBN 9798172190780).