# The 30-60-90 day plan for a PMM interview. A template and an example.
> How to build a 30-60-90 day plan for a product marketing interview, with a one-page template, a payroll company example, and the follow-ups to expect.

Source: https://mokk.ai/guides/pmm-30-60-90-day-plan (updated 2026-09-22)
Markdown: https://mokk.ai/guides/pmm-30-60-90-day-plan.md

A 30-60-90 day plan shows a hiring manager what you would do first and, more revealing, what you would leave alone. Spend the first thirty days learning from sales calls, customers, and the product team, and ship a small written output anyway. Use days 31 to 60 to finish one contained project, and own a launch or a positioning decision with a metric by day ninety. Keep it to one page, with your assumptions at the top.

## What the manager reads into your plan

Nobody expects your plan to survive week one. The manager asking for it wants to see three judgments at once. Would you listen before rewriting their messaging? Would you pick a first project small enough to finish? And would the work connect to something the business already measures, such as win rate or activation?

Plans fail in two opposite directions. The ambitious version promises a full repositioning by day ninety, which tells the manager you have never tried to get sales, product, and leadership to agree on a positioning document. The timid version spends thirty days “getting up to speed” and produces nothing, which reads as someone who waits to be told what to do. The plan that works learns fast and still ships something small in month one.

## A one-page template

A 30-60-90 day plan template for a product marketing role
| Phase | Goal | What you do | What you deliver |
| --- | --- | --- | --- |
| Days 1 to 30 | Learn, visibly | Sit in on sales and support calls. Meet product, sales, and customer success leads one on one. Read the current positioning and the last two launch briefs. | A one-page readout of what you heard, the three biggest gaps, and the questions you still can’t answer |
| Days 31 to 60 | Finish one thing | Pick one contained project, such as the message for the segment with the weakest win rate, and build it with the people who will use it. | A shipped asset and feedback from the reps or customers who used it |
| Days 61 to 90 | Own a decision | Take the next launch or a positioning call from brief to results. Agree the metric before you start. | A launch plan with an owner, a metric, and a review date |

Put your assumptions at the top of the page, for example “I’m assuming there is an existing positioning document and a sales team of about twenty.” A wrong assumption is useful. The manager corrects it, and now you are discussing their real situation.

## An example for a payroll software company

Say you’re interviewing for a mid-market payroll startup that sells to finance leaders at companies of 100 to 500 people. Everything below is invented, and yours should name the real product, segments, and rivals you found in your research.

### Days 1 to 30

- Listen to fifteen recorded sales calls, split between won and lost deals, and note the objection that comes up most.
- Ask each product and sales lead what they wish product marketing had done last quarter.
- Compare the homepage claim with how customers describe the product in reviews.
- Share a one-page readout with my manager by day 25, including the one gap I would work on next.

### Days 31 to 60

- Rewrite the core message for companies switching from an older payroll provider, since that is where the lost-deal notes cluster.
- Test it in live deals with two reps who volunteer, and collect what buyers push back on.
- Ship a one-page comparison against the most common rival.

### Days 61 to 90

- Own the launch of the next release end to end, from the brief to enablement to the results readout.
- Agree a target with product, such as the share of new accounts that turn on the feature in the first month.
- Propose one change to how launches get briefed, based on what went wrong in the last two.

## The follow-ups that test the plan

The plan is the opening. The conversation that follows is where you are scored, and the questions are predictable.

Follow-up questions on a 30-60-90 plan and what a good reply does
| The manager asks | What they are checking | A good reply |
| --- | --- | --- |
| What if a launch lands in week three? | Whether your plan bends | Say you would support it as a contributor, learn from it, and keep the readout on schedule |
| What would you not do in your first ninety days? | Whether you know what to cut | Name something tempting, such as a website rewrite, and why it waits |
| How would you know the message is working? | Whether you measure | Give a leading signal from calls and a lagging one from win rate |
| Who would you meet first? | Whether you know where PMM work comes from | Sales and support before leadership, because they hear buyers every day |

On the [rubric](https://mokk.ai/pmm-rubric), a Strong plan sequences work by impact, knows what to cut, and names a measurable outcome. Exceptional adds timing. It notices that the pricing change on the public roadmap makes day 45 the real deadline, or that fixing the switching message first will make the next launch easier to sell.

## Presenting it in the room

Walk through it in about two minutes and then stop. Lead with your assumptions, spend most of the time on the first thirty days, and close with the question you would most want answered in week one. When the manager pushes on an assumption, adjust the plan out loud. That exchange is worth more than the plan itself.

If they want it in writing, send one page. A six-page plan with a Gantt chart signals that you would build process before earning trust.

## Plans that lose the hiring manager

- **A launch in month one.** It tells the manager you would ship before you had heard a single customer.
- **A plan that fits any company.** If you could swap in a competitor’s name and nothing breaks, you haven’t researched this one.
- **Three projects in the middle phase.** Pick one and finish it.
- **No names.** A plan that says “meet stakeholders” instead of naming the sales lead and the support manager reads as a template.

## Frequently asked questions

**Should I bring a written 30-60-90 plan to the interview?** Bring one page if you were asked for it, or keep it ready if the round is with the hiring manager. Otherwise be ready to talk through it in two minutes. An unrequested document is fine to offer at the end but shouldn’t open the conversation.

**How specific should the plan be?** Specific enough to prove you researched the company, so name the segments, rivals, and teams. Loose enough that the manager can correct your assumptions without the plan falling apart.

**Is a 30-60-90 plan different for senior roles?** Yes. A senior plan spends less time on assets and more on the decisions you would force, such as which segment the team stops chasing. It also names how you would assess the existing team.

**What if I have no inside information?** That is expected. State your assumptions and build from what is public, such as the product, the pricing page, launch posts, and customer reviews.

## Practice

**Defend the plan out loud.** A Mokk interview asks you to walk through your priorities and presses on the trade-offs.