We scan new podcasts and send you the top 5 insights daily.
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.
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.
Categorize risks to prioritize action. 'Tigers' are critical threats that will kill the project. 'Paper Tigers' are perceived risks that are actually under control, requiring only reassurance. 'Elephants' are the unspoken, uncomfortable truths that need to be surfaced for discussion.
Treat your product and engineering teams as stewards of the company's most precious capital: their time. A capital allocation framework forces leadership to ask if this "investment" is being spent on the initiatives with the highest strategic return, not just fulfilling requests.
Instead of complex prioritization frameworks like RICE, designers can use a more intuitive model based on Value, Cost, and Risk. This mirrors the mental calculation humans use for everyday decisions, allowing for a more holistic and natural conversation about project trade-offs.
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 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.
When a project tanks, the headcount is at risk. A savvy manager immediately moves those engineers to a promising project. Then, they report to leadership, "Project A failed, but good news: I've moved the team to Project B, which is now moving twice as fast." This prevents headcount clawbacks by creating new value.
A superior prioritization framework calculates your marginal contribution: (Importance * [Success Probability with you - Success Probability without you]) / Time. This means working on a lower-priority project where you can be a hero is often more valuable than being a cog in a well-staffed, top-priority machine.
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.