Why SMART Goals Are a Trap for Ambitious People

George Doran coined SMART goals in a 1981 management-review article. The idea, reasonable at the time, was that vague managerial objectives produced vague outcomes, and that forcing people to write goals that were Specific, Measurable, Achievable, Relevant and Time-bound would pull performance upward. For ordinary corporate work — hitting a quarterly sales number, delivering a project on time, training a team on a new process — SMART goals are fine. For people trying to do something genuinely ambitious, they are a trap.

The problem is baked into the A. Achievable, in practice, means "I can see how to hit this number from where I'm standing now." By definition, it excludes goals that would require new capabilities, new relationships, or new assumptions about what's possible. If you're already capable of something, it's not really ambition. It's just execution. Ambitious people who set SMART goals quietly narrow their horizons to what their current self can see, and they spend careers executing well-specified versions of the wrong ambition.

The Research That Supports SMART — and Its Limits

Edwin Locke's goal-setting theory, which underpins most of the SMART thinking, was developed in the 1960s and 70s and is one of the best-supported frameworks in organisational psychology. Locke's research showed that specific, difficult goals produce better performance than vague "do your best" goals. The difficulty bit is often forgotten — Locke's data showed that the specific-and-difficult condition outperformed everything else, including specific-and-easy. Difficulty was the variable that mattered most.

SMART goals, as actually used in corporate settings, have gradually eroded the difficulty piece. The A has shifted over forty years from "ambitious but grounded" to "realistic." The T has shifted from a stretch timeline to a comfortable one. The R ("Relevant") often collapses into "relevant to my manager's Q3 priorities," which is a much smaller aim than the original framework intended.

What you end up with is a framework that's excellent at producing moderate, reliable performance and poor at producing anything exceptional. For the majority of corporate work, this is the right trade. For the ambitious individual trying to build a career or a business that isn't like last year's, it's a handbrake.

Where SMART Goals Break Down for Ambitious People

Specific failure modes I've watched repeatedly in executive coaching.

The "Achievable" ceiling

An executive sets a goal of growing her department 30% year-over-year. It's achievable — she can map out exactly how. She hits it. Meanwhile, the division next door doubled, because their head set a goal of 2x and then reasoned backward from that about what would need to be true. The 2x goal wasn't achievable by the standards of Q1 — it required a new hire, a new product line, and a budget fight with finance. The 30% goal was achievable. She ran the race she could already see. Her peer ran a race that required inventing new capabilities, and built those capabilities as a byproduct.

The "Measurable" trap

You optimise what you measure. If your goal is to grow newsletter subscribers by 10,000 this year, you'll spend effort on subscriber acquisition. But the underlying purpose — building a relationship with readers — is hard to measure, and the measurable proxy quietly displaces it. A year in, you have 10,000 more subscribers and they mostly don't read the newsletter. The measurement was achieved; the goal, if the goal was actually the relationship, was missed.

This is Goodhart's Law, stated in 1975: when a measure becomes a target, it ceases to be a good measure. SMART goals are vulnerable to it by design. They require measurability, and the measurable proxy almost always misses something the real objective contained.

The "Time-bound" distortion

Hard deadlines create anxiety, and anxiety narrows creative options. A goal of "launch the new product by December 31" forces the team toward whatever can demonstrably launch by December 31. Often that's a worse version of the product than the team would have shipped two months later. The deadline wasn't real; it was a SMART artefact. The framework demanded a date, so a date was chosen. The date then shaped the work.

Some goals genuinely need deadlines — regulatory filings, external commitments, contracts. Most personal-development goals and many strategic goals do not. The T in SMART imposes a constraint that's rarely warranted.

The Alternative: Aspirational Objectives with Measurable Steps

The replacement I use is a simple two-layer structure. A top-layer aspirational objective — something bigger than what I can currently see how to achieve. A bottom-layer of measurable, time-bound actions — specifically the SMART version of what I'm doing this quarter toward the aspirational objective.

The aspirational objective is explicit about not being achievable yet. "Build a consulting practice that can sustain my family on two days a week of work" is an example. When I set it, I had no idea how I'd get there. I wasn't supposed to know — that was the point. The aspiration was big enough to require new capabilities.

The quarterly SMART goals, underneath, were things like "close three retained clients by end of Q2" or "write and publish six case-study pieces by end of Q3." These were achievable, measurable, time-bound. They were also obviously inadequate to achieve the aspiration on their own. That's fine — the SMART bits are the next step, not the whole journey.

The structure forces a specific kind of thinking. Every quarter, I ask: given where I am, what's the best next step that's achievable and would plausibly move the aspiration forward? This is different from asking "what's achievable?" in isolation, because the aspiration is pulling the possible next steps toward harder, more ambitious choices.

Specific Examples of the Two-Layer Model

Aspirational objective: Become known inside my industry as the person people call for complex go-to-market problems in mid-market SaaS, within three years.

Q1 SMART goals:

• Publish 6 long-form pieces on specific GTM topics by March 31.
• Run 2 live workshops with target-audience attendance by end of Q1.
• Conduct 15 structured interviews with senior GTM leaders, one per week.

Notice the aspiration isn't measurable in any SMART way. "Become known as" is fuzzy. Three years is distant. The audience is specific but the metric of recognition isn't. And that's the point — the aspiration is shaping the direction of the quarterly work without pretending to be a quarterly goal itself.

The Questions That Test Your Goals

When you've written a goal, apply three tests before committing:

• If I hit this exactly, will my life be meaningfully different? If the honest answer is no, the goal is too small. You've written a task in the language of a goal.
• Can I already see how to do this? If yes, and the goal is meant to be ambitious, it's probably not. Truly ambitious goals have, at the time of setting, at least one piece you don't yet know how to do.
• Am I trying to be careful or am I trying to be honest? This one's uncomfortable. If you look at what you just wrote and you can already feel yourself planning not to fail, you've set the wrong goal. You've chosen protection over ambition.

Most SMART goals fail the first two tests. They're tasks dressed up as goals. They're achievable because they're small. They're specific because nothing bigger would be achievable. The framework is doing what it was designed to do — produce reliable moderate performance — and most ambitious people don't actually want that, even if they've been trained to think they do.

The Cost of the Alternative

In fairness: aspirational goals have failure modes too. You can set a goal so big that it produces paralysis rather than action. You can chase a vision that turns out to be wrong, and waste years on it. You can use the aspiration as a way to avoid accountability on the quarterly work, because the big thing isn't achievable this year anyway.

The defences are specific. First, the quarterly SMART layer is non-negotiable — you still deliver measurable progress every quarter, even while the aspiration is years out. Second, the aspiration gets reviewed annually and adjusted; it's not a sacred text. Third, if no reasonable quarterly SMART goal would move the aspiration, that's data — either the aspiration is wrong or the bridge to it hasn't been built yet.

The framework isn't perfect. It's just meaningfully better, for ambitious people, than optimising the SMART layer on its own.

Who Should Ignore This Advice

Honest caveat. If your job is genuinely about reliable execution — you're an operations manager, a project manager, a compliance officer, a controller — SMART goals are right for your work. You don't want ambiguity in your quarterly objectives. You want predictable delivery. The framework is well-designed for you.

If your job involves meaningful creation — building a business, building a career in a direction that doesn't already exist, writing something new, selling something new — the SMART framework is, quietly, too small a container for what you're trying to do. Use it for the tactical layer. Don't let it define the whole picture.

The specific tell: if your most ambitious peers, the ones whose careers have compounded hard over a decade, would look at your goals and describe them as "solid" rather than "ambitious," you're living inside the SMART framework in a way that's costing you. Solid is not the compliment it sounds like.