SMART goals define exactly what you're trying to achieve, by when, and how you'll know you've succeeded. This guide covers the framework and the tracking cadence that keeps goals alive past week six.
SMART goals define exactly what you're trying to achieve, by when, and how you'll know you've succeeded. George T. Doran introduced the framework in 1981 in Management Review, and it became the most widely adopted goal-setting system in organizational management.
The evidence is substantial: specific, challenging goals outperform vague "do your best" instructions in 400+ studies spanning 40,000+ participants. That's Locke and Latham's 35-year meta-analysis, one of the most replicated findings in organizational psychology.
The catch: 90% of businesses fail to achieve their strategic objectives even after writing structured goals. Setting a SMART goal and achieving one are two separate problems. This guide covers both: the framework itself and the tracking cadence that keeps goals alive past week six.
One caveat: the original "A" in SMART is not what most sources claim, and that distinction matters for remote teams.
SMART goals are objectives written to five criteria: Specific, Measurable, Achievable, Relevant, and Time-bound. The framework gives any goal a testable format: you can verify whether it qualifies before starting, and confirm whether you succeeded when done.
The standard writing formula: "[Action verb] [specific outcome] by [date] as measured by [metric or KPI] by [execution method]."
One example: "Increase monthly organic traffic from 10,000 to 15,000 sessions by September 30, 2026, as measured by Google Analytics, by publishing 3 SEO-optimized articles per week."
Most sources attribute SMART to Doran's 1981 article in Management Review. They're right about the attribution but wrong about the acronym. Doran's original criteria were: Specific, Measurable, Assignable (who will do it), Realistic (what results can realistically be achieved given available resources), and Time-related.
The "Achievable" and "Relevant" substitutions happened through practitioner adoption in the 1990s and 2000s, not through any revision of Doran's original text. No top-10 SERP article on SMART goals acknowledges this distinction.
The irony: Doran's original "Assignable" criterion captures exactly the team-ownership dynamic that remote work demands (who owns the goal, not just whether it's attainable). The modern substitution quietly discarded that angle.
Doran's original "Realistic" was explicit about resource constraints. The modern "Achievable" carries a different implication: that goals should target 100% attainment.
This sits in direct tension with Locke and Latham's finding that difficult goals consistently outperform easy ones. Specific, difficult goals improve performance by 10-25% vs. vague targets across 35 years of research.
The practical resolution: calibrate to 70-80% confidence, not 100%. A goal you're certain to hit incentivizes sandbagging. A goal you're 70% sure you can hit keeps difficulty high enough to produce the performance effect while staying within reach.
Each criterion does a distinct job. Missing one removes a specific feedback signal, not just a box on a checklist.
Specificity answers who is doing what, exactly, and why it matters. "Improve customer satisfaction" fails the specificity test. "Increase NPS in the enterprise segment from 32 to 45 by Q3 2026" passes.
The test: a third party should be able to read the goal and know exactly what success looks like without any follow-up questions. If the goal requires interpretation, it isn't specific enough.
A measurable goal has a clear metric and a baseline. Without a baseline, you know the endpoint but not the distance traveled: progress is invisible.
The metric also creates the feedback signal: if you're off track in week three, the number tells you before the deadline forces the realization.
"Improve team engagement" is not measurable. "Increase monthly 1:1 completion rate from 60% to 90% by Q2, tracked in the team dashboard" is. The baseline (60%), the target (90%), and the measurement method (team dashboard) are all explicit.
The "Achievable" criterion guards against aspirational targets that collapse under real constraints. The calibration question is not "can I imagine doing this?" but "given current resources, constraints, and history, is this within reach?"
The 70-80% confidence benchmark is the working answer: difficult enough to require focused effort, realistic enough that focused effort is sufficient.
Goals at 100% confidence tend to be too easy. Goals below 50% confidence tend to demotivate once initial momentum fades, because the gap between effort and visible progress grows.
A relevant goal passes the "why does this matter now?" test. Relevance asks whether this goal is the right priority at this moment, aligned with broader strategy, and within the goal owner's actual scope of influence.
Goals that pass the other four letters but fail relevance are a form of goalwashing. They look complete on paper but deliver no organizational value, because they aren't connected to what the team is actually trying to move.
A deadline without a tracking cadence is just a date. The "Time-bound" criterion is the most under-developed letter in nearly every SERP article on SMART goals, and it's where most goals die in practice.
For remote and async teams specifically, Time-bound requires three distinct things: a hard deadline, intermediate milestones with specific dates, and a structured check-in cadence that surfaces progress without requiring a synchronous meeting. The async execution section below covers this in detail.
Step | Question to answer | Example |
|---|---|---|
Specific | What exactly am I trying to achieve? | Increase enterprise NPS |
Measurable | How will I know I succeeded? | From 32 to 45, tracked monthly via in-app survey |
Achievable | Is this realistic given resources? | Q3 is 3 months; 13 points is challenging but feasible |
Relevant | Does this tie to team strategy? | Retention is the top company priority this quarter |
Time-bound | What is the exact deadline? | By September 30, 2026, with biweekly milestone reviews |
Full goal | "Increase enterprise NPS from 32 to 45 by September 30, 2026, measured monthly via in-app survey, by implementing 5 targeted onboarding improvements." |
SMART goals are not the only goal-setting system, and they're not always the right one. Understanding where SMART fits in the broader framework landscape prevents the common mistake of applying it universally.
Dimension | SMART Goals | OKRs | BHAG | WOOP |
|---|---|---|---|---|
Level | Individual / task | Team / company / strategic | Organization (10–30 yr) | Individual |
Focus | Output (what you'll do) | Outcome (what changes) | Visionary aspiration | Psychological contrasting |
Attainment target | 100% (achievable) | 60–70% (ambitious) | Directional | Completion of plan |
Cycle length | 30–90 days | Quarterly | Multi-year | Task-specific |
Best for | Individual performance, operational tasks | Strategy, innovation, cross-team alignment | Cultural north star | Obstacle anticipation |
Weakness | Can incentivize sandbagging | Harder to adopt; requires org commitment | Not executable | Doesn't scale to teams |
How SMART goals compare to OKRs, BHAG, and WOOP
Sources: [IdeaPlan, Harmny, Perdoo, Teamflect]
The emerging practitioner consensus across IdeaPlan, Perdoo, Oboard, and Teamflect is consistent: these frameworks solve different problems and work better together than either alone.
OKRs set the strategic direction at 60-70% attainment targets, designed to be ambitious. SMART goals define the specific, executable steps inside each Key Result.
The hierarchy: strategy is OKR territory; individual execution is SMART territory.
Perdoo's analysis of organizational psychology research quantifies the upside: "Setting specific, ambitious goals lifts an average team to the 80th percentile of performance. Add measurable metrics and regular feedback on progress, and that jumps to the 88th percentile. That's the top 12%!"
Perdoo's critique of SMART goals is worth taking seriously: the "Achievable" criterion rewards 100% attainment by design, which creates pressure to set goals you're certain to hit rather than goals that stretch. When SMART goals feed performance reviews, teams learn that easy targets generate better outcomes than ambitious ones. The behavioral response is rational but damaging.
Operational tasks and deliverables with clear completion criteria suit SMART at 100% attainment. Strategic direction suits OKRs at 60-70%. Using the frameworks in the right contexts removes the structural incentive to sandbag.
No top-18 SERP result addresses this angle, yet it's the central use case for professionals managing goals without passive proximity. Remote and async teams face a structural execution problem that co-located teams avoid: in a shared office, goal drift surfaces naturally.
A manager walks past a desk; a weekly standup reveals who's stuck. Async teams have none of those signals.
The "Time-bound" criterion on a SMART goal looks fundamentally different without an ambient accountability loop. A deadline set in January without a structured review cadence is invisible by February.
51% of organizations don't attempt to develop aligned goals, per a 2020 Phoenix Business Journal study. For distributed teams, the infrastructure gap runs deeper: no ambient proximity signals substitute for structured review.
Time-bound requires explicit milestones for async work, not just a final deadline. Each milestone needs a specific date and a defined output. Not "progress on X" but "draft complete," "first 20 clients surveyed," or "v1 shipped to staging."
The milestone structure becomes the async tracking artifact. Each week, the goal owner updates the milestone checklist in a shared document. No meeting required.
The document is the status report, readable by any stakeholder at any time. This is the practical implementation of the time-blocking approach remote professionals use for deep work: protect the execution time, not just the deadline.
As Tability observed, structured goal cycles are routinely abandoned by week six, not because the goals were badly written, but because the tracking infrastructure never materialized.
The most durable tracking system embeds goal review directly into recurring meetings: 1:1s, weekly team syncs, and quarterly planning sessions.
The SMART goal's metrics appear on the weekly 1:1 agenda as a standing item. The manager and report spend 5-10 minutes on directional flags (on track / at risk / blocked) before discussing other topics. This makes the check-in mandatory rather than optional, and surfaces drift early enough to course-correct before it compounds.
A SMART goal with a deadline is an intention. A SMART goal with calendar blocks for the execution steps is a system. Justin Sung, who researches learning and productivity systems, describes the distinction:
"The point of thinking in systems is that you reduce your reliance on thinking in terms of willpower and motivation. The aim is to reduce your dependency on these two things."
Justin Sung, "How to Build Systems to Actually Achieve Your Goals"
For remote professionals, calendar blocking translates the SMART goal's execution steps into protected time. "Publish 3 articles per week" becomes three recurring 2-hour writing blocks each week, not a weekly target competing with reactive work. The calendar block is the system; the SMART goal is the destination it's pointed at.
For distributed teams, attach this structure to every SMART goal at the time of writing:
The template takes 10 minutes to complete. Skipping it is the primary reason goals fail by week six, not poor goal writing.
Teams routinely abandon the tracking infrastructure that keeps SMART goals alive. The goal-writing phase succeeds; the follow-through doesn't.
Tability's LinkedIn post captures the pattern: "Have you ever started an OKR cycle full of energy… only to quietly abandon it by week 6? You're not alone." SMART goals show the same failure shape: heavy investment in the writing phase, tracking treated as optional.
James Clear's framing of the execution gap is the sharpest description available:
Goals are for people who care about winning once. Systems are for people who care about winning repeatedly.
The goal defines where you're going. The system is what you run every day to get there. Without a system, a well-structured SMART goal still competes with daily friction and loses.
With a system, the daily execution actions become automatic regardless of motivational state. The "Time-bound" criterion produces results only when paired with a structured weekly review cadence. The cadence is the system the framework itself doesn't provide.
Research from ATD found accountability partners and weekly check-ins raise goal attainment from 25% to 95% (treat the direction, not the exact figure, as the signal from a single source). Locke and Latham identified feedback on progress as a required moderator: remove the review loop and the performance effect disappears regardless of how well the goal was written.
The minimum viable tracking cadence for any SMART goal:
This requires 15-20 minutes per week per goal. For most remote teams, that's the missing piece.
The best SMART goal examples are specific enough to borrow directly. Vague templates ("increase revenue by Q4") are prompts, not examples.
Weak goal: Increase revenue this quarter.
SMART goal: Close 12 new enterprise accounts (minimum ACV $50,000) by June 30, 2026, tracked weekly in Salesforce CRM, by running 3 qualified demo calls per day from the existing pipeline.
Weak goal: Grow the blog.
SMART goal: Increase monthly organic blog traffic from 8,000 to 14,000 sessions by September 30, 2026. Measure via Google Analytics. Publish 2 SEO-optimized articles per week starting June 1, with keyword targeting approved by the SEO lead.
Weak goal: Learn AWS.
SMART goal: Complete the AWS Solutions Architect certification by August 31, 2026, by studying 1 hour daily using A Cloud Guru, tracking weekly progress in a Notion dashboard with a monthly accountability check-in.
Weak goal: Improve team engagement.
SMART goal: Increase monthly 1:1 completion rate across the team from 58% to 90% by August 31, 2026. Track in the team calendar system. Schedule recurring 1:1 blocks for all 8 direct reports by June 15.
You cannot measure improvement without knowing where you started. "Increase NPS to 50" is not a SMART goal if your current NPS is unknown.
Before writing the measurable criterion, verify the baseline: pull the current metric, note it in the goal document, and make it an explicit part of the goal statement. A goal with no baseline is a milestone, not a SMART goal.
Distributing attention across 8 active SMART goals doesn't create parallel progress. It dilutes focus until nothing moves.
Asana and experienced managers on r/managers consistently recommend the same limit: 3-5 active SMART goals at one time. Above that, every deadline competes with every other deadline and the Time-bound criterion becomes meaningless.
"Publish a case study by July 31" passes all five SMART criteria. Without the execution steps (who interviews the client, who writes the draft, who approves it, when each step must be complete), the deadline is just a date. SMART goal writing should end with two things: the goal statement and the first three calendar-blocking actions that move toward it.
Experienced managers on r/managers flag the limits of universal SMART application: not everything important is measurable. A goal like "build stronger cross-functional relationships in Q3" has genuine strategic value but resists the Measurable criterion. Forcing a proxy metric (number of coffees scheduled) can make the goal look complete on paper while entirely missing the actual objective.
Use SMART for operational tasks and deliverables with clear completion criteria. For relational, cultural, or exploratory goals, the weekly directional flag replaces the metric as the progress signal.
Writing a goal in January and reviewing it in December is a reporting exercise, not a tracking system.
The Leapsome Workforce Trends Report found that 1 in 3 employees is unsatisfied with how their organization handles goal-setting. The single most common complaint: the absence of structured, ongoing review.
The goal needs a weekly or biweekly review moment built into an existing meeting. A directional flag in the 1:1 agenda takes two minutes and surfaces problems while they're still fixable.
When SMART goals determine performance evaluations, goal difficulty drops structurally. Teams learn that 95% confidence targets generate better review outcomes than 70% confidence targets.
The behavioral response is rational but damaging: easy goals guarantee attainment at the cost of actual performance improvement. The organizational fix: decouple SMART goals from compensation for developmental and strategic goals. Operational tasks (client deliverables, compliance deadlines, process completions) suit SMART at 100% attainment because completion is the correct standard.
Learn how time blocking works, the science behind it, 5 proven methods, common mistakes, and the best apps for remote professionals in 2026.
The Pomodoro Technique breaks your workday into 25-minute focused sprints with 5-minute breaks. Learn the 6-step method, the neuroscience behind it, and how to adapt it for remote work.
Proven time management tips for remote professionals. Frameworks, techniques, and tools to reclaim focus and reduce stress.
