GUIDINEE.COM › Microsoft Project › Level 6 › 6.5

6.5 · Field feedback

Level 6 · In practice

6.5Field feedback

Goal: retain the principles Project practitioners repeat, and set aside misconceptions.
Estimated time: 9 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Living schedule: “link, don't date” and “update, otherwise your schedule lies” — a schedule is built on dependencies and kept up to date.
  • Measurement: “set your baseline before you leave” and watch the critical path — without a baseline, no drift is measurable.
  • Accuracy: in multi-project settings, share resources, and go beyond the myths — “I enter the dates”, “% complete is enough”, “baseline later”.

Meriem's thread — what the old hands repeat

Over the sites in Algiers, Meriem has heard the same principles come back from experienced project managers: “link, don't date”, “set your baseline before you leave”, “update, otherwise your schedule lies”. She drew a little end-of-project debrief from them that she keeps for herself — and she learned to spot the false obviousnesses that lull you to sleep.

Read this feedback as guardrails: if you recognise yourself in a misconception, correct it from the current week.

What practitioners repeat

Beyond features, a few principles come back constantly among those who steer their projects calmly. Each fits in one sentence — and is worth more than a long catalogue.

The living schedule

A schedule is built on dependencies and updated: “link rather than date” and “update” are the two reflexes that separate a steering tool from a mere drawing.

Going beyond the myths

“I enter the dates, it is simpler”, “% complete is enough”, “baseline later”, “everyone plans in their own corner”: these phrases lull you to sleep. A schedule dated by hand freezes, a flattering % complete hides drift, and isolated projects create invisible overallocations.

✓ Do

  • “Link, don't date”: a schedule is built on dependencies, not frozen dates.
  • “Set your baseline before you leave”: without a baseline, you will never know whether you are drifting.
  • “Update, otherwise your schedule lies”: a file never refreshed quickly becomes wrong.
  • “Watch the critical path”: that is where the finish date is decided, not elsewhere.
  • “In multi-project settings, share resources”: otherwise you promise the same people everywhere.

✗ Avoid

  • “I enter the dates, it is simpler” — no: the schedule no longer recalculates.
  • “% complete is enough” — a task “90% done” for 3 weeks hides a problem.
  • “I will set the baseline later” — too late, the first weeks of tracking are lost.
  • “Each project plans in its own corner” — that is the recipe for invisible overallocations.
  • “The schedule is pretty, so it is accurate” — a decorative Gantt never updated steers nothing.
Common misinterpretation: “these principles are quotes from real practitioners”. No: this is an anonymous synthesis of widespread good practices, not attributed testimonials. The profession is learned through regular practice: link, baseline, update.
Text version of the diagram (SEO / screen readers / translation): 1) Repeated good practices — link rather than date, set your baseline before you leave, update otherwise your schedule lies, watch the critical path, share resources in multi-project settings. 2) Misconceptions to set aside — “I enter the dates, it is simpler”, “% complete is enough”, “baseline later”, “each project plans in its own corner”. 3) Field loop — update, compare with the baseline, debrief, capitalise in your templates. Lesson: a few principles applied always are better than a toolkit used sometimes.

Script ready to say — end-of-project debrief (30 s)

“What drifted? Was it a fundamental (mode, links, calendar, baseline)? What do I document? Which reflex do I reinforce?”

Say this at every project closure.

Script ready to say — recalling the principles (30 s)

“Link, don't date; set your baseline before you leave; update otherwise your schedule lies; watch the critical path; share resources in multi-project settings.”

Five principles to repeat at the start of a project.

Copy-paste template — project debrief

Project: [site]
What drifted: [schedule / cost / resource]
Missing fundamental: [mode / links / calendar / baseline]
Action to anchor: [1 single habit]
Reusable: [.mpt template / macro / lesson]

Copy-paste template — going beyond a myth

Myth       : “I enter the dates, it is simpler”
Reminder   : the schedule no longer recalculates
Consequence: any drift is invisible
Reflex     : link through dependencies, stay in automatic mode

VSE / small budget

One-line debrief sheet: drift, missing fundamental, action, proof — the essentials are enough.

Algiers SME

Adapt the myths to the field: irregular supplies, bad weather, several sites, one person who knows everything.

Remote / hybrid

At a distance, writing replaces the corridor: dated debrief, shared update, variances reported in writing.

Intercultural

Make the principles explicit: what seems self-evident (link early, update) must be said for every new team.

Caution: Generic reminder: this feedback is an anonymous synthesis of good practices — not attributed testimonials; never let a schedule rest on a single person or a single file, and keep the original baseline before any rescheduling.

48h challenge — apply it tomorrow

Fill in the project debrief above: 1 drift observed, 1 habit to anchor and the missing fundamental identified.

Section exit checklist
  • I retain the principles practitioners repeat.
  • I spot and set aside misconceptions (myths).
  • I have done the 48h challenge or scheduled its date.
Self-assessment 1-5: are my reflexes consistent?are my myths set aside?
← Previous : Toolkit (V3)Next : Going further (V3) →
Check your understanding

Which field principle helps Meriem most to keep a reliable schedule?

💡

Field golden rule: this feedback is an anonymous synthesis of widespread good practices — link rather than date, set your baseline, update.