PM Situation;Example;What to do;Where to learn
<b>I'm going through an interview, and I was asked to build a service diagram of a real application</b>;“Please draw us the architecture of the Tinder dating app”;I build the architecture (service diagram): frontend, services, databases, API, external integrations. I start from the beginning of the CJM (for example, user registration) and move along its steps;Chapters "Service Blueprint and Architecture" of the simulator "Tech for PMs" link=https://productdo.io/tech_pm;
<b>I moved to a new team/product, trying to figure it out</b>;Moved to the “Delivery” product of a large store;I ask knowledgeable colleagues to draw a general architecture in order to understand what is connected with what inside and outside my product and to find my clients and dependencies;Chapters "Service Blueprint and Architecture" of the simulator "Tech for PMs" link=https://productdo.iotech_pm;
<b>I need to estimate the cost/complexity of developing projects/features</b>;Trying to estimate how long it will take to add the “Tips for the courier” feature;I build the architecture and fill out the “Full Product Review” checklist (full for the project, and short for the feature). The final word on estimating the complexity is up to the team, but over time, the PM can calibrate their estimate and use it for a constructive debate with the techies (“There will be 1 new field in the database and 1 integration, are you sure it will take 2 months?”);Chapters “Architecture” and “Full Product Review” of the “Tech for PMs” simulator link=https://productdo.io/tech_pm;
<b>I'm writing a development strategy for a large product or PRD feature</b>;Strategy: we are moving from food delivery to delivering everything. <br>New feature: calculating the approximate delivery time;I build the architecture and fill out the “Full Product Review” checklist: I evaluate the business and technical aspects of the product / feature idea; Chapters “Architecture” and “Full Product Review” of the “Tech for PMs” simulator link=https://productdo.it/tech_pm;
<b>New business ideas needed;I figured out how to expand food delivery to parcel delivery around the city</b>;I build a detailed architecture. After that, it will become clearer what useful features for business can be added relatively easily (building on Tech Insights);Chapters "Architecture" and "Music Streaming Service" of the "Tech for PMs" simulator link=https://productdo.io/tech_pm;
<b>New functionality that is already available via API inside or outside the company is needed</b>;We need to integrate payments for courier tips;I study API documentation, parameter details, write a task for integration with the API;Chapter "API" of the "Tech for PMs" simulator link=https://productdo.io/tech_pm;
<b>The client requires creating new functionality via API</b>;They ask to return the estimated delivery time;I study / discuss the client's requirements, offer input/output, write a task to create an API for the team, agree with the client on SLI/SLO;Chapter "API" of the simulator "Tech for PMs" link=https://productdo.io/tech_pm;
<b>The product works, but we do not understand how healthy it is</b>;It seems that the delivery is delivering, but what metrics are associated with which?;I build a full tree of metrics: NSM (North Star Metric), main metrics, product level, SLI of my services, SLI of external integrations;Chapter "Full Metrics Tree" of the simulator "Tech for PMs" link=https://productdo.io/tech_pm;
<b>Development has become time-consuming, everything is going slowly, programmers are complaining</b>;Adding the “Basket” feature took 5 months;Most likely, this is one of the “diseases” of architecture: Strong coupling, Duplication, Useless dependency, or Monolith.<br>I build the architecture, discuss it with the tech lead and prepare for complex migrations;Chapter “Architecture” of the “Tech for PMs” simulator link=https://productdo.io/tech_pm;
<b>The product is constantly breaking</b>;We've just had an accident: the delivery service was down for 5 hours;I deal with this accident using the Post-mortem protocol, prepare proactive protection for the product (SLIs, functional and non-functional testing, alerts, etc.);Chapter "Product Health" of the "Tech for PMs" simulator link=https://productdo.io/tech_pm;
<b>Developers say: “We need to do a major refactoring and migration”</b>;Developer: “We urgently need to rewrite the entire logic of delivery payments!”;The product manager does not make the final decision on the need for refactoring (“reworking”) the code, but can argue reasonably:<br>1) What problem and why does refactoring solve? (understanding what and how are the main PM issues)<br>2) What will happen if we do nothing? (This helps to understand how techies themselves assess importance)<br>3) What business process will it improve and by how much? (This will help make a business decision: an important change in an unimportant process is ultimately unimportant);Simulator "Tech for PMs" link=https://productdo.io/tech_pm;
