Roles and teams
Technical program manager
Also calledTPgM, TPM (program), Program manager
The person who owns how and when complex work lands across several teams: dependencies, timelines, risks and release coordination. They do not decide what gets built.
A technical program manager makes multi-team work land on time. They map dependencies, run the schedule, surface risks early and coordinate releases. The product manager owns the what and why; the program manager owns the when and how.
The role becomes necessary when cross-team dependencies no longer fit in one planning conversation, typically somewhere around ten squads in a growing company, earlier in a large one.
Common mistake
Hiring a program manager to cover for unclear product ownership. A TPM cannot fix a missing decision about what to build; they will only schedule the confusion efficiently.