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.
Mike Dalton recommends a virtual drum: t-shirt-size projects as small, medium, large, or extra large and estimate how many of each the organization can run at full speed. He says this high-level method delivers about 90% of the value without task-by-task detail. Lowering work in process then exposes hidden constraints, like rocks under receding WIP.
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 describes a CEO's casual idea that became a project; when the team showed it would not make money, the CEO said it was just an idea and accepted the finding. He says the best CEOs are careful about sharing ideas because people overinterpret them. Without a feedback mechanism, one sentence can redirect everyone.
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.
Mike Dalton uses a customer value lens for industrial products: customers typically need a 12-to-24-month payback, and a 12-month payback makes adoption easier because it does not hit this year's budget. From the expected savings and payback, you can back into the price the customer will pay and test whether it is a win-win.
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.
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.
