RoadmapOne Release 3.2 is here
Introducing PowerPoint Export, and your Finance team's favourite feature
Announcing RoadmapOne Release 3.2. Featuring Powerpoint Export, a simplified user interface, and the one feature your Finance team care the most about
RoadmapOne Release 3.1 is here
Tuned to perfection!
Following on from version 3, here is release 3.1 with new financial and cost modelling capabitilites.
RoadmapOne's JIRA Integration
Bridge the Gap Between Strategy and Execution
RoadmapOne is the Strategic layer, JIRA is the execution layer. Let's recognise the difference, use the right tool for the job, but ensure that the two tools sing in perfect harmony
Objective Prioritisation, The Science of Sequencing Strategy
Objective prioritisation is the brutal art of choosing which objectives to fund first. Learn how RICE, ICE, WSJF, MoSCoW, NPV, ARR, Kano, Cost of Delay, Payback Period, Buy a Feature, ROI, Benefit, GIST, and twenty other frameworks—including strategic tagging, discovery methodologies, and metrics frameworks like HEART and North Star—turn infinite backlogs into executable roadmaps.
Objective Tagging, The Missing Connectivity between your backlog and The Board
A unifying guide on how roadmap tagging turns strategy into daily decisions, accelerates board alignment, and becomes effortless with RoadmapOne.
Key Result Tagging, The Science of Measuring What Matters
Transform how you measure success—Key Result tagging reveals whether you're measuring the right things, with the right confidence, using the right methods.
Product Discovery in Roadmaps: Why Your Invisible Discovery Work Keeps Getting Cut
Make Discovery Visible, Measurable, and Defensible
Discovery work is invisible in most roadmaps—which is why it gets cut first and costs you most. Here's how to make discovery visible, measurable, and defensible when stakeholders ask why you're not shipping faster.
SaaS Financial Metrics: The Numbers That Determine Your Destiny
SaaS financial metrics like Rule of 40, Magic Number, LTV:CAC Ratio, and CAC Payback Period determine whether your business is healthy. Learn how these metrics connect to your roadmap—and why your roadmap is the lever that moves them.
Priority Whiplash: Why Your Best Engineers Are Updating Their CVs
Constant reprioritisation destroys engineering morale faster than anything else. If your team never finishes anything because leadership keeps changing direction, here's what's actually going wrong—and how to fix it.
Dual Track Agile: Balancing Discovery and Delivery on Your Roadmap
Dual track agile—running discovery and delivery in parallel—is essential for empowered product teams. But most implementations fail because they ignore the capacity constraint. Here's how to make it actually work.
Feature Factory to Outcome Team: Breaking the Pattern That's Killing Your Product
Is your product team a feature factory—shipping features without measuring impact, celebrating releases instead of results, burning out your engineers? Here's how to recognise the pattern and break free.
Initiative vs Epic vs Story vs Task: A Clear Hierarchy for Your Roadmap
Initiative, epic, story, task—the hierarchy of work items confuses almost every product team. Here's how to think about it clearly and what actually matters for your roadmap.
Now Next Later Roadmaps: The Simple Framework That Oversimplifies Strategy
Now Next Later roadmaps are popular for their simplicity, but they hide critical capacity constraints and let teams avoid hard prioritisation decisions. Here's why I'm skeptical—and what to use instead.
OKR vs Roadmap: They're Not Competing (Here's How They Connect)
OKRs and roadmaps aren't competing approaches—they're complementary tools. Learn how to connect your Objectives and Key Results to your product roadmap for strategic alignment that actually works.
Outcome-Based Roadmaps: A Practical Guide for Product Teams
Outcome-based roadmaps focus on measurable business results rather than feature lists. Learn how to shift from output-driven planning to outcome-focused product strategy that aligns teams, satisfies boards, and actually moves the needle.
Product Roadmap vs Product Backlog: Different Tools, Different Jobs
Product roadmaps and backlogs serve different purposes for different audiences. Conflating them—or using Jira as your roadmap—is a recipe for strategic confusion and tactical chaos.
Quarterly Roadmap Planning: The Cadence That Actually Works
Quarterly roadmap planning hits the sweet spot—short enough to avoid wasting resources on the wrong things, long enough to achieve meaningful outcomes. Here's how to run a quarterly planning cycle that actually works.
Should You Have a Public Roadmap? A SaaS Decision Framework
Should your SaaS company publish a public roadmap? The answer is 'it depends'—but I've seen public roadmaps transform customer relationships when done right. Here's a decision framework, including a story about a customer who literally shouted in my face.
Vision vs Strategy vs Roadmap: Understanding the Product Hierarchy
Vision, strategy, and roadmap form a hierarchy that most teams collapse or skip entirely. Here's how to think about each level clearly—and why missing the strategy layer is the most common failure.
CAC Payback Period: The Cash Flow Metric That Gates Your Growth Speed
CAC Payback Period reveals how long until customer acquisition investments break even. Learn how this cash flow metric determines how fast you can grow—and how your roadmap can accelerate payback from both sides.
LTV:CAC Ratio: The Unit Economics Metric That Determines SaaS Survival
LTV:CAC Ratio reveals whether your customers generate more value than they cost to acquire. Learn how this fundamental unit economics metric determines SaaS sustainability—and how your roadmap can improve it from both sides of the equation.
Rule of 40: The SaaS Health Metric That Investors Actually Care About
The Rule of 40 is the single metric that tells investors whether your SaaS business is healthy. Learn how growth rate plus profit margin reveals whether you're building sustainably—and how your roadmap can move the number.
SaaS Magic Number: The Growth Efficiency Metric That Reveals Your GTM Truth
The SaaS Magic Number measures whether your sales and marketing investments generate proportional revenue returns. Learn how this efficiency metric separates sustainable growth from expensive growth—and how your roadmap can improve it.
Ansoff Matrix: Strategic Tagging for Growth Risk, Not Prioritisation
Visualise Your Risk Profile, Then Use Real Frameworks to Prioritise
The Ansoff Matrix categorises growth strategies by risk profile—Market Penetration, Market Development, Product Development, Diversification. It's a tagging framework for visualising portfolio balance, not a prioritisation framework.
Dot Voting Has No Business Near Your Roadmap
Democratic Theatre Belongs in Retros, Not Prioritisation
Dot Voting is everywhere—design sprints, retros, roadmap workshops. It belongs in facilitation, not prioritisation. Here's why democracy produces roadmaps that reflect politics, not value.
Double Diamond: Process Framework, Not Prioritisation—And It Needs a Time-Box
Diverge-Converge Twice Is Great Advice, But Discovery Still Has to End
The Double Diamond describes how to do discovery—diverge, converge, diverge, converge. It's a process framework, not a prioritisation framework. Without time-boxing, it becomes an excuse for endless exploration.
Elements of Value Pyramid: Interesting Theory, Limited Practice
An Academic Framework That Doesn't Survive Contact with Roadmaps
Bain's Elements of Value pyramid—30 types of value from functional to life-changing—is an interesting academic framework and training aid. It's not useful for actual roadmap prioritisation. Skip it for practical work; reference it for product thinking discussions.
GE-McKinsey Matrix: Board-Level Portfolio Strategy, Not Feature Prioritisation
When Nine Boxes Beat Four—And When They Don't
The GE-McKinsey Matrix helps boards decide which product lines deserve investment. It's portfolio strategy, not feature prioritisation—here's when the 9-box grid earns its complexity over simpler alternatives.
GIST Framework: You Probably Already Have This Under Different Names
Take the Confidence Meter, Skip the Extra Terminology
GIST (Goals, Ideas, Steps, Tasks) offers a layered planning framework from strategy to execution. Learn how it compares to OKRs, when the confidence meter concept is genuinely useful, and why you probably don't need the full framework.
HEART Framework: Tag Your Roadmap for User-Centred Balance
Happiness, Engagement, Adoption, Retention, Task Success—Are You Measuring All Five?
Google's HEART framework—Happiness, Engagement, Adoption, Retention, Task Success—provides user-centred metrics coverage. Use it as a tagging framework to ensure your roadmap is balanced across UX dimensions, not just shipping features.
Impact Mapping: Always Think About the User (Because Most Roadmaps Don't)
Goals → Actors → Impacts → Deliverables: The Framework That Stops User-Free Planning
Gojko Adzic's Impact Mapping forces the question most roadmaps ignore: who are we building for, and what behaviour change do we need from them? It's the 'always think about the user' framework that architects desperately need.
Leading vs Lagging Indicators: Know If You're Winning Before It's Too Late
Predict Success with Leading Metrics, Confirm It with Lagging Ones
Leading indicators predict success; lagging indicators confirm it. Good OKRs pair lagging Objectives with leading Key Results—so you know whether you're on track before it's too late to course-correct.
North Star Metric: One Metric to Align Them All
Tag Your Roadmap to See What Percentage Actually Targets Core Value
Your North Star Metric is the single metric that captures core value delivery to customers. Tag Objectives in RoadmapOne to see what percentage of your roadmap directly targets your North Star—and whether the balance is right.
Opportunity Solution Trees: Discovery That Maps to Roadmap Reality
Outcomes → Opportunities → Solutions → Experiments (And How It All Becomes OKRs)
Teresa Torres' Opportunity Solution Tree connects outcomes to opportunities to solutions to experiments. It maps directly to RoadmapOne: Outcomes are Objectives, Opportunities and Solutions become Key Results, and we're always running experiments.
Product Lifecycle Stage: The Tag That Changes Everything About Prioritisation
Why the Same BRICE Score Means Different Things for Different Products
Product Lifecycle Stage—Introduction, Growth, Maturity, Decline—is a tagging framework that changes how you interpret prioritisation scores. A high-BRICE initiative for a declining product might still be the wrong investment.
PULSE Framework: The Outdated Metrics Model Your Dashboard Might Still Follow
If Your Metrics Look Like This, You're Missing the User
PULSE (Page views, Uptime, Latency, Seven-day active users, Earnings) is the outdated metrics framework that HEART replaced. It's still useful as a diagnostic—if your dashboard looks like PULSE, you're missing user-centred measurement.
Stack Ranking: The Prioritisation Panacea That Never Works
Why 'Just Put Them in Order' Ignores Reality
Stack ranking feels like the ultimate prioritisation solution—just order everything from 1 to N and execute. In practice, it ignores capacity, dependencies, and team skills. The item ranked last often must be built before the item ranked first. Roadmaps are art as much as science.
Technical Debt Classification: Internal Insight, Not Board Governance
When Categorising Debt Helps—and When It's Overhead
Technical debt classification helps Product & Engineering teams understand debt composition—but don't expect board engagement on categories. Tag debt-related Key Results by type (deliberate vs accidental, business-blocking vs aesthetic) when debt is a significant problem requiring structured remediation.
The 100 Dollar Test Is an Alignment Tool Disguised as Prioritisation
Use It for Buy-In, Not Backlogs
The 100 Dollar Test forces trade-offs by giving stakeholders fake money to allocate. It's better for alignment than prioritisation—the real value is the conversation it creates, not the numbers it produces.
The Eisenhower Matrix Has No Place in Roadmap Planning
It's Vocabulary, Not Methodology—Here's What to Use Instead
The Eisenhower Matrix isn't a prioritisation framework—it's vocabulary. Learn when the Urgent/Important grid helps board conversations and when it creates dangerous blind spots in your roadmap.
User Story Mapping: Tag Key Results by User Journey Stage
See Which Parts of the Customer Experience You're Actually Measuring
User Story Mapping isn't prioritisation—it's a tagging framework. The backbone represents user journey stages; tagging Key Results by backbone position shows which parts of the customer experience you're measuring. Use it alongside Pirate Metrics for complete journey visibility.
Weighted Scoring Is Subjectivity Wrapped in a Veneer of Objectivity
Why Bespoke Criteria Usually Produce Score-Gaming Theatre
Weighted Scoring promises customised prioritisation through bespoke criteria and adjustable weights. In practice, it usually produces score-gaming theatre. Learn when it works, when it fails, and why simpler frameworks usually win.
Stop Overloading Your Roadmap: Why WIP Limits Are the Most Important Rule in Product Planning
Why the single most important rule for building great product roadmaps is limiting work in progress—and how WIP limits transform both delivery speed and stakeholder conversations.
Objective Prioritisation: BRICE
RICE + Strategic Alignment = Roadmaps That Actually Serve Business Goals
BRICE extends RICE with Business Importance—forcing teams to explicitly score strategic alignment before reach and impact. Stop building high-impact features that don't matter to the business.
Objective Tagging: Pirate Metrics (AARRR)
Charting the Customer Voyage from First Click to Profit
A deep dive into Dave McClure's "Pirate Metrics", showing product teams how AARRR tagging reveals funnel leaks, drives focused experimentation, and turns growth conversations with the board from foggy to forensic.
OKRs for Product Teams: Why Most Implementations Fail (And How to Fix Yours)
The Implementation Guide That Doesn't Treat You Like a Beginner
76% of product teams attempt OKRs. Only 28% are satisfied with the results. Here's how to be in the 28%—with practical frameworks for objectives, key results, and roadmap connection.
Keeping The Lights On in Product Roadmaps
Stop pretending that 100% of your P&E team is doing feature development
Every engineering team must spend time on KTLO work—bug fixes, security patches, compliance updates, and technical debt. Yet many roadmaps assume 100% feature development. Here's why that's unrealistic and how to plan honestly.
Objective Tagging: Opex vs Capex
Help your finance team understand capital vs operational spend across your roadmap, enabling smarter budget allocation and tax planning.
How to Build a Product Roadmap That Actually Works
The Human Work Most Teams Skip
Most roadmaps fail not because of poor tools, but because teams skip the human work of building consensus. Here's how to create a roadmap stakeholders actually believe in—not just tolerate.
Objective Prioritisation: Benefit
When Absolute Value Matters More Than Investment Efficiency
Benefit prioritisation ranks objectives by pure value delivered—revenue gained or costs saved—over 12, 18, or 24 months. No ratios, no formulas, just pounds. The simplest framework the board will actually understand.
Objective Prioritisation: ROI (Return on Investment)
The Timeboxed Benefit Calculator Finance Actually Trusts
ROI prioritisation ranks objectives by benefit-to-cost ratio over 12, 18, or 24 months—simpler than NPV, more financially credible than gut instinct. When finance demands numbers but won't accept spreadsheet theatre.
Capacity-Based Roadmap Planning: Why Resource Allocation Matters More Than Feature Lists
PowerPoint roadmaps promise 47 initiatives. You have 12 squads and 26 sprints. The math doesn't work. Learn how capacity-based roadmap planning forces honest conversations about what actually fits—and why showing stakeholders the capacity constraint is your secret weapon for managing expectations.
Firebreak Sprints: When Your Entire Engineering Team Needs to Stop and Fix the Foundation
SonarQube just flagged 347 critical security vulnerabilities. Your DORA metrics are in the red. A threading bug is crashing microservices across the platform. Sometimes the whole team needs to stop feature work and fix the foundation. Learn how firebreak sprints work, when to call one, and how to insert them into your roadmap without destroying delivery commitments or losing stakeholder trust.
From Objectives to Key Results: How Product Managers Lead the Discovery Breakdown
Leadership allocates objectives. Empowered teams define key results. But how does that actually happen? Discovery is the collaborative workshop where product managers facilitate the breakdown from 'Increase retention 65% to 75%' to specific, validated, measurable key results teams commit to delivering. Master this moment—it's where PM leadership matters most.
Grid vs. Timeline: Why Squad×Sprint Grids Reveal Capacity Truth That Gantt Charts Hide
Gantt charts look impressive in stakeholder presentations. They're also lying to you about what's actually possible. Timeline views hide capacity constraints, create planning illusions, and let stakeholders believe you can 'just add one more feature.' Learn why grid-based roadmap planning forces honest conversations about trade-offs—and why that honesty is your competitive advantage.
Master Roadmaps vs. Scenario Planning: How to Plan for Multiple Futures Without Losing Your Mind
What if the budget gets cut 30%? What if we pivot to enterprise? What if the acquisition happens? Scenario planning lets you explore alternatives without destroying your master roadmap. Learn how to create, compare, and convert scenarios—without the version control chaos that kills strategic planning.
Milestones in Product Roadmaps: How to Track External Events, Board Meetings, and Governance Dates Without Chaos
Most roadmap tools mix milestones with delivery work, creating confusion about what's being shipped vs. what's happening externally. Learn how to track board meetings, product launches, conferences, and regulatory deadlines as first-class roadmap elements—ensuring teams plan backwards from constraints that matter.
Time-Boxed Discovery: Why Concentrated Discovery Beats Drip-Drip Validation Every Time
Most teams let discovery drip along for months, creating context switching and unpredictable capacity drain. Time-boxed discovery sprints produce better validation outcomes while making capacity planning honest. Learn why concentrated discovery beats ongoing research—and how to implement it.
7 Common Product Discovery Mistakes (And How to Avoid Them)
Avoid the seven most common product discovery mistakes that cause teams to build the wrong things. Learn how to conduct effective discovery that validates assumptions, engages customers, and delivers business value.
Allocating Team Capacity for Product Discovery: How Much Is Enough?
Learn how to allocate the right amount of team capacity to product discovery. Practical frameworks for balancing discovery and delivery based on uncertainty, risk, and product lifecycle stage.
Introducing RoadmapOne Version 3
Your Feedback Made This
RoadmapOne Version 3 is here—featuring full collaborative editing, first-class Discovery activities, customizable Objective Prioritisation with 15 frameworks, expanded Key Result and Objective tagging, plus major performance improvements. Built on your feedback.
Measuring Product Discovery Success: The Metrics and KPIs That Actually Matter
Learn which product discovery metrics actually matter. Stop counting activities and start measuring validated learning, cycle time, and outcome velocity with practical KPIs that drive better product decisions.
Product Discovery for Remote and Distributed Teams: Making It Work Across Time Zones
Master product discovery with remote and distributed teams. Learn practical strategies for running effective customer interviews, synthesis sessions, and collaborative discovery when your team is spread across locations and time zones.
The Product Manager's Guide to Leading Discovery: Building Team Ownership and Engagement
Master the product manager's most critical leadership role - guiding teams through discovery to break down objectives into key results, building ownership and enthusiasm for outcomes that matter to the business.
Objective Prioritisation: ARR
When Your Customers' Cheque Size Decides Your Roadmap
ARR prioritisation ranks features by the recurring revenue at stake—letting your highest-value customers vote with their wallets. When does revenue-driven roadmapping create strategic clarity, and when does it turn your product into a consulting service?
Objective Prioritisation: Buy a Feature
Gamification for Stakeholder Alignment—When Democracy Meets Budgets
Buy a Feature prioritisation turns stakeholder alignment into a budgeting game—give them fake money, price features by cost, let them buy what matters. Works brilliantly until the exec with the loudest voice monopolises the budget.
Objective Prioritisation: Cost of Delay
The Economics of Waiting—When Time Is Literally Money
Cost of Delay prioritisation quantifies the economic damage from waiting—then divides by duration to find maximum value per time. Every week you delay shipping costs £X. Which features cost the most to postpone?
Objective Prioritisation: Kano
When Customer Delight Drives the Roadmap—But Only After the Basics Work
Kano prioritisation sequences features by customer satisfaction psychology: Must-Haves first (or your product isn't viable), then Performance, then Delighters. Ship the basics before chasing wow moments.
Objective Prioritisation: NPV
When Finance Owns Your Roadmap (And Why That Might Be Good)
NPV prioritisation brings finance-grade rigour to roadmap decisions by calculating the present value of future cash flows. When should product teams embrace the spreadsheet complexity—and when should they run?
Objective Prioritisation: Payback Period
The Financial Metric Product People Actually Understand
Payback Period prioritisation ranks features by time to recover investment—the CFO's favourite metric because it answers 'when do I get my money back?' Simpler than NPV, more intuitive than IRR, but blind to what happens after break-even.
Objective Prioritisation: ICE
Fast Roadmap Decisions for Teams Who Can't Afford Analysis Paralysis
Sean Ellis's ICE framework—Impact × Confidence × Ease—is RICE's scrappy younger sibling. Built for speed over precision, ICE thrives when startups need decisions today, not perfect data tomorrow.
Objective Prioritisation: Manual
Executive Override and Political Triage—When Simple Beats Scientific
Manual prioritisation—a simple 1-10 scale—is what you use when frameworks feel like theatre and executive judgment beats algorithmic scoring. It's not surrender; it's pragmatism about how decisions actually get made.
Objective Prioritisation: MoSCoW
Scope Negotiation for Fixed-Deadline Projects That Can't Fail
MoSCoW—Must have, Should have, Could have, Won't have—is prioritisation stripped to its brutal essence. Perfect for fixed deadlines when stakeholders need to see exactly what gets cut if the timeline slips.
Objective Prioritisation: PIE
Potential, Importance, Ease—Prioritisation for Growth Teams Who Test Everything
Chris Goward's PIE framework—Potential × Importance × Ease—prioritises experiments and features by upside if successful. Built for growth teams optimising conversion, now used everywhere fast decisions matter.
Objective Prioritisation: RICE
Data-Driven Roadmaps for Teams Who Measure Everything
Intercom's RICE framework—Reach × Impact × Confidence ÷ Effort—turns gut instinct into quantitative roadmap decisions. Learn when RICE is your best weapon, and when it betrays you.
Objective Prioritisation: Value vs Complexity Matrix
Visual Clarity for Teams Who Think in Quadrants, Not Numbers
The Value vs Complexity Matrix—a visual 2×2 grid that turns abstract prioritisation debates into clear quadrants. Quick Wins, Major Projects, Fill-ins, or Money Pits—see your roadmap at a glance.
Objective Prioritisation: WSJF
Cost of Delay Economics for Large-Scale Agile—When It Works
WSJF—Weighted Shortest Job First from SAFe—prioritises by cost of delay divided by job size. Perfect for enterprises optimising economic urgency. Just beware SAFe's gravitational pull toward process over outcomes.
Opportunity Scoring: The Prioritisation Framework That Finds What Customers Actually Need
Importance Minus Satisfaction = The Gaps Worth Closing
Most prioritisation frameworks measure what you could build. Opportunity Scoring measures what customers desperately need but can't get. Stop guessing—find the gaps that matter.
Objective Tagging: Gartner's Run / Grow / Transform Modal
A pragmatic guide to Gartner's Run-Grow-Transform portfolio lens and how product managers can use it to balance operational excellence with bold innovation.
Key Result Tagging: Committed vs Stretch Goals
The OKR Distinction That Separates Winners from Wishful Thinkers
Master the OKR fundamental that Google lives by—Committed goals demand 100% delivery, Stretch goals target 60-70% ambition—so boards and teams finally speak the same language about expectations.
Key Result Tagging: Confidence Level %
From Static Predictions to Dynamic Risk Signals
Track evolving confidence (0-100%) in achieving each key result—not as a static guess but as a living signal for when to double down, pivot, or pull the plug before it's too late.
Key Result Tagging: Level of Ambition
From Moonshots to Certainties—Calibrating Stakeholder Expectations
Signal where teams stretch versus deliver with certainty—Low, Medium, High ambition, or High Integrity Commitments—so stakeholders calibrate expectations and debates shift from blame to learning.
Key Result Tagging: Metric Type
When Numbers Tell Half the Story—Balancing Metrics with Meaning
Balance numbers with nuance—tag key results as Quantitative (metrics), Qualitative (insights), or Boolean (yes/no outcomes) to ensure you're not optimising spreadsheets while missing the stories that matter.
Key Result Tagging: Outcome vs Output vs Input
The Measurement Hierarchy That Separates Motion from Progress
Stop celebrating deliverables while impact stalls—tag key results as Outcomes (impact achieved), Outputs (deliverables produced), or Inputs (activities performed) to measure what actually moves the business.
Key Result Tagging: R&D Tax Credit
From Engineering Work to Tax Relief—Tagging What Qualifies
Turn qualifying R&D work into tax relief by tagging key results that prove technical uncertainty, systematic investigation, and genuine innovation—making claims audit-ready before HMRC comes knocking.
Key Result Tagging: Validation Method
Experiments vs Assumptions—The Difference Between Science and Wishful Thinking
Distinguish hypothesis-driven experiments from assumption-based guesses—tag how you're validating key results to expose which teams build on data and which gamble on intuition.
Objective Tagging: Core vs Context
Crossing the Chasm by stopping the Resource Drain on Work That Won't Win the Market
How Geoffrey Moore's Core-versus-Context distinction helps SaaS leaders protect differentiation, outsource the ordinary, and explain tough resourcing calls to the board.
Objective Tagging: Customer Journey Stage
From First Touch to Loyal Advocate—Mapping Roadmap Work to Lifecycle Stages
Map your roadmap to the customer lifecycle—Awareness, Consideration, Conversion, Retention—and ensure balanced investment across every stage from first touch to loyal advocate.
Objective Tagging: Jobs-to-be-Done
Why Customers Hire Your Product—and How to Tag Your Roadmap Accordingly
Stop building features and start hiring your product for jobs—Functional tasks, Emotional desires, and Social aspirations—that reveal why customers truly choose you.
Objective Tagging: Kano Maps
Using Kano Maps to Build Love, Not Just Loyalty
Leveraging the Kano model—Must-Have, Performance, and Delighter attributes—to balance foundational reliability with wow moments on the product roadmap.
Objective Tagging: McKinsey's Three Horizons of Growth
How RoadmapOne users can use McKinsey's Three-Horizons model to structure short-term wins, mid-term bets, and long-term moon-shots without starving any of them.
Objective Tagging: SAFe Enablers vs Business Features
Giving Platform Work the Story it Deserves
Demystifying SAFe's Enabler-type backlog items and showing product teams how explicit tagging sharpens conversations with technical architects and boards alike.
Objective Tagging: SVPG Product Risks
Categorising Value, Usability, Feasibility, and Business Viability to de-risk the Roadmap
Using Marty Cagan's four product-risk categories—Value, Usability, Feasibility, Business Viability—to tag roadmap items, focus discovery, and make risk mitigation a first-class metric.
Objective Tagging: The Balanced Scorecard
Turning Strategy into Everyday Product Choices
Translating Kaplan & Norton's Balanced Scorecard into a roadmap-tagging lens that aligns product portfolios with strategy through Financial, Customer, Internal Process, and Learning & Growth perspectives.
Objective Tagging: The BCG Product Portfolio: Stars, Cows, Question Marks, Dogs
Letting the BCG Matrix Tell You When to Milk and When to Feed
Applying the classic BCG Growth-Share Matrix (Stars, Cash Cows, Question Marks, Dogs) to product portfolios and showing how roadmap tagging clarifies funding bets.
Objective Tagging: The Innovation Ambition Matrix
Escaping the Core Comfort Zone
Use RoadmapOne to align ExCo on your your Product Roadmap. Analyse according to a dozen resource allocation models, including the Innovation Ambition Matrix. Instantly categorise Objectives according to Core, Adjacent, and Transformational.
Size REALLY Matters: Finding the Squad Size Sweet Spot
Your Squads should be three developers, plus or minus two. Discover why squad size impacts planning effectiveness, why individual-level planning creates fragility, and how to structure teams for accountability and successful delivery.
Start with Why: Why We Are Building RoadmapOne
In 'Start with Why', Simon Sinek's proposes that great leaders and organizations inspire action by first explaining *why* they do what they do before explaining *what* they do or *how* they do it. So here's our Why...