Get your free personalized podcast brief

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

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.

Related Insights

To overcome emotional attachment to projects, turn each of 200+ initiatives into a playable card with stats. By getting the senior team to play a game, they naturally discard the "weaker" projects, painlessly culling the list without emotional debate.

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.

A critical challenge for corporate innovation is a lack of transparency between silos. Executives report teams discovering they've worked on the same project for months, wasting hundreds of thousands of dollars. Simple tools like shared, visible roadmaps are a crucial unlock to prevent redundant efforts.

A simple 2x2 framework can clarify project strategy. Plot ideas on axes of internal team passion and external market evidence. This creates four quadrants: Kill (low/low), Find a Champion (low passion/high evidence), Sandbox (high passion/low evidence), and Scale (high/high), providing a clear path for each initiative.

Annual corporate financial cycles lock in project budgets once a year, effectively restricting creativity to an annual cadence. Because innovation is dynamic and non-linear, projects will fail. To build a responsive portfolio, leaders should negotiate funding around agreed-upon performance outcomes or key value metrics (such as emissions reductions or revenue milestones) rather than specific initiatives, giving teams freedom to reallocate resources across backlogs dynamically.

As companies scale, roadmaps become a list of stakeholder commitments. To maintain focus, leaders must relentlessly communicate the "why" behind every initiative and tie it to a clear investment ROI. This ensures all teams are running in the same direction, not just checking boxes.

To rationalize a project portfolio, first define your organization's core services from a customer's viewpoint. Then, map every ongoing project and team to these services. This visual exercise immediately reveals where investment is clustered, where it's missing, and where efforts are being duplicated.

Conduct an "alignment analysis" by tagging every investment—projects, products, operations—to your strategic themes. This process inevitably creates an "other" category for items that don't fit, making misalignment visible and forcing leadership to defund pet projects.

To avoid low-value tech projects, Unum maps all investments to specific, business-owned "value streams." This structure forces the company to prioritize work based on expected business outcomes and to say "no" to lesser initiatives, shifting from an IT-centric to a value-creation mindset.