What should a new product manager do in their first week?

Listen, don't fix. Run 1:1s with every engineer, designer, and support or sales person who touches the product, and ask what's broken that nobody talks about, what they'd build with a free week, and what past decision still doesn't make sense to them. Building an accurate map of the product and the team matters more in week one than shipping anything.

Should a new PM propose changes in the first 30 days?

Generally no. The first 30 days are for understanding why the roadmap and priorities look the way they do before trying to change them — most decisions that look obviously wrong have a reason nobody documented. Save proposals for after you've shipped one small, visible win and built enough context to back them up.

What's a realistic 30-60-90 day plan for a product manager?

Days 1-30: listen and map the product, team, and politics without shipping anything. Days 31-60: ship one small but visible win to prove you can close a loop. Days 61-90: propose one well-evidenced bet, framed with a kill criterion, rather than a full roadmap. Specificity — named people, a real metric, a real experiment — is what separates a plan people reread from one they forget.

How do I turn my first 90 days into a portfolio case study?

Document the small win and the bet you proposed as you go: the before-state, the specific decision and why you made it, and the metric it moved, even if modest. A fast, real case study from your first quarter at a new company is more credible evidence than a polished strategy deck with nothing shipped behind it.

The First 90 Days as a Product Manager (A Plan That Actually Works)

Product Leader.

We use cookies for analytics and to remember your preferences. "Necessary" is always on.

💬