SMART
A test for goals you already have — which is not the same as a way to write them.
What is SMART?
SMART is five criteria: Specific, Measurable, Achievable, Relevant and Time-bound. Almost everyone has met it, most people can recite it, and two of those five words are not the ones the man who coined it actually wrote.
The important thing about SMART is what it was designed to be: a test applied to objectives you already have, not a machine for producing them. That distinction decides whether it helps or hurts as a prompt. Ask a model for "SMART goals" with no other input and it will give you five criteria satisfied perfectly — specific, measurable, time-bound, and set at a level anybody would hit by doing nothing differently. It has to: two of the five criteria actively reward caution, and nothing in the acronym asks how hard the goal should be. SMART with no baseline is a formatting exercise. Supply the current numbers and the ambition, and it becomes what Doran meant.
Where SMART Came From
George T. Doran, Management Review, November 1981
SMART has an exact source, which is rare here. George T. Doran, then director of corporate planning at the Washington Water Power Company, published "There's a S.M.A.R.T. way to write management's goals and objectives" in Management Review, volume 70, issue 11, pages 35–36. Two pages, forty-odd years ago, and it is still the default way organisations write objectives.
The A and the R have quietly changed meaning
Doran's five were Specific, Measurable, Assignable, Realistic and Time-related. The modern "Achievable, Relevant" is a later rewrite by other hands. The loss worth caring about is Assignable — who is going to do it — which vanished entirely. A goal with no named owner is a wish with a deadline, and the original acronym guarded against exactly that. Put it back in your prompt whatever the poster on the wall says.
Why the substitution made SMART weaker
Look at what the two versions optimise for. Assignable and Realistic ask who and is this grounded. Achievable and Relevant ask can we hit it and does it matter — and the first of those is a question a nervous team answers by lowering the target. Doran's version had one caution criterion; the modern one has two, and no owner.
The 5 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
Name the metric and the population it applies to. "Improve customer satisfaction" is a category; "raise CSAT on tickets that required an escalation" is a goal, because you can tell whether it happened.
The half that gets left out is from what. A target with no baseline cannot be judged as ambitious or timid, and it is the single most common omission in a SMART prompt. State the query or method too, so nobody wins by changing the measurement.
Not the team. A person or a role, one per goal. "The support team will reduce…" gives everybody a share of the responsibility, which is the same as nobody having it. If you also want the modern Achievable, ask for it separately rather than trading the owner away.
Realistic is not a promise, it is a claim with reasoning behind it — and the reasoning is the useful part. "We hit this rate in Q1 before the volume rise, so this is a return rather than a record" is checkable. "We think we can do it" is not.
A single end date thirteen weeks out is a goal nobody looks at for twelve of them. Give the deadline a checkpoint, because the value of the T is that somebody notices early enough to act.
One Task, Before and After
The task: Three quarterly goals for a six-person customer support team. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.
Write some SMART goals for my support team.
Eight words. You will get five perfectly-formed criteria wrapped around targets like "improve first-response time by 10%" — invented, unowned, and measured against a baseline the model made up.
Write three quarterly goals for a customer support team, each one specific, measurable, assignable, realistic and time-bound. Baseline, so the goals are set against something real: first-response time is currently 9.4 hours median, CSAT is 4.1 out of 5 across 1,900 rated tickets last quarter, and 31% of tickets are reopened at least once. The team is six agents and one lead. No headcount is being added and the ticket volume is forecast to rise about 15%. Work through what each target would actually require from a six-person team before you propose it, and weigh it against the volume rise. The ambition is deliberate: these should be uncomfortable but reachable, not goals engineered to be passed. If a target you propose would be met by doing nothing differently, raise it and say so. Restore the owner. Doran's original A was Assignable, not Achievable - every goal must name the role accountable for it, not the team as a whole. Write 400 to 500 words as three numbered goals. Under each, give one line per criterion, in this order: Specific, Measurable, Assignable, Realistic, Time-bound. For example: ``` Goal 2 - Cut ticket reopens. Measurable: reopen rate from 31% to 20% of tickets, measured monthly on the same query. Assignable: the support lead, with the escalation owner accountable for the top three reopen causes. Realistic: 20% was the rate in Q1 before the volume rise; this is a return, not a new record. ``` Every number you propose must be justified against a baseline figure above. Do not invent benchmarks, industry averages or targets you cannot trace to the numbers given, and do not propose a goal that requires headcount.
Ninety-one, and the paragraph doing the most work is the baseline — five numbers that turn every target from a guess into a claim somebody can argue with.
Ninety-one, and nothing in the score can tell a brave goal from a safe one
One check is structurally out of reach, and the risk that actually matters is not measured anywhere:
No persona slot — SMART is five criteria, not a brief. A role is simply outside the acronym here: add "you are a head of support" if you want the points, and expect the same goals.
The whole risk, and completely invisible. "Cut median response from 9.4 hours to 9 hours" and "…to 4 hours" score identically — both are specific, measurable, time-bound and owned. Only the baseline you supply lets anyone tell which is a goal and which is a formality.
A target with no stated method can be met by changing the method. "Measured monthly on the same query" costs six words and no rubric rewards it.
Which is why the most useful line in a SMART prompt is not one of the five criteria: "if a target you propose would be met by doing nothing differently, raise it and say so." Left alone, a model optimises for passing the test — because passing the test is literally what SMART asks for.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
[Baseline first — the current numbers, the team size, the constraints. Without this the rest is formatting] [State the ambition: uncomfortable but reachable, and raise any target that would be met by doing nothing differently] Specific: [The metric and the population it applies to] Measurable: [From what, to what, measured how and how often] Assignable: [The named role accountable — not the team] Realistic: [Why it is reachable, as an argument against a real figure] Time-bound: [The date, plus a checkpoint and what result triggers a re-plan] [Every number must trace to a baseline figure above. No invented benchmarks or industry averages]
When SMART Fits — and When It Does Not
- Quarterly and annual objectives where the current numbers are known.
- Performance reviews and development plans, which need an owner and a date.
- The key-results half of an OKR, once the qualitative objective is already written.
- Onboarding and first-90-days plans for a new hire.
- Personal goals — fitness, study, career changes — where the baseline is honest.
- Auditing goals somebody else wrote, which is the job Doran designed it for.
- Research and exploration, where the right measure is the thing you are trying to find.
- Ambitious or transformational goals — two of the five criteria pull the target downward.
- Creative work. "Write a better product page" does not survive being made measurable.
- Anything with no baseline. Without a starting number, SMART is formatting.
- The objective in an OKR, which should be qualitative and inspiring. SMART fits the key results.
10 Ready-Made SMART Prompts
Every prompt below was produced by the Frompting generator with SMART selected — not written by hand for this page. Each is scored by our prompt checker; the median is 87/100. Click one to open it, then copy.
Quarterly goals for a support team 81
You are a seasoned customer support strategist. Your task is to craft a set of quarterly objectives for a customer support team. First, define each objective with a clear, concrete action the team will undertake. Second, attach a quantifiable target that indicates success (e.g., percentage improvement, volume count). Third, ensure each objective is realistic given the team’s current capacity and resources. Fourth, align every objective with the broader business priorities of the organization. Fifth, specify that each objective must be completed by the end of the upcoming quarter. The deliverable should be a markdown list of **[NUMBER_OF_GOALS]** objectives, each presented as a single sentence followed by a brief bullet‑point note of the metric and deadline. Keep the total length between 150–250 words. Quality criteria: - Clarity: each objective is unambiguous and actionable. - Measurability: the metric is specific and can be tracked. - Alignment: objectives reflect the team’s role in supporting overall company goals. Exclude any references to frameworks, acronyms, or methodology names. If any essential detail (such as the exact metric to use, the team’s current capacity, or the company’s strategic focus) is unknown, indicate it with a placeholder in the form **[PLACEHOLDER_LABEL: brief hint]** and proceed. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop.
Objectives for a first-time sales manager 88
You are a seasoned sales leadership consultant. Your task is to craft a concise set of performance objectives for a first‑time sales manager. 1. Define a clear, concrete objective that specifies exactly what the manager should achieve. 2. Attach a quantifiable metric so progress can be tracked. 3. Ensure the target is realistic given the manager’s experience and resources. 4. Align the goal with the broader sales strategy and business priorities. 5. Set a definitive deadline for completion. The objectives should be written for **[AUDIENCE: e.g., the sales manager’s direct supervisor]** and presented as a bullet list, each bullet no longer than 30 words. **Quality criteria**: - Each objective is unambiguous and actionable. - Metrics are precise and verifiable. - The list reflects a balanced mix of short‑term and longer‑term targets. **Boundary**: Do not include any training or onboarding activities—focus solely on performance goals. If any essential detail is missing, state your assumption and ask up to three clarifying questions before finalizing the objectives.
Development goals for a performance review 92
You are a professional career development coach tasked with drafting concise personal development goals for an upcoming performance review. The goals must be clear, quantifiable, realistic, aligned with the employee’s responsibilities, and include a target completion date. Write **four** goals, each presented as a single sentence followed by a brief (1-2 line) explanation of how progress will be tracked. - Total length: **≈ 340-450 words**. - Use a professional yet approachable tone. - Ensure each goal is directly actionable and includes a specific deadline. **Quality criteria**: 1. Each goal is unambiguous and includes a measurable indicator. 2. The explanation ties the indicator to a concrete tracking method. 3. The set of goals collectively supports the employee’s growth and the organization’s priorities. **Boundary**: Do not include any personal strengths, weaknesses, or past performance details that are not provided. If any essential detail is missing, state your assumption and ask up to three clarifying questions before finalizing the goals. [ROLE]: Specify the employee’s job title (e.g., Software Engineer, Marketing Analyst). [DEPARTMENT]: Specify the department or functional area. [TIMEFRAME]: Specify the review period or target end date for the goals (e.g., Q4 2024). Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Marketing goals for a launch quarter 87
You are a seasoned go‑to‑market strategist tasked with crafting a concise set of marketing objectives for an upcoming product launch quarter. First, define the precise outcome you want to achieve for the launch, describing the product, target market, and desired market impact. Next, translate that outcome into quantifiable targets (e.g., revenue, lead volume, conversion rate, brand awareness lift). Then, ensure each target is realistic given the resources, budget, and team capacity you have. After that, confirm that the targets align with the overall business priorities and the value proposition of the product. Finally, attach a clear deadline that marks the end of the launch quarter and any intermediate milestones needed to track progress. **Output**: a bullet‑point list of 5 marketing goals, each following the above progression, limited to 150 words total. **Quality criteria** - Each goal is unambiguous and can be verified with a single metric. - The set collectively covers acquisition, engagement, and brand positioning. - The language is concise, professional, and free of filler. **Boundaries** - Do not include detailed tactical plans, budget line items, or channel‑by‑channel tactics. If any essential detail is missing, state your assumption and ask up to three clarifying questions before finalizing the goals. [PRODUCT TYPE]: brief description of the product being launched [BUSINESS MODEL]: B2B SaaS / B2C consumer / physical goods / services (select one) [TARGET SEGMENT]: key characteristics of the primary market (e.g., industry, size, demographics) [POSITIONING STATEMENT]: core positioning phrase for the product [GO‑TO‑MARKET MOTION]: primary sales/marketing motion appropriate to the business model [PRICING MODEL]: chosen pricing approach (e.g., subscription, tiered, value‑based) [LAUNCH SEQUENCE]: high‑level launch phases (e.g., beta → GA, soft launch → full rollout) [KEY ECONOMIC METRIC]: most relevant unit‑economics metric for the model (e.g., CAC payback, contribution margin) Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
Goals for reducing technical debt 69
You are an experienced engineering manager tasked with crafting clear, trackable objectives for an engineering team focused on reducing technical debt. Your output should be a concise list of goals, each written as a single statement that: 1. Defines exactly what the team will address (e.g., specific code areas, backlog items, or architectural concerns). 2. Includes a quantifiable target or metric that can be measured (e.g., percentage reduction, number of tickets closed, or defect count). 3. Describes a realistic effort level given the team’s capacity and resources. 4. Aligns with the broader product or business priorities of the organization. 5. Specifies a deadline or time window for completion. Write **5–7** such goals, each no longer than **30 words**. Present them as a numbered list. Quality criteria: - Each goal must be unambiguous and directly actionable. - Metrics should be concrete and verifiable. - Timeframes must be realistic for an engineering team. [TEAM SIZE]: provide the number of engineers on the team. [CURRENT DEBT METRIC]: indicate the current measure of technical debt (e.g., % of code with high cyclomatic complexity, number of legacy modules). [PRIORITY AREAS]: list the top areas or systems where debt reduction is most critical. If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before finalizing the goals.
Fitness goals from a standing start 83
You are a personal fitness coach who designs beginner-friendly workout plans. Your client is a complete novice with no prior exercise experience. Create a set of fitness objectives that are clear, trackable, realistic, relevant to a healthy lifestyle, and include a defined timeline. The output should be a concise list of five goals, each described in a single sentence, followed by a brief (30–50 word) explanation of how to achieve it. Total length: approximately 250 words. Quality criteria: - Each goal is precise and actionable. - Progress can be quantified with simple metrics. - Goals are attainable for someone starting from zero and align with overall health improvement. Exclude any advanced training techniques, equipment requirements beyond basic bodyweight movements, and medical advice. If any essential detail is missing, state your assumption and ask up to three clarifying questions before finalizing the goals. [FITNESS FOCUS]: specify the primary area (e.g., cardiovascular endurance, strength, flexibility). [TIMEFRAME]: indicate the desired period to achieve the goals (e.g., 8 weeks, 3 months). [AVAILABLE DAYS PER WEEK]: indicate how many days the client can commit to training. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
First-90-days goals for a new hire 68
You are an experienced HR strategist tasked with creating a set of clear, trackable onboarding objectives for a new employee’s first 90 days. The objectives must be organized so that each goal: 1. Describes exactly what the employee should accomplish. 2. Includes a way to measure success. 3. Is realistic given the employee’s starting point. 4. Aligns with the team’s and organization’s priorities. 5. Specifies the deadline or milestone within the 90‑day period. Produce **five** concise goals, each presented as a single paragraph (≈40–60 words). Use a professional yet approachable tone. **Include placeholders for any details you do not have:** - [ROLE: specific job title of the new hire] - [TEAM: name of the team or department] - [KEY RESPONSIBILITIES: top 2‑3 duties the role will focus on] If any of these placeholders are unknown, state your assumption before drafting the goals and ask up to three clarifying questions to fill the gaps. **Quality criteria:** - Each goal must be actionable and measurable. - The set of goals should collectively cover learning, contribution, and integration aspects. - Language should be clear, free of jargon, and suitable for a new employee handbook. **Boundary:** Do not include any company‑specific policies, compensation details, or performance rating scales.
Goals for reducing customer churn 81
You are a strategic growth analyst tasked with crafting a set of actionable objectives to reduce customer churn. Your work should be organized as a progressive series of statements that flow from a clear definition of the desired outcome, through quantifiable targets, realistic pathways, alignment with business priorities, and a concrete deadline. The deliverable is a concise plan of **four to six objectives**, each written in plain language and limited to **no more than 120 words total**. Present the objectives as a numbered list. **Quality criteria**: 1. Each objective must be directly actionable and tied to a measurable indicator. 2. The plan should reflect feasibility given typical SaaS unit‑economics and cohort‑analysis considerations. 3. Language must be clear, free of jargon, and suitable for presentation to senior leadership. **Assumptions**: state any assumptions you make about current churn rate, customer segmentation, or resource availability. If key details are missing, include up to three clarifying questions such as: - What is the current monthly churn percentage? - Which customer segments are most at risk? - What budget or headcount can be allocated to retention initiatives? [CURRENT_CHURN_RATE]: provide the present churn metric (e.g., “5% monthly”). [TARGET_REDUCTION]: specify the desired reduction amount (e.g., “reduce churn by 2 percentage points”). [TIMEFRAME]: indicate the period for achieving the reduction (e.g., “by Q4 2025”).
Goals for a fundraising campaign 88
You are a nonprofit fundraising strategist. Your task is to craft a set of clear, trackable objectives for a fundraising campaign. First, define each objective with a precise description of what the campaign will achieve. Second, attach a quantifiable target that can be measured (e.g., dollar amount, donor count, event tickets). Third, ensure each objective is realistic given the organization’s resources and past performance. Fourth, link each objective to the mission and strategic priorities of the nonprofit. Fifth, specify the exact deadline or time window for each objective. Produce **five** objectives, each presented as a single concise paragraph (≈40–50 words). The output must be written in a professional yet approachable tone, free of jargon, and each paragraph should stand alone without headings or bullet points. Quality criteria: 1. Every objective is unambiguous and includes a numeric target. 2. The objectives collectively cover donor acquisition, revenue growth, donor retention, event participation, and awareness. 3. The timeframes are realistic and aligned with typical campaign cycles. Exclude any assumptions about the nonprofit’s size, budget, or staff unless you state them explicitly. If any required detail is unknown, use a placeholder in the form **[PLACEHOLDER: brief hint]** (e.g., [TARGET_AMOUNT: desired fundraising total]). If you need clarification, first list up to three high‑value questions, then state any assumptions you are making before drafting the objectives. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
Learning goals for a career change 96
You are a career transition coach specializing in data analysis. Your task is to create a concise, step-by-step list of learning objectives for a person who is switching careers to data analysis. 1. Begin with a clear, concrete statement of what the learner wants to achieve in data analysis. 2. Follow with criteria that allow the learner to track progress (e.g., specific metrics, milestones, or deliverables). 3. Ensure each objective is realistic given the learner’s background and resources. 4. Align the objectives with the typical responsibilities of a data analyst role. 5. Conclude with a realistic schedule that outlines when each objective should be completed. **For whom:** [TARGET AUDIENCE: specify the learner’s current profession or background, e.g., “marketing manager with 5 years of experience”]. **Timeframe:** [TIME HORIZON: indicate the overall period for the transition, e.g., “6 months”]. **Output:** a plain-text list of 5-7 learning objectives, each no longer than two sentences, followed by a brief timeline table (objective | target date). Total length ≈ 200 words. **Quality criteria:** - Objectives are specific enough that the learner can verify completion without external validation. - Progress metrics are quantifiable (e.g., “complete 3 SQL projects on GitHub”). - The schedule respects realistic pacing for a career changer. If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three clarifying questions before finalizing the objectives. Note on length: this supersedes any word count given above. Covering the 5 sections and the table needs roughly 590–790 words in total. Use that range rather than compressing any section to fit a smaller one.
Scores range from 68 to 96. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.
SMART vs the Alternatives
The closest sibling, and it adds the slot SMART lacks: Action. SMART says what the goal is; TOAST also asks what you are going to do about it.
What to run first. SWOT tells you which goals are worth setting; SMART makes the ones you chose checkable.
For reporting rather than setting. PPP is how you tell someone how the goal is going; SMART is how you wrote it.
The framework for when the quarter changes underneath the goal. SMART assumes a stable world for thirteen weeks; OODA is what to do when that assumption breaks.
The other end of the same cycle. SMART sets the target; STAR is how you describe having hit it in a review or an interview.
Five Ways People Get SMART Wrong
The defining SMART failure. Without "from what", a target is unjudgeable and the model will invent a starting point to make its number look reasonable. Five current figures at the top of the prompt change everything downstream.
Asked to make a goal achievable, a model lowers it. That is the criterion working as written. If you want a goal that requires a change in behaviour, you have to say so explicitly — nothing in SMART will.
Doran wrote Assignable and the modern version dropped it. Shared accountability is the same as none; name a role for every goal.
If the query is not fixed, the metric can be met by redefining it. State how it is measured and how often, in the goal.
A deadline with no checkpoint is discovered too late to act on. Give every goal a mid-point read and say what result triggers a re-plan.
Some objectives genuinely are not quantifiable, and forcing a number onto them produces a proxy metric that gets optimised instead of the goal. Use SMART where it fits and say plainly when it does not.
SMART Questions
What does SMART stand for?
Today: Specific, Measurable, Achievable, Relevant, Time-bound. Originally: Specific, Measurable, Assignable, Realistic, Time-related.
Who invented SMART goals?
George T. Doran, in "There's a S.M.A.R.T. way to write management's goals and objectives", Management Review 70(11), November 1981, pages 35–36. He was director of corporate planning at the Washington Water Power Company at the time.
Is it Achievable or Assignable?
Doran wrote Assignable — who is going to do it. Achievable came later, from other authors. The substitution cost the acronym its only question about ownership, which is why this page recommends putting Assignable back in your prompt.
Why do SMART goals end up unambitious?
Because two of the modern five reward caution and none of them asks how hard the goal should be. Supplying a baseline and stating the ambition explicitly is the fix; without it, the safest target that satisfies all five criteria is also the one most likely to be produced.
Are SMART goals the same as OKRs?
No, though they combine well. An OKR objective is meant to be qualitative and ambitious; the key results underneath it are where SMART belongs.
Does every goal need all five criteria?
No, and treating it as mandatory is how organisations end up measuring proxies. Where a genuine outcome cannot be quantified, say so rather than inventing a number that will be optimised in place of the real thing.
Generate a SMART Prompt Instantly
Skip the manual template — Frompting applies SMART to your topic in one click.
Try it FreeFramework Details
| Name | SMART |
| Stands for | Specific-Measurable-Achievable-Relevant-Time-bound |
| Domain | Strategy & Planning |
| Steps | 6 |
| Access | Pro |