Workplace Discussion: The Launch Delay
A product manager tells her team the launch is moving three weeks. Under the official reason sits a client, a bug, and an onboarding problem — watch how the truth surfaces. · C1 · Workplace Discussion
Step 1 — Listen (no transcript yet)
Listen once or twice without reading. Just follow the story: who is speaking, where, and what changes?
Real voices for this lesson. Slow plays the same voices at 75% speed.
…or listen with your device voice:
Step 2 — Comprehension questions
Answer from memory first. Each question trains a named skill.
Step 3 — Reveal the transcript
In the transcript: Phrasal verbDifficult wordIdiom
📄 Show Transcript
Karen: Thanks, both of you, for squeezing this in. Straight to it: we're not launching on the fifteenth. We're moving to the sixth of next month.
Dave: Three weeks? Karen, the build has been ready since Monday. My team has been in polish mode for ten days.
Karen: I know, and the build is genuinely good. This isn't about the build.
Priya: Then it's about the Meridian demo.
Karen: It's about making sure our first impression lands with everyone, not just one client.
Dave: That's a yes wearing a suit. Karen, if Meridian wants changes after the demo, three weeks of polish becomes three weeks of rework — and my team carries it.
Karen: If Meridian signs, Dave, your team doubles. I've seen the term sheet. That's not a rumor; that's a signature away.
Priya: Can I name the thing under the thing? We're not delaying a launch. We're redesigning it — the onboarding flow Meridian's people struggled with in testing is the same flow our own users flagged. The demo just gave us permission to admit it.
Karen: That's uncomfortably accurate.
Dave: Okay. If we're admitting things: the payment bug. It hits maybe two percent of checkouts, only on older phones. I didn't put it in the report because two percent sounded small. It's not small when it's someone's rent money failing.
Karen: Thank you for saying it in this room first. Here's my proposal: we use the three weeks properly — fix payments, rebuild onboarding, and run the Meridian demo with the new flow as the launch preview. No theater, no fake dates.
Priya: One more condition: the announcement can't say 'exciting changes.' People hear that phrase and reach for their résumés. It should say what broke, what we're fixing, and when — in that order.
Priya: And we tell the whole company the real reasons. People can handle a delay. What they can't handle is a fog.
Dave: Agreed. I'll write the technical note tonight — bug, fix, timeline, in plain English.
Dave: And if Meridian hates the new flow, we ship the old one on the sixth anyway. The date doesn't move twice.
Karen: Then we're a team again. The announcement goes out tomorrow morning, together, with all three names on it.
Step 4 — Difficult expressions
Thanks, both of you, for squeezing this in.
My team has been in polish mode for ten days.
That's not a rumor; that's a signature away.
Can I name the thing under the thing?
I'll write the technical note tonight — bug, fix, timeline, in plain English.
Step 5 — Pronunciation & reductions
American English shrinks unstressed words. This is what the speakers really did with their mouths:
You read:
That's a yes wearing a suit
You hear:
That's a YES wearing a SUIT
Dave delivers it flat and dry — deadpan stress on the image words. The dryness is the criticism.
You read:
It's about making sure our first impression lands with everyone, not just one client
You hear:
…lands with EV-eryone — not just ONE client
Karen's pause before 'not just one client' is a dodge you can hear: she stresses the general to avoid naming Meridian.
You read:
What they can't handle is a fog
You hear:
What they CAN'T handle is a FOG
Hard stress on 'can't' and a slow final word — Priya turns a metaphor into a verdict.
You read:
No theater, no fake dates
You hear:
NO theater — NO fake dates
Parallel negatives with matching beats: the rhythm of a promise being made in public.
🗣️ Practice this pronunciation →
Step 6 — Shadow
Play the audio and speak with the voices — same words, same rhythm, half a second behind them. Use Slow if you need to. Two or three passes, out loud.
Step 7 — Speak
You are Karen. Record a 45-second announcement to the whole company: the new launch date, two honest reasons for the delay, and one promise about how you'll communicate. No fog.
Record yourself, play it back, and compare with the model. Recordings stay in your browser — nothing is uploaded.
Step 8 — Final comprehension check
One last pass: dictation and quick questions. No transcript peeking this time.
Keep training this skill
🗣️ Pronunciation Lab — sounds, stress, reductions & shadowing (A1–C1)🎙️ Speaking Studio — dialogues, role-plays and interviews🌱 Vocabulary Builder — grow the words you heard🔗 Phrasal Verbs Lab — the verbs native speakers actually use💬 Idioms — one idiom in every Step by Step lesson🇺🇸 Real-Life English — Say It Right, the mistakes clinic🎓 TOEFL Listening — the exam version of this skillKeep going
Ad space