Business English Podcast · Meetings & Status Updates · Episode 23

Giving a No-Blame Account of a Failed Milestone

A milestone has failed — how to analyse causes instead of culprits: nuanced English for an honest post-mortem (C1).

C1 · Dialogue · 5 Min. · free

▶ Listen to the episode To the comprehension test +49 511 4739339

All episodesPodcast catalog →More gamesSimmonds English Games →

Editorially reviewed by James Simmonds – English teacher since 2004Published 9 September 2026

SceneThe customer pilot has missed its milestone. Team lead Jonas tells senior director Richard what happened — causes instead of culprits, with lessons learned and a joint plan.

0:00 / 5 Min.

Tip: listen to the episode twice before you start the test. · Worksheet (PDF)

✓ To the comprehension test

Jonas — Team lead, software projectRichard — Senior director

You may also like

Next episode: B1 · Explaining Why a Small Task Is Late · 3 Min.B1 · Correcting an Update: "Aktuell" Does Not Mean "Actually" · 3 Min.B1 · Telling the Team What You Will Finish This Week · 3 Min.All podcast episodes →

Transcript

The full transcript opens after the comprehension test — so you train real listening instead of reading along.

German support

RichardJonas, the pilot milestone has slipped, and I'd like the full picture. Walk me through what happened — and to be clear, I'm interested in causes, not culprits.„Causes, not culprits" – Ursachen statt Schuldige: der Kern jeder No-Blame-Kultur.

JonasI appreciate that framing, because the honest answer is that no single person dropped the ball. I see three contributing factors, and they reinforced each other.„Contributing factors" – Einflussfaktoren; „to drop the ball" – einen Fehler machen, etwas versäumen.

RichardGo on.

JonasFirst, the customer's test data arrived two weeks late — a dependency we had never flagged as critical. Second, our only integration specialist went on parental leave in the same period; that was a single point of failure we created ourselves. And third, the pilot customer tightened their security policy mid-project, which invalidated part of our setup.„Single point of failure" – die eine Stelle, an der alles hängt.

RichardWhen did you first realise the milestone was genuinely at risk?

JonasHonestly? Later than we should have. With hindsight, the warning signs were visible in April — the test data slipping, the handover gaps. I raised it with our chef as soon as the picture was clear, but that was mid-May.„With hindsight" – im Nachhinein. Und Achtung: „chef" ist im Englischen der Koch!

RichardYour chef? Unless the kitchen is running the pilot, you mean your boss — 'Chef' is a classic German false friend; in English a chef cooks. But the timing is noted. Why so late?

JonasFair correction — my boss, of course. As for why: our reviews tracked activity, not outcomes. The board showed green because tasks were being completed, not because the integration actually worked. We were measuring motion, not progress.

RichardThat's a systemic observation, and a useful one. So what changes? I want lessons, not apologies.

JonasThree lessons learned. One: a dependency register with named owners, so nothing external surprises us again. Two: no single point of failure on critical skills — every specialist role gets a trained backup. Three: milestone reviews will test outcomes, not activity. If the integration doesn't run, the status isn't green.

RichardGood. What I value about this account is that it doesn't apportion blame — systems fail first, and then people get blamed for the system. Send me the revised recovery plan by Thursday?„To apportion blame" – Schuld zuweisen, verteilen.

JonasBy Thursday, yes. One request: I'd rather we present it to the customer jointly. It's the team's recovery plan, not mine alone — and it lands better when leadership visibly stands behind it.

Key phrases

contributing factors

the elements that together caused a result

The report lists three contributing factors for the delay.

to drop the ball

to fail to do something you were responsible for

Nobody dropped the ball — the process itself was flawed.

single point of failure

one element whose failure stops the whole system

Having only one admin is a single point of failure.

with hindsight

looking back, knowing what we know now

With hindsight, we should have escalated in March.

warning signs

early indications that something is going wrong

The warning signs were there weeks before the failure.

lessons learned

conclusions drawn from experience to improve future work

We documented the lessons learned in a short review.

to apportion blame

to decide who is at fault

The review focused on causes rather than apportioning blame.

recovery plan

a plan to get a failed project back on track

The recovery plan brings the pilot back on track by Q4.

Language notes

In this episode a team lead tells his senior director why a customer pilot missed its milestone — without blame, with three contributing factors and three lessons learned. You learn the vocabulary of no-blame analysis ("contributing factors", "single point of failure", "with hindsight") and the "Chef/chef" trap (level C1).

Causes, not culprits: the language of no-blame

Word choice decides whether a post-mortem becomes honest. Richard frames the conversation with "causes, not culprits"; Jonas answers with impersonal structures: "three contributing factors", "a dependency we had never flagged", "a single point of failure we created ourselves". Passives and the collective "we" shift the focus from people to systems — in English the hallmark of a professional post-mortem. Naming names ("Because Mr Weber forgot…") ends the openness in the room instantly.

The "Chef/chef" trap

German "Chef" is "boss", "manager" or "line manager" in English — an English "chef" is strictly a cook. "I raised it with our chef" sounds to native speakers as if the kitchen had been escalated to. At C1 this error rarely comes from ignorance, but often as a fossilised reflex under pressure. Register-aware alternatives: "my boss" (neutral), "my line manager" (formal), "senior management" (collective).

Measuring outcomes, not activity

Jonas's strongest analysis is systemic: "We were measuring motion, not progress." The status showed green because tasks were being ticked off — not because the integration ran. His third lesson learned draws the consequence: "Milestone reviews will test outcomes, not activity." This distinction — activity vs. outcomes, motion vs. progress — is core vocabulary of English-language project governance, and ideal for separating substance from busyness in a steering meeting.

Keep practising: Learn business English online — with real teachers from Simmonds, since 2004.

Frequently asked questions

What language level is this episode for?

Level C1 (CEFR). The dialogue uses nuanced management English with idioms ("to drop the ball") and technical terms ("single point of failure"); all eight key terms are explained bilingually.

How do I report a failed milestone without naming culprits?

With impersonal structures: factors instead of people ("three contributing factors"), a collective "we" instead of names, honest hindsight ("later than we should have") and concrete lessons learned with system changes.

Does German "Chef" translate as "chef"?

No — an English "chef" is a cook. German "Chef" is "boss", "manager" or "line manager". "I told my chef" literally means you spoke to your cook.

Where can I practise conversations like this at C1 level?

In the online business English courses from Simmonds Language Services (englisch-lehrer.com/online): live lessons with real teachers on Zoom, with a free consultation first — for companies and individuals across Germany, since 2004.

Is there a transcript to read along?

Yes, the full transcript with German support notes is on this page — listen first, then take the test, then read along.

Want to practise these phrases in a real conversation?

The podcast trains your ear — in our online lessons you practise the conversation yourself, with real teachers. For companies across Germany since 2004.

Online lessons with real teachers Book a free consultation

Call