Get your free personalized podcast brief

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

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.

Related Insights

Teams often default to 90-day timelines because it fits the quarterly business calendar, not because it's the actual time required. By simply asking 'How is it that every problem can be solved in exactly 90 days?', leaders can force more first-principles thinking about project scoping.

CEO Dylan Field combats organizational slowness by interrogating project timelines. He seeks to understand the underlying assumptions and separate actual work from "well-intentionally added" padding. This forces teams to reason from first principles and justify the true time required, preventing unnecessary delays.

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 Theory of Constraints states every business has one primary bottleneck limiting its growth. Instead of guessing, use this powerful thought experiment. By mentally stress-testing your system with a sudden influx of demand, the weakest link—the true bottleneck—will become immediately obvious.

Pushing for extreme speed does more than just accelerate timelines; it forces teams to triage ruthlessly. It creates a filter that naturally eliminates work on problems that don't absolutely need to be solved, preventing over-engineering and wasted effort. It's not about more hours, but higher focus.

People have a "subtractive neglect bias," overlooking solutions that involve removing tasks. By physically visualizing all commitments (like on Post-it notes), teams and individuals can immediately see they are overcommitted, forcing them to clarify priorities and remove or pause lower-impact projects.

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.

When stakeholders want to ship a high-fidelity prototype immediately, counter by explaining the required effort using numbers. Frame the work in terms of scale (e.g., "This must support 200 products, each requiring a week of testing") to manage expectations and justify proper engineering.

The purpose of setting impossibly aggressive deadlines isn't just to move faster. It is a strategic tool to force a team to identify the true critical path. By asking 'what prevents us from doing this in 6 months instead of 36?' you reveal the few real constraints that must be attacked or eliminated.