Product roadmap presentation: one roadmap, four audiences

Once a roadmap is agreed, it has to leave the product team. The workshop had only a few people in it; the engineers and the salespeople who talk to clinics every day weren't there. You share a roadmap for three reasons:

• Inspiration: people see why the work matters.
• Alignment: every team can plan its own work around it.
• Ownership: people care more about a plan they've had a hand in.

The board, sales and marketing, engineering and a partner all need something different, and the tempting answer is a separate roadmap for each. Don't. Separate roadmaps drift apart within weeks, and then two teams plan around two different stories.

Keep one foundation for everyone: vision, objectives, themes and timeframes. Then build a view per audience by adding what that audience needs on top: progress for the board, confidence for sales, dependencies for engineering, conditions for a partner. Change the foundation, and every view changes with it.

A board thinks in investments and returns. In fifteen minutes it wants to know three things: where the product is going, whether it's working, and what the money buys.

So the board's view adds to the foundation:

• the vision and the objectives, with what their key results show so far;
• what has changed in the market, such as how the clinic channel is developing;
• what next quarter's budget buys.

Keep the details on hand, not on the slides: RICE scores, the warehouse migration plan with its milestones, the stage of every item and the “not now” list. If a director asks about the portal or the quiz, answer briefly and move on.

Putting the full internal roadmap in front of a board looks thorough, but it invites the board to manage the work itself. Fifteen minutes spent re-ranking candidates are fifteen minutes not spent on whether the objectives are worth the money.

A board's appetite for detail falls as its trust grows. When directors are confident the work is going well, they ask about objectives, the market and money. When they start digging into individual features, how a quiz is designed or which screen comes first, they are usually worried about how the work is going.

That changes what you do next. Adding more feature detail to the next deck feeds the worry; it tells the board that managing the details is now their job. Inviting directors into design sessions does the same.

What rebuilds trust is making progress easy to see:

• what moved: for example, 8 of 9 pilot orders without a call, stock-outs down from 6 to 5 a month;
• what didn't: churn still at 9%, said plainly before anyone asks;
• what happens next, and what it depends on.

The less the board needs to ask, the better it's usually going. Your job is to report so clearly that the digging stops by itself.

Sales and marketing plan campaigns and customer conversations, so their view adds to the foundation exactly what those plans depend on:

• the stage of each theme: is it being explored, tested or built?
• the target customers: which theme is for subscribers, which for clinics, which for new owners;
• the confidence the team has in each column, so they know what's safe to talk about;
• the external events they plan around, such as the conference on 23 May.

Two things stay out. Prioritization scores such as RICE are internal working material; in a sales deck they invite debates about the method instead of the customer. And a launch date for something that isn't on the plan, like the clinic portal, would turn a wish into a promise the moment a salesperson repeats it to a clinic.

A good test: could a salesperson read this view and know what to say to a clinic tomorrow, and what not to say yet?

Confidence, the per-column measure from Going deeper, matters most right before money is spent. Brochures, ads and a launch at a stand are bets that something will exist and work by a date. Make them when the item is being built and confidence is high, not while it's still being tested.

Marketing wants to print brochures for the conference on 23 May: “The CatChow clinic portal, now live.” The portal isn't even on the plan; the form is, and it is still being tested. Printing that claim now would turn a candidate into a public promise, and if it slipped, the brochures would go in the bin along with some of your credibility.

That doesn't mean telling marketing to wait with nothing. Give them what is solid:

• the outcome they can plan the stand around: clinics reordering without a phone call;
• a date for the decision: what to print gets decided at the March review, once the form has run in all 14 PurrPoint clinics;
• real proof to use then, such as a pilot clinic's numbers.

Engineers read a roadmap to plan the work, so their view goes deepest. Under each theme it adds:

• the likely features: for the clinic theme, the online form for all 14 PurrPoint clinics, then the other partner clinics;
• the stage: testing, building;
• the dependencies: clinic orders move to the new system first, then the form can reach all PurrPoint clinics;
• the risks: parts of the old system nobody documented.

Features go to engineers for feasibility feedback, not as orders with deadlines. They know where the hard parts are, and their answer can change the order.

This view also gives technical debt a line: old shortcuts and features that slow down every change. The example of Lucy, the tech lead, is gift cards: twelve people used them last year, yet the team tests them in every release. On the roadmap, that cost competes for time in the open instead of eating it quietly.

The board doesn't need gift cards and PurrPoint doesn't need dependencies. Same roadmap, different depth.

Picture two scales: how much detail a view carries, and whether the reader is inside the company or outside. Internal views for the board, sales and engineering carry detail and new directions. An external roadmap for customers or the public shows far less of both. The further out the reader, the less detail.

Customers ask for features and dates, but what they usually need is proof that you've heard them, that you're working on their problem, and that you'll tell them more when you know it.

A public roadmap page has three risks:

• Overpromising: anything on it reads as a commitment.
• Competitors read it too, for free.
• The Osborne effect: announcing a better product too early, so customers stop buying the current one and wait for the next. If CatChow announced a clinic portal, new clinics might wait for it instead of signing now, and sales would drop before the portal even existed.

So a public page has to earn its place, and when it exists, it shows what's delivered or contractually fixed.

Every audience gets the same vision, objectives, themes and timeframes, plus what it needs to act:

• The board judges the investment: progress on the key results, changes in the market, what the budget buys.
• Sales and marketing plan campaigns: stage, target customers, confidence, external events.
• Engineering plans the work: likely features, dependencies, risks, technical debt.
• A partner like PurrPoint needs to see its own problem being solved: what changes for its clinics, what's been delivered, what comes next and on what condition, and a partner disclaimer, one of the audience versions from Timeframes and the roadmap disclaimer.

The partner page is the one most easily ruined. Write it for the people who read it, here a procurement manager and her admins. Put their results in (an order now takes about five minutes instead of a twenty-minute call). State the condition next to the date: February for all 14 clinics, once clinic orders move in January. A condition they know about is a plan; a condition they discover later is a broken promise. And leave out everything that isn't theirs: subscribers, other clinics, Later.

You don't need four decks written from scratch. Before each meeting, answer four questions:

1. Who's in the room, and what have they seen before?
2. What do you want from them: input, agreement, or just awareness?
3. What do they care about?
4. Which parts of the roadmap answer that?

Then tell it in the same order every time:

1. Why: the vision and a real story, like the clinic admin who used to lose her Monday mornings on the phone.
2. Progress since last time: what's live, what the pilot showed, and what hasn't moved yet.
3. The near term: the next quarter and what it depends on.
4. The longer term, with confidence clearly falling.

Progress comes before the plan because trust comes from what you've done, not what you promise. For a two-minute opening, use only the first two parts, with real numbers, including the ones that haven't moved.

How it fits together: One foundation, a view for each audience, and the same telling order every time: why, progress, near, long. Next, Keeping it fresh: what happens when the plan meets the next month.