What a Senior } should know

Shapes API strategy for the product. Defines public vs private API. Ensures developer portal and API documentation.

Defines AI strategy for the product process. Implements AI tools in the team workflow. Evaluates new AI capabilities for product management.

Shapes AI dev tools usage strategy for the product team. Defines policies for AI-generated code. Evaluates security and compliance implications.

Develops AI-powered product workflows. Integrates prompt engineering into product processes. Evaluates and implements new AI capabilities.

Deeply understands the product's system architecture. Makes product decisions considering technical trade-offs. Can challenge technical decisions.

Understands engineering workflow at a deep level. Participates in branching strategy discussions. Uses Git analytics for delivery insights.

Builds backlog management processes at the product line level. Balances strategic initiatives, tactical improvements, and technical debt. Ensures backlog alignment with product strategy.

Builds data infrastructure for product analytics. Defines event taxonomy and data governance. Creates self-service analytics for the team.

Builds an experimentation culture within the product team. Designs complex multivariate tests. Defines the quarterly experiment strategy, prioritizing hypotheses by potential impact.

Builds a comprehensive funnel metrics system for the product. Applies advanced analytics: LTV forecasts, churn prediction, segment-specific funnels. Makes strategic decisions based on funnel data.

Creates comprehensive GTM strategies for the product line. Optimizes go-to-market motion (product-led, sales-led, hybrid). Analyzes GTM effectiveness through metrics.

Builds a continuous experimentation process. Prioritizes hypotheses by expected impact and cost of validation. Establishes an experiment backlog and tracking system.

Applies JTBD as a strategic tool for product discovery. Combines with Opportunity Solution Trees. Defines product positioning based on job differentiation.

Builds a market intelligence practice for the product. Uses market data for strategic planning. Forecasts market trends and adapts strategy.

Cascades OKRs from company-level to team-level, ensuring alignment. Designs a metrics framework for the product line. Uses OKRs for feature go/no-go decisions.

Builds a multi-level roadmap system: strategic (year), tactical (quarter), operational (sprint). Manages dependencies between products. Adapts the roadmap to changing market conditions.

Updates and adapts product vision based on market changes and feedback. Builds cascading: vision, strategy, objectives, key results. Ensures stakeholder buy-in.

Manages a complex stakeholder matrix (C-level, partners, key customers). Negotiates resources and priorities. Builds a regular cadence process for stakeholder communication.

Builds a continuous discovery system: regular interviews, feedback analysis, NPS/CSAT monitoring. Combines qualitative and quantitative research. Creates data-driven user personas.

Applies story mapping for quarterly strategic planning. Combines with impact mapping and opportunity solution trees. Teaches the technique to other PMs and designers.

Adapts Scrum for product and team specifics. Scales through Scrum of Scrums or LeSS. Defines how-to for non-standard situations (distributed teams, multiple products).

Builds a delivery metrics system for the product. Balances speed and quality. Uses DORA metrics to assess engineering health.

Minimizes dependencies through architectural decisions. Builds processes for cross-team alignment. Manages complex dependency chains.

Applies probabilistic estimation (Monte Carlo, cone of uncertainty). Builds a culture of estimation transparency. Uses the #NoEstimates approach where applicable.

Applies Kanban as a delivery management system. Combines Kanban with other approaches (Scrumban). Uses the flight-level model (operational, coordination, portfolio).

Systematically optimizes processes at the product level. Applies lean thinking and waste elimination. Implements a continuous improvement culture.

Builds release cadence for the product. Manages dependencies between teams. Balances feature releases, bug fixes, and tech debt.

Manages resource planning for the product line. Balances resources between projects. Creates hiring plans together with Engineering Managers.

Builds a risk management system for the product line. Balances risk-taking and risk-mitigation. Uses riskiest assumption testing for product discovery.

Masterfully visualizes complex concepts. Creates strategic visualizations: Wardley maps, ecosystem maps, opportunity landscapes.

Builds knowledge management practice for the product line. Standardizes documentation processes. Implements docs-as-code.

Shapes documentation strategy for the product. Integrates docs into the product release process. Ensures self-service support through documentation.