Your first week as a product manager, planned day by day
The short answer
Spend the first week producing one small, useful thing rather than absorbing everything. Monday: read the feedback nobody has read. Tuesday: meet the three chairs, engineering, design and whoever owns the number. Wednesday: pull the metric the company actually optimises and its counter metric. Thursday: write a one-page memo with one claim, the evidence and a recommended next step. Friday: deliver it, take the questions, and write down what would change your mind. You will know more about the product than most people in the building by then, and you will have shown how you work.
Monday: read what nobody has read
Every company has a pile of feedback that nobody owns: app store reviews, the support inbox, cancelled-subscription reasons, sales call notes. On your first day, ask for access to all of it and read for three hours. Do not summarise yet. Keep a table of exact quotes with a source and a date.
This does two things. It gives you first-hand knowledge that is not filtered through anyone's opinion, and it means that by Tuesday afternoon you can quote real users to people who have been too busy to read them. That is worth more than any onboarding deck.
Tuesday: meet the three chairs
Three people shape what you can do: the engineering lead who decides what is feasible this quarter, the designer who decides what the product feels like, and the person who owns the number the company is judged on, often a founder or head of growth. Ask each the same four questions. What is the last thing this team shipped that worked? What is the last thing it cancelled, and who decided? What do you wish someone would look into? What would make your next month easier?
Write their answers down verbatim, the same way you did with reviews. You will notice that the three chairs describe three different products. That gap is your job.
Wednesday: find the number and its counter
Ask what number the company would most like to see go up. Then ask what number would tell you that it went up for a bad reason. Revenue with churn. Signups with activation. Session count with task completion. Pull both for the last six months and look at the shape, not the latest value.
If nobody can tell you the counter metric, that is a finding, and it belongs in Friday's memo. If the dashboards are broken, that is a finding too. A product manager who cannot get a number should say so plainly rather than guess.
Thursday: write one page
By Thursday you have a table of quotes, three interviews and two charts. Write one page. Not a strategy, not a roadmap: one claim you can defend, the evidence for it, what you would do next, and what you do not yet know. A claim looks like "around a fifth of bill payment attempts on the current version fail at the OTP step, and it started with release 4.2". A wishlist looks like "we should improve login".
Keep it to a page because people will read a page. Put the claim in the first sentence. Put the evidence in the next paragraph with the counts. End with the next step and the open questions. Then sleep on it.
Friday: deliver it and take the questions
Send the page to the three chairs in the morning and ask for fifteen minutes in the afternoon. Expect to be challenged, because you have been there four days. Do not defend the claim beyond what the evidence supports. When someone raises a point you cannot answer, write it down as a question you will go and answer, and say so.
The purpose of the meeting is not to win. It is to show the building how you work: from evidence, in writing, with a next step, open to being wrong. People will bring you problems after that, which is the moment the job actually starts.
Do this week
- Day one: request access to reviews, support tickets and the analytics tool before lunch.
- Day two: book the three chairs for thirty minutes each with the same four questions.
- Day three: pull the company's headline metric and its counter metric for six months.
- Day four: write a one-page memo with one claim, the evidence, a next step and the open questions.
- Day five: deliver it, collect the questions you could not answer, and make those the plan for week two.
Three terms, defined
- The three chairs
- Engineering, design and the owner of the business number: the three people whose agreement any product decision needs.
- Counter metric
- The number that reveals when a headline metric went up for a bad reason.
- One-pager
- A single page with one claim, its evidence, a recommendation and the open questions.
Questions people ask
What if the company has no product process at all?
Then this week is the process. A memo written from evidence is the smallest possible version of a product practice, and it is easier to grow one from a working example than to introduce one from a slide.
Should I ship anything in the first week?
No. Shipping in week one usually means shipping someone else's unexamined idea. Learning something true and writing it down is the right first deliverable.
What if my manager wants a roadmap by Friday?
Offer the memo as the first item on it, with the evidence, and explain that the rest of the roadmap will be better in two weeks once you can support it. Most managers prefer a defensible first item to a decorative full list.