Senior PM -> Lead PM

Diagnose whether it's a skill gap (they don't know how) or a confidence/habit gap (they know how but don't). Skill gap: targeted practice with low-stakes opportunities and explicit feedback. Confidence gap: progressive exposure, prep support, and visible wins. Don't reassign communication away from them — that cements the weakness.

Lead PMs are evaluated on: team output quality (not personal output), PM development track record, operating model effectiveness, cross-functional leadership at the leadership level, and strategic coherence across their product area. Their individual product judgment is assumed; their leadership judgment is what's tested.

First, make the cost of the dependency visible with data (how often, what's delayed, what's the business impact). Then propose a structural solution — team topology change, shared OKR, or embedded resource — rather than asking the same partner team to prioritise differently each quarter.

First, diagnose: is it a strategy problem (wrong bet), a discovery problem (wrong solution), a delivery problem (can't ship), or a measurement problem (wrong metric)? Each requires a different intervention. Pressuring the team harder without diagnosis just accelerates the wrong direction.

Brain teasers with no signal value, vague 'tell me about yourself' openers, product critique without context, and interviewers who score on confidence rather than reasoning. Replace with: structured problem-framing, prioritisation scenarios, and behavioural questions tied to specific competencies.

A Lead PM is accountable for outcomes across multiple product areas they don't personally own day-to-day. They can't control every decision — they must build the conditions (clarity, judgment, trust) so PMs make good decisions independently. Micromanaging is a signal of failure, not diligence.

Modelling the behaviour you want to see: giving design and engineering genuine input on strategy, not just execution; representing their interests in leadership forums; and calling out collaboration failures publicly when they occur in your area. The team mirrors the Lead PM's cross-functional posture.

The bar, not just the process. Lead PMs define what 'good' looks like at each level, design interview rubrics that test for the right signals, calibrate interviewers, and make the final call on offers. Delegating hiring to HR without owning the bar produces inconsistent teams.

When team OKRs don't connect to area or company OKRs — teams are working hard on things that don't contribute to shared goals. Prevented by: reviewing team OKRs before they're finalised, running explicit 'how does this connect to our area objective?' conversations, and killing OKRs that can't be traced up.

A principle that every hire should raise the average quality of the team — not just fill a seat. Applied by asking: is this candidate better than the median of our current team at the things that matter most? If not, keep looking, even under resource pressure.

A cross-manager process to normalise performance ratings across teams — ensuring 'exceeds expectations' means the same thing for every PM. Without calibration, ratings reflect manager generosity, not actual performance. Lead PMs participate in calibration to protect their team and maintain credibility.

A systematic process for tracking competitor moves, positioning changes, and market signals — not ad hoc googling. Operationalised through: assigned ownership per competitor, a shared living document updated quarterly, and a cadence for reviewing implications with the team.

Delegating by sharing the goal, the constraints, the why, and the decision rights — not just the task. Enables PMs to make good calls in unexpected situations without escalating. Task-only delegation creates robots; context delegation creates leaders.

The process of defining how many PMs are needed, at what level, and in which areas — typically done in annual or bi-annual cycles. Lead PMs should own the business case for each hire: what outcome does this PM enable that isn't possible today? Headcount without a rationale gets cut first.

Managing ICs: coach on craft, clear blockers, set context. Managing managers: develop their leadership judgment, calibrate their standards, and hold them accountable for team health — not just output. The feedback loop is longer and the failure modes are harder to see.

A norm of reviewing failures openly to extract learning, without blame. Built by: running blameless post-mortems yourself, framing failures as system problems not people problems, sharing post-mortem outputs widely, and following up on action items. Teams that hide failures can't learn from them.

The shared beliefs, behaviours, and norms that govern how product decisions are made. Shaped by: what the Lead PM celebrates (insights or features?), what they tolerate (HiPPO decisions or evidence?), and how they behave in ambiguous situations. Culture is modelled, not declared.

A structural partnership between the Lead PM and the engineering director (or equivalent) to jointly own team health, strategy, and delivery. Not just coordination — genuine shared accountability for outcomes. When this partnership is misaligned, it creates confusion for every team below.

Over-reliance on easily measured proxies (click rates, feature adoption) because true outcome metrics are hard to move or measure. Emerges at scale because Lead PMs need dashboards that aggregate across teams. Fix: insist on outcome metrics even when they're harder, and treat proxy improvement without outcome improvement as a warning sign.

Psychological safety without accountability produces a comfortable team that misses goals. Accountability without safety produces a fearful team that hides problems. Lead PMs hold both: clear expectations (accountability) + safe channels for flagging concerns early (safety). They're complementary, not opposing.

Regular 1:1s with PMs who report to managers that report to you. Used to: get unfiltered signal on team health, develop relationship with high-potential ICs, and identify where managers might be shielding problems. Not a channel to bypass managers — always close the loop with the relevant manager.

Managing a network of senior stakeholders — C-suite, board members, key customers — across multiple product areas simultaneously. Requires: knowing each stakeholder's goals and concerns, ensuring no sub-team PM is damaging a key relationship, and personally owning the most strategically sensitive relationships.

The process of translating company-level strategy into product-area strategy, then into team-level OKRs or themes. Lead PMs ensure the cascade is tight: every team's priorities should be traceable back to a company goal. Loose cascades produce effort without strategic alignment.

Spending time on exciting strategic questions without doing the harder work of driving alignment, clearing blockers, and holding teams accountable for execution. Strategy tourism produces good decks and weak results. Lead PMs are judged on outcomes, not the quality of their frameworks.

Giving a PM a project or responsibility slightly beyond their current level to accelerate growth. Effective when: the PM has the foundational skills to succeed with support, the stakes are manageable, and the Lead PM is actively coaching through the stretch. Unsupported stretch becomes a failure experience.

Feedback tied to a specific observation, the behaviour's impact, and a clear alternative. Format: 'When you [did X] in [situation], the effect was [Y]. What I'd suggest instead is [Z].' Structured feedback is more actionable than 'you need to be more strategic' and less personal than character assessments.

Deliberately building a team with complementary strengths — not clones of yourself. A team of all strategic thinkers with no execution depth fails. Map current gaps: who is weak on data, on stakeholder management, on technical fluency? Hire to the team's shape, not a generic spec.

When sub-teams under a Lead PM develop incompatible cultures, inconsistent standards, or competing priorities. Caused by insufficient cross-team communication and Lead PMs who operate as individual managers rather than a unified leadership layer. Fix: shared rituals, cross-team reviews, and consistent standards.

A structured plan covering: first 30 days (learn — team, product, stakeholders), 60 days (contribute — own a problem area), 90 days (lead — drive a decision or initiative). Lead PMs who don't own onboarding leave new hires to absorb culture by accident rather than design.

When decisions default to whoever is most senior, rather than whoever has the best evidence. Countered by: creating forums where evidence is presented before opinions, publicly praising data-driven decisions regardless of who makes them, and pushing back on HiPPO calls — including your own.

An explicit description of what excellent PM work looks like at each stage: discovery, prioritisation, writing, stakeholder communication, and measurement. Without a defined standard, 'quality' is subjective and inconsistently applied. Craft standards enable coaching, hiring calibration, and promotion decisions.

A mapping of which decisions are made by the PM alone, which require alignment with engineering/design/data, and which require leadership approval. Prevents both under-escalation (PMs making calls they shouldn't) and over-escalation (PMs seeking approval for calls they own).

A development plan is forward-looking: what skills or experiences will prepare this PM for their next level? A performance plan is corrective: what must change to meet current expectations? Conflating them signals to high performers that development only happens when something is wrong.

A single view of leading and lagging indicators across all products in the area. Typically: key outcome metrics per team, trend direction, experiment velocity, team health signals, and flagged risks. Lead PMs use it to identify where to intervene before problems become visible to the business.

A job description lists responsibilities. A scorecard defines the outcomes expected in the first 6–12 months and the competencies required to achieve them. Used to evaluate candidates against objective criteria — not gut feel. Makes hiring decisions defensible and consistent.

A product review covers one team's metrics and roadmap. A portfolio review covers the entire product surface: which teams are on track, which are struggling, where investment is misallocated, and whether the combined strategy is coherent. Lead PMs run portfolio reviews; senior PMs present in them.

A product area strategy covers a coherent customer problem space across multiple teams and products. A team strategy covers one team's initiatives. Lead PMs own the area strategy — ensuring that individual team strategies add up to something coherent rather than independently optimised fragments.

A recurring forum where product leaders across teams share strategy, surface dependencies, review cross-cutting priorities, and maintain alignment. Needed when multiple PMs are working on adjacent spaces and informal coordination is no longer sufficient.

A crisp story explaining: what problem space you own, why it matters to the business, what the product does and doesn't do, and where you're going. Audience: new hires, partner teams, investors, and the board. Lead PMs write and own this narrative — it should be consistent regardless of who tells it.

An annual or bi-annual process to set or refresh product area strategy. Typically: market and user review → team input → draft strategy → cross-functional pressure testing → final leadership alignment. Lead PMs design the process, not just participate in it. Good planning cycles surface disagreement early.

A periodic leadership discussion assessing team member potential, retention risk, and succession readiness. Lead PMs should bring: a clear view of each PM's trajectory, their top retention risks and why, their proposed next-level opportunities, and at least one succession candidate for key roles.

A formal, documented plan setting specific expectations, a support structure, and a timeline for a PM who isn't meeting role requirements. Used after coaching hasn't produced change and before a separation decision. A PIP done well is a genuine attempt to help; done poorly it's a paper trail for a foregone conclusion.

The system that governs how product decisions are made, by whom, and on what cadence. Includes: discovery rituals, roadmap review cadence, decision rights, escalation paths, and cross-functional ways of working. Lead PMs design the operating model; ICs operate within it.

A shared reference defining how the team collaborates: meeting cadences, communication norms, how decisions are documented, how feedback is given, and how conflict is resolved. Lead PMs own this document — without it, norms form by accident and vary across sub-teams.

A senior leader (often C-suite) who champions a product initiative at the executive level. Lead PMs cultivate executive sponsors by keeping them informed, giving them talking points for internal advocacy, and ensuring their sponsorship translates into real resource or priority decisions — not just verbal support.

Objectives (qualitative, inspiring goals) and Key Results (measurable outcomes that signal the objective was achieved). Lead PMs design area-level OKRs that are: outcome-focused not output-focused, ambitious but achievable, and specific enough that teams can derive their own OKRs from them.

The belief that it's safe to speak up, disagree, or admit a mistake without punishment. Built through: modelling vulnerability (sharing your own failures), rewarding candour over consensus, never shooting the messenger, and following up when someone raises a risk that turns out to be real.

Flying in on a decision already in progress, making a loud intervention, then flying out — leaving the team to clean up. Seagull management undermines PM ownership and creates learned helplessness. Lead PMs should engage early and continuously, or trust the PM to lead without interference.

Lead PMs set the strategic frame that individual PMs execute within. They own the 'why we're playing here and what winning looks like' — and then get out of the way. Overreaching into execution erodes PM ownership and slows the team.

From 'I am the best product thinker on my team' to 'my job is to make every PM on my team a better product thinker than I was.' Lead PMs multiply through others. Personal output becomes secondary to team output quality.

Feedback: telling someone what you observed and its impact. Coaching: asking questions that help someone arrive at their own insight. Lead PMs use feedback for clear performance gaps and coaching for development — conflating them produces neither accountability nor growth.

They're driving company-level strategy, not just product-area strategy. They're developing other leaders, not just PMs. They have credibility with the board and C-suite. And they've successfully hired and grown a team that delivers results independent of their direct involvement. The title confirms an already-visible reality.

Lead PMs who stay in IC mode create dependency, suppress PM growth, and become the bottleneck on every decision. The goal is to build a team where decisions are made well *without* the Lead PM in the room. That requires deliberately stepping back, not stepping up.