We scan new podcasts and send you the top 5 insights daily.
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.
To avoid pursuing low-value AI initiatives, use the RICE scoring method (Reach, Impact, Confidence, Effort). This product management framework helps teams quantify and rank potential projects, ensuring resources are allocated to initiatives with the highest potential return on investment.
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.
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.
Don't just tweak last year's product plan. Start from a blank slate by defining business goals first, then allocate resources to the value propositions needed to win. This avoids getting stuck in maintenance mode and forces a focus on strategic priorities.
Aim for "good enough" financial estimates to differentiate multi-million dollar opportunities from thousand-dollar ones. This high-level sorting is more valuable and efficient than creating detailed, yet still speculative, forecasts for every idea.
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.
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.
To decide where to start with AI, use a framework that maps Possibilities to their Payoff and Probability of success to find the expected value. Then, divide this by the required Perspiration (effort) to get a final Priority score. This structured approach helps focus resources on high-impact, achievable projects.
Product managers should evaluate every initiative as if they were investing their own capital. This shifts focus from a "feature factory" to outcome-driven management, ensuring resources are allocated to the highest-impact work and treating the product like a mini-company with its own P&L.