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.

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.

IBM uses a visual artifact called the "Golden Thread"—a living document showing product vision, value, and a feedback loop. This low-cost tool aligns diverse stakeholders, from the boardroom to developers, around outcomes instead of features, thereby de-risking innovation.

To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.

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.

Jacobs's team uses the acronym WOTWOM—Waste Of Time, Waste Of Money—as a rapid check on new ideas. Any suggestion can be challenged with this label if it doesn't clearly contribute to organic revenue growth or margin expansion. This simple tool creates a culture focused on high-leverage activities.

Instead of large, multi-year software rollouts, organizations should break down business objectives (e.g., shifting revenue to digital) into functional needs. This enables a modular, agile approach where technology solves specific problems for individual teams, delivering benefits in weeks, not years.

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.