How to Present a Product Roadmap to the Board

Most advice about presenting a roadmap to the board is really advice about making slides. Use fewer words. Don’t read from the deck. Colour-code your confidence levels. Tell a story.

I have sat through a lot of roadmap presentations from the other side of that table — as a non-executive director, and in due diligence on businesses somebody is about to buy. I have never once formed a view about a product team based on their slide design. What I form a view about is whether the thinking behind the roadmap is any good, and whether the person presenting it has done the work.

To present a product roadmap to the board, split it into three conversations rather than one. Run work needs no meeting, only an annual allocation figure. Grow work gets presented and pressure-tested every board meeting, as a cycle of hypotheses and outcomes. Transform work needs individual conversations with board members weeks in advance, so the meeting itself ratifies a decision rather than debates one.

That structure is easier to hold when the roadmap itself is built around capacity rather than dates. RoadmapOne exists to make the allocation visible: which squads are working on which objectives, in which sprints, and what percentage of your engineering capacity is flowing to each tier. A board cannot pressure-test a resourcing decision it cannot see, and most roadmap decks hide exactly that — they show what the team is doing, never what the team is not doing as a consequence.

Sign up (free) to show your board where capacity actually goes

What the Board Is Actually Buying

One of the more important jobs of a board is to pressure-test the management team: to ask the questions that probe the thinking underneath a plan. So when a CPO stands up with a roadmap, what the board is looking for is evidence and insight — why now is the moment to resource hypotheses X, Y and Z, and why those matter more than D, E and F, which are not getting resourced at all.

That last clause is the whole game, and almost nobody puts it on a slide.

“Clarity of Thought” Is Not a Platitude If You Can Say What It Looks Like

Every article about board presentations tells you the board wants clarity. Fine. But clarity is observable, and so is its absence.

A team with clear thinking can tell you which customer problem they are solving, for which segment, what they expect to change, and what they are giving up to do it. They can describe the two or three problems they considered and discarded, with the numbers that made them discard them. Push on a figure and they can tell you where it came from and which parts of it they doubt.

A team without clear thinking presents a list of things they are going to build, each with a benefit attached, and every benefit is positive. Nothing has been given up. No trade-off appears anywhere. Push on any number and the answer is fluent and non-specific.

The tell is not confidence — plenty of muddled teams are confident, and some of the best product people I know are visibly uncomfortable presenting uncertainty honestly. The tell is whether the reasoning survives one layer of questioning.

The Unresourced List Is the Most Valuable Slide You Will Ever Write

If there is one change I would make to most roadmap decks, it is this: add the list of things you are not doing, and say why.

It feels like exposure. It is actually the opposite. A roadmap where everything is resourced tells the board nothing about your priorities, because a priority is only real when something else loses. There is always more work than capacity — the board knows this perfectly well, and a deck that pretends otherwise reads as either naïve or evasive.

It also protects you. When the discounted list is visible, the conversation about whether you picked correctly happens in the open, with the board’s experience in the room. When it is invisible, that conversation happens later, without you.

Three Tiers, Three Different Conversations

The most common mistake is treating the roadmap as one artefact requiring one presentation. It is three, and they need radically different treatment. I use Run, Grow, Transform as the organising frame because boards grasp it immediately, but the point is not the specific taxonomy — there are twenty-odd objective tagging methodologies and plenty of businesses are better served by a custom “how we will win” split. The point is that different categories of work deserve different levels of board involvement.

Run: No Meeting Required

The board does not need a discussion about keeping the lights on. It needs one number: over the course of twelve months, we will allocate somewhere between 20% and 40% of our roadmap capacity to Run.

I have never sat in a board meeting where a realistic KTLO allocation was questioned. Not once. Boards understand that software needs maintaining and that a business which stops paying this tax pays a much larger one later.

What I have seen several times is Run work dressed up as Grow work to keep the ratios looking respectable — a compliance upgrade filed under customer experience, a platform migration presented as a growth enabler. That is a bad smell, and not because of the dishonesty. It signals that the team has not thought hard enough about which customer problems they want to solve, so they are backfilling the growth column with work that was happening anyway. The honest version is easier to defend, and the maintenance number was never going to be challenged.

Grow: Presented, Pressure-Tested, and Compounding

Grow is the tier that belongs in the meeting itself. This is where the board should be testing that you are making good decisions — not micro-managing your delivery.

Credibility here is built one meeting at a time, in a cycle: present the hypothesis for a good problem to solve, go and solve it, come back and present the outcome — including the ones that did not work. Do that three or four quarters running and the questioning gets shorter every time. That is what earned autonomy looks like, and no single excellent presentation grants it.

Transform: Where the Board Earns Its Keep

Transform is different in kind. These are the initiatives that change what the business is, they are usually expensive, you can rarely resource all of them, and the discussion is frequently contentious.

A transformational investment should never appear at a board meeting for the first time as a funding request. By the time it is formally on the agenda, it should have been discussed, challenged and reshaped over several previous conversations. More on the mechanics of that below, because it is the part of this article that contradicts everything else written on the subject.

The Guardrails Are Annual Ratios, Not Quarterly Rules

A useful starting point is roughly 20–40% Run, 50–60% Grow, and around 10% Transform. Treat those as guardrails to structure the thinking, not as a compliance target.

Two caveats matter enormously. First, these are ratios you expect over twelve months, not rules for the next three. A quarter that is 70% Run because you are finally replacing an ageing platform is not a failure; a year that looks like that is a business quietly deciding to stop growing. Second, the right split depends on where each product sits in its lifecycle and what else is happening commercially — a portfolio of products at different stages will have several sensible splits rather than one, which is exactly why balancing them against a single capacity pool is a board-level conversation.

Watch for a team managing the ratio rather than the business. Once a number becomes a target somebody will hit it, and they will hit it by relabelling work rather than changing it.

What a Good Grow Slide Actually Contains

Here is the shape I want to see for a Grow initiative. Not a feature list — an argument.

We are going to spend three months improving our early-life customer experience, because we believe we can get 10% more new customers to become active. That reduces our cost per acquisition and increases revenue. Here are the specific problems we have identified in that first-run experience. Here are our hypotheses about how we might solve them. Here is what we expect to accrue if we are right, and here is how we will know.

That is one slide, and it does more work than twenty feature bullets, because it connects a customer problem to a business outcome and puts a falsifiable number on it. It is also written in the language of outcomes rather than outputs , which is what makes it discussable by people who do not work in your product organisation.

The Discounted Problems Slide

I am not a fan of now/next/later as a roadmap format, but for Grow initiatives there is a version of the idea that earns its place: a slide covering the problems you looked at and chose not to pursue.

For example: we see 60% drop-off immediately after search, and reducing it by 10% would improve conversion by two percentage points — roughly a million dollars of annual revenue. We are not doing it this quarter, because those numbers look very different for large customers than for small ones and we need more time in discovery before we jump to solutions.

Read that as a board member. The team has quantified an opportunity they are declining, spotted a segmentation problem in their own data, and resisted the urge to build anyway. I would fund that discovery time without hesitation — the opposite of what most people fear when they admit they do not yet know.

Four Questions That Separate an Earned Number From a Decorated One

Any team can put “10% uplift in activation” on a slide. In a twenty-minute agenda slot, the board cannot audit the analysis. So we probe instead, and the questions are always some version of these four.

1. Which segments are disproportionately getting through?

This is a request for the data underneath the hypothesis. Has the team genuinely unpacked it, or is this half-hearted?

The worst case is real and common: it turns out 80% of large customers make it through the flow and only 30% of small ones. Optimise the average and you risk making life worse for the big, valuable customers while chasing an uplift among the small ones. Users do not experience averages , and a single blended conversion number is often hiding two completely different products being used by two completely different populations.

A good answer names the segments and the split. A bad answer says “we looked at it and it’s broadly consistent” without showing the cut.

2. How will you roll it out — and can you roll it back?

A/B test, or a staged ramp at 1%, 2%, 5%, 10%, 15% of traffic? What is the kill criterion, and can you reverse it cleanly?

This question is not really about product reasoning; it is about engineering credibility. A team that has thought about staged rollout and rollback is a team that expects to be wrong occasionally and has built the machinery to survive it. A team that has not is planning to ship a change to 100% of customers on the strength of a slide they wrote for a board meeting.

3. What did recently joined customers actually tell you?

By segment. What did they say that made you believe this uplift is achievable?

The trap here is inferring intent from behaviour that has none. Some proportion of the people abandoning your onboarding were only ever shopping and will never convert, no matter how elegant you make the flow. If the team has talked to recent joiners and can quote them, the number gains weight. If the entire case rests on funnel analytics with no human contact, it is a decorated number.

4. Where is the moment of truth, and how is the current experience failing it?

Almost every product has a threshold moment where a browser becomes a customer — funding a wallet, inviting a colleague, uploading the first real data set, completing a first transaction. If a team cannot name theirs, they do not yet understand their own activation problem, and the rest of the slide is decoration.

If they can name it, the follow-up is simple: what specifically about the current experience stops people crossing it, and how do you know?

Sign up (free) to connect roadmap outcomes to squad capacity

Transform: The Real Work Happens Before the Meeting

Now the part that contradicts the rest of the internet.

If a major Transform investment is being challenged for the first time during the board meeting, you have already failed at the job. By the time it reaches the agenda, everybody in the room should already be signed up.

The Reframe: the Board Is a Resource, Not an Audience

The pre-meetings are not lobbying. They exist so that the CPO can use the experience of the board to inform the Transform roadmap. That is a genuine reframe: not “CPO reports to board”, but “board helps CPO”.

Most boards contain people who have done versions of what you are about to attempt — entered a new market, taken a platform product to a new customer segment, survived a pricing transition. Presenting a finished plan to that group wastes them. Walking them through the problem while the plan is still forming does not.

Yes, This Rewards the Politically Fluent — Deliberately

Does this advantage the CPO who spends time with the non-executives over the one who simply has better evidence? Yes. And that is what I want from the role.

Spend the time. Walk them through the proposals individually. Let them ask their questions before the meeting, then go away and come back with the data points that address their challenges. There are no universally right or wrong board members to work with — knowing who has the most to offer on a given initiative is the political savvy the job requires. As a CPO it is far better to take a hard challenge in a one-to-one than to be exposed by it in front of the full board.

This is also good news for the honest but less political product leader, because it is a process rather than a personality. Sequenced conversations, revised evidence, no surprises. Anyone can learn that.

What a Transform Ask Has to Contain

The questions get harder at this tier, and they are mostly about whether the rest of the organisation is ready to deliver.

Which customers have you actually spoken to, and how many have agreed to take the solution? What does the rollout plan look like? Is sales trained, support staffed, marketing ready, pricing agreed? And why is this initiative more important than the other two we cannot fund this year?

I have watched a great many teams tie themselves in knots here, and the root cause is almost always the same: they cannot articulate the value of the competing initiatives clearly enough to rank them, and they have not lined up customer commitments. Without those two things prioritisation collapses into advocacy, and the loudest initiative wins. A proper business case is the antidote, and the most under-used artefact in product management.

The other Transform failure is resourcing. Work handed to a team side-of-desk will not happen, however enthusiastic the meeting was. It needs a dedicated minimum viable team — two engineers and a product person, protected and full-time, as a floor. If the business cannot find that, the initiative is not funded, and it should come off the roadmap rather than linger as a zombie .

What Actually Happens When a Team Fails the Questions

Here is the part nobody warns product leaders about. The board waves the deck through anyway — particularly for Grow, where intervening would be micro-management.

But something has changed. There is now a question about resource allocation and about process, and the credibility of the CPO is in play. Can we trust them going forward? Should we spend more time explaining what we expect? Keep it up and, eventually, the exit lounge beckons.

The same lens applies in due diligence, where we are always assessing the calibre of the team. Are these leaders or caretakers? Will we have to invest in extra headcount or capability once we own the business? A roadmap that cannot survive four questions rarely stops a deal — it gets written up as a management-team risk and priced in, which is a slower and more expensive verdict than being told no.

Transform is the exception to the wave-it-through rule. There, insufficient clarity hits a much more robust roadblock, because the money is larger and the organisational commitment is deeper.

A Note on R&D Spend as a Percentage of Revenue

Boards do ask what proportion of revenue goes into research and development, and it is worth having the number to hand. It is also worth being careful with benchmarks, which get quoted with far more authority than they deserve.

Different companies at different lifecycle stages run wildly different ratios, and an innovator may legitimately spend twice what a laggard does. Comparing yourself with a published median tells you very little about whether your own number is right.

What is genuinely diagnostic is the shape of the series. In diligence I look for a discontinuity: 8.5%, 9%, 9.5%, then suddenly 7%. That is rarely an efficiency gain. It is usually a management team flattering the P&L ahead of a process, and the buyer inherits an underinvestment that costs more to dig out of than was ever saved. If your own R&D line has a step change in it, get in front of it — somebody will find it. (This deserves its own article, and will get one.)

The Board Pack: Five to Ten Slides, Because They Have Read Fifty Decks

A non-executive may read fifty decks between your board meetings, and will skim yours among many others, often the night before. So the pre-read is a five-to-ten-slide summary whose job is to set up the discussion and carry the salient points — not to contain everything you know. Depth goes in an appendix the interested reader can reach for and the busy one can ignore.

Lead with the allocation picture — how capacity splits across the three tiers, and how that compares with last quarter — then the Grow outcomes from last time, the Grow hypotheses for next time, and whatever Transform decision is live. Write it so that someone who reads only the first slide still knows what you want from the meeting.

When These Rules Change

All of the above assumes a business broadly on plan. If you are missing revenue targets, the board will dive much more deeply into Grow and the polite division of labour evaporates — appropriately, because governance intensity should track business risk. A company mid-platform-replacement, or preparing for a transaction, will want far more detail on Run than usual. The tiers are a default, not a constitution: frameworks are tools in a kit bag , and the situation decides which one you reach for.

Common Mistakes

In rough order of how often I see them: presenting output rather than outcome , so the deck is a feature list with dates and no statement of what changes for customers or the P&L; hiding the trade-off, so the board cannot see what was declined; smuggling Run work into Grow to protect the ratio; bringing a Transform funding request cold; presenting a blended metric that conceals two very different segments; and treating the board as an audience to impress rather than experienced people to use.

A special mention for the roadmap that changes shape every quarter. Boards forgive a plan that missed; they do not forgive a plan that keeps being replaced , because it tells them nobody is actually steering.

Sign up (free) to make your board’s allocation question answerable

Frequently Asked Questions

What should be in a product roadmap for a board?

A board roadmap needs four things: the allocation split across Run, Grow and Transform over the next twelve months; the outcomes delivered since the last meeting; the hypotheses you are resourcing next, each tied to a customer problem and a business metric; and the significant opportunities you have deliberately declined, with the reasoning. Feature lists and delivery dates belong in the appendix, not the summary.

Can you provide an example of a product roadmap slide for a board?

A strong Grow slide reads as an argument: “We will spend three months improving early-life customer experience, targeting 10% more new customers reaching active status, which lowers CPA and raises revenue. These are the three problems we found, these are our hypotheses, this is how we will measure it, and this is what we expect to accrue.” One slide, one customer problem, one falsifiable number.

What questions do boards ask about the product roadmap?

The recurring four are: which customer segments are disproportionately affected, and what does the data show when you cut it? How will you roll this out, and can you roll it back? What did recently joined customers tell you that makes this achievable? And where is the moment of truth where a shopper becomes a customer, and how is today’s experience failing to get them there?

How often should a CPO present the roadmap to the board?

Every board meeting, but not with the same content each time. Grow belongs in every meeting as a rolling cycle of hypotheses and outcomes. Run needs only an annual allocation figure. A Transform initiative should appear several times across quarters — as an emerging problem, then as a shaped plan, and only then as a funding request.

Should the board approve the product roadmap?

No. The board’s job is to pressure-test the thinking behind the allocation, not to sign off the contents. Boards that approve roadmaps end up owning delivery, which removes the accountability that should sit with the CPO. The exception is a major Transform investment, where the capital commitment genuinely is a board decision.

What are some tips for presenting effectively to executives?

Lead with the decision you want, not the background. Keep the pre-read to five to ten slides and push detail into an appendix. Never let a hard question be asked for the first time in the room — surface it in a one-to-one beforehand. Show what you declined as well as what you chose. And answer “I don’t know yet” honestly when it is true; it costs less than a fluent guess that unravels later.

Conclusion

The best roadmap presentations I have seen from the board seat had nothing in common visually. What they shared was a team that had genuinely done the work, could show the data underneath their claims, and were willing to say out loud what they had chosen not to do. The worst ones were confident, comprehensive and completely unfalsifiable.

Split the conversation into three. Give Run a number and move on. Use Grow to build credibility one honest cycle at a time. Take Transform to your board members individually, early, while the plan is still soft enough for their experience to improve it. Then make the meeting itself the least surprising twenty minutes of the whole process.

Boards are not scoring your slides. They are deciding whether you are a leader or a caretaker — and the roadmap is simply the evidence you have chosen to submit.