Defines API-first strategy for the division. Establishes API governance. Ensures API design consistency across products.
Roles · Product Manager · Lead
What a Lead } should know
32 core skills, 47 in total. Expectations per skill, and what changes at the next level.
This page lists what a Lead } is expected to know and do, skill by skill. Core skills are the ones a manager and peers assess in a review cycle; the rest count only in self-assessment. Main areas: API & Integration, AI-Assisted Development, Architecture & System Design.
Core skills for a Lead
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
API & Integration · 1
AI-Assisted Development · 3
Defines AI adoption strategy for the product division. Trains PMs on AI usage. Establishes guidelines for responsible AI use.
Defines developer experience strategy including AI tools. Standardizes the approach to AI coding assistance for the division.
Defines prompt engineering standards for the division. Creates shared prompt libraries. Trains the team on advanced techniques.
Architecture & System Design · 1
Participates in strategic architectural decisions. Ensures alignment between technical and product strategy.
Version Control & Collaboration · 1
Defines standards for documentation-in-code. Uses Git data for engineering management insights.
Product Management · 14
Defines experimentation standards for the product division. Trains junior PMs on A/B testing methodology. Implements feature flagging and progressive rollout processes at the organizational level.
Standardizes backlog management practices for multiple product teams. Trains PMs on prioritization and decomposition techniques. Ensures cross-product backlog synchronization.
Defines metric standards for the product division. Standardizes funnel analysis approaches. Trains the team on working with data and formulating data-driven hypotheses.
Defines GTM strategy for the division. Coordinates cross-product launches. Establishes launch playbooks and GTM processes.
Defines experimentation culture for the division. Standardizes validation and decision-making processes. Trains PMs and designers on rapid experimentation methods.
Implements the JTBD approach across the product division. Trains PMs on conducting JTBD interviews. Uses JTBD for strategic product portfolio decisions.
Defines the market research approach for the division. Establishes competitive strategy. Participates in strategic decisions about new markets and product lines.
Defines metric culture for the division. Standardizes the OKR process for multiple teams. Ensures cross-functional alignment through shared OKRs.
Standardizes the analytics stack for the division. Defines data strategy and analytics tooling investments. Trains teams on working with data.
Defines planning standards for the product division. Coordinates roadmaps across multiple products ensuring synergy. Establishes processes for roadmap governance and stakeholder alignment.
Shapes portfolio vision for a group of products. Ensures vision consistency across related products. Mentors PMs on formulating and communicating vision.
Represents the product division at the executive level. Builds strategic alliances with stakeholders. Trains PMs on executive communication and influence without authority.
Defines research strategy for the product division. Implements tools and processes for scaling research. Trains the team on UX research and customer development methods.
Standardizes scope decomposition and visualization approaches at the division level. Applies story mapping for cross-product initiatives.
Project Management · 9
Standardizes delivery metrics for the division. Defines benchmarks and targets. Uses metrics to optimize cross-team dependencies.
Defines organizational design for minimizing dependencies. Implements team topologies and API contracts. Establishes cross-team collaboration processes.
Standardizes estimation practices for the division. Trains PMs and tech leads on estimation techniques. Defines when to use estimates vs forecasts.
Defines the flow-based approach for the division. Trains teams on Kanban practices. Scales Kanban to the organizational level.
Defines process excellence standards for the division. Trains teams on continuous improvement methods. Establishes a culture of experimentation.
Standardizes the release process for the division. Coordinates cross-product releases. Establishes release governance.
Defines staffing strategy for the division. Establishes organizational design for optimal resource utilization.
Defines risk management framework for the division. Establishes risk-aware decision-making processes. Trains PMs on risk assessment.
Defines agile methodology for the division. Develops agile coaches, trains PMs on Scrum. Optimizes processes for enterprise scale.
Documentation · 3
Standardizes visual standards for the division. Defines diagramming guidelines and templates.
Defines knowledge sharing strategy for the division. Ensures cross-team knowledge transfer.
Defines documentation standards for the division. Establishes a tech writing practice.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
What changes at Principal
0 skills get a higher expectation or become core when moving from Lead to Principal. The biggest jumps first.
} in the open competency matrix: 47 skills across 5 levels. The matrix is free for individuals and stays free.