On tailoring, purpose, and holding the instrument lightly.
When I am teaching someone to schedule, I sometimes take the scheduling tools away. Produce the delivery schedule, I tell them — the one that would normally live in Microsoft Project or Primavera P6 — but do it in Excel, or with sticky notes on a wall. It looks perverse: the wrong tool, deliberately chosen, for a job that has perfectly good tools built for it. But the moment the software is gone, so is the place to hide. The learner can no longer let the tool do the thinking — arrange the dependencies, enforce the logic, produce the tidy artefact — and has to reach instead for the thing underneath it: what a schedule is actually for. Why it exists, before what it contains or how it is built. The constraint is the teacher. Take away the easy path and people are forced to understand — and understanding is the only thing the exercise is really about.
I have come to think this is not a training trick but the truth of the whole craft. The tool is never the job. Every serious delivery framework, read properly, says as much about itself. The most important thing PRINCE2 teaches is not its processes or its themes; it is tailoring — the instruction, built into the method, that you adapt it to the situation rather than apply it whole. I carry that into every framework I meet: SAFe, agile, lean, six sigma, and the rest. Fluency in them matters, and I have it — but fluency is not the skill. The skill is knowing what each is for, well enough to judge how much of it this situation actually needs: which parts to use, which to leave, where to blend one with another. A framework applied slavishly is a tool being allowed to think for you, which is exactly the habit the scheduling exercise exists to break.
The clearest sign of this is how often the right answer wears the wrong label. I have seen product management do the work that service management would classically own, and service management do the work of product — and succeed, because the situation called for it, whatever the textbook said. The name on the method is not the point; the fit is. And you cannot know the fit from the outside, by matching a situation to a category. You know it the way you come to know anything real: by listening, observing, and understanding what is actually in front of you, rather than what the framework expects to find.
None of this is an argument against frameworks, any more than the scheduling exercise is an argument against Primavera. The rigour is necessary; the fluency is necessary; a schedule still has to be right and a method still has to be sound. The frameworks are scaffolding, and scaffolding is how buildings get built. The failure is only ever mistaking the scaffold for the structure — treating the instrument as the achievement, when it was always just the means.
Because when you strip a delivery framework all the way back, what it is really for is not control, or documentation, or the artefact. It is confidence. A schedule is a promise people can believe in. A method is a shared language that lets a group of people trust the work is coherent and in hand. Beneath all of it, the job is to give faith and confidence to everyone the work touches: the people doing it, who need to believe it is possible and that their part makes sense; and the executives accountable for it, who need to believe it is under control. That is the real deliverable, and the frameworks are only ever in service of it. Which is what the exercise teaches last, and teaches deepest — not how to build a schedule, but how to create that confidence out of your own understanding, when the tool that usually manufactures it has been taken away, and to discover, often for the first time, that you can.
This matters more now, not less. The tools have never been more capable of doing the what and the how for us, faster and more fluently than ever — and the temptation to let them own the why as well has never been stronger. But a person who has let the tool hold their understanding is fine right up until the moment the tool does not fit, and is then stranded, with no purpose to fall back on and no confidence to offer anyone. Setting the tool aside on purpose, now and then, to keep the understanding alive and your own, is not nostalgia. It is how you stay useful in the one situation the tool was not built for — which is usually the situation that matters most.
So I go on giving people the wrong tool for the right job, on purpose. It is the quickest way I know to teach that the right job was never really the tool at all. It was the understanding — and the quiet confidence that understanding lets you give to everyone around you.
Further reading: Complicated Is Not Complex · Find What’s Already There