How to Create a Roadmap as a Product Manager in a New Job
9 min read ยท 2026-11-16
To create a roadmap as a product manager in a new job, start by listing what the company has already promised. Then learn the numbers leadership watches, build a one-page draft around problems, check it against engineering capacity and walk each approver through it alone before the sign-off meeting. Over 90 days, this method gives you the best chance of getting your first roadmap approved without throwing out work the team has already committed to.
This guide covers how to create a roadmap as a product manager when you have just joined a company and leadership expects your plan. Each step has a time frame and a milestone you can check. You also get a filled example in dated phases and prepared answers to the questions executives ask.
The roadmap at a glance
Goal: A first product roadmap, written in your first 90 days, ready for leadership sign-off and trusted by the team. Duration: 90 days
Inherit the roadmap that already exists (Days 1-10)
No team starts from zero. Sales has made promises, contracts have dates, and engineering is in the middle of something. Find all of it before you plan anything new.
- Ask your manager for the current roadmap, even if it is an old slide or a spreadsheet.
- Ask sales and account managers which features they have mentioned to customers.
- Check contracts, partner deals and compliance work for fixed dates.
- Ask the engineering lead what is in progress and what cannot stop.
Milestone: A list of every commitment already made, with who made it and its date.
Learn the numbers leadership watches (Days 8-25)
Leadership will judge your roadmap against a few metrics. Find out which ones before you choose a single theme.
- Ask your manager which two or three numbers the CEO looks at every month.
- Get the current value of each one, or write down that nobody tracks it yet.
- Read the last board or leadership update to see how they discussed the product.
- Note where the data is missing. That gap can become a theme.
Milestone: A one-page baseline with the metrics, their current values and the gaps.
Ask what decision the roadmap must support (Days 20-35)
Leadership asks for a roadmap for a reason: a budget, a hiring plan, a sales push or a board meeting. That reason decides how far ahead you plan and how much detail you show.
- Ask your manager: "What will you decide with this roadmap?"
- Confirm the time horizon, for example one quarter or two.
- Confirm who approves it and who only needs to be informed.
- Ask about the format and keep the one the company already uses, so leadership can compare your plan with the others easily.
Milestone: A short written brief: the decision, the horizon, the approvers and the format.
Draft version zero around problems (Days 30-45)
Write the first draft from what you heard, not from a feature list. Every item should name a customer or business problem and the evidence behind it.
- Write three to five problems, each tied to a metric from your baseline.
- Add the evidence for each: support tickets, customer calls, lost deals, usage data.
- Keep every inherited commitment on the page, even the ones you would not have chosen.
- Label the document "draft" so nobody reads it as a promise.
Milestone: Version zero on one page, with problems, evidence and existing commitments.
Check it against real capacity (Days 45-60)
When you are new, it is easy to plan more than the team can deliver. Sit down with the engineering lead before anyone else sees the draft.
- Go through each item and ask: "How big is this, roughly?"
- Subtract the work already in progress and the maintenance the team always carries.
- Move what does not fit to a later phase, with a note on why.
- Add a confidence level to every date: high, medium or low.
Milestone: Version one, with sizes, confidence levels and a realistic first phase.
Preview it one on one with each approver (Days 60-75)
In a group meeting, an objection can turn into a debate. If you hear it alone first, you have time to prepare an answer or adjust the plan.
- Book a short slot with each approver and with each stakeholder whose request was moved.
- Show the draft, then ask: "What would stop you from approving this?"
- Write down every objection and decide whether to change the plan or explain it.
- Before the meeting, tell the people whose requests were moved why.
Milestone: A log of objections, each one either resolved or with a prepared answer.
Get sign-off and set the first review (Days 75-90)
The meeting should confirm a plan people have already seen. Don't use it to show the plan for the first time.
- Open with the decision you are asking for, then the problems, then the phases.
- Show what is not in the plan and why.
- Send a written summary of the decisions and open questions the same day.
- Put the first monthly review in everyone's calendar before you leave the room.
Milestone: A written decision and a review date accepted by every approver.
Week-by-week milestones
The 7 steps overlap, so a weekly view helps you check whether you are on track. The sign-off meeting happens in week 13, and the first review date is set there.
If you fall a week behind, cut the scope of the draft, not the previews. The previews let you hear objections before the meeting, while you still have time to answer them.
- Week 1: current roadmap found, first meetings with your manager and engineering lead.
- Week 2: list of inherited commitments complete.
- Week 3: metrics leadership watches identified.
- Week 4: baseline written, data gaps noted.
- Week 5: decision, horizon and approvers confirmed in writing.
- Week 6: version zero drafted with evidence for each problem.
- Week 7: capacity check started with the engineering lead.
- Week 8: version one ready, with confidence levels.
- Week 9: working session with the team held.
- Week 10: first one-on-one previews done.
- Week 11: all previews done, objections logged.
- Week 12: final version and summary page ready.
- Week 13: sign-off meeting, written decision, first review booked.
A filled example: first roadmap for a B2B invoicing product
Say you join a company that sells invoicing software to small businesses. Your manager says the roadmap will decide next quarter's hiring. The metric the CEO watches is churn among new accounts. You inherited two commitments: an accounting integration that sales promised a partner for the end of the quarter, and a security update with a fixed compliance date.
Here is the roadmap you would bring to the sign-off meeting, in dated phases for a quarter that runs from January to March.
The low confidence on Phase 3 is not a weakness. It ties straight to the hiring decision leadership wants to make, and that decision is why they asked for the roadmap in the first place.
- Phase 1, January: fixed commitments. Security update, then the partner integration. Confidence: high. Milestone: both live by the end of January.
- Phase 2, February: "Get paid faster." Rebuild the payment reminders behind most support tickets. Metric: share of invoices paid on time. Confidence: medium. Milestone: new reminders live for all accounts.
- Phase 3, March: "First week success." Guided setup for new accounts. Metric: accounts that send a first invoice in week one. Confidence: low, because it depends on one backend hire. Milestone: setup flow in beta.
- Not in this quarter: a mobile app redesign, because it does not move churn among new accounts.
The 5 questions leadership will ask, with answers ready
Here are the questions, with answers based on the example above. Swap in your own facts.
Each answer points to something on the page. If an answer needs a long explanation, that part of the roadmap is not clear yet.
- "Why this order?" "Phase 1 is already committed. Phase 2 tackles the biggest source of support tickets. Phase 3 attacks churn in the first week."
- "When will it ship?" "Phase 1 by the end of January, with high confidence. Phase 3 stays low confidence until the backend hire is made."
- "What happened to the mobile redesign?" "It is on the not-in-this-quarter list because it does not move the metric we are targeting."
- "How will we know it worked?" "On-time payments for Phase 2, and first invoice in week one for Phase 3. We check both at the monthly review."
- "What do you need from us?" "Approval for one backend hire. Without it, Phase 3 moves to next quarter."
If you lead other product managers
When you join as a head of product or group PM, your first roadmap is a frame rather than a list of items. Agree with leadership on the shared goals, the format and the review calendar. Then each PM builds the roadmap for their own area using the 7 steps.
Your job is the combined view. Look for two teams that rely on the same platform work, inherited commitments nobody owns and goals no team covers. Take each conflict to leadership with a recommendation, not just the problem.
Run one working session with your team
Hold it in week 9, after the capacity check and before the previews. Invite the engineering lead, the designer and someone from sales or support. Ask them to challenge the plan, not to rewrite it.
Stick to three questions: what is missing, what is too big for its phase, and what depends on someone outside the team. As a new PM, you also gain something here: the team sees its own input in the plan before leadership does.
Checklist before the sign-off meeting
Go through this list the day before the meeting. Any item you cannot tick is a question leadership is likely to ask.
- Every inherited commitment appears on the page.
- Every phase ties to a metric leadership already watches.
- Every date has a confidence level.
- The not-in-this-quarter list gives a reason for each item.
- Each approver has seen the draft one on one.
- You can say in one sentence which decision you are asking for.
Common mistakes to avoid
- Replacing the existing roadmap in week two, before you understand why it looked that way.
- Leaving out commitments sales has already made, then finding them in the meeting.
- Picking metrics nobody in leadership watches.
- Bringing a new format when every other team presents the same way.
- Promising dates before the engineering lead has sized the work.
Frequently asked questions
How long does it take to create a first roadmap as a new product manager?
Plan on about 90 days from your start date to a version ready for sign-off. You can have a one-page draft by week 6. The rest of the time goes to past commitments, the metrics and capacity. That groundwork helps you avoid surprises in the sign-off meeting.
What should you show a CEO who has five minutes?
One page: the decision you need, three to five problems tied to the metrics they already watch, the phases with confidence levels, and what is not in the plan. Keep the detail for the team version.
How do you present a roadmap when you have no data?
Say so plainly and make getting the data part of the plan. Use the evidence you do have, such as support tickets, customer calls and lost deals. Add a first milestone that sets up tracking for the key metric, and mark the later phases as low confidence until tracking is in place.
Who should approve a product manager's first roadmap?
Usually your manager and the leaders whose budget or teams the plan depends on, often engineering and the CEO or a business unit head. Confirm the list in step 3 and preview the draft with each of them before the group meeting.