Product Ops: Day 31 - 60 in role
What does month 2 look like and what should you aim to achieve?
This is the second of a three-part series exploring what the first 90 days in a Product Operations role should typically involve. Here, I explore the second 30 days - now having built some early relationships and played the sponge for a few weeks, absorbing as much feedback as possible, it is time to sit down, analyse and plan what to focus on.
This guidance is for both experienced Product Ops folks as well as those new in role.
[If you have not read Day 1 - 30 in role yet, click here]
You are into month 2. I hope you have had some positive feedback from your line manager about the conversations you have been a part of, and the relationships you have begun to build. I would not expect much more than this at this stage.
You will almost certainly have a long shopping list of feedback items, ideas, problems to solve, and being a great Product Ops professional, a desire to help people.
The next step with all of this is to step back and take holistic stock of what you have learnt. What are the common themes? What are the most passionate pleas for change, and similarly what is being staunchly defended? You will likely have picked up on vibes and feelings too, particularly about existing relationships between teams or divisions, and the quality of those relationships. As much as any specific improvements you will go on to make, improving (or rather facilitating the improvement of) relationships between other teams is a key part of Product Operations.
Analysis
Now is the time to review all the feedback and research you have collected to-date. I say to-date because this never ends. Just like in product management, we are always quietly in discovery mode, listening to ideas and feedback and integrating those into plans where appropriate and sensible along the way.
Keep reading with a 7-day free trial
Subscribe to Practical Product Ops to keep reading this post and get 7 days of free access to the full post archives.