1.2 · SMART objectives & deliverables

Level 1 · Project framing

1.2SMART objectives & deliverables

Goal: turn fuzzy intentions into SMART objectives and verifiable deliverables.
Estimated time: 12 min · self-paced reading · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • SMART: Specific, Measurable, Achievable, Realistic, Time-bound — no more vague intentions.
  • An objective states what to achieve, how to measure it, by when; it stays the project's stable course.
  • Each objective gets deliverables with a "done" criterion: the foundation you commit to.

Running mini-case — Bilal rewrites "improve stock"

"Improve stock management," asks the owner. Bilal rewrites: "cut stockouts by 30% and bring inventory accuracy to 98% by June 30". Associated deliverables: configured software, control inventory, variance report. The owner balks at the figure — perfect, that's exactly the discussion SMART was meant to trigger before spending.

Sequel to case 1.1 — Bilal turns the validated note into a measurable commitment.

1. The SMART method

A project without clear objectives is unmanageable. The SMART method turns a vague intention ("improve the site") into a precise objective: Specific, Measurable, Achievable, Realistic, Time-bound.

A good SMART objective states exactly what must be achieved, how it will be measured, and by when.

2. Objectives and deliverables

These objectives come with deliverables: the concrete, verifiable outcomes the project must produce.

Objectives (the measurable why/what) and deliverables (the tangible products) form the contractual foundation: what you commit to, and what you will be judged on.

Common misinterpretation: "An ambitious, vague objective motivates more than a quantified one." No. "Do better" states neither what, nor how much, nor when — nobody knows whether it is met. Precision kills neither ambition nor motivation: it states where to aim and when to applaud. And objective (measured outcome) is not deliverable (tangible product).
A SMART objective Precise and steerable Specific & MeasurablePrecise, quantified+Achievable & RealisticWith available means+Time-boundBounded by a deadline Each objective gets concrete deliverables with a done criterion.
Precise and steerable
Text version of the diagram (SEO / screen readers / translation): 1) Specific and Measurable: Bilal quantifies (stockouts −30%, 98% inventory). 2) Achievable and Realistic: with his team and budget, not a wish. 3) Time-bound: June 30 deadline. Lesson: figure and date turn an intention into a commitment — and each deliverable gets its "done" criterion.

The wall of fuzzy objectives (seen live, anonymized)

"Improve stock."
Verdict: improve what? by how much? by when? → 0/5.
"Zero stockouts, zero variance, zero budget."
Verdict: the impossible trinity — the team checked out at the second zero.
"Be the best!!!"
Verdict: three exclamation marks replace neither figure nor date.

Moral: if your objective makes people grin awkwardly, run it through the SMART sieve above.

🔎 Concrete example — 🔎 Concrete example — From vague to SMART

Rewriting an objective.

Vague: "improve the site".
SMART: "cut loading time to < 2 s by June 30".
→ associated deliverable: "optimized site delivered + performance report".

Outcome: a measurable success, not a feeling.

Reflex: attach a "done" criterion to each deliverable.

Section vocabulary

SMART objective
Specific, Measurable, Achievable, Realistic, Time-bound objective. Makes ambition precise and steerable.

Simple example: "Cut stockouts by 30% by June 30" at Bilal's.

What it is not: "improve stock" with no figure or date.

Reflex: any objective without figure or deadline must be rewritten.

Deliverable
Concrete, tangible, verifiable outcome produced by the project (document, software, building, training).

Simple example: The configured software and variance report delivered by Bilal.

What it is not: the objective itself ("cut stockouts").

Reflex: list tangible products, not intentions.

Success criterion
The indicator telling whether the objective is met (e.g. "loading time < 2 s").

Simple example: "98% reliable inventory" to judge Bilal's project.

What it is not: a feeling ("it feels better").

Reflex: write before starting how success will be observed.

Specific / Measurable
Specific: precise and unambiguous. Measurable: quantifiable, so achievement can be observed.

Simple example: "−30% stockouts": what (stockouts) and how much (−30%).

What it is not: "do better": neither what nor how much.

Reflex: underline the figure in each objective.

Realistic / Time-bound
Realistic: achievable with available means. Time-bound: bounded by a deadline.

Simple example: "By June 30, with the current team" for Bilal.

What it is not: "zero defects tomorrow" with no credible means or deadline.

Reflex: check means and date with the sponsor before signing.

In practice — In practice — Writing SMART objectives and listing deliverables

  1. Take a vague project objective ("improve X") and rewrite it SMART (precise, quantified, with a deadline).
  2. Check each letter: is it Specific? Measurable (by which criterion)? Achievable and Realistic? Time-bound?
  3. List the concrete deliverables embodying this objective (documents, products, milestones).
  4. Attach a "done" criterion to each deliverable (when can it be called finished and compliant?).
You turn fuzzy intentions into SMART objectives and verifiable deliverables: the project becomes steerable and its success measurable.

Ready-to-say script — negotiating a SMART objective with the sponsor (1 min)

"Improve stock — I propose translating it: stockouts cut by 30% and 98% reliable inventory, by June 30, with these three deliverables. If the figure looks wrong to you, we adjust it now — after validation, it becomes our course."

Say to the sponsor: negotiate the figure before committing, not after spending.

Copy-paste template — SMART objective + deliverables sheet

VAGUE OBJECTIVE (start): _______________
SMART OBJECTIVE (rewritten): _______________
MEASURE (how we will observe it): _______________
DEADLINE: _______________
DELIVERABLE 1 + "DONE" CRITERION: _______________
DELIVERABLE 2 + "DONE" CRITERION: _______________

Small business / small project

One single SMART objective is often enough: one quantified sentence + one deliverable + one date, posted on the wall.

Remote / multi-site

Write the objective and its criteria in the shared space: remotely, "done" must be verifiable without a meeting.

Algerian SME

Bilal sets the deadline accounting for local realities (activity peaks, Ramadan, vendor lead times): a credible Time-bound objective beats a heroic, unkeepable date.

Client-imposed objective

Translate the injunction into SMART and get the rewrite validated: if the client refuses the figure, they refuse the commitment — clarify before signing.

✓ Best practices

  • Quantify the objective and bound it by a deadline.
  • Attach a "done" criterion to each deliverable.
  • Keep the objective stable: it is the project's course.

✗ Common pitfalls

  • Settling for a vague, unmeasurable objective.
  • Confusing objective (measured outcome) with deliverable (tangible product).
  • Letting the objective silently drift during the project.

Key takeaways

  • SMART: Specific, Measurable, Achievable, Realistic, Time-bound.
  • A SMART objective states what to achieve, how to measure it, by when.
  • Deliverables are the project's concrete, verifiable outcomes.
  • Objectives + deliverables = the foundation you commit to and will be judged on.

48h Challenge — apply tomorrow

Rewrite 1 vague objective of your project SMART (figure + deadline), list its deliverables with "done" criteria and get them validated by the sponsor. 20 minutes is enough.

Section exit checklist
  • I can name the 5 SMART letters without hesitating.
  • I've rewritten 1 vague objective SMART (figure + date).
  • Each deliverable has its "done" criterion.
Self-rating 1-5: do my objectives state what, how much and when?does each deliverable have a "done" criterion?

Frequently asked questions

What is the difference between an objective and a deliverable?

The objective states the expected outcome and its measure ("cut processing time by 30% by June"). The deliverable is the tangible product contributing to it ("the new processing software delivered"). One objective may require several deliverables. You steer deliverables to meet objectives. Confusing the two leads to delivering products without knowing whether they truly meet the goal.

Can an objective evolve during the project?

Ideally, the objective stays stable (it is the course). If it must change, that calls for a formal sponsor decision, with cost/schedule/quality triangle reassessed — not a silent drift. In agile, you keep a stable vision while adjusting delivery details across iterations. An objective changing without an explicit decision signals a drifting project.

Check your understanding

What does SMART mean for an objective?

Additional resources (optional, to go further)

Level 1 examFresh, harder questions to test what you've learned