English for Technical Programme Managers: Cross-Team Communication and Risk Language

Technical Programme Managers (TPMs) sit at the intersection of multiple engineering teams, business stakeholders, and external dependencies. Their primary communication challenge is conveying complex, interdependent technical work in clear language — and doing so both upward to leadership and horizontally to peer teams. This guide covers the vocabulary, the status update language, and the escalation phrases that effective TPMs use.

Core TPM Vocabulary

Dependency — a piece of work that one team or component relies on another team or component to complete before proceeding. “The payments team has a hard dependency on the identity team’s new auth token format; until that is shipped, payments cannot proceed with their integration.”

Blocking dependency — a dependency that completely halts progress until resolved. “We have a blocking dependency on the third-party data provider’s API — without their updated contract, we cannot begin the integration work.”

Hard dependency vs. soft dependency — a hard dependency is one where work literally cannot proceed; a soft dependency is one where work can continue but will require rework if the dependency changes. “The API contract is a hard dependency; the design specifications are a soft dependency — we can begin development before they are finalised but may need to iterate.”

Risk — an uncertain event or condition that, if it occurs, has a positive or negative effect on the programme. Always expressed with a probability and an impact. “There is a medium-probability risk that the external vendor will not deliver their SDK update by the agreed date; the impact would be a two-week delay to our integration milestone.”

Risk register — a document that lists identified risks, their probability, impact, owner, and mitigation actions. “The risk register for this programme has 12 open items; three are rated high priority and require mitigation plans this week.”

Mitigation — an action taken to reduce the probability or impact of a risk. “Our mitigation for the vendor delay risk is to begin a parallel track evaluating an alternative SDK, so we have a fallback if they miss the date.”

Contingency — a plan or resource held in reserve to address a risk if it materialises. “We have a two-week contingency buffer built into the plan for exactly this type of delay.”

Milestone — a significant point in the programme timeline, typically marking the completion of a phase or deliverable. “The first milestone is the API contract sign-off, scheduled for the end of this sprint.”

Critical path — the sequence of dependent tasks that determines the minimum total duration of the programme. Any delay to a task on the critical path delays the entire programme. “The database migration is on the critical path; if it slips by more than three days, the whole programme end date moves.”

Slack / float — the amount of time a task can be delayed without affecting the critical path or the programme end date. “There is two weeks of slack in the frontend build; it is not on the critical path, so a short delay there does not concern me.”

RACI — a responsibility assignment matrix. Stands for Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), and Informed (kept up to date). “Before the kick-off, let’s align on the RACI for the compliance review — I want to be clear who is accountable versus who is merely consulted.”

Programme Status Update Language

Status updates need to be clear, accurate, and action-oriented. Avoid vague language like “progressing well” without evidence.

Overall programme status:

• Green — on track: “The programme is currently green; all milestones are on track and there are no open blockers.”
• Amber — at risk: “The programme is amber this week due to the vendor API delay; we have a mitigation plan in place but cannot yet confirm the overall end date is safe.”
• Red — significantly at risk or delayed: “The programme is red. The critical-path task has slipped by two weeks; the end date is no longer achievable without either descoping or additional resource.”

Reporting progress:

• “As of this week: three of five milestones are complete; the fourth is in progress and on track for Friday; the fifth depends on the external API contract which remains open.”
• “The payments integration is two days behind forecast due to an unexpected schema mismatch discovered during testing; the team is working to resolve it and expects to be back on track by Thursday.”

Flagging a blocker:

• “I need to raise a blocker: the identity team has not yet provided the updated token format, and the payments team cannot proceed without it. I need alignment on priority from both team leads by the end of the day.”

Escalation Language

Escalation is a normal part of programme management, not a sign of failure. Use clear, factual language that focuses on the decision needed.

Escalating a risk:

• “I am escalating this risk because it has moved from medium to high probability, and the mitigation options available to me at programme level are insufficient. I need a senior stakeholder decision on whether to descope Feature X or accept the extended timeline.”

Escalating a dependency:

• “The dependency on Team B’s API has been outstanding for three weeks; at programme level I have had two conversations without resolution. I am escalating to [name] to request a prioritisation decision.”

Escalating a resource conflict:

• “Two programmes are competing for the same two engineers during the same two-week window; I cannot resolve this conflict at programme level. I need a prioritisation decision from leadership.”

Framing an escalation:

• “I am not asking you to solve this for me — I am asking for a decision on [specific question]. The options are A, B, or C; my recommendation is B, but I need your approval to proceed.”

Example Programme Status Sentences

1. “The programme is amber this week: the critical-path infrastructure work is on track, but the vendor integration has a high-probability risk that could push the overall end date by one to two weeks if it materialises.”

2. “We have a hard dependency on the security team completing their penetration test before we can open the beta — that dependency is on the critical path and is currently scheduled for the week of the 12th.”

3. “The risk register has one new high-priority item added this week: the third-party authentication provider has announced a breaking API change; we have flagged this to the identity team and are awaiting their assessment.”

4. “I want to clarify the RACI for the compliance sign-off: engineering is Responsible for preparing the evidence pack, Legal is Accountable for the final approval, and the CISO is Consulted but not the decision-maker.”

5. “I am escalating the resource conflict between Programme Alpha and Programme Beta because both have the same two engineers on the critical path during the same sprint; I need a prioritisation decision from the engineering director by end of week.”