This is a personal blog, Hiro's room!


After you joined a new team as a product manager

Cover Image for After you joined a new team as a product manager

You finally joined a new team as a product manager. Congrats! Here, we discuss what you should do as a product manager in the first week, the first 30 days and the first 60 days after you joined the team.

In a week - Set the stage!

At first, you need to understand basic things: team members, product and development process. You have coffee break, lunch and 1on1 meetings with many members in the team in order to get to know each other. Remember the names and faces of everyone you meet, and have them remember you at the same time. You can get the reporting lines in the team during the conversations or you may discuss the pain points faced by the team members at work. If you have never used the product, you might be lucky! You cannot be a good product manager for sure unless you use it a lot from now on, however you can get the real impressions with unbiased view. Then, write down your impressions of the product about anything good or bad and any questions for the time when you can ask to the team members. In addition, you need to understand the development process as a product manager. You should get the permissions of development tools as well as join the meetings of ongoing projects even though it is hard to understand what they discuss. After getting the permissions to access the repository, you can read the prior PRDs. What were developed or not scoped and why would be figured out through the PRDs.

In 30 days - Deliver the quick win!

You can work on a small feature that affects something positive to the users so that you can experience a whole development process. You can learn how the team communicates and writes documentations. The documentation describes well the team's cultures. After releasing the feature, you learn how to collect statistics on the product and actually measure the impact of the released feature. In addition, you should investigate the behavior of bugs that are already reported so that you prioritize the bugs as well as understand the technical architectures as much as possible, which will be essential to define the specifications for more complex features. If you have still leeway, you can start market research and product planning. You can investigate the user experience from user interviews, the tech trends from news/communities or the competitors from some analysis frameworks. You may be able to propose interesting hypotheses to make the product more interesting. Moreover, you can join the business unit's meetings in order to know what KPIs are concerned by marketers or how the roadmap for the company's growth is like.

In 60 days - You are the product!

Finally, you can work on a big feature or new product that affects something on large scale to the users. You know how to communicate smoothly with every stakeholders, so you need to acquire trust from them. You take the lead of the product team from planning to releasing. In addition, you should report the impact of KPIs by your release. Even though it failed, you cannot hide the failure but share what you learn from the failure to the organization instead.

Failure is not a failure as far as we can learn something.

# product management# teamwork
Copy Link to Share

Related Posts

Introduction to product vision with examples

A product team needs to have a clear vision of where to take the product in order to be fully committed. A product vision describes the future state of a product in a long-term and what problems it tries to resolve or what ambitions it tries to fulfill.

# product management# teamwork

The power of data without compromising privacy by Data Clean Room

In today's digital world, companies have access to more customer data than ever before. While this data can be incredibly valuable for understanding customer behavior, improving products and services, and driving business growth, it also raises significant privacy concerns.

# data# privacy# marketing

What is Agile Software Development?

Agile Software Development - also referred simply as Agile - is an iterative approach to focus on continuous releases and incorporating customer feedback with every iteration. In short, Agile is important for software development to delight customers and be more competitive.

# engineering# teamwork

How to define product requirements from many perspectives

The main role of product managers is to define product requirements and put them into words as a PRD. In this phase, product managers have to take many perspectives into account, otherwise the product requirements need to be changed over and over again during development or even after finishing it, but how?

# product management