Most product teams know what they're building next week and can't say what they're building next quarter, or which company objective it serves. Initiatives get decided in one conversation and built in another, design finds out late what development can actually do, and Sales and Customer Success learn about a feature from the release notes. This guide walks you through three processes that fix that: a product roadmap that links every initiative to the company's objectives and shows what each one is worth and how long it takes, a way of working through each initiative with design, development, Sales, Customer Success and Marketing, and a monthly product review that checks whether what you shipped is working. Start with one, or run all three together.
The roadmap is a list of features with dates, and nobody can say which company objective each one was meant to move.
Design and development work from different ideas of the feature, and Sales sees it for the first time when a customer asks about it.
A handful of accounts try it once, and the next roadmap gets planned without anyone asking why.
What keeps a product team building the right things is a handful of habits, each with one job: decide which initiatives deserve the year and roughly how long each will take, bring every team in at the moment their knowledge changes the decision, and check every launch against what it was meant to achieve. Here are the three that matter most, who they're for, and when each one helps.
Product leads map the initiatives that support the company's objectives, each with a brief, user stories, a mock-up and a rough estimate, and place them in quarters.
Start here if your roadmap is a list of features nobody can connect to the company's goals.
Process 2 · Every initiativeProduct works through each initiative with design, development, Sales, Customer Success and Marketing, from the competitive analysis to the internal training.
Start here if design, development or the teams who sell and support it keep finding out about decisions too late.
Process 3 · Every monthProduct, development and design leads look at what shipped, how it's performing and what's stuck, and decide what to keep, improve or remove.
Start here if you ship a lot but can't say what's actually moving the numbers.
They work on their own and they work better together. The roadmap decides which initiatives are worth the year, the initiative process brings every team in at the right moment so each one gets built well, and the product review checks whether it worked before the roadmap is revisited.
A roadmap is not a list of promises. It's a map of how the product will support the company's objectives over the year, with every initiative described well enough to discuss, estimated well enough to compare and placed in the quarter you expect to work on it. It will change as you learn more about your users, and it's built to.
Every initiative on the roadmap should be there because it helps the company reach one of its objectives for the year. Write those objectives down first, then gather the initiatives, features and product changes that could move each one, whether they come from customers, Sales, Customer Success, the data or your own view of where the product needs to go.
Every initiative answers to an objective.
If an initiative can't be linked to one of the company's objectives, either it points to an objective nobody has written down yet, which is worth raising with leadership, or it doesn't belong on this year's roadmap.
A long list of candidate initiatives is hard to hold against five objectives at once. AI can do the first pass, so the team spends the session debating the links rather than drawing them.
Mobile app was the most requested idea of the year, and it still didn't link to any of this year's objectives. Writing that down is what lets the team say so with a reason.
An initiative can't be compared with the others until people can picture it. Hold a short session for each one with product, design and development, and leave with a one-page brief that explains the problem or the opportunity, a handful of general user stories, a rough mock-up of what it could look like and an honest sense of how long it might take.
A starting point, not a promise.
Nothing in the session commits the team to building exactly that. It's where the initiative starts, based on what you know today and the company's objectives, and the solution will change as you learn what users actually want, what they really need and what they're willing to pay for.
Most of a roadmap session goes to writing. AI can draft the brief and the user stories from the notes you already have, so the hour goes to the conversation, the sketch and the estimate.
Ten minutes of sketching on a whiteboard is enough. Its job is to make sure everyone discussing the estimate is picturing the same thing, not to decide what gets built.
With every initiative briefed and estimated, the conversation the roadmap is really for finally becomes possible: which initiatives bring more revenue or get you closer to the goal, and how fast each one gets you there. A six-month initiative that could double expansion revenue and a one-month change that unblocks five deals are both good bets, and the roadmap is where you decide their order, write down why, and place each one in the quarter you expect to work on it.
Revisit the roadmap every quarter with what you've learned since the last one. Some initiatives will turn out bigger or smaller than they looked, some will matter less once you talk to customers and some will jump the queue because of a deal or a competitor. That's the roadmap working as intended, as long as every change goes into the decision log with its reason.
AI can suggest a first order across the year from the values and estimates you've agreed, and point out the dependencies and trade-offs before the team sits down to decide.
The chart doesn't make the decision for you. It makes the fast wins obvious and puts the slow, expensive bets where everyone can see them, so the discussion is about the ones that are genuinely hard.
This is where product gets hard. Every initiative touches design, development, Sales, Customer Success and Marketing, and each of them knows something product doesn't. This process is the minimum sequence that brings each team in at the moment its knowledge changes the decision, from the competitive analysis at the start to the internal training before launch, and you can add your own key sessions along the way.
Before deciding what the initiative should become, look at who already solves this problem and how. List the competitors with similar features or solutions, be honest about where you are today compared with them, and then decide where you want to be, because not every feature needs to be the best in the market and some of them could be the reason customers choose you.
Sometimes the honest answer is that being at par is enough, which can save months of work. Other times the analysis shows that something no competitor does well is exactly where you can win, and that changes how much the initiative deserves.
AI can do the first round of research across competitors' sites, help centres and reviews, so the team starts the discussion from a complete picture instead of from memory.
The brief turns the roadmap session and the competitive analysis into one page the whole team can work from. It's the first thing design, development, Sales, Customer Success and Marketing read about the initiative, so it explains the problem, who has it, why it matters now and how you'll know it worked, without deciding the solution yet.
Everything the brief needs already exists in the roadmap session notes and the competitive analysis. AI can pull it into one page, so product reviews and sharpens it rather than writing it from scratch.
A list of requirements hides the order in which people actually use something. A user story map lays out the steps a user goes through from left to right, with everything they need at each step stacked underneath, so the team can see every requirement at once and draw a line under what goes into the first release.
AI can turn the brief into a first draft of the map, which is often the fastest way to find the steps and stories the team forgot.
Everything above the line lets an admin complete the journey from start to finish. Everything below it is real, and it waits for what the first release teaches you.
Design gets the brief, the story map and the release line, along with a checklist of what the solution will be evaluated against. The checklist keeps design focused on the decisions that matter, and it gives product, design and development the same way to judge the result, so the review is about the checklist rather than about taste.
AI can write the design checklist from the brief and the story map, and come back to it at the review to check each option against every item.
Developers see costs and shortcuts in a design that nobody else can. Share the design with them before it's final and ask what's feasible, what's expensive and which alternatives would deliver most of the value in less time, because a small change on paper at this point can save weeks of development later.
AI can review the design from a developer's point of view before the session, so the team arrives with the likely cost drivers and a few alternatives already on the table.
Four weeks saved before a line of code was written, and the first release still covers every story above the line.
Sales and Customer Success talk to customers every day and know things that product and design often don't. Asking them "any feedback?" gets you opinions about colours, while asking specific questions gets you the information that changes decisions: use cases nobody considered, clients who could test it early, things already promised and risks you haven't seen.
AI can send the questions, collect the answers from everyone in Sales and Customer Success and turn them into the handful of decisions product needs to make, instead of a thread nobody has time to read.
Some initiatives need a yes from the CEO, the CFO or a department leader before development starts, because of their cost, their risk or what they promise to customers. Put that approval here, once design, development, Sales and Customer Success have shaped the initiative and before the expensive part begins, rather than at the demo when a no costs weeks of work.
The same spot works for any other key session your initiative needs, such as a pricing review, a security or legal check, or an architecture review. Add the ones that matter for your product and leave out the rest, so the process stays as light as it can be.
Approvers say yes more confidently when the trade-offs are spelled out. AI can turn everything gathered so far into a short approval summary and anticipate what the approver will ask.
Everything left of the approval line is paper. Everything right of it is development time, which is why the hard questions belong before it.
The handoff is a simple session with one goal: making sure Marketing understands what's being launched, what's new or has changed in the product, what they should communicate and promote, the strategy behind it and how they can support Sales. If AI is already part of your process, it can pull this information together from the brief, the competitive analysis and the stakeholder feedback and share it with Marketing as soon as the first release is agreed. Otherwise, follow the list below and cover it in the session.
When the process already runs with AI, the handoff is mostly assembled before the session starts, because everything it needs was produced in earlier steps. The session then goes to Marketing's questions instead of to reading a document aloud.
Marketing decides whether to mention what's coming. Knowing the phases is what lets them choose, instead of finding out in Q1 that the launch story had a second chapter.
With the handoff in hand, Marketing decides the strategy and the tactics, together with product, Sales and Customer Success. Every launch raises the same set of decisions: whether to inform existing clients, promote it to new ones, inform the team internally, run a promotion or change pricing, and in what order. Once those are decided, they become an action plan with an owner and a date for every task, before, on and after launch day.
AI is a useful brainstorming partner here. It can suggest tactics the team hasn't considered, propose an order and, once Marketing decides, turn the chosen tactics into an action plan the team can follow, then remind each owner as their dates get close.
The tactics that didn't make it are written down too, so nobody reopens the pricing question two days before launch.
Everyone who talks to customers should hear about the change from product before a customer asks them about it. Hold a training session on what's new, what has changed and how to talk about it, and record it, so the people who couldn't make it, and everyone who joins later, can watch it in their own time.
AI can prepare the session from everything the initiative has produced, then turn the recording into chapters and an FAQ people can search later.
The meeting that keeps the roadmap honest. It closes the loop on every initiative you launch, feeds what you learn back into the next roadmap review, and works just as well on its own if you aren't running the other two processes yet.
Once a month, the people who decide what gets built look at what actually happened: what shipped, how recent launches are doing, which numbers moved and what's stuck. Updates happen in writing beforehand, so the time together goes to decisions rather than status.
AI can summarise every pre-read in one view, pull the latest numbers and draft the launch scorecard, so the meeting starts from the facts instead of from opinions. After the meeting it captures the decisions and reminds owners before each date.
Retention is the only number moving the wrong way, so it gets the deep dive this month.
SSO closed both enterprise deals that depended on it, and we're calling it a keep. Usage reporting reached 52% of admins against a 70% target, mostly because people don't find it, so we want to pin it to the admin home page this month.
People skip steps they don't understand and miss handoffs nobody wrote down. Before the first initiative goes through the process, make three things obvious to everyone involved, in product and in every team product works with.
Everyone can see which step each initiative is in, what has to happen to move it on and who is waiting on whom.
Each initiative has one product owner and each approval has one approver. Write down who decides, who gives input and who just needs to know.
Spell out the small things: Sales and Customer Success answer their questions within three working days, development sees every design before it's final, and nothing launches before the internal training.
| Process | Moment | When | Who | Bring | Leave with |
|---|---|---|---|---|---|
| Roadmap | Objectives and initiatives | Once a year or every half | Product leads, with leadership | Company objectives and every candidate initiative | Each initiative linked to an objective, and a parked list |
| Roadmap | Initiative session | One per initiative | Product, design and development | What you know about the problem | A brief, user stories, a mock-up and a rough estimate |
| Roadmap | Roadmap planning | Once every initiative is sketched | Product leads and leadership | Value and estimate for each initiative | Initiatives placed in quarters, and a decision log |
| Roadmap | Roadmap review | Every quarter | Product leads | What you learned since the last review | An updated map, with every change in the log |
| Initiative | Competitive analysis | Start of the initiative | Product, with Sales input | The competitors you meet in deals | Where you are, where you want to be, and whether it's an advantage |
| Initiative | Brief and story map | Before design starts | Product, with design and development | Roadmap session notes and the analysis | A shared brief and a first-release line |
| Initiative | Design | One to three weeks | Product and design | Brief, story map and checklist | A design reviewed against the checklist |
| Initiative | Development feedback | Before the design is final | Development, product and design | The design | Feasibility, alternatives and a new estimate |
| Initiative | Sales and CS feedback | Before development starts | Sales, Customer Success and product | Five specific questions | Use cases, pilot clients, promises and risks |
| Initiative | Approval (optional) | Before development starts | CEO, CFO or a department leader | A short approval summary | Approved, changed or declined, in writing |
| Initiative | Marketing handoff | Once the first release is agreed | Product and Marketing | Purpose, audience, assets, phases, nuances and metrics | Marketing ready to define the strategy |
| Initiative | Go-to-market plan | Four to six weeks before launch | Marketing, product, Sales and CS | The handoff and the launch date | Chosen tactics, in order, and an action plan |
| Initiative | Internal training | About a week before launch | Everyone who talks to customers | A live demo and the FAQ | Trained teams and a recording to watch later |
| Product review | Monthly product review | Every month | Product, development and design leads, with Sales and CS | A short pre-read, 48 hours early | Launch verdicts and owned actions |
Agree on these once, out loud, and put them at the top of every brief and review for the first quarter.
If it can't be linked to one of the company's objectives, it doesn't go on this year's roadmap.
Briefs and mock-ups are where an initiative starts. The solution will change as you learn, and the decision log records why.
No initiative is ranked on value alone. How fast it gets you there is part of the decision.
No design is signed off until development has said what's feasible and what could be done for less.
Sales and Customer Success get questions about use cases, clients, promises and risks, never just "any feedback?".
If Marketing hasn't had the handoff and the teams haven't been trained, it isn't ready to launch, however finished the code is.
Every process in this guide has steps someone has to do: researching competitors, drafting briefs and story maps, collecting answers from Sales and Customer Success, writing the marketing handoff, turning tactics into an action plan, preparing the training. Today those steps land on your product managers, who should be spending that time with customers, designers and developers. They can land on AI instead, and that's how a product team ships more without growing its headcount.
Most product teams try AI as a chat window on the side. Someone pastes in the competitor notes, gets a summary and copies it into the brief. That saves one person a few minutes, but the initiative doesn't move any faster, because the AI has no idea what the roadmap decided, what design and development agreed or who is waiting on what.
AI starts adding real capacity when it lives inside the process your team already follows, connected to the same brief, story map, feedback and launch plan as everyone else. It knows what earlier steps concluded and who comes next, so you can assign it a step exactly the way you'd assign a person, and it can take over the back-and-forth that slows initiatives down today: collecting answers, drafting the first version and chasing what's missing before launch.
A task is something one person does and ticks off. A step is part of how the team works together: it gets what it needs from the step before, has an owner, and hands something to the next person. When AI owns a step, it moves the whole initiative forward instead of answering one-off questions.
Same initiative, same team. AI takes three of the six steps, so people spend their time with customers and on the decisions only they can make.
Briefs, summaries and handoffs that used to wait for a free afternoon arrive the same day, so an initiative keeps moving from one team to the next.
AI takes whole steps of the process, so product managers can run more initiatives without dropping the follow-up on the ones already launched.
Writing and chasing stop eating your product managers' week, and their time goes back to customers and the calls only they can make.
This only works when the process, the team's decisions and the AI live in the same place. That's the idea behind Nova: product work is set up there for collaboration across every team, and AI has a seat at the table, so you can assign it steps in the same process your team follows. The templates below come with these AI steps already set up.
Each template comes with the steps, the questions and the timing built in. Adapt it to your team, connect it to your calendar so recurrences and reminders run on their own, and bring AI into any step.
Every initiative linked to a company objective, sketched, estimated and placed in a quarter.
One initiative, from the competitor comparison to the launch, with every team brought in at the right moment.
Short pre-reads, the numbers on one screen and a verdict on every recent launch.
Use these alongside the three processes, or on their own when you need them.
See how competitors solve the same problem, and decide where you want to be.
Lay out the user's journey step by step and draw the line under the first release.
Give Marketing everything they need to define the strategy and support Sales.
Score a proposal by impact, confidence and ease, and gather feedback before it's decided.
Look back on how the initiative went while it's still fresh.
Agree what each department owes an initiative before the work starts.
Nova AI replies instantly · A human expert follows up by email