Get your free personalized podcast brief

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

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.

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.

Mike Dalton says doubling the number of active projects makes every project take twice as long—simple, unbeatable math. He also notes that multitasking cuts effectiveness roughly in half, so context switching compounds the delay. The real cost is not just duration but lost productivity from constant plate-spinning and status reporting.

Indecision is more damaging than a bad decision because it doesn't just waste time; it dramatically reduces the team's available options. Delaying a hard choice (e.g., on a compliance issue) eats up the time needed to develop creative workarounds, forcing last-minute cuts to essential elements.

Paul Graham argues that a large team is a greater liability than low cash when a startup needs to pivot. Having many employees forces the founders to find a new idea that fits the existing team's capabilities, drastically limiting their options compared to a small founding team that can pursue anything.

Mike Dalton recommends zero-based budgeting for projects: fill capacity by rank-ordering opportunities on return per unit of effort. Put the next ones on a backlog and leave the bottom third without a start date. If customer-value work is good, better opportunities will replace the bottom-ranked projects.

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.

At the executive level, roadmapping is capital allocation. Product leaders should frame engineering capacity as a multi-million dollar investment and constantly ask where that capital will generate the highest rate of return over the next 2-3 years. This clarifies trade-off decisions and focuses on business outcomes.

True strategy involves making tough choices about what not to do. Many executive teams resist this, preferring to keep all options open. This attachment to optionality leads to weak, unfocused strategies where everything is a priority, spreading teams thin and hindering real progress.

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.