Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Mike Dalton says companies often plan each project in isolation, then execute in a world of shared resources. Because project management and resource management are treated separately, plans ignore what else is running. That makes execution nearly impossible and causes resource blocks to cascade through the portfolio.

Related Insights

Organizations routinely juggle too many projects for their available resources, trapping teams in costly context switching. Establishing transparent, explicit selection criteria and categorizing initiatives—such as breakthrough, platform, derivative, and support buckets—creates clarity and prevents leadership pet projects from dominating.

To solve resource overload, don't compare all projects directly. Categorize them into "buckets" (e.g., bold innovations vs. minor fixes). Then, rank and kill the lowest-performing projects *within* each bucket to reallocate resources effectively and protect bolder initiatives.

The primary cause of failure in engineering projects is not technical incompetence but a lack of visibility into budget, schedule, scope, and risk. Successful project execution hinges on addressing these core management areas before they derail the work.

A critical challenge for corporate innovation is a lack of transparency between silos. Executives report teams discovering they've worked on the same project for months, wasting hundreds of thousands of dollars. Simple tools like shared, visible roadmaps are a crucial unlock to prevent redundant efforts.

Mike Dalton says shared-resource conflicts should be resolved by sending the resource to the project most at risk of finishing late, not to the loudest or most influential project manager. Healthy projects can absorb small delays; at-risk projects cannot. This early-warning rule replaces squeaky-wheel allocation with portfolio-level risk.

Mike Dalton says starting ten projects when you can run five limits your ability to take a great new opportunity because killing a halfway project is hard. Adding it anyway cascades delays across the portfolio. Spreading work over two years also sacrifices cash flow this year, and that lost cash flow is gone forever.

After defining strategic themes, link them visually in a "strategy map." This map reveals critical dependencies (e.g., product goals depending on hiring the right skills), forcing a holistic planning process that accounts for necessary precursors and prevents siloed execution.

Focusing the entire company on one critical path item creates "second grade soccer" syndrome, where everyone swarms one problem while others are neglected. Instead, deploy small, independent "SWAT teams" to attack blockers, allowing the rest of the organization to maintain progress on parallel tracks.

The primary source of friction between product and project functions isn't a lack of skills but rather unclear ownership, siloed planning, and conflicting success metrics. The solution is proactive, early alignment on roles, tools, and a shared definition of success.

Standard prioritization techniques fail because departments optimize for their own goals in silos (e.g., marketing, IT, HR). Without a senior leadership team taking a "balcony view" to assess the cumulative demand on employee time across all initiatives, the organization inevitably becomes overloaded.