SMART Goals

A simple explanation

The SMART framework asks five questions of a goal: is it Specific, Measurable, Achievable, Relevant, Time-bound? Pass all five and the goal is operational. The framework's gift is real: a goal that has passed the five questions can be acted on without further translation. Its limit is also real: nothing in the five questions tests whether the goal belongs to the person setting it.

SMART makes execution legible. It does not make meaning legible. A goal can be perfectly SMART and entirely borrowed.

An everyday example

Your manager asks for SMART goals for the quarter. You produce three: Ship feature X by April 12; reduce support tickets by 18% by end of Q2; complete two leadership trainings by June 30. Your manager nods. The document is exemplary.

By April 12, feature X has shipped. The tickets are down 19%. Both leadership trainings are complete. The framework worked exactly as advertised. You sit in your June review with three green checkmarks and a faintly familiar hollowness. The goals were SMART. They were also not particularly yours. The framework had no way to know — and no way to ask.

Why do SMART goals feel productive but hollow?

Because the framework operates on a different layer than meaning lives on. SMART optimises the path between goal stated and goal completed. It does not — and cannot — optimise goal worth completing. The hollowness is not a flaw in the framework; it is the silence the framework leaves where the existential question used to be.

The Meaning System, handed a SMART framework, gets one of its problems solved cleanly: the how becomes legible. The other problem — the whether — is left exactly where it was, only now disguised by the apparent rigour of the answer. A SMART goal can feel like a meaning decision when it is only an execution decision dressed up.

The behavioral loop

A loop that converts execution into apparent meaning:

1. Vague intention — a sense that something matters and should be pursued.
2. Framework prompt — work, school, or self-help culture asks the intention to be made SMART.
3. Specification work — the intention is narrowed into a target. The narrowing itself produces clarity-relief.
4. Time binding — a deadline is set. The body feels the future as nearer.
5. Disciplined execution — daily action proceeds along the legible path.
6. Closure — the target is met or not met on the scheduled date.
7. Verdict — success or failure is logged on the operational layer.
8. Silent layer — the existential question, never asked, generates a residue that accumulates across quarters into the I keep hitting goals and still don't feel anything signature.

Emotional drivers

Four feelings around the framework:

• A relief at the clarity it imposes — the noise of what should I want gets converted into the manageable noise of what should I do.
• A faint pride in being legibly disciplined.
• A creeping suspicion, often deferred for years, that the deposit on completion is smaller than the framework promised.
• A reluctance to question the framework, because it has worked — operationally — too many times.

What your nervous system does

The act of specifying a goal — the S — produces a small executive-function relief: the prefrontal cortex stops running open-ended search and starts running closed-ended planning. The energy cost drops. The measurability — the M — recruits the dopaminergic system around quantifiable progress markers, generating small reward hits with each unit advanced.

These responses are genuinely useful and the body works better with them than without. The cost is that the same circuits that light up around any measurable progress can light up around progress toward something that was never yours. The body's signal is progress, not meaningful progress. The Meaning System has to do its own discernment work; SMART will not do it for the System.

The DojoWell interpretation

SMART goals are a clean example of a delayed_harvest signature that splits across two layers. The operational deposit arrives reliably — friction is reduced, completion is more likely, the path between intention and action is shorter. The existential deposit depends entirely on whether the goal was honestly chosen before the framework was applied.

The framework's most common failure mode is sequence: applied before the existential question is asked, it converts an unclear longing into an executable target by collapsing the question. The longing was should I be reaching toward this at all? The framework re-states the longing as by when, with what metric. The translation looks like an answer. It is, in fact, the framework's silence on the original question.

Used well, SMART comes second. The Meaning System first chooses the future; the framework then renders the chosen future executable. Used poorly, SMART comes first, and the framework's clarity is mistaken for the meaning that should have preceded it. The density verdict is mixed precisely because the same framework produces high-density harvest when sequence is right and low-density residue when sequence is wrong.

How do I make SMART goals feel less like a project plan?

The fix is not in the framework but in what precedes it.

Three moves:

1. Run the meaning question first. Before any letter of SMART is applied, ask whether the underlying intention is yours and worth the life it costs. The framework cannot answer this. Answering it elsewhere is the only safeguard against optimising the wrong thing.
2. **Allow the R to do real work.** Relevant is the framework's one existential prompt and is almost always treated cosmetically. Slow down on it. Relevant to what? To whom? To which version of you? An honest R will sometimes kill the goal before specification begins, which is the framework working correctly.
3. Build in a permission to revise. Time-bound goals tend to lock in the originally-stated future even when reality has shifted. A six-week revision checkpoint converts the framework from a contract into a working draft.

Practical steps

1. Write the goal as a sentence before you SMART it. A pre-framework sentence captures intent the framework will narrow. Keep both.
2. **Ask the R in writing, with at least three lines.** Relevant because… is where most borrowed goals get exposed.
3. Pair every SMART goal with one meaning sentence. This matters because… The meaning sentence is the framework's missing layer.
4. At the deadline, evaluate the deposit on both layers. Did the operational target get hit? Did the existential one? Two separate yes-no answers.
5. Retire the framework for any goal whose meaning sentence cannot be written honestly. A goal that cannot pass the meaning sentence is not made meaningful by being SMART.

Reflection questions

• For your most recently completed SMART goal, what was the existential deposit, separate from the operational one?
• Where have you used SMART specification to avoid the harder question of whether the goal was yours?
• Which goal in your current list would fail the Relevant test if you answered it honestly?
• What would you set if you allowed yourself to name a goal before making it SMART?

Frequently Asked Questions