Ask a project manager for the project plan and watch what happens next.
A laptop gets turned around. On the screen: bars. Hundreds of small blue bars marching left to right, with one red one somewhere in the middle that everybody has quietly agreed not to mention. Dependencies. Resource assignments. Phases broken into sub-phases, activities broken into sub-activities, all of it built with real care by somebody who is very good at building it.
That is a schedule.
It is not a plan.
Right?
The Choreography
Say you are planning to rob a bank. Not recommended, but it works.
You decide who digs the tunnel and who cuts the alarm. You pick the drill that goes through the safe door, and you time it. You work out how many minutes you have before the car has to pull away from the corner. All of it on one page, in order, with a name next to every task.
That is a fine piece of work. It is also nothing more than choreography.
Because none of it tells you what to do when there are forty people in the lobby instead of twelve. Or when the man with the drill gets picked up by a patrol car two streets away and never arrives. Or when a security guard decides that today is the day he becomes a hero. Who takes over? Who is allowed to speak to the police, and what exactly are they allowed to say? At what point do you walk out with nothing rather than stay another ten minutes?
No answers to those questions means no plan. It means a timetable and some optimism.
Plan to Control
The PMBOK is not a thrilling read, but it gets the definition right. A project plan is “a formal, approved document used to guide both project execution and project control.”
Read those last two words again.
Control is the part that gets skipped, because control is the part that cannot be drawn as a bar. Where is the governance model? Who decides, who only gets to advise, and at what point does a decision stop belonging to the project manager and travel up to the steering committee? What is the tolerance before that happens?
What happens to a risk when it stops being hypothetical? Is there money reserved against it, with a named owner and a mitigation action somebody has actually agreed to carry out... or is there a row in a spreadsheet with the word “monitor” in it?
Which changes are admissible, and which one forces a re-baseline? Where does an issue go when the team cannot solve it, and how long is it allowed to sit there? Who needs to know what, and when, and who is going to deliver the half of the report nobody wants to hear?
Answer those, and the dates start to mean something. Skip them, and the dates are decoration.
The Professor
Money Heist did not become a global hit because the Professor could read a clock and hand out tasks.
He is interesting because he spent months imagining the thing going wrong. Every way it could go wrong. The hostage who runs. The negotiator who does not behave the way the profile said she would. The team member who breaks the one rule that holds the rest together. For each of those, he has a response ready, and a rule for who decides when he cannot be reached.
He planned for the plan failing.
That is the difference, and it costs nothing except the willingness to sit in a room and say out loud what could go wrong. Which is, apparently, the most expensive hour in project management.
By all means, keep the Gantt chart. A timetable is useful, right up to the moment the timetable stops being true.
But when the alarm goes early, and the tunnel is flooding, and the man with the drill is sitting in the back of a patrol car, nobody in that building turns around to look at the bars.
They look at you.
And you will have a beautiful chart.