Situation: I’ve just been promoted from IC PM to manager of PMs. My focus must shift from doing tactical product work to enabling the team, while preserving domain and technical credibility.
Weekly time reallocation (before → after, approximate):
- Individual contributor work (80% → 10%): stop owning feature specs end-to-end.
- 1:1s and coaching (0% → 25%): weekly 30–45m 1:1 per direct, plus ad-hoc coaching.
- Strategy & roadmap alignment (10% → 25%): set vision, prioritize initiatives, stakeholder syncs.
- Cross-functional coordination (5% → 20%): unblock teams, escalate risks, align with Eng/Design/Sales.
- Talent & hiring (0% → 10%): recruiting, interviews, onboarding improvements.
- Metrics, reporting & org-level initiatives (5% → 10%): OKRs, health metrics, process improvements.
Changes in deliverables & KPIs I’ll own:
- From: PRDs, specs, sprint tasks. To: team OKRs, roadmap outcomes, hiring plans, growth/career plans.
- KPIs: team delivery predictability (on-time %), outcome metrics (activation/ retention/ revenue tied to roadmap), cycle time/throughput, PM satisfaction/engagement, ramp time for new hires, quality (bugs escaped), stakeholder NPS.
- I’ll still sign off on major product decisions and ensure alignment to business goals but delegate execution.
Maintaining technical credibility:
- Keep a lightweight technical practice: biweekly deep-dive with each lead PM on architecture decisions and technical trade-offs; attend critical design reviews; pair with engineers on one technical spike per quarter.
- Teach by example: ask informed questions, translate technical impacts into product trade-offs, and contribute to RFCs rather than authoring every spec.
- Invest in continuous learning: dedicate 2–3 hours/week to reading architecture docs, hands-on prototypes, or demos from the team.
- Empower technical leads: mentor rather than micromanage; when needed, facilitate cross-team technical forums so I stay current and visible.
Why this works:
- Shifts effort from output to multiplier effect—amplifies team impact.
- Replaces task ownership with outcome ownership via measurable KPIs.
- Preserves credibility by staying engaged on technical signals without reverting to IC behavior, enabling trust and better coaching.
