Craig slunk away. Mira quietly re-opened the Change Control Log.
The GTA’s problem wasn’t technical. The tunneling machine, “Big Bertha,” worked fine. The issue was pure, unadulterated complexity. The project touched 14 municipalities, three Native American tribal councils, a rare bat habitat, and a senator whose brother owned a competing logistics firm. Pmbok 6th Edition.pdf
The real fight, however, was over . The GTA’s culture was to hide problems until they became crises. Mira held a “Risk Poker” session. She pulled up the PDF’s list of 18 standard risk responses (Escalate, Avoid, Transfer, Mitigate, Accept). Craig slunk away
The project was progressing. Costs stabilized. Then, six months in, a new VP of Operations, a man named Craig, arrived. Craig was a “death by PowerPoint” executive who believed project management was common sense. He mocked the PMBOK® . The tunneling machine, “Big Bertha,” worked fine
The train opened on time, within 2% of its revised budget.
Silence. Then, a junior geologist raised a hand. “The soil three kilometers east of the river… the samples are inconsistent. There’s a 30% chance of a methane pocket.”
“The 7th Edition is about principles and performance domains,” she said. “It’s leaner. More agile. But the 6th Edition? That was the last great atlas of process . It taught us that project management isn't about predicting the future. It’s about having a systematic way to respond when the future refuses to be predicted.”