Mentavo
The standard answer to badly written goals has been the same for forty years: specific, measurable, achievable, relevant, time-bound. That isn't wrong, and it still doesn't solve the most common problem.
Because most goals don't fail for being imprecise. They fail because after being written they disappear — recorded on a Sunday, last seen the following Tuesday.
So a usable goal isn't primarily one that measures well. It's one that reappears in everyday life without you having to go looking for it.
The short version
- Goals fail on invisibility more often than on vagueness.
- A goal needs a place and an occasion at which it turns up anyway.
- Outcome goals ("lose ten pounds") can't be done; action goals can.
- The crucial detail isn't the deadline but the first concrete occurrence.
- Three simultaneous goals is the ceiling for most people.
- A goal still worded identically after four weeks was probably too general.
Why SMART only solves half of it
The five criteria describe a good formulation. What they don't describe is the route from the sentence to the day.
"Run thirty minutes three times a week until 31 March" is exemplarily specific, measurable and time-bound — and still says nothing about what actually happens on Tuesday at six. Between the sentence and that Tuesday lie twelve weeks in which nobody reads the sentence.
There's a second point. Measurability tempts you to make the measurable thing the goal. Set "read ten books" and you have a goal about book counts, not about reading — and you end up optimising for thin books. Why a reached goal can then feel surprisingly empty is covered in the piece on that exact moment.
Four test questions
1. Is it something I can do — or something that should happen?
The key distinction. "Lose ten pounds", "get promoted", "be calmer" are states that should come about. You can't do them on Tuesday.
An action goal describes something that either takes place on Tuesday or doesn't: "cook for myself on three evenings a week", "prepare the conversation with my manager every Friday".
Outcome goals aren't worthless — they set direction. But they belong a level up, and underneath them there needs to be at least one action goal, or there's nothing to do.
2. Where does it reappear?
The question no goal-setting method includes, and the one that decides most goals. A goal sitting in a notes app under two hundred other notes won't be read again.
Usable answers are concrete: it's attached to a calendar entry. It appears on Monday morning. It hangs on the door. It's tied to a routine that happens anyway.
If the answer is "I'll remember it", that's not an answer. Remembering is exactly the job that goals don't perform in everyday life.
3. When does it happen for the first time?
Not: by when is it finished. Instead: on which day, at which occasion, does the first instance take place?
That shift from deadline to beginning has real consequences. A deadline three months out produces neither pressure nor action. A first instance on Thursday evening produces both.
It also exposes unrealistic goals early: if no slot can be found for the first occurrence, none will be found for the twelfth either.
4. How will I know I've given it up?
The most uncomfortable question and the most honest. Goals rarely end with a decision. They end by not having happened for six weeks while nobody says so.
A stopping criterion fixed in advance — "if it drops out three times in a row, I'll look at it again" — turns quiet disappearance into a decision. Why criteria set in advance generally hold better than weighing things in the moment is covered in the piece on decision criteria.
From outcome to action: an example
Starting point: "I want to change jobs." That's a direction, not a goal.
One level down: "By the end of March I'll know whether I'm looking inside or outside the company." Still a state, but a checkable one.
Action level: "Every Sunday, thirty minutes: either prepare a conversation or go through one job posting seriously." That can be done on Sunday.
Place of reappearance: Sunday afternoon, right after tidying up — an occasion that happens anyway. First occurrence: this Sunday. Stopping criterion: three missed Sundays in a row.
Five lines, and the goal has a date, an occasion and an endpoint. That's more than SMART delivers.
Three at a time, no more
The number isn't magic but it holds up in practice: more than three simultaneous goals means none of them gets a fixed place in everyday life — not out of laziness, but because the available occasions are limited.
Six goals is in truth a wish list. What that does in your head is covered in the piece on chasing too many goals at once.
An explicit second list helps: things that matter but will not happen this quarter. That isn't renunciation, it's scheduling — and it stops them running along as background guilt.
Adjusting is part of it
A goal still worded exactly as it was four weeks ago is usually too general. Good goals get more precise on first contact with reality.
Three typical corrections:
- The occasion doesn't fit. Sunday afternoon sounded good and is in fact the busiest part of the weekend. Change the occasion, not the goal.
- The unit is too big. Thirty minutes drops out more often than ten. Better ten that happen.
- The goal was really a different one. After three weeks it sometimes turns out this wasn't about the job change but about a conversation you haven't had. Then the work wasn't wasted.
Keeping goals and routines in one place makes corrections visible sooner: in Mentavo goals sit beside the daily focus and the routines, so what's due turns up on the relevant day — and after a few weeks it becomes visible what actually took place.
When the goal depends on other people
A large share of what people set out to do isn't fully in their own hands: a promotion, an agreement, a resolution in a relationship. Goals like these fail particularly often — not in the doing, but because they are quietly waiting on somebody else's decision.
The usable form is to cut the goal down to your own share. "Get promoted by March" becomes "by the end of February, have had two conversations in which I named my interest concretely". The outcome stays open; your part becomes unambiguous.
That cut feels like a step backwards, because the thing you actually want disappears from the sentence. In practice the opposite happens: a goal describing only your own share can be assessed without anyone else agreeing — and it still made sense if the answer turns out to be no.
Two questions help with the cut:
- Which part of this would happen even if nobody responded?
- What would have taken place by February that I can still influence now?
What's left is usually smaller than the original goal and considerably closer to what there is to do.
What this article doesn't claim
No goal-setting method has demonstrated superiority, and this piece doesn't propose one. The four questions are an ordering, not a procedure.
It also doesn't claim everyone needs goals. Some people develop along opportunities and get further without formulating any.
And it doesn't claim that failed goals are down to bad wording. Life phases, load and circumstances often explain more than any method.
In closing: a goal needs a Tuesday
The decisive question about a goal isn't how it will be measured. It's when it will next be in front of you.
What you can do rather than what should happen. An occasion that occurs anyway. A first instance with a date. A criterion that tells you it's over.
Everything else is a declaration of intent — and those have never changed a Tuesday.
