Get your free personalized podcast brief

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

Kirby Montgomery says only one project this year had no material change to the product and technology value creation plan. Yet quarterly business reviews often do not know the product roadmap or whether the post-close technology honey-do list was done, turning the plan into a spreadsheet that nobody tracks.

Related Insights

A true product roadmap is a strategic document outlining problems and outcomes, allowing for pivots. If your artifact is a timeline of features with fixed commitments and swim lanes, you don't have a roadmap; you have a project management Gantt chart, a tool for execution, not strategy.

Committing to a quarterly roadmap is futile when the AI landscape and customer needs change daily. Instead of detailed feature plans, leaders should set broad strategic objectives and focus on short-term, validated learning cycles. This approach builds a foundation that can adapt to rapid market shifts.

Three-quarters of B2B product teams, including leaders, admit their roadmaps are frequently altered by sales-driven commitments. This isn't an occasional exception but a fundamental, systemic mode of operation, indicating that sales, not product, often owns the roadmap in practice.

Effective Value Creation Plans (VCPs) are not static documents chiseled in stone at the deal's close. They must be treated as organic and reviewed every quarter. The operational reality of a business always differs from diligence, requiring continuous adaptation to address new challenges and opportunities.

Product leaders should reframe roadmaps from a list of features to a series of barriers they are removing for customers. This shifts focus to high-leverage outcomes like reducing complexity, enabling zero-handholding onboarding, and accelerating time-to-value.

When a product team is busy but their impact is minimal or hard to quantify, the root cause is often not poor execution but a lack of clarity in the overarching company strategy. Fixing the high-level strategy provides the focus necessary for product work to create meaningful value.

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.

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.

Shift your team's language from tracking output (e.g., 'deployed XYZ API') to tracking outcomes. Reframe milestones to focus on the business capability you have 'unlocked' for other teams. This small linguistic change reorients the team toward business impact and clarifies your contribution to metrics like NPS.

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.