Product Manager Interview (+ AI PM) · Strategy, Prioritization & Execution · Lesson 3 of 4
Roadmaps, trade-offs & working with eng
Execution rounds test whether you can turn priorities into a shipped product with limited time and people. The recurring theme is trade-offs: scope vs time vs quality, and how you communicate them.
- Roadmap = outcomes over time, not a feature calendar. Tie each item to a goal/metric, and keep it flexible.
- The iron triangle: scope, time, resources/quality — you can't fix all three. Decide which to flex and say why.
- Cut scope, not corners: ship a smaller slice that delivers value (MVP) rather than a late, bloated release.
- Work with eng: bring the problem and priority, not a spec to obey; let them own the how; respect estimates and tech-debt trade-offs.
- Manage stakeholders: align execs, design, sales, support early; over-communicate changes and the reasoning.
Don't dictate the howHanding engineers a rigid solution and a deadline erodes trust and quality. Bring the why and the priority; collaborate on the how. PMs who respect eng judgment get better estimates and fewer surprises.
A launch is slipping — what now?Reassess against the iron triangle: cut scope to a valuable MVP, or move the date, or add focus — but never silently sacrifice quality. Then communicate the trade-off and reasoning to stakeholders early.
◆ Lock it in
- A roadmap is outcomes over time tied to metrics — not a fixed feature calendar.
- Respect the iron triangle: flex scope/time/quality deliberately and say why.
- Work with eng by bringing the problem + priority, not a dictated solution.
Feynman drill — say it out loudA feature will miss its launch date. Walk through how you'd use the scope/time/quality triangle to respond.
Step 1 rate your confidence · Step 2 pick your answer
A launch is running late. What's the strongest PM move?
Step 1 — how sure are you?