FAST vs SMART Goals Coaching: A Complete Worked Guide

FAST vs SMART goals coaching is most useful when it changes a real decision. A client can write a precise objective and still discover that another department never accepted the work required to achieve it. Equally, discussing an ambitious target every morning does not make the target meaningful or the workload feasible.

Coachful is our #1 recommendation for organizing the coaching side of that work: an original goal worksheet, linked actions, progress evidence and private client conversations. This is our editorial recommendation for the workflow, without a comparative efficacy claim or a promise that software will deliver the goal. External approvals and other people's work remain real dependencies.

Use SMART to examine the objective and FAST to examine how the objective operates among people. The frameworks overlap. The practical aim is a clear result supported by appropriate review, authority and information, rather than a choice of team acronym.

Start with the actual meanings and evidence limits

George T. Doran's 1981 Management Review article introduced Specific, Measurable, Assignable, Realistic and Time-related. It also cautioned against insisting on numerical quantification in every situation and emphasized the objective together with its action plan. The original was management guidance, not a clinical or coaching comparison trial.

Later versions use different words. University of Florida's own organizational guide uses Attainable and Relevant in the middle. State which version you are using rather than attributing every modern variation to Doran. University of Florida: developing SMART goals.

Donald Sull and Charles Sull proposed FAST in their 2018 article: Frequently discussed, Ambitious, Specific and Transparent. They describe company research, a proprietary dataset exceeding half a million goals and a literature review. Their argument concerns organizational goal systems; it is not a randomized head-to-head coaching trial. They also recognize privacy exceptions, the limits of ambition and discussion beyond a fixed annual or quarterly cycle. MIT Sloan Management Review: the original FAST article.

The coaching questions, records and fictional case below are our original applications. They do not reproduce either source's company cases or prescribe a validated combined intervention.

Use SMART to make the objective inspectable

A useful goal statement lets two people assess the same situation without having to guess what the author meant. Using Doran's original version, check the following distinctions. The examples are practical drafting questions, not quotations from his article.

If using the later Relevant criterion, explicitly ask why this goal matters to the client's chosen purpose. Attainable can prompt a resource check, but retain an owner even when Assignable is no longer a letter in your version. These additional questions are worth keeping regardless of the acronym.

A precise goal can still be the wrong goal. “Send twenty emails by Friday” is easy to count but may reward unnecessary contact. Ask what the emails should enable, what a recipient can decline and what evidence would change the plan. Do not use specificity to disguise an unwanted obligation.

For a client learning an unfamiliar task, distinguish learning from performance. Investigating two methods and explaining their limitations is a different goal from achieving an outcome that depends on an untested method. Neither should silently replace the other after a result disappoints. Our SMART goals guide develops objective drafting further.

Build four operating agreements around the goal

Frequently discussed: give the conversation a decision

Our practical adaptation begins with a decision route, not a meeting count. Identify what could change while the work happens: an input arriving late, an unsafe request, a resource conflict or a failed quality check. Decide who should hear about each change and how soon a decision is needed.

A short scheduled review can handle ordinary uncertainty. A separate escalation rule handles information that cannot wait. If a critical input becomes unavailable today, waiting for next month's coaching session may be unreasonable. The coach may help the client prepare a request; the appropriate manager or specialist still makes the decision.

For each review, ask for changed evidence, its consequence and one unresolved decision. Finish with a named owner or an explicit decision to hold. If there is no decision or useful interpretation to discuss, an appropriately shared written update may be enough. Include the time needed to read and answer it.

Ambitious: distinguish a stretch from a commitment

Write down what the client is exploring and what someone is entitled to rely on. A stretch can invite a different method. A committed service date may carry a separate duty. Do not describe a customer's unmet need as a successful experiment simply because the team learned something.

Test ambition against a real constraint. What work will stop, what help has been accepted and what risk remains? “Try harder” does not supply missing permission or create receiving capacity. An aspiration can remain interesting while its current delivery plan is rejected.

Set a boundary before pressure rises. You might agree that an experiment stops when it would require unapproved overtime, exposing personal data or skipping a quality check. Aiming beyond today's performance does not require waiving those conditions. There is no universally correct percentage of missed targets.

Specific: make the evidence compatible across roles

Start with the same list of cases, the same deadline and the same definition of done. A producer may count a draft while a reviewer counts an accepted record. Both stages can be worth tracking, but adding them together as completed outcomes creates an error.

Separate the evidence into action, acceptance and effect. The client may have sent a request; the recipient may have accepted a narrower proposal; the broader result may still be unknown. A useful record can preserve all three states instead of forcing everything into a single green indicator.

Agree how errors will be corrected. Retain the earlier version and explain the change, particularly if a sponsor already received it. If a denominator changes, show the original and revised population. Removing difficult cases can make a percentage rise without any better result.

Transparent: choose an audience and level of detail

Our coaching adaptation uses purposeful visibility rather than universal publication. Identify who needs the objective, the dependency, the operational decision and the private coaching material. Those are not necessarily the same audience.

A colleague may need to know that permission is pending, without receiving the private explanation or the coach's hypothesis about someone's confidence. Ask about reading, editing, forwarding and retention as well as initial access. A sponsor's funding does not settle every disclosure question.

Make the limits understandable to the client. In a practice using a shared operational record, say which content is shared and which stays in the coaching conversation. Do not promise that a colleague will keep an exported document private merely because the original portal has access controls. Our weekly accountability guide offers a separate individual review structure.

Compare the choice against the actual problem

For example, a client deciding whether to apply for a course may privately compare entry requirements and ask one admissions question. They do not need an organization-wide dashboard. A stable duty may likewise need a reliable standard and an exception route rather than a larger target every quarter. Use the smallest change that addresses the actual difficulty.

Follow a complete fictional goal and review cycle

All people, records, dates, figures and outcomes here are fictional. Mina manages an internal archive project. Rafi checks records, Elspeth controls permission for one source and Cleo authorizes the project scope. Inez coaches Mina. They work on ten named records, A–J, rather than an open-ended incoming queue. Times use Europe/London.

In a previous separate ten-record exercise, four records met its deadline and checks. That is a descriptive starting comparison, not a matched control group. Mina initially wants “a FAST goal to finish everything sooner.” She has not yet distinguished a drafted record from one that can actually be released internally.

Complete the objective before raising the ambition

During a 45-minute coaching session on 14 November 2039, Mina identifies that she can prepare records but cannot grant source permission or approve her own quality checks. She drafts the following objective and obtains the relevant colleagues' agreement on 15 November:

By 24 November 2039 at 14:00, complete at least eight of the ten named internal archive records A–J. Complete means the required description and source are present, necessary permission is established and Rafi's check has passed. Mina owns preparation and the status record. Rafi owns the checks he accepts. Cleo authorizes this limited pilot. Ten is an exploration aspiration, not a promise. No record is released without its conditions, and no unapproved overtime is used.

Rafi accepts up to eight minutes for each initial check, with a separate total allowance of 90 minutes for checks, rechecks and the final count review. He also accepts the separately counted coordination work below. Elspeth says she can assess her permission question, without promising approval. Cleo agrees to the limited pilot and says that work beyond it requires another decision.

This makes eight a demanding target compared with the earlier four. It does not establish that eight is guaranteed, or that reaching ten would always be better than protecting the conditions. Mina retains the original ten-record denominator when she learns which cases are difficult.

Write the review and visibility arrangement

The colleagues agree this original operating record before work begins:

• Scheduled discussion: Mina and Rafi meet for 15 minutes on 18 and 21 November to address changed evidence and blocked decisions.
• Earlier trigger: missing permission or a failed check is held and raised with the appropriate owner rather than waiting for the final deadline.
• Authority: Mina can revise her draft; Rafi decides whether his check passes; Elspeth decides her source-permission question; Cleo decides additional scope.
• Visibility: the five participants receive operational status and necessary decisions through the approved internal record. Source files remain with their authorized audiences. Private coaching comments are excluded.
• Count: only records meeting every stated condition count as complete. Drafted, held and not ready remain separate states.
• Ending: review the count at the original cutoff, issue a corrected final notice and make no automatic commitment to the remaining work.

They decline Mina's first suggestion of a daily call. The two planned reviews and an exception route fit their actual needs and capacity better. That is their case choice, not a FAST rule requiring two meetings.

Use the discussion to change actual work

At the 18 November review, Rafi explains that G's description points to the wrong source version. Mina initially treats the file's existence as sufficient. Rafi says it cannot pass his check. They agree that Mina will correct the source reference; he accepts one recheck within the available allowance. Mina uses 15 minutes within her 90-minute production allocation to repair G. Rafi's 12-minute recheck on 20 November passes.

A different obstacle remains for H. Mina asks Elspeth: “Can you authorize use of this source in H for this pilot by 21 November? If not, please tell me whether I should hold it rather than describe it as cleared.” Elspeth's actual reply says: “I cannot authorize this use for the current pilot. The rights question needs review on 2 December. Please leave H held; that date is a review, not promised permission.”

Mina and Rafi read the consequence into their 21 November review: H remains outside the completed count. They do not copy Elspeth's private supporting material into the shared update. Cleo reads the operational dependency and confirms that she is not extending the pilot or overriding the permission owner. These messages and their receiving work are included in the ledger.

The conversations have now produced decisions: repair one record, keep another held and retain the authorized scope. They have not made the original outcome target disappear.

Correct the final count instead of moving the finish line

At the 24 November cutoff, Mina's draft status marks A–H complete because eight records have files. Rafi's final review catches the old mistake: H still lacks permission. Mina corrects the record before issuing the final notice.

The actual result is seven of ten, or 70%, against eight of ten required. It is not eight of eight “available” records. The target is missed by one, and the ten-record aspiration is also unmet. The prior four of ten was 40%, giving a descriptive difference of 30 percentage points; the different exercise and lack of a comparison design prevent a causal claim about the frameworks.

Mina's complete final notice says: “At the original 24 November, 14:00 cutoff, seven of ten named records meet all conditions: A–G. H remains held for permission; I and J are not ready. The eight-record target was missed. An earlier draft incorrectly counted H because a file existed; this notice corrects that count. No additional work or release is authorized by this update. Elspeth's 2 December review remains a future dependency, without a promised outcome.”

Rafi, Elspeth and Cleo each read the notice in the counted closing work. Mina does not claim another reply or a new approval from them. The uncompleted records are visible without assigning their owners an unaccepted extension.

Review the system and the complete effort

In a later coaching review on 26 November, Mina recognizes that the early conversations helped her act on G and obtain an unambiguous answer about H. She is still frustrated by the missed target and by her own mistaken completion entry. Inez does not describe that frustration as resistance or the pilot as a proven performance intervention.

The 15-minute review allocation for each person contains ten minutes of live conversation and five minutes of written handling. Inez sends a bounded comment in Mina's private client conversation: “Your corrected count preserves the original condition. Before another pilot, which dependency would you seek earlier, and who can actually accept that work?” Mina reads and replies that she will first ask about source availability; no new pilot is approved or delivered.

Total actual effort is 497 person-minutes within 555 available, leaving 58. Rafi's checking suballocation uses 64 + 12 + 6 = 82 of its 90 minutes; his other coordination time is separate. Time remaining does not waive permission or create the missing sources. The December review and any further production are future work, excluded from these actual totals.

Organize the coaching record in Coachful

1. Keep the agreed objective explicit. Use an original worksheet to separate the result, evidence, owner, deadline, outside decisions and audience. Check the assigned client's access before using it.
2. Link the client's actions to the goal. Record requesting permission or correcting a draft as actions, while retaining whether the external answer or check is pending. Linked activity is not independent verification.
3. Check what the finish line means. Coachful distinguishes the goal's lifecycle from milestone counts and supports explicit finish-line behavior. Configure and inspect the actual goal rather than treating every completed task as proof of the intended result.
4. Return feedback through a real client-facing route. Coach review on a submitted worksheet is private to the authorized coach team. Use the client's actual conversation for promised feedback, as Inez does, and account for reading and replying.
5. Share an agreed operational update separately. Do not give colleagues or sponsors the client's private coaching material to make the goal look transparent. Preserve the original target and correct mistaken reports.

The product demonstrations here illustrate goal organization and structured questions, not Mina's archive or an automatically generated FAST score. Explore Coachful's features against your actual service and permissions.

Troubleshoot the goal system

Reviews repeat status without decisions: ask what changed, who can act and what decision is needed. Reduce unnecessary meetings only after preserving a route for urgent exceptions.

A stretch becomes a promise: restate the commitment, aspiration and protection conditions before accepting dependent work. A new label cannot undo an earlier promise to a recipient.

The dashboard improves after cases disappear: reconstruct the original population and show any genuine scope change separately. Keep pending, rejected and unfinished cases visible.

Transparency discourages honest reporting: inspect the actual audience, consequences and power relationships. Share the coordination fact at the appropriate level, rather than demanding more private disclosure.

Frequently asked questions

Is FAST better than SMART for coaching?

The original FAST article offers an organizational management argument, not universal comparative coaching evidence. Choose the practices that address the specific problem, and inspect what actually changes.

Can the same goal be both FAST and SMART?

Yes. A clear, owned and dated objective can operate within useful discussions and appropriate visibility. The added practices should help real decisions, rather than add reporting for its own sake.

Does SMART always mean Achievable and Relevant?

No. Doran's original used Assignable and Realistic. Later versions vary. Name the version, retain useful ownership and purpose checks and avoid attributing a modern adaptation to the original author.

Does FAST require everyone to see every goal?

The original emphasizes organizational visibility while acknowledging exceptions. A coaching adaptation should make its audience limits explicit. Private personal goals and confidential records need separate consideration.

How often should goals be discussed?

Agree a rhythm around uncertainty and decision needs, with an earlier route for material changes. Neither a daily meeting nor a quarterly reset is a universal requirement for every coaching client.