A count cannot tell you how the action started
Imagine two people who both read on six of the last seven evenings.
One begins only after two alerts and a late negotiation with the streak display. The other notices the book after placing a mug on the bedside table and begins before checking the tracker. Their completion counts match. The route into the action does not.
That is the difference between repetition and automaticity.
- Repetition is the occurrence of the behaviour across relevant opportunities.
- Automaticity is the degree to which the response is initiated or carried out with less conscious remembering and deliberation when its cue appears.
Repetition matters because it supplies the experiences from which a cue–response association can be learned. But attendance is not the association itself. A completion can be produced by a stable cue, an alarm, a deadline, social pressure, a burst of motivation or a combination of these.
If you measure only completions, all those pathways look the same.
Why researchers ask about automaticity
In early real-world formation research, participants repeatedly reported both whether they performed a chosen behaviour and how automatic it felt. Lally and colleagues modelled automaticity as a curve that often rose quickly at first and then more slowly toward a personal plateau. The study did not define habits by a fixed number of repetitions. Lally et al. (2010).
Gardner and colleagues later tested a four-item automaticity subscale, the Self-Report Behavioural Automaticity Index. Its items concern experiences such as acting automatically, without conscious remembering or thought, and starting before fully noticing. The researchers found the shorter measure performed well against the longer Self-Report Habit Index across several datasets.
The SRBAI is useful in research, not a diagnostic quiz; its authors did not publish one “habit complete” score. Self-report also has limits. The practical lesson is to stop asking a completion count to measure an experience it never observed.
Use the two-lens log
For one week, record only genuine opportunities for one clearly defined action.
| Opportunity lens | Experience lens |
|---|---|
| Did the planned cue occur? | What brought the action to mind? |
| Did I perform the action? | Did I remember before an external prompt? |
| Which version did I perform? | Did starting feel familiar or negotiated? |
| Was this the usual context? | Did the sequence flow or need rebuilding? |
Keep answers brief. “Cue / yes / ordinary / usual” and “mug / before alarm / familiar / flowed” are enough.
At the end of the week, read across the columns.
- High repetition, low experienced automaticity: the support system is producing action, but the cue may not yet carry the start. Keep useful scaffolding and inspect whether the real-world cue is specific enough.
- Lower repetition, clear automaticity in the usual setting: the habit may be context-specific. Misses elsewhere do not prove the learned pattern vanished; they point to a transfer problem.
- Cue noticed, action not begun: remembering may be working while the action remains too large or inconvenient.
- Action completed before the chosen cue: another cue may actually control the pattern. Name the cue you observe, not the one the plan claims.
- Neither repetition nor automaticity matters anymore: revisit the purpose. Measurement should not preserve an irrelevant habit.
This is an editorial reflection tool inspired by research distinctions, not a substitute for the SRBAI or a validated assessment.
Example: the tracker is doing more than you thought
Suppose you want to sketch for ten minutes after clearing lunch. You have logged 24 completions in 28 days and assume the habit is established.
During a one-week two-lens check, you notice that the sketchbook does not come to mind when lunch ends. A 2:00 p.m. notification triggers almost every session. On two days you dismiss the alert and forget entirely.
The count was accurate. The conclusion was premature.
You do not erase the 24 repetitions. Improve the cue path: place the sketchbook beside the tray before lunch and keep the notification as backup. After two weeks, check whether clearing the tray prompts the first pencil mark before the alert.
The tracker has changed jobs. It is no longer a scorekeeper proving identity; it is a way to compare the intended cue with the cue that actually started the action.
When to measure which thing
Measure repetition when you are learning whether the plan gets enacted, which opportunities disappear, or which version fits the week. An opportunity-based log is more informative than a raw streak if the habit is not truly daily.
Measure experienced automaticity when you are deciding whether to taper reminders, reduce logging or test the habit in a slightly varied context. Use a short observation period rather than rating yourself forever.
Measure friction when the cue reliably brings the action to mind but beginning still fails. The bottleneck may be materials, size, location or an unclear first step.
Measure value when both the count and the automaticity score are rising but you no longer care about the outcome. A behaviour can become familiar without remaining worth your time.
One metric should lead to one kind of decision. Trouble begins when a streak is used to measure character, a self-rating is used to predict every future context, or a day count is treated as a universal finish line.
Graduate support with a reversible test
If the familiar cue often brings the action to mind before your external prompt, reduce one support for two weeks.
Choose one:
- silence the backup reminder but keep the materials visible;
- log weekly rather than after every repetition;
- hide the streak while retaining the opportunity list;
- keep the cue and ordinary version unchanged while removing one prompt.
Do not remove the cue, change the setting and enlarge the action at the same time. If repetition falls, you will not know what mattered.
Set a restoration rule in advance:
Graduation is not a vow to need no support again. It is a test of whether support can become lighter. A context change, busy season or redesigned action may make scaffolding useful later.
The right measure is the one that changes a decision
Repetitions answer whether you acted. Automaticity observations answer something about the path into action. Context notes explain where the path holds. Value determines whether you still want to travel it.
Keep those questions separate and the data becomes kinder and more useful. A missed completion stops being proof that no habit exists. An intact streak stops being proof that reminders are unnecessary. Measurement returns to its proper role: helping you reflect, adjust, return and eventually graduate the support that has finished its job.
Evidence notes and sources
- Gardner, B., Abraham, C., Lally, P., & de Bruijn, G.-J. (2012). Towards parsimony in habit measurement. International Journal of Behavioral Nutrition and Physical Activity, 9, 102. The SRBAI isolates four self-report items about automaticity; it does not establish a universal completion threshold.
- Lally, P., van Jaarsveld, C. H. M., Potts, H. W. W., & Wardle, J. (2010). How are habits formed: Modelling habit formation in the real world. European Journal of Social Psychology, 40, 998–1009. The study recorded performance and self-reported automaticity separately and modelled varied individual curves in a modest sample.
- Wood, W., & Rünger, D. (2016). Psychology of Habit. Annual Review of Psychology, 67, 289–314. This review describes habits as efficient default responses learned through repetition in recurring contexts, while also explaining how habitual and deliberate control can work together.