The thing to understand about project managers is that they are not romantics. They will clutch at anything (a half-decent spreadsheet, a clear dashboard, even a scribbled note) if it genuinely makes the labor of delivery lighter. If they are not swooning over your gleaming, multimillion-dollar enterprise “PM” tool, it is not because they are technophobes. It is because the contraption does not serve them. This is not resistance to change. It is resistance to a Trojan Horse. Whose Tool Is It, Really? If project managers did not ask for it, then they were never its intended beneficiaries. Follow the pipelines of data and the victors quickly reveal themselves: Finance, Compliance, Audit, Controlling. These are the true clients. For them, the new system is a godsend; no more clunky macros, no more bloated spreadsheets. Their reports are clean, their dashboards luminous, their enthusiasm unmistakable. But this is not empowerment for project managers. It is conscription. They are reduced to

In the holy theater of the Steering Committee, risk is treated as a ghost: acknowledged in the liturgy, ignored in the sermon, and exorcised from the budget. The Project Risk Log is bowed to, as one might nod at the Ten Commandments, and then briskly violated. Funds for mitigation? Contingency? A bridge too far—indeed, a bridge they propose to cross when it is already on fire. Here Comes the Bride Permit, for once, a domestic parable. You are the father of the bride: dazed by the prospect of your princess leaving the citadel, and newly acquainted with the medieval custom that her joy will be financed by your treasury. The dress was chosen at thirteen, the napkin colors at fifteen; the bill is due now. You hire a wedding planner—your project manager—who compiles requirements, drafts a plan, and totals the cost. Mr Murphy is Also Invited Do you then sleep the untroubled sleep of the credulous, persuaded that a fairytale admits no plot twists? Or do you, like any sentient mammal, ask what

Corporate folklore holds that the surest way to find a project manager is to trawl the aquarium for the fattest subject-matter fish. Whoever knows the most about the content, runs the lore, must surely be the best to run the project. This is wrong in the same way that Instagram influencers' “science” is wrong: it confuses adornment with aerodynamics. Content over Competence Seasoned project managers know the ritual. You’re vetted by an intermediary whose first sacramental question is, “Do you have experience with System Utopia?” Answer “No,” and the catechism concludes: “Too bad—client insists on deep Utopia expertise.” Your history of delivering complex efforts in a controlled manner is waved away. Content is king; competence is court jester. Product versus Process Knowledge Consider the farce as it would look in any other arena. You’re hiring someone to organize a rock festival. The decisive criterion? Not whether they can plan logistics, wrangle suppliers, manage risk, and keep 50,0

Let us begin with a proposition so banal that it passes, in boardrooms, for daring originality: most projects are approved on the understanding that reality will behave itself. The Best Case Scenario—capitalized, canonized, and deified—is treated as the baseline, as if Fortune herself had joined the payroll. One could call this optimism. One could also call it, with greater accuracy, a cult of false hope. It Usually Starts Well A conscientious project manager, the sort who still believes numbers mean something, will dutifully inventory features, tasks, effort, time, and cost. She will even do the unfashionable thing: risk analysis. That tiresome discipline asks what might go wrong, how likely it is to do so, how hard it will bite when it does, and what mitigations cost. From this arithmetic of contingency, two bookends emerge. Best Case: nothing untoward happens; all risk remains theoretical, pristinely inert. Worst Case: the entire rogues’ gallery of risks strolls onstage, plus a few

“On time and on budget” sounds like discipline; in practice, it often certifies luck. When punctuality and thrift are treated as the whole of performance, coincidence is misread as competence and the organization learns the wrong lesson. Yes, a team can, by Forrest-Gump serendipity, hit the date and the number. That proves a calendar was met and a ledger balanced, not that the right thing was built the right way. In cinema, luck is charming; in management, elevating luck to evidence is an epistemic failure because it rewards the appearance of control over the substance of value. How the Slogan Shrunk the Goal The phrase began as shorthand for balanced delivery; right thing, right way, right cost, right time. Taken literally, it amputates what makes the effort worthwhile: Scope: Did we deliver the thing we promised, not just something with the same label? Quality: Is it usable, reliable, and safe (or merely demo-able)? When these vanish, organizations celebrate counterfeits: features ki

Let us begin with a heresy so obvious it will strike some as revelation: your beloved MS Project file is not a project plan. Neither is any other Gantt-bedizened liturgy of bars and dates. It is not the droning procession of activities, milestones, and dependencies that will save you from your own wishful thinking. The Mix-Up Time and again, when one asks the perfectly straightforward question—May I see your project plan?—what arrives, with the air of a conjurer unveiling Excalibur, is an .mpp file. If we had a coin for each time this happened, we would not be millionaires; we would merely dine better, which in our experience is a far more reliable measure of human progress. The MPP Monster Yes, an MS Project schedule can be impressive in its way. A hinge-point here, a dependency there, resources assigned with the precision of a Swiss watchmaker. Some go so far as to break down phases into sub-phases, activities into sub-activities, until the thing resembles a never-ending pattern of m