Project Management is Boring | Podcast on RSS.com

Project Management is Boring

Project Management is Boring

by Jordon Keen

Season 3

Target Canada - Empty Shelves, Full Warehouses

This episode focuses on the contradiction at the heart of Target Canada’s operations: stores could have empty shelves while distribution centers had inventory. The issue was not simply “not enough product.” It was a flow problem involving systems, warehouse processes, forecasting, data, vendor coordination, and store execution. For PMs, this episode is about handoffs, dependencies, and the danger of managing functional silos instead of end-to-end outcomes. Key PM Questions: Where are the handoffs most likely to fail? Can the system move work from request to customer outcome? Are teams optimizing their piece while the whole process breaks?

Target Canada: The Data Was the Critical Path

This episode examines one of the most important lessons from Target Canada: bad data can break a business. Product dimensions, vendor information, units of measure, tariff codes, item descriptions, and other data elements affected purchasing, warehousing, replenishment, and shelf availability. The episode argues that “boring” data work was actually mission-critical. PMs must learn to treat data readiness as a major launch dependency, not a background task. Key PM Questions: Who owns data quality? What does “clean enough” mean? How should data readiness be tested before launch?

Target Canada - SAP Was Not the Villain

This episode focuses on Target Canada’s technology environment, including the implementation of SAP. The lesson is not simply “ERP projects are hard.” The deeper lesson is that enterprise systems require disciplined processes, trained users, strong governance, clean master data, and realistic integration planning. SAP became part of the story because the business depended on it before the surrounding operating model was mature enough to support it. Key PM Questions: When is a system implementation actually a business transformation? How do PMs tell the difference between software readiness and operational readiness? What questions should PMs ask before trusting an enterprise platform to support launch?

Target Canada - Big Bang Expansion

This episode explores Target Canada’s aggressive store-opening approach. Instead of entering slowly, learning from early locations, and adjusting, Target moved toward a large-scale launch. The pace reduced the organization’s ability to test assumptions, absorb feedback, and stabilize operations before expanding. For PMs, this episode focuses on rollout strategy, pilots, phased delivery, and the dangers of confusing deployment with adoption. Key PM Questions: What should a pilot actually prove? When is a phased rollout better than a large-scale launch? How do PMs protect learning time when leaders want speed?

Target Canada - The Deal That Started the Clock

Primary Focus: Target’s acquisition of Zellers lease locations PM Lesson: Strategic commitments can become project constraints before the project team is ready. This episode examines the real estate decision that gave Target rapid access to the Canadian market. Acquiring lease interests allowed Target to enter Canada at scale, but it also created enormous pressure to open stores quickly. Once money was committed and locations were secured, delay became expensive and politically difficult. The PM lesson is that projects often inherit constraints created by strategy. A project manager may not create the business case, but they must manage the consequences of it. Key PM Questions: When does a strategic opportunity become an execution trap? How do sunk costs distort decision-making? What should PMs do when the timeline is driven by business commitments rather than readiness evidence?

Target Canada — The Launch That Outran Reality

This opening episode introduces the Target Canada case, the major causes behind the failure, and the core themes of the season. It explains why this case matters to project managers: it was a major strategic initiative with compressed timelines, technology implementation challenges, data quality problems, supply chain breakdowns, weak readiness signals, and customer expectation gaps. The episode frames Target Canada as a project system, not merely a retail failure. It introduces the central idea of the season: the launch date became more real than operating reality. Key PM Questions: What assumptions were treated as facts? Where did urgency begin to overpower readiness? How should PMs listen for weak signals before failure becomes visible?

PMIB Season 3 Trailer: Target Canada

The trailer introducing Season 3 of the Project Management is Boring podcast - Target Canada

Season 2

The Anti-Knight Framework

We’ve spent this season studying one of the most expensive operational failures in modern markets. Knight Capital lost approximately $440 million in about forty-five minutes. That headline is dramatic. But the deeper lesson was never the dollar amount. It was the structure. Or more accurately— the absence of it. Because Knight Capital did not fail from one mistake. It failed from multiple weaknesses interacting inside a high-speed system. A flawed deployment. Legacy logic still alive. Unclear escalation. Delayed containment. Insufficient safeguards. Governance that did not match velocity. And that’s why this final episode matters. Because the real goal of this season was never to simply point at Knight and say: “They got it wrong.” That’s easy. The real goal was to ask a better question: What does right look like? What is the boring architecture that protects high-speed systems? What operating model helps organizations move quickly without becoming fragile? What structures allow leaders to scale speed without scaling chaos? Today we assemble everything. Not blame. Doctrine. Not hindsight. Design. This is the Anti-Knight Framework.

Technical Debt is Leadership Debt

This season has explored a pattern many organizations miss: Failures rarely begin in the moment of collapse. They begin earlier. In assumptions left unverified. In controls left untested. In drift left unmanaged. In governance that looked stronger than it was. Today we’re talking about another one of those quiet beginnings: Technical debt. Usually, technical debt is discussed like an engineering inconvenience. Messy code. Old systems. Deferred cleanup. Something the technical team should “handle later.” But technical debt is rarely just technical. Because every unresolved weakness survives through organizational choice. Someone funded features instead of remediation. Someone accepted short-term speed over long-term resilience. Someone tolerated fragility because the consequences were not immediate. That means technical debt is often leadership debt. It reflects decisions about what risk is allowed to remain. And this episode is about how project management helps make that risk visible. Because leadership decides what gets fixed. And leadership also decides what risk lives.

Nothing Broke, So It Must Be Fine

We’ve talked about assumptions. We’ve talked about speed pressure. We’ve talked about governance theater— what happens when controls exist on paper, but not in practice. Today, we’re talking about something quieter. Something slower. Something that rarely feels urgent when it begins. Drift. Because many organizational failures do not begin with dramatic mistakes. They begin with gradual relaxation. A process gets skipped once. A review gets shortened. A control that used to matter becomes optional. A team says, “We’ve done this plenty of times.” And nothing bad happens. So the change sticks. That’s drift. And drift is often blamed on culture, discipline, or people. But most of the time— drift is administrative. It happens because no system exists to notice it, challenge it, or correct it. This episode is about how collapse often begins in comfort— and how project management helps organizations stay disciplined after success. Because systems rarely fall apart overnight. They loosen first.

1 of 5