Day 1 — 7 days of Tenderfoot Product Manager

So, here is the original post for the plan for 7 days. Today is time for day 1.

Feel the Team

What it means is that you need to know in depth about your Team and who takes care of what.

If you are a PM you need to know about following verticals. Remember that there can be one person handling multiple things

  1. Development — Who is the lead with whom you will coordinate along with second in command and other team members.
  2. UI/UX — Who is the person in charge of the UI/UX design? Remember that he can be a shared person across verticals
  3. QA — Who is QA lead and who are its team members who work on your piece
  4. Data and system access — Who is the go to person for data access setup. You need to ensure that you have first hand access to every required data, in other words you take the data directly from system and not from somebody in the system.
  5. Operations — Who is the operation team head, who are his team members. What are the primary things they do in the operations.
  6. TP integrations — Do you have Third party data / API integrations in your piece? if yes who watches over the day to day sanity of these data / integrations and whom to contact in case of trouble
  7. Build Deployment — What is the process for build deployment on QA and production environment, who is responsible for doing it
  8. Production issue debugging — who is till date responsible for debugging the production issue.
  9. Production Monitoring — who is in charge of production monitoring? Also, get yourself added in all related production monitoring emails
  10. Production Backup plans — Who is responsible for production backup plans? What are the plans in place?
  11. Stack-holders — Who are the stack-holders for your product (people who use your product directly, it can be departments within OR external customers OR external / internal applications)

This should take you around 2 hours max. Ensure that you document all this information as you will definitely wont be able to remember it all.

The next in line is

Feel the Product

Here are the things you should know about your product at high level

  1. Why it exists — What is the problem/ pain point it is solving, what are the USP of the product
  2. KPIs tracked — What are the KPI (Key Performance Index, in other words parameters which tell you about health/ progress of product , like revenues OR customers OR APPs installed, etc.). Which KPI is linked with other teams / stack-holders
  3. Product Features — List of all product features. The best way to get this if it does not exist as a single document, is to ask QA for test scenarios of product
  4. Schedulers / Backend Processes — List of all such processes and where they put in the data
  5. API / Third Party Integrations — list of all TP / API and for what purpose they are integrated
  6. Product Road Map — Get access to your Agile Project Management tool and view your current build’s road map
  7. Product Master Data — what are the tables representing 80% of used Product master data, where they are stored (table names) and who updates them
  8. Product Operational Data — What are the tables representing 80% of the daily operational data
  9. Product BI Data — what are the tables representing 80% of the Business Intelligence data and how exactly it is generated.

I bet the product exercise will take considerable time but a high level document regarding all 9 points can be made in 3–4 hours max.

I will be explaining the 2nd day next. Do comment to let me know if you find this helpful.

Like what you read? Give Ankur Saxena a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.