Career and promotion

for Product Managers

check list

Technical skills link=https://productdo.io/tech_pm;Only basic ones (backend, frontend, APIs);Understanding of individual pieces of the product (services, data, APIs, metrics) that help write high-quality stories for development; Can really launch complex projects by understanding the structure of products “from the inside,” and therefore, seeing the pitfalls;✖ Bothers the team with solutions (“I know better”) ✖ Does not understand technology at all: thinks that “the site works on its own” Product analyticslink=https://productdo.io/data_driven; Looks at the most basic metrics for his product, does not understand what questions to ask; Knows how to ask the right questions to analysts (even if not knowing how to find answers); Knows how to find the answer to simple/medium questions on their own. Knows how to formulate complex questions to analysts;✖ Does not know how to match work and the correct metric ✖ Received an answer, but does not know what to do with it Planning horizonslink=https://productdo.io/planning; Leads sprints, sets OKRs with manager support, vision/strategy is set from above; Leads sprints, sets OKRs, has some kind of strategy and vision; Everything Core plus strategy involving new/complex areas or expansion across multiple teams;✖ Sets unrealistic goals and fails them ✖ Chases too big a vision Prioritizationlink=https://productdo.io/planning;Simple choice (user story): A or B;Projects of medium complexity, choice between 10 opportunities that require data analysis and understanding of dependencies and technologies;Complex/vague projects, 100 opportunities that require data analysis and understanding of dependencies and technologies;✖ Can’t negotiate with other teams ✖ Does only what the boss has prioritized Market researchlink=https://productdo.io/discovery;Uses research results;Participates in CustDev and other studies;Can independently organize CustDev;✖ Does not think, but immediately applies the template ✖ Eternal CustDev, never actually starts working A/B testinglink=https://productdo.io/ab_testing;Basic understanding, runs tests with a mentor (metrics, hypothesis);Runs tests from a hypothesis to making a decision independently. A must-have in large companies!;An expert, understands subtle concepts (p-value, power) and teaches others.;✖ Doesn’t understand when to use the tool and how ✖ Seems like they've started everything, but can’t make decisions based on metrics Unit economicslink=https://productdo.io/discovery;Rarely;Sometimes, when startups require analysis for entering a new segment;Often in startups, when a new product or segment is launched. Or in large companies to analyze ROI.;✖ Does not understand the monetary/ROI component of the company and product at all Machine Learninglink=https://productdo.io/ml_basics; Understands the basics: why and where to apply; Sees problems that can be solved using ML and can create tasks for analysts; Launched 2-3 ML features, understands the differences between algorithms and the intricacies of data cleaning and model training;✖ Doesn’t understand ML at all ✖ To any task, says “We can add AI here” Documentation: PRD, user story, strategy; Clear stories, basic structure of PRD (problem/what we are doing); Clear stories, PRD (problem, what we are doing, profit, technical requirements, risks), good strategy, briefs;Crystal clear structure, everyone’s reaction is “they've explained a complex thing in simple language”;✖ Too confusing and long documents ✖ It’s unclear why and what is being done Delivery/project skills;No experience of independent launches;Has 1-2 launched projects under their belt (who, when, roadmaps, surprise fixes, etc.);Has 5 launched projects under their belt;✖ Nothing to tell when asked to give an example of a project and what went wrong ✖ Good ideas, but can’t bring them to launch