ENGLISH FOR WORK · B2/C1 · 50 min

The First Person to Say Red

A new chief executive walked into a company losing billions, asked one question every week, and got the same answer for a month: everything is fine.

Today: a true story about the hardest thing to do in a new job — admit you don't know something — and the language that lets you ask, check and flag a problem without sounding incompetent: could you tell me how…, I was wondering whether…, just so I'm clear…
Before we start. Talk these through out loud.
Discuss:
  • Think back to your first week anywhere — a school, an office, a hospital. What was the question you wanted to ask and didn't? Why not?
  • In your workplace, what actually happens to the person who says "this isn't working"? Be honest.
  • Is it worse to look like you don't know something, or to be found out later? Does your answer change depending on how senior you are?

The vocabulary you'll need

Ten items. Work through the four activities — say your answer out loud before you reveal it.

A · What do they mean here? Work it out from the context

1. He had run an aircraft manufacturer, not a car company. He did not know the models, the suppliers, the dealers or the union agreements, and he had roughly eight weeks to learn them. It was, by any measure, a steep learning curve.
a steep learning curve (n) — a situation where you have to learn a great deal very quickly. "It's been a steep learning curve." Note: in everyday use steep means hard, even though a steep curve technically means fast progress. Nobody minds. Related: to be thrown in at the deep end.
2. Nobody was asking their team to solve the problem for them. They simply had to put it on the chart, in front of everyone, so that the room could see it existed. They had to flag it.
to flag something (v) — to draw attention to an issue so others can see it. "I want to flag a risk." · "Flagging this early." Useful neighbours: to raise an issue, to surface a problem, to escalate (send it upward).
3. What changed in that room was not the numbers. It was that people stopped believing they would be punished for saying something was wrong. Researchers have a name for that belief: psychological safety.
psychological safety (n) — a shared belief that the team is safe for taking interpersonal risks: asking a question, admitting a mistake, disagreeing. Coined in this sense by Amy Edmondson. Note what it is not: it is not comfort, and it is not lowered standards.

B · Which term means…?

Three terms: buy-in · candour · to escalate. Say the right one, then reveal.

1. Which noun means honesty and directness, especially when the honest thing is uncomfortable to say?
candour (n; US candor) — adjective candid. "I'd welcome your candour." · "To be candid with you…" Stronger and warmer than frankness; it implies courage rather than bluntness.
2. Which verb means to pass a problem to someone more senior because it cannot be solved at your level?
to escalate (v) — noun an escalation; an escalation path (who you go to next). "I'm going to escalate this." Careful with register: in some cultures escalating reads as normal process, in others as going over someone's head. Ask early which one you are in.
3. Which noun means the agreement and genuine support of the people who have to make a plan work?
buy-in (n, uncountable) — to get / secure / build buy-in. "We have the budget but not the buy-in." The verb is separate: to buy into an idea. Note it means active support, not mere permission — which is exactly why it is hard to get.

C · Choose the meaning — a / b / c

1. Every one of them had worked there for twenty years, and none of them could see the thing the newcomer noticed in his first week. It was a collective blind spot. A blind spot is…
  (a) a deliberate secret   (b) something you consistently fail to notice, precisely because you are too close to it   (c) a disagreement between two departments
(b) — a blind spot (n), from driving. "That's a blind spot for me." The useful professional point: a new starter can see blind spots for about three months, and then stops being able to. Those first weeks are an asset with an expiry date.
2. He had not read the report, so he talked confidently around the subject and hoped nobody would ask him anything specific. He was winging it. To wing it means…
  (a) to prepare thoroughly in advance   (b) to delegate the task to someone else   (c) to improvise, without preparation, hoping to get away with it
(c) — to wing it (informal). Also to bluff, to blag it (British, informal), to busk it. All informal — use them about yourself, in conversation, and never in writing about a colleague.

D · Collocation & word building

1. Two phrases every job advertisement and every new starter uses. One means to become productive immediately: to hit the ground ___. The other means to reach the level of knowledge everyone else already has: to get up to ___. Complete both.
to hit the ground running and to get up to speed (also to bring someone up to speed). Worth noticing that the first is what employers say they want and the second is what actually happens — and that saying "I'm still getting up to speed on that" is a completely respectable sentence in week two.
2. The whole system was designed so that leaders could see the true state of every project. Complete the noun for that: v___. Then give the adjective, and say what verb goes in front of it in "we don't ___ visibility of the real numbers."
visibility (n) — adjective visible. The verb is have: "we don't have visibility of…"; also to give / provide visibility. In this story it becomes a compliment: "that's great visibility" means "thank you for letting us see the truth".

Now use them — out loud

Before we read:
  • Using psychological safety, to flag, candour and blind spot, predict what stops people telling a new boss the truth about a failing project.
  • Which of these would you say in a meeting, which in an email, and which only to a colleague you trust? Sort them out loud — and say which one you would never write down.

The story, in three parts

Read each part. After it, there's a quick check (answer from memory first), then one question to discuss.

Part 1 — The outsider

In September 2006, Ford hired a new chief executive. His name was Alan Mulally, he was fifty-nine, and he had spent his entire career at Boeing building aeroplanes. He had never worked in the car industry. He did not know the models. He did not know the suppliers, the dealer network, or the union agreements. Detroit noticed all of this immediately, and said so.

The company he was joining was in serious trouble. Ford would end that year with a loss of around twelve billion dollars. It had mortgaged almost everything it owned, including the blue oval logo itself, to raise cash. And it had a culture that people inside it described with a kind of grim pride: you did not bring problems to a meeting. You solved them quietly, or you presented around them, and you certainly did not say in front of your peers that your part of the business was failing.

Mulally's response to knowing nothing was not to pretend otherwise. He asked, constantly and without embarrassment, what things meant — including things a chief executive might be expected to know. He read. He sat in on meetings and listened. And then he introduced a weekly meeting of his own, on Thursday mornings, which every senior leader had to attend in person, with no delegates and no substitutes.

Quick check — from memory, then reveal:

1. What made Mulally's appointment surprising, and what state was Ford in?

2. How did he handle the fact that he didn't know the industry?

1. He came from Boeing with no experience of the car industry at all. Ford was heading for a loss of roughly twelve billion dollars that year and had borrowed against nearly all of its assets, including its own logo.

2. He asked openly and constantly what things meant, including basic things, rather than concealing the gaps — and he listened before changing anything.

Discuss:
  • He asked basic questions openly, from the most senior position in the company. Would you have that freedom in your role — and if not, who does?

Part 2 — A month of green

The Thursday meeting worked on a simple system. Every leader brought a summary of their part of the business, and every item was colour-coded. Green meant on plan. Yellow meant at risk. Red meant off plan, in trouble, not going to happen as promised.

The first week, the charts came back almost entirely green. So did the second. So did the third. Around the room sat the people running a business that was, at that moment, losing money at a rate of roughly a billion dollars a month — and according to their own charts, everything was proceeding as planned.

Mulally let it run, and then said the obvious thing out loud. The company was going to lose billions of dollars this year. Was there anything, anywhere, that was not going well? Nobody spoke. It was not that they did not know; every person in that room could have named three things. It was that the first person to put a red mark on a chart would be alone in a room full of green, in a company where being the visible problem had historically been the end of a career.

Quick check — from memory, then reveal:

1. What did the three colours mean, and what did the first weeks look like?

2. Why did nobody answer his question?

1. Green = on plan, yellow = at risk, red = off plan. For roughly the first month everything reported was green, while the company was losing about a billion dollars a month.

2. Not through ignorance — everyone could have named problems. The risk was personal: the first person to show red would stand alone, and in that culture being the visible problem had ended careers.

Discuss:
  • A room of experienced people, all with information, all silent. Where does that happen in your organisation — and what would it cost the first person to break it?

Part 3 — Red

Then one Thursday, Mark Fields, who ran the Americas, put up a red. The launch of a new vehicle was being held because of a technical problem with a tailgate, and it was not going to happen on schedule. He said so, in front of everyone, with his name on the chart.

There was a silence, and by several accounts the people in the room thought they were about to watch a colleague be dismantled. Instead Mulally started clapping. He said something close to: great visibility, Mark — now who can help him with this? And people began to answer. Someone had a supplier contact. Someone had seen the same fault elsewhere.

The following week, the charts came back in every colour. Once one person had shown a red and been thanked rather than punished, the reporting became roughly accurate — which meant that for the first time the leadership could see the actual condition of their own company, and could put effort where it was needed rather than where it was comfortable.

What followed is a matter of record. Ford restructured, sold off brands, and borrowed heavily and early — before the credit markets closed. When the financial crisis hit in 2008 and General Motors and Chrysler took government rescue money, Ford did not. It was the only one of the three that never took a bailout. There were many reasons for that, and mortgaging the logo in 2006 was probably the largest. But the leadership of that company have said repeatedly that none of it would have been possible while the charts were still green.

Quick check — from memory, then reveal:

1. What did Mulally do when the first red appeared, and what did the room expect?

2. What was the practical consequence of accurate reporting?

1. He applauded, called it good visibility and immediately asked who could help. The room had expected the person to be punished.

2. Within a week the charts showed real colours, so leadership could finally see the true state of the business and direct effort to where the problems actually were.

Discuss:
  • Mulally's reaction took about four seconds and changed what the whole room believed was safe. What is the equivalent four seconds for someone in your position?

Asking without losing face

In a new job you have to do three things constantly, and all three feel risky: ask for information you think you should already have, check that you have understood, and tell someone that something is not going to work. English has a very precise set of tools for doing all three without sounding either incompetent or aggressive.

1 · Indirect questions — the single most useful structure for a new starter.
Take a direct question and put a frame in front of it. The word order then goes back to normal statement order, and do/does/did disappears.
• "Where do I send the form?" → "Could you tell me where I send the form?"
• "Who approves this?" → "Do you know who approves this?"
• "Has the client seen it?" → "I was wondering whether the client has seen it." (use whether or if for yes/no questions)

The frames, roughly from neutral to most careful: Do you know… · Could you tell me… · I was wondering… · Would you happen to know… · Any idea… (informal, spoken only).
The classic error: "Could you tell me where is the meeting?" → "…where the meeting is."
2 · Checking that you've understood — the sentences that stop small misunderstandings becoming a fortnight of wasted work:
• "Just so I'm clear — you'd like the draft before Thursday, not the final version?"
• "Can I play that back to you? You want…" · "So if I've understood correctly…"
• "I'm not sure I follow — could you take me through that part again?"
Notice that the last one blames the sentence, not yourself. "I'm not sure I follow" is neutral; "Sorry, I'm being stupid" teaches people to doubt you.

3 · Admitting a gap without apologising for existing:
• "That's new to me — could you point me at the background?"
• "I'm still getting up to speed on that. Who would be the best person to ask?"
• "I don't know, but I'll find out and come back to you by Friday." ← the strongest sentence on this page.
4 · Flagging a problem — softening the delivery, never the fact.
• "I want to flag a risk with the timeline." · "There's something I'd like to put on your radar."
• "I don't think we're going to make Friday — here's what I'd suggest instead."
The reverse skill, and the point of the story: know when to stop softening. "There may possibly be a slight risk that the date could potentially slip" tells your manager nothing and protects only you. Hedge the tone; never hedge the red. And always arrive with the problem and a proposal — that single habit is what separates a new starter who is a burden from one who is an asset.

1. Make it indirect

Your first week somewhere new. Rewrite each blunt question using the frame in brackets. Write only the missing words.

1. Where do I find the staff handbook? → "Could you tell me the staff handbook?"

2. Who approves time off? → "Do you know time off?"

3. Has next week's schedule already been circulated? → "I was wondering already been circulated."

4. When does the team usually take lunch? → "Would you happen to know lunch?"

5. Why do we do it this way? → "I'd be interested to know this way."

1. where I find   2. who approves   3. whether next week's schedule has   4. when the team usually takes   5. why we do it

Check every answer for the two markers: no do/does/did, and statement word order. If you wrote "where do we store", the frame is fighting the question.

2. Soften the delivery, keep the message

Each sentence is true and badly delivered. Rewrite it so a manager can act on it. Write only the missing words.

1. "This deadline is impossible." → "I want to a risk with the deadline — and suggest an alternative."

2. "I have no idea what you're talking about." → "I'm not sure I — could you take me through that again?"

3. "Nobody told me about this system." → "That's me. Could you point me at the guidance?"

4. "You said Thursday. Or Friday. Which?" → "Just so I'm — you'd like it Thursday, not Friday?"

5. "I don't know." → "I don't know, but I'll and come back to you by Friday."

1. flag   2. follow   3. new to   4. clear   5. find out

Look at what survived. Every one of these still says the difficult thing. Softening is about how the other person can receive it — the moment it removes the message, you have written a green chart.

3. Week two — complete the conversation

You are three weeks into a new job. You have realised something you were given cannot happen on time, and you did not draw up the plan. Complete what you say to your manager, then read it aloud.

"Can I take two minutes? I want to something rather than leave it. I'm still up to speed on how the approvals work here, so tell me if I've read this wrong. As I understand it, the approval has to come through before we can confirm the booking — could you tell me that's right? If it is, we won't make the twelfth, because we're still waiting on approval. I'd two options: we move it to the nineteenth, or we confirm provisionally this week and accept we may lose the deposit. I don't which of those you'd prefer, and it's your call — but I didn't want the first you heard of it to be on the twelfth."

flag · getting · whether (or if) · suggest (or propose) · know

Read the last clause again. "I didn't want the first you heard of it to be on the twelfth" is the whole lesson in one sentence — and it is a sentence a manager remembers about a new starter for years.

Take these into the Speak tab: you'll be asking, checking and flagging under time pressure.

Going deeper

A note on the story: it is well documented and widely retold, and like every good corporate story it has been polished in the retelling. The dates and the outcome are a matter of record; the exact words in the room come from participants' later accounts.

What the story actually shows. The usual moral is "be honest, and good things happen." That is not quite what happened, and the difference matters enormously if you are the one starting a new job. Mark Fields did not simply decide to be brave. He was a senior executive with a strong record, running one of the largest parts of the business, reporting to a boss who had spent weeks explicitly inviting bad news. He had about as much protection as a person in that position can have — and by every account he still expected to be punished for it.

So the real lesson is about who moves first, and it points at the manager rather than the newcomer. What changed the room was not Fields's courage; it was the four seconds afterwards. If Mulally had said "so what are you doing about it, Mark?" in a cold voice, the charts would have stayed green for another year and the story would never have been told. Honesty is not a personal virtue that individuals supply on demand. It is a thing that becomes affordable, or doesn't, depending on what happened to the last person who tried it.

Which leads to the uncomfortable version, and the one worth taking seriously in your first month. "Just be honest and flag problems early" is excellent advice in a room where that is rewarded, and career-ending advice in a room where it isn't. Plenty of organisations applaud candour in the values statement and quietly mark down the person who supplies it. So the genuine skill for a new starter is not courage — it is reading which room you are in, quickly and accurately, before you need to know. Watch what happens to other people's bad news for a few weeks. Notice whether problems reach your manager early or late, and what happens when they do. Then calibrate. That is not cynicism; it is the same observation Mulally spent his own first weeks making.
Talk it through:
  • Whose achievement was this — the executive who showed the red, or the one who applauded? Argue it both ways, then say which you find more useful and why.
  • How would you work out, in your first month somewhere new, whether bad news is genuinely welcome? Name three specific things you would watch for.
  • A new starter can see an organisation's blind spots for about three months, then stops being able to. What should someone do with that window — and what are the risks of using it?
  • Is there a difference between a culture that says it wants candour and one that has it? How would you tell them apart from the inside — and what would you do if you found yourself in the first kind?

Speak

All of it out loud, against the clock.

Useful language: could you tell me where… · I was wondering whether… · just so I'm clear… · I'm not sure I follow… · that's new to me… · I'm still getting up to speed… · I want to flag… · I don't know, but I'll find out.
Time remaining: 4:00
Task A · Tell the story (4 minutes)

Tell this to someone who has never heard it. Structure it: the outsider who knew nothing → the state of the company → the Thursday meeting and the colours → a month of green → the first red → what happened in the four seconds afterwards → and what followed.

Finish with one sentence saying what you take from it. Use at least five key terms (steep learning curve, to flag, psychological safety, candour, escalate, buy-in, blind spot, wing it, up to speed, visibility).

Task B · Your first week, out loud (4 minutes)

You started a new role on Monday. Ask your partner eight questions you would genuinely need answered by Friday — and every one must be indirect or framed: could you tell me…, do you know…, I was wondering whether…

Your partner answers as a helpful but busy colleague. Then swap. Then do it again in ninety seconds, keeping only the four questions that mattered most — choosing which four is the exercise.

Task C · Saying red (4 minutes)

You are three weeks in. Something you were given is not going to work, and it is not your fault. Tell your manager, one minute, using the shape from the Grammar tab: flag it → say what you may have misunderstood → state the problem plainly → offer two options → hand back the decision.

Then your partner replays it two ways: once as a manager who welcomes it, once as one who doesn't. Discuss what you'd do differently in the second room.

Prefer not to use your own job? Take one of these instead:

  • A new teacher given a class set of books that arrive two weeks into term.
  • A new nurse on a ward where the handover notes are consistently incomplete.
  • A new project manager who finds the timeline was agreed before anyone asked the supplier.
  • A new analyst who spots that a monthly report has been double-counting one region.
  • A new engineer who realises the delivery date assumes testing nobody has scheduled.
  • A new shop manager whose stock figures have never matched the shelves.

To finish — the harder questions

  1. Is it braver to show the red, or to applaud it? Which one are you more likely to be asked to do in the next year?
  2. "I don't know, but I'll find out." Why is that so hard to say in week one — and what does it cost you not to say it?
  3. You join somewhere and quickly see a serious blind spot. You have no credit in the bank yet. What do you actually do — and when?
  4. Before you go — from memory: ask three indirect questions about a job you have actually done, using three different frames. Then say the hardest one again as a direct question, and say which version you would really use on Monday.