Have you ever been on a project or program where all the PMs knew that their project was in trouble, but they were waiting for someone else to admit their problems first? It happens often enough, as soon as one PM admits that they have a problem, everyone else discovers problems too.
The Prisoner’s Dilemma
From the PM’s position, it’s a version of the Prisoner’s Dilemma. In the Prisoner’s Dilemma, two suspects are arrested by the police. The police have insufficient evidence for a conviction, and, having separated both prisoners, visit each of them to offer the same deal. If one testifies (defects) for the prosecution against the other and the other remains silent, the betrayer goes free and the silent accomplice receives the full twenty-year sentence. If both remain silent, both prisoners are sentenced to only one-year in jail for a minor charge. If each betrays the other, each receives a five-year sentence. Each prisoner must choose to betray the other or to remain silent. Each one is assured that the other would not know about the betrayal before the end of the investigation.
How should the prisoners act?
The Project Manager’s Dilemma
So you’re managing a project, doing your best, but you made a mistake and need more time with a critical resource. The problem is, there is another project that need this same person.
You are putting together your status report. You know the economy’s bad and the rumors are all over. The company’s going to have cuts and people are going to get laid off.
- If you confess your need for the resource and the other PM doesn’t confess, your project will get the resource and safely go on.
- If you confess your need and other PM also confesses their need, there’s going to be an evaluation and both projects will lose people and be put at risk.
- If you don’t confess and the other PM does, he will get the resource and succeed and you and your team will be fired.
- If neither of you confess and wrangles on quietly for the resource, both projects will probably be late, but they will succeed. There might be some people cut, but both PMs will keep their job.
What are you going to do?
Early detection and escalation dictates that you confess i.e. raise the issue as soon as it arises. If you sit on the resource requirement, you know you’re doing your project a disservice.
hi andrew.
i meant bit exaggerated .. especially the firing part … there might be a possibility of accommodating few people in another project (even if the economy is bad and company is laying off — if it(company condition+economy) that bad then there going to be lay offs any case … irrespective of PM actions)
Also the fourth point where you’ve mentioned
(If neither of you confess and wrangles on quietly for the resource, both projects will probably be late, but they will succeed. There might be some people cut, but both PMs will keep their job.)
both PM might not keep the jobs …. (as economy is bad + company is in bad shape + unaccounted delay is eating valuable resources)
Your articles are nice and informative … learning a lot from it … 🙂
Sorry if you’ve felt bad bout that exaggeration comment.
Ranjeet,
Thanks. And for the record, no one has ever, and I mean EVER, accused me of exaggerating.
A
Awesome analogy !
Although few actions are bit exaggerated … but they drive the point well 🙂