SMART goals versus tiny behaviours

SMART goals come from George T. Doran's 1981 note in Management Review: specific, measurable, assignable, realistic, time-related (the popular expansion to "achievable, relevant" arrived later in training decks). They were a way to write management objectives, not a theory of automaticity. Tiny behaviours come from BJ Fogg's work: shrink the act until ability is high, attach it to an anchor you already do, and let it grow. Using SMART on a floss habit is a category error. Using tiny as your only tool for a six-month product launch is the error in the other direction.

Goals versus systems versus habits is the three-way split. This post is the phrasing fight: how you write the outcome versus how you write the first repetition.

What SMART is good at

Locke and Latham's goal-setting programme found that specific, difficult goals with feedback beat vague encouragement on performance tasks. SMART, at its best, is a checklist for that kind of goal: what exactly, how you will know, who owns it, whether it is in range, by when. "Submit the draft of chapter 3 by 30 October" is a SMART-ish object. You can miss it. Missing it is information. You then run a system (desk, kettle, one paragraph) to make the next miss less likely.

SMART fails as a daily habit because "measurable" and "time-related" tempt you to put a quarterly number on a Tuesday checkbox. "Read 40 books this year" is a goal. It does not tell 7:30 a.m. what to do. "Lose 8 kilos by June" is a goal. After dinner, the tiny behaviour is a walk, or the leftover stays in the fridge, not a weigh-in that spirals. How to log weight without spiraling is the measurement caution.

Realistic / achievable is the SMART letter people use to shrink a goal until it is safe, which can also shrink it until it is boring. Locke and Latham wanted difficult specific goals for performance. Fogg wants easy first actions for habits. Both can be true because they are not about the same object. The launch can be difficult. The first two minutes of writing can be easy.

What tiny is good at

Fogg's MAP (motivation, ability, prompt) predicts that when motivation dips, only a high-ability act still happens. The floss-one-tooth example is the teaching case: after a reliable bathroom cue, a behaviour so small that pride cannot veto it. Lally et al. (2010) needed a defined daily act in a stable context for automaticity to grow. Tiny is how you keep the act defined and the context stable when the week gets ugly.

Gollwitzer's implementation intentions are the grammar: if [anchor], then [tiny act]. SMART has no if. It has a by-when. You need both sentences in different notebooks. Implementation intentions: if-then plans that stick is the study trail. Tiny habits and the two-minute rule is Clear's neighbouring shrink.

Charles Duhigg popularised cue, routine, reward. Tiny is a routine small enough to attach to a cue. SMART is not a routine. If you try to "reward" a SMART miss with a streak reset, you import project failure into a habit loop, which is the abstinence violation effect wearing a Gantt chart.

Wendy Wood's context work says the tiny act has to live in a real setting. "Meditate 20 minutes, five days a week, measurable by the app, relevant to my stress, by Q1" is SMART and still has no chair. "After I put the kettle on, I sit in the chair and take three breaths" has a chair. Grow duration later, as ability allows, not as a quarterly OKR.

Phrase	Use it for	Do not use it for
SMART objective	A finite outcome with a date	Tuesday's floss, stretch, or pages
Tiny behaviour	The first repetitions of a daily act	The only plan for a six-month project
If-then sentence	Attaching tiny to a cue	Replacing a deadline you actually need
Weekly number	Feedback on the goal	A daily streak you will fake

How to write a habit in one sentence should come out tiny, not SMART. A 30-day habit experiment you can actually finish is a bounded test, which is closer to a mini-goal around a tiny act: one behaviour, thirty days, then you look at the data. That is SMART-ish at the experiment level and tiny at the daily level. Mixing the levels in one row is the failure.

If your tracker only accepts SMART-shaped titles ("Read 20 pages every weekday at 80% consistency"), you can still keep the tiny version in the first week and let the target be a later switch of log type. Yes/no, quantity, timer, or a 1-to-5 scale can grow with you. The title should still contain an after.

Habit AI is a useful example of starting from a spoken line rather than a six-field SMART form: you can type the tiny sentence, then let target and schedule fill in without a management-objective workshop. Keep the quarterly SMART page elsewhere. The daily row stays small.

Write two sentences this week: one with a date on an outcome you can finish, one with an after on a behaviour you can do when you are tired. If you only have the first, you will white-knuckle Tuesdays. If you only have the second, you may never check whether the project moved. You are allowed both. You are not allowed to confuse them.

Read next

Tiny habits and the two-minute rule is the shrink. Implementation intentions: if-then plans that stick is the grammar. For a daily row that can stay tiny, see how Habit AI works.