SMART goals are objectives written to pass five tests: Specific, Measurable, Achievable (and Assignable), Relevant (and Realistic), and Time-bound. They let a CEO, COO, CFO, or supply-chain director audit the plan without translating slogans.
This guide is for C-Level teams in Mexico–US logistics: cascading strategy into operations indicators (OTIF — On Time In Full —, cost per kilometer, cycle time, audit recovery). OCL Cargo is an autonomous TMS with agents: it turns “M” and “T” into a trip file, not a close Excel. When you audit 100% of the pilot flow, the typical pattern is recovering 5–7% of freight spend in 6–8 weeks.
- Doran publishes SMART (Management Review)
- 1981
- tests auditable in QBR / board
- 5
- ambition above, operable KPI below
- OKR+SMART
- pattern when auditing 100% of pilot freight
- 5–7%
Useful cluster: distribution KPIs · SWOT / FODA · lean supply chain.
What SMART goals are (short answer)
SMART is an acronym for writing management objectives that can be verified. Each letter is a test: if one fails, the objective invites political debate instead of a decision.
In logistics it does not replace a key performance indicator (KPI) dashboard or a transportation management system (TMS). It sharpens the sentence the team commits to close in a quarter: what moves, on which lane, with which metric, who owns it, and by when.
Doran 1981 and the A / R ambiguity
George T. Doran published “There’s a S.M.A.R.T. way to write management’s goals and objectives” in Management Review (November 1981). His original version is not exactly what generic courses teach.
S
Doran 1981 (original): Specific
Modern boardroom reading: Specific
What OCL requires: Subject + lane + scope (not “improve service”)
M
Doran 1981 (original): Measurable
Modern boardroom reading: Measurable
What OCL requires: Number + unit + data source
A
Doran 1981 (original): Assignable
Modern boardroom reading: Achievable
What OCL requires: Named owner + credible path with resources
R
Doran 1981 (original): Realistic
Modern boardroom reading: Relevant
What OCL requires: Aligned to strategy and feasible with capacity
T
Doran 1981 (original): Time-related
Modern boardroom reading: Time-bound
What OCL requires: Close date or window (quarter, 8 weeks)
OCL SMART infographic (five tests)
This is our version — not a clone of SaaS templates. Five overlapping circles with labels, an executive question under each letter, and the Doran note on A and R.
FIGURE 1 · OCL INFOGRAPHIC
Five SMART tests for freight and operations objectives
Primary: Specific · Measurable · Achievable · Relevant · Time-bound. Secondary on A/R: Assignable and Realistic (Doran 1981).
- SSpecificWhat, where, which lane?
- MMeasurableWhich number and source?
- AAchievableAssignable (Doran)Resources + owner?
- RRelevantRealistic (Doran)Tied to strategy?
- TTime-boundClose date?
Print or paste into the QBR: if one letter fails, rewrite before voting the budget.
Doran 1981 framework + OCL operating playbook — calibrate to your KPIs and capacity.
C-Level: OKRs vs SMART and cascade to freight KPIs
The typical leadership mistake is mixing horizons. OKRs (Objectives and Key Results) align ambition. SMART sharpens the operating commitment finance and the control tower can audit.
OKR (ambition and focus)
- Qualitative Objective for unit/company
- Stretched Key Results
- Quarterly alignment cycle
- Useful for “where we are going” and priorities
SMART (auditable close)
- Sentence with number, owner, and date
- Operable KPI or Key Result target
- Short window (quarter / 6–8 weeks)
- Useful for “what will close”
Typical cascade for a Mexico–US shipper or 3PL:
Cascade
From strategy to operable KPI
Strategy
Margin / service
OKR
Quarter focus
KPI
OTIF / cost / cycle
SMART
Owner + deadline
Strategy
C-Level example: Protect margin on Monterrey–Laredo
Write it SMART when…: It drops to a cost or recovery KPI
OKR
C-Level example: Objective: “Freight paid = freight evidenced”
Write it SMART when…: Key Results have a number and an owner
Ops KPI
C-Level example: OTIF, cost/km, shipment cycle
Write it SMART when…: Formula, unit, and source exist (GPS, POD, TMS)
Cash / audit
C-Level example: 5–7% recovery auditing 100% of the pilot
Write it SMART when…: Universe, deadline, and exception owner exist
Letter by letter: executive questions
Use these questions in the board or QBR. If someone cannot answer in one sentence, the goal is not ready.
S — Specific
C-Level question: What moves, on which lane or DC, and what is out of scope?
Typical freight failure: “Improve service” with no route or segment
M — Measurable
C-Level question: Which number, unit, and system is the source of truth?
Typical freight failure: OTIF with OR (inflates the KPI) or Excel without trip IDs
A — Achievable + Assignable
C-Level question: Is there capacity and a named owner?
Typical freight failure: Heroic target with no trucks, dock, or “everyone owns it”
R — Relevant + Realistic
C-Level question: Why this quarter, and does capacity allow it?
Typical freight failure: Pretty KPI that does not move margin or cash
T — Time-bound
C-Level question: Close date or window (quarter / 8 weeks)?
Typical freight failure: “During the year” with no milestones or review
Before / after: SMART rewrites (Mexico logistics)
Real boardroom examples — not diets or marathons. The right column passes the five tests.
Improve OTIF
After (SMART): Raise OTIF (AND) from 86% to 92% on Monterrey–Laredo in Q3; owner: Tower manager; source: TMS + POD
Letters that were missing: S, M, A, T
Cut freight cost
After (SMART): Cut net cost/km 4% on Bajío–Laredo vs Q2 without OTIF under 90%; owners: CFO + traffic
Letters that were missing: S, M, R, T
Speed up shipments
After (SMART): Cut pickup–POD cycle from 6.2 to 4.5 days in 8 weeks across 2 pilot DCs; owner: operations
Letters that were missing: S, M, T
Audit freight better
After (SMART): Audit 100% of the pilot (~800 trips/month) and recover 5–7% of spend in 6–8 weeks; typed exceptions to accounts payable
Letters that were missing: M, A, T
Digitize operations
After (SMART): Close 95% of pilot trips with a trip file (rate+GPS+POD) before pay in 8 weeks; owner: accounts payable
Letters that were missing: S, M, R, T
Template + checklist for board and QBR
Copy the template. If a field stays empty, the goal does not enter the board pack.
| Field | What to write | Example |
|---|---|---|
| Objective (1 sentence) | Verb + metric + scope | Raise OTIF AND to 92% on MTY–Laredo |
| Baseline | Current number + period | 86% in Q2 (n=1,240 deliveries) |
| Target | Number + unit | 92% |
| Source of truth | System / evidence | TMS + POD tied to trip ID |
| Owner | Name + role | Ana R. — Tower manager |
| Deadline | Date or window | Close 30-Sep (Q3) |
| Out of scope | What does not count | Spot loads outside SLA |
| Review | Cadence | QBR + biweekly check |
Elige un paso para ver el detalle
Detalle del paso · 01
S — Closed scope
Check 1
SMARTER: evaluate and review
SMARTER adds two letters QBRs often skip: Evaluate and Review. Without them, SMART becomes a dead contract.
E — Evaluate
Question: Did the number move with the right evidence?
In Mexico–US freight: Recalculate OTIF AND; cross GPS/POD; no “tower feeling”
R — Review
Question: Do we adjust target, scope, or resources?
In Mexico–US freight: If border or demand changed, rewrite; do not hide red
When not to use SMART alone
SMART shines on operable closes. It becomes harmful when you fake precision while still exploring.
Exploration (new lane, new 3PL, agent pilot)
What to use: Hypotheses + learning metrics
Why: No reliable baseline yet; forcing SMART invents the number
Moonshot / stretch OKR
What to use: Ambitious OKR + SMART on the operable floor
Why: Stretch motivates; SMART prevents self-deception on cash and OTIF
Crisis (border closure, mass failure)
What to use: War-room + 48–72h horizons
Why: Quarterly SMART arrives late; then return to SMART
Instrumented continuous improvement
What to use: SMART + lean / Pareto / Ishikawa
Why: The goal aims; the tools attack root cause
How OCL turns the goal into evidence
Many freight SMART goals die on “M”: the number has no trip file. OCL Cargo attacks that stretch.
OCL is an autonomous TMS with agents (computer use: they operate the screens you already use). It builds the trip file, reduces the human bridge, and — when applicable — can stamp invoice and Carta Porte. It coexists with your TMS; no day-one migration. Your team decides exceptions.
Evidence
From SMART goal to close
Define
KPI + owner
Tie
GPS + POD to ID
Audit
100% pre-pay
Exceptions
Your team decides
Key takeaways5 points
- SMART = five writing tests: Specific, Measurable, Achievable/Assignable, Relevant/Realistic, Time-bound.
- Doran (1981) used Assignable and Realistic; modern boards often say Achievable and Relevant — require both readings.
- OKRs align ambition; SMART sharpens the operating KPI (OTIF, cost/km, cycle, audit recovery).
- A vague goal (“improve service”) cannot be governed; a SMART goal is auditable in a QBR with owner, number, and date.
- Do not use SMART alone in exploration or moonshots: learning leads there; SMART closes what you can already measure.
Do your freight goals pass the five letters?
Related reading
Frequently asked questions
Objectives written to pass five tests: Specific, Measurable, Achievable (and Assignable), Relevant (and Realistic), and Time-bound — so a board or QBR can audit them without guessing.
George T. Doran published it in Management Review (November 1981): Specific, Measurable, Assignable, Realistic, Time-related. Modern boardroom reading often uses Achievable and Relevant; at OCL we require both readings of A and R.
OKRs align ambition and focus at company/unit level. SMART sharpens the operating objective or Key Result that must close in a quarter. Not rivals: strategy cascades with OKRs; freight, OTIF, or audit-recovery KPIs are written SMART.
OTIF by lane, cost per kilometer, shipment cycle time, freight-audit recovery (typical 5–7% when auditing 100% of the pilot), and typed exceptions in the trip file — not marathons or diets.
In exploration (new lane, new product, AI pilot without a baseline) and moonshots where the value is learning, not 100% attainment. Use hypotheses + stretch OKRs there; leave SMART for the measurable close.
A common extension: Evaluate (with data) and Review (adjust). In a QBR: reopen the objective — do not only paint green/red.
OCL is an autonomous TMS with agents: it builds the trip file (rate, GPS, proof of delivery), can stamp invoice and Carta Porte when applicable, audits pre-pay, and escalates exceptions. It turns M and T into evidence, not a close Excel.