Project Management — B2 Lesson

B2 project communication

Managing a high-stakes delivery crisis

Use precise English to disclose risk, take accountability, and present a recovery plan with confidence.

Lesson preview

Advanced programme vocabulary for governance, risk, and recovery.

Functional language for serious client conversations and board-level updates.

Role play based on a delayed 3M euro ERP implementation.

40 minutes B2 Upper-Intermediate 6 stages

Stage 1 — Warm-up

Programme-level thinking

5 minutes · Critical discussion

Discuss with your partner:

1. What is the difference between a project manager and a programme manager? At what point does complexity require programme-level governance?

2. How do you manage competing priorities between multiple stakeholders who each believe their workstream is the most critical?

3. When a project is failing, what are the signs a PM should look for early — and what is the ethical obligation to the client when those signs appear?

Teacher note: At B2, focus on programme governance, strategic communication with senior stakeholders, and the language of formal change control. Key structures: passive voice in formal reporting, modal perfect for counterfactual analysis, hedged assertions for recommendations under uncertainty.

Today's scenario — Project Meridian: a 3M euro ERP implementation at a manufacturing firm:

Student A — Programme Director

You have just discovered that the external implementation partner has been concealing delays. The project is 6 weeks behind, 400k over budget, and the client board meets in 48 hours. You must decide: disclose now, manage the fallout, and restructure the delivery plan.

Student B — Client Sponsor

You are the client executive who commissioned the project. You have just been told there is a problem. You are angry but professional. You need answers: how did this happen, who is accountable, and what guarantee do you have it will be delivered?

Crisis disclosureERP implementationAccountability

5 min

Stage 2 — Vocabulary

Advanced programme management vocabulary

10 minutes · Gap-fill exercise

Click a word from the box, then click a blank. Hover for definitions.

remediation

RAG status

change control

critical path

dependency

SLA

post-mortem

decommission

Complete the sentences with the correct word from the box.

A formal plan has been submitted to the steering committee, with weekly progress checkpoints.

The project has been reported as amber for three consecutive weeks — it should have been escalated to red by now.

Any addition to scope must go through formal — we cannot simply absorb it into the existing timeline.

The data migration task sits on the — any delay there flows directly into the go-live date.

The reporting module has a hard on the data warehouse being live — we cannot start it earlier.

We are at risk of breaching the for system availability — if that happens, penalty clauses are triggered.

I would recommend scheduling a formal within two weeks of go-live, while the experience is still fresh.

The legacy system will be ed in phases over six months to reduce transition risk.

10 min

Stage 3 — Functional language

High-stakes project communication

8 minutes · Study and practise

Disclosing a serious problem

I owe you a direct and complete account of where the project stands, and I want to do that now rather than waiting.

The position is more serious than our recent reports have conveyed, and I take full accountability for that.

There has been a failure of reporting discipline on our side, and I am not going to minimise that.

I want to be transparent about the root cause before we discuss the path forward.

Taking and attributing accountability

Ultimately, the accountability for delivery rests with my organisation, not the subcontractor.

I should have implemented more rigorous RAG reporting governance at the outset — that is a lesson I will carry forward.

There were systemic failures in our change control process that allowed scope to expand without budget adjustment.

I am not here to assign blame — I am here to fix this — but the root cause analysis is important.

Presenting a credible recovery plan

We have modelled three recovery scenarios. My recommendation is the one I call Option B.

The critical path has been re-sequenced to protect the go-live date, at the cost of deferring two non-critical workstreams.

I am proposing weekly steering group check-ins for the remainder of the project, with full RAG transparency.

I can commit to that revised timeline with high confidence, provided the dependency on your internal data team is resolved.

Responding to client challenge

That is a fair challenge and I do not intend to deflect it.

I understand your concern about continuity of leadership. I will personally oversee the remaining delivery.

I recognise that trust has been damaged here. The only way I can rebuild it is through consistent delivery.

If, after hearing the recovery plan, you feel escalation to the board is appropriate, I will fully support that.

Agreeing remediation and governance

We are agreed: weekly steering group, full RAG reporting, and a formal change control log from this point forward.

I will circulate the revised programme plan and risk register by 9am tomorrow.

The next milestone is a go/no-go gate on the 14th — if we are not ready, we pause and reassess.

I would ask that we agree a communication plan for the board before either of us speaks to them independently.

At B2, the language of accountability is precise and active: "I should have...", "I take full accountability for...", "The root cause was...". Avoid passive deflection: "Mistakes were made" signals evasion. "I failed to implement governance" signals leadership.

8 min

Stage 4 — Language in use

B2 programme management language drill

10 minutes · Multiple choice

10 min

Stage 5 — Role play

The crisis disclosure conversation

12 minutes · Pair work

How to use: Student A must disclose the full situation, own accountability, and present a credible recovery plan. Student B must ask hard questions, express legitimate frustration professionally, and ultimately decide whether to continue the engagement or escalate to the board. Neither should lose composure.

Student A — Programme Director

[Open by signalling the seriousness of the conversation. Acknowledge that you have asked for this meeting because you owe the client a full and transparent account. Do not minimise. State the headline: 6 weeks behind, 400k over budget.]

Student B — Client Sponsor

I appreciate you coming to me directly. But I have to be honest — I am deeply concerned. We have had three amber RAG reports in a row. Why was I not told about this sooner?

Student A — Programme Director

[Take full accountability for the reporting failure. Do not blame the subcontractor initially. Explain the root cause: reporting discipline broke down, scope expanded without proper change control. Own it.]

Student B — Client Sponsor

So scope expanded without authorisation and without adjustment to the budget. How did that pass through governance without anyone flagging it?

Student A — Programme Director

[Explain the change control failure honestly: informal requests from the client's own internal team were absorbed into delivery without a formal change log. Acknowledge shared causation carefully — without deflecting your own accountability.]

Student B — Client Sponsor

I need to understand the path forward. We have a board meeting in 48 hours. What do I tell them? And more importantly, do you have a credible recovery plan, or are you here to tell me the project is failing?

Student A — Programme Director

[Present the recovery plan with clarity: critical path re-sequenced, two non-critical workstreams deferred, new go-live date confirmed, weekly steering group with full RAG transparency. Commit personally to leading delivery from this point.]

Student B — Client Sponsor

If I take this to the board, they will ask me whether I still have confidence in your organisation to deliver. What do I tell them? And what happens if you miss this new date?

Student A — Programme Director

[Answer directly and with measured confidence. Propose a governance structure for the remaining period. Offer a joint communication plan for the board. Propose a go/no-go milestone in two weeks. Close by asking the client to tell you what they need to maintain confidence.]

Student B — Client Sponsor

[Decide: after hearing the plan, express cautious conditional confidence. State what you need from the PM going forward. Close by agreeing the next steps and the communication plan for the board.]

Extension: the board presentation

Swap roles. Student A is now the client sponsor presenting the situation to the board (Student B plays a board member). Student A must explain what happened, why they still have confidence in the supplier, and what governance is now in place. Student B asks hard questions about decision-making and financial exposure.

12 min

Stage 6 — Summary

Lesson complete!

5 minutes · Review

Today's lesson

B2 — Upper Intermediate

Project Management

~40 minutes

What you practised:

8 advanced programme vocabulary words: remediation, RAG status, critical path, change control, SLA, post-mortem

Phrases for 5 high-stakes PM functions: crisis disclosure, taking accountability, presenting recovery plans, responding to challenge, agreeing governance

6 B2 drills: modal perfect for accountability, "provided" conditionals, passive voice in formal reporting, precise governance language

A crisis disclosure role play requiring full accountability, a credible recovery plan, and negotiated governance structure

Homework ideas:

1. Write a formal crisis communication email (150-200 words) from the Programme Director to the client board, disclosing the delay and presenting the recovery plan.

2. Conduct a mock post-mortem. Write 5 lessons learned from the Meridian project scenario, formatted as: What happened / Why it happened / What we will do differently.

3. Research the difference between a project RAG report and a programme dashboard. Write 3 sentences explaining when you would use each and who the audience is.

Outstanding work. Disclosing a project crisis to a senior client — in a foreign language, under pressure, with precision and accountability — is one of the hardest professional communication challenges there is. You practised all of it today.