6.5Field feedback
The essentials in 30 seconds
- Principle #1: scoping time pays back — a poorly scoped project is paid in rework.
- Underused levers: writing exclusions and alerting early with options, instead of enduring in silence.
- Misconceptions: a good-looking schedule is enough, agile means improvising, more tools means better steering, the review can wait.
Bilal thread — 1 year on: what he keeps from the field
One year on, what Bilal keeps from his practice matches exactly the synthesis below: his best habit was writing exclusions before every start, and his click moment was alerting early with options instead of hiding a delay. Nothing heroic: scoping, remaining work, and consistency.
Read this feedback as guardrails: if you recognize yourself in a pitfall, fix it this very week.
What practitioners repeat
Beyond methods, a few principles constantly recur among those leading projects daily.
✓ Do
- “Scoping time pays back a hundredfold”: a poorly scoped project is paid in rework.
- “Steer by remaining work”: time spent says nothing of what remains.
- “Write exclusions”: what isn't written becomes a misunderstanding.
- “Alert early, with options”: hiding a problem grows it.
- “Projects play out as much on people as technique”: leadership and stakeholders often decide success.
✗ Don't
- “If the schedule looks good, the project will go well” — no: a Gantt without dependencies or tracking is an illusion.
- “Agile means improvising” — no: it is adaptive planning, not its absence.
- “More tools = better steering” — method and buy-in beat tools.
- “We'll do the review when we have time” — with no review, the same mistakes repeat.
Ready-to-say script — alert early with options (1 min)
“Here is where we stand (remaining work): [facts]. The risk: [consequence]. My options: A [content, impact], B [content, impact]. I recommend [choice]. Shall we decide together?”
Copy-paste template — monthly practice debrief (10 min)
DEBRIEF OF THE MONTH — [month]
1. My best project decision: ...
Why it worked (which fundamental): ...
2. My miss of the month: ...
What I take from it (no self-flagellation): ...
3. Feedback received (team, sponsor, peer): ...
4. ONE habit to keep: ...
ONE habit to change: ...
5. Next month: the project where I will apply it: ...Small business / tight budget
The debrief can be oral over coffee: one win, one miss, one habit to change.
Algeria SME
Value early alerts despite peaks: that is what avoids the costliest breaks when margins are thin.
Remote / hybrid
Provoke feedback in writing (short message, dedicated slot): people dare less live at a distance.
Cross-cultural
Adapt the feedback request: in private first, never in public, and accept indirect wordings.
48h challenge — apply tomorrow
Fill the monthly debrief above for the past month, and test 1 early alert with options on your ongoing project.
- I know the 5 principles and the misconceptions to discard.
- I have filled a debrief and tested an early alert (or scheduled).
- I did the 48h challenge or scheduled its date.
A colleague tells Bilal: “agile means improvising, no need to plan”. What does the field synthesis answer?
⚠️ Integrity: this feedback is an anonymous synthesis of widespread best practices — not attributed quotes. For named opinions, we would rely on real, sourced references.