Starting as a product manager somewhere new is strange. You're expected to have opinions about the product quickly, but you don't yet know why things are the way they are. Some decisions that look odd from outside had good reasons. Others really are mistakes. You can't tell which is which yet.
I joined WiZR in 2025 as a senior product manager, after almost five years at Travelxp. Moving from a company where I knew everyone and every system to one where I knew nobody made me think carefully about how to use the first few months. This is roughly the approach I'd recommend.
Days 1 to 30: learn
The main job in the first month is understanding. Resist the urge to fix things.
- Use the product properly. As a real user, on every platform. Write down what confuses you, because you'll stop noticing it soon.
- Meet people one to one. Engineering, design, sales, support, leadership. Ask what's working, what isn't, and what they wish product did differently.
- Read the history. Past roadmaps, strategy documents, launch reviews, postmortems. They tell you what's been tried.
- Look at the data. Key metrics, how they're defined, and how they've moved.
- Talk to customers. Even a few conversations will tell you a lot.
I keep a running list of observations and questions. Not conclusions yet, just things to understand better. The requests will start arriving anyway, and the urgent vs important matrix helps me avoid saying yes to everything in week one.
Days 31 to 60: contribute
By the second month you should start adding value, in small and visible ways.
- Pick a small win. Something useful that won't take long, like fixing a confusing flow, clarifying a metric or unblocking a stuck decision. It builds trust.
- Share what you've learned. A short summary of what you heard from people and customers, with patterns. People appreciate being listened to.
- Start forming views. Test your early opinions with people who've been there longer. Some will hold up, some won't.
- Understand the decision process. Who decides what, and how. Formal and informal.
Days 61 to 90: lead
By the end of the third month you should be making real decisions and setting direction for your area.
- Propose priorities. Based on what you've learned, suggest what your team should focus on and why. If there's no clear strategy to hang them on, that's worth raising. I wrote about strategy vs roadmap separately.
- Make a hard call. Probably saying no to something, or changing a direction that isn't working. Explain it clearly.
- Set up your rhythm. Regular reviews, updates, and the habits you want to keep.
Earning trust
What matters most in the first 90 days is whether people start to trust your judgement. That comes from listening, being consistent, keeping small promises and being honest about what you don't know yet.
I've found that saying "I don't know enough about this yet, let me find out" builds more trust early than confident opinions that turn out wrong.
Mistakes to avoid
| Mistake | Why it hurts |
|---|---|
| Changing everything in week two | You don't know what you're breaking yet |
| Only talking to leadership | You miss what's really happening on the ground |
| Bringing your old company's process unchanged | What worked there might not fit here |
| Avoiding decisions to stay liked | People start working around you |
| Criticising past decisions publicly | The people who made them are still in the room |
Stakeholders early
Learn early who your key stakeholders are and what they care about. The stakeholder management post covers how to handle competing requests once they start arriving.
If you've moved from a project management role, like I did earlier in my career, some of this will feel familiar and some won't. I wrote about that transition separately.
At 90 days
Take stock. What do you understand now that you didn't before? What are you most and least sure about? What would you tell yourself on day one?
Then write it down. It's useful to look back on later, and it's a good thing to share with your manager.