Technical Program Manager (TPM)
Technical Program Managers operate in the space between engineering, product, and leadership — and they live by the quality of their written and spoken communication. A weekly status update that buries the risk, an escalation that does not clearly name the ask, or a dependency conversation that leaves ownership unclear can derail a multi-team program. This path builds the vocabulary and communication patterns to run programs that stay on track.
Topics covered
- cross-team coordination
- dependency mapping
- risk vocabulary
- program status communication
- technical scope language
Vocabulary spotlight
4 terms every Technical Program Manager (TPM) should know in English:
A fixed time-box (typically 8–12 weeks) during which a set of teams delivers a coordinated set of features
"We are three weeks into the program increment and two critical dependencies are already at risk."
A piece of work that one team requires from another before they can proceed with their own deliverable
"The authentication service is a dependency for the new onboarding flow — without it, the frontend team is blocked."
The sequence of dependent tasks that determines the minimum time to complete a program; any delay on the critical path delays the whole program
"The database migration is on the critical path, so we need to de-risk it first."
A document that tracks identified risks, their likelihood, potential impact, and mitigation plans
"I will add the third-party API deprecation to the risk register and assign an owner before Friday."
A chart assigning Responsible, Accountable, Consulted, and Informed roles to each task in a program
"The RACI matrix shows you are consulted on the API design but the backend team is responsible for the decision."
The defined route for raising a blocked issue to the appropriate level of management when normal resolution channels have failed
"We have been stuck on this dependency for two weeks — it is time to use the escalation path."
📚 Vocabulary Reference
Key terms organised by category for Technical Program Manager (TPM)s:
Planning
Risk & Status
Roles & Ownership
Delivery
Recommended exercises
Real-world scenarios you'll practise
- Writing a weekly program status update that clearly signals a risk without creating panic.
- Escalating a cross-team dependency that has been unresolved for two weeks with a clear ask for leadership.
- Presenting program risks to leadership in a way that informs rather than alarms.