Product Management Topics
Product leadership, vision articulation, roadmap development, and feature prioritization. Focuses on product strategy and business alignment.
Product Documentation (PRD, PR/FAQ)
Writing the artifacts that align teams and drive decisions: PRDs, one-pagers, and the PR/FAQ (working-backwards) format. Covers document structure and clarity, the press release lead, the external and internal FAQ, hard-question answers, success metrics and acceptance criteria, engineering-ready requirements and constraints, and reviewing or pressure-testing a draft. Also covers using written narrative to sharpen thinking and secure buy-in across functions, and running PR/FAQs as a team practice: intake and review process, versioning, onboarding and co-creation workshops. Assesses written product communication and documentation strategy.
Product and Engineering Collaboration
The working partnership between product and engineering: assessing technical feasibility with engineers, negotiating scope and timelines against technical constraints, and balancing feature delivery against reliability, security and maintenance work when the two functions disagree. Covers making sure engineers understand the why behind work, bringing engineers into discovery, joint planning, estimation and capacity, pushing back on or accepting product requests with engineering risk, holding the line on quality or launch dates when sales or senior leadership press for commitments, making engineering concerns visible and winning funding for technical investment, mediating release, migration and downtime disputes, rebuilding trust and running blameless post-incident conversations after rushed releases or outages, agreeing scope, baselines and what done means up front, and building shared ownership of outcomes. Assesses how a candidate works with the other side of the product-engineering line, not how they rank a backlog or measure debt in the abstract. Prioritization frameworks, technical debt measurement and reduction, and service-level objective mechanics are covered elsewhere.
Pricing Strategy and Business Model
Setting and evolving prices and the monetization model they sit in. Covers pricing metrics and structure (per-seat, tiered, usage-based, hybrid, outcome-based), packaging and bundling, freemium versus paid versus ad-supported monetization, and migrating between pricing models, including from perpetual licences to subscription and consumption billing. Includes estimating willingness to pay and price elasticity (van Westendorp, Gabor-Granger, conjoint, observational and causal methods), designing and analysing price tests and reporting their results, discount and deal-desk policy, regional and personalized pricing, and quantifying the revenue, churn, LTV and margin impact of a price or packaging change. Also covers fee design and surge pricing on two-sided marketplaces, responding to competitor price cuts, and rolling out algorithmic pricing safely. Assesses commercial judgment and quantitative rigor on pricing decisions from product, sales, finance and analytics angles. Business-model archetype selection, unit-economics definitions and go-to-market execution are adjacent topics, not the focus.
Market Sizing and Estimation
Producing defensible order-of-magnitude estimates and market sizes from first principles and stated assumptions. Covers structuring the estimate, choosing reasonable inputs, sanity-checking the result, and reasoning transparently about uncertainty. Assesses quantitative structuring under incomplete information.
Experimentation and Validation
Designing experiments, prototypes, and validation plans to de-risk product decisions before full investment. Covers A/B testing, prototyping strategy, experiment roadmaps and phasing, and reading results honestly. Assesses hypothesis-driven product development and evidence-based decision making.
Product Metrics and KPIs
Selecting, defining, and instrumenting the metrics that measure product health and success, including North Star metrics, KPI trees, OKRs, and guardrail metrics. Covers choosing the right metric for a product stage, diagnosing metric movement, and avoiding vanity or gameable measures. Assesses quantitative product judgment and goal-setting rigor.
Problem Definition and Framing
Turning an ambiguous prompt into a well-scoped, clearly-stated problem before proposing solutions. Covers structured decomposition, clarifying assumptions, identifying the real user and job-to-be-done, and framing the problem to fit the constraints. Assesses disciplined problem-first thinking under ambiguity.
Prioritization and Trade-Off Decisions
Making and defending a ranked decision about what to work on among competing options under conflicting goals, incomplete data, and time pressure. Covers explicit prioritization frameworks (RICE, ICE, MoSCoW, Kano, weighted scoring, impact vs effort, cost of delay, WSJF) and how to make their inputs honest: handling low-confidence estimates, testing whether a ranking is stable, and guarding against gaming, sponsor seniority and recency bias. Also covers backlog and request triage, feature and scope trade-offs, technical debt, reliability, security, compliance and accessibility work versus new features, large-customer and sales-driven requests versus the roadmap, sequencing a limited set of options, urgent interruptions and incidents versus planned work, deciding whether a single initiative on the list should continue or stop, saying no or not now and communicating a deprioritization, documenting a call and later checking whether it was right, and the governance and escalation used to settle prioritization disputes. Assesses whether a candidate can make and stand behind a defensible call rather than treating everything as equally important. Excludes architecture and technology-selection trade-offs, supplier and sourcing decisions, experiment and metric design, portfolio budget and headcount allocation, and delivery trade-offs inside an already committed project.
Stakeholder Management and Cross-Functional Alignment
Getting engineering, design, sales, marketing, finance, security, legal, and leadership to agree on and execute a specific product decision when their interests conflict. Covers mediating disagreements between named parties (for example sales versus engineering, design versus engineering, product versus security), settling contested ownership or shared capacity between teams and business units, defining decision rights and escalation paths, sequencing pre-alignment touchpoints for a launch or roadmap change, running a working session that ends in a decision people will stand behind, agreeing what to promise publicly when timelines and lead times collide, and communicating a decision or a changed plan back to each party. Emphasizes the alignment process around a product call rather than the prioritization framework itself.