Work / decisions and responsibility

LISTENING • C1 ADVANCED • MAIN ARGUMENT

Who Owns the Decision?

Listen to Nora, the project lead, Dev, the technical lead, and Leila, the operations lead, reviewing the launch of a reserve-and-collect service. Choose A, B or C.

Overall meaningDecision-makingShared responsibility

1. What problem is at the centre of the discussion?

2. How does the conversation develop?

3. Which course of action do they agree on?

Work / decisions and responsibility

LISTENING • C1 ADVANCED • FILL THE GAPS

Who Owns the Decision?

Listen again. Type ONE TO THREE WORDS from the recording. Questions follow the order of the conversation.

Exact wordsOperational detailsListening for information

Work / decisions and responsibility

LISTENING • C1 ADVANCED • SPEAKER POSITIONS

Who Owns the Decision?

Choose the speaker who makes each point: A — Nora, B — Dev, or C — Leila. You may use each name more than once. Match the point actually made, rather than guessing from a person’s job title.

Speaker positionsPartial agreementAccountability

Work / decisions and responsibility

LISTENING • C1 ADVANCED • TRANSCRIPT

Who Owns the Decision?

C1 Advanced • 3 speakers • Transcription

Workplace decisionsAccountabilityConditional approval

Nora

Dev, Leila, thanks for making time. The reserve-and-collect launch hasn't gone as we'd hoped. Customers can send requests, but some have arrived at shops expecting books that nobody has located yet. Before we discuss fixes, I want to understand what each of us thought we were agreeing to.

Leila

I'd start by separating the service working on a screen from the shops being able to deliver it. People are describing this as a launch problem, which is fair enough, but that phrase is making several different decisions sound like one.

Dev

My checks used test accounts. Requests reached the shops, and the responses came back. When I said ready, I meant that route had been tested. I didn't mean we'd established how every shop would check availability during a busy shift. I should have made that distinction clearer.

Nora

I read your message alongside Leila's offer to support a trial. I put the two together and kept the launch date. Looking back, that was my interpretation, not a decision either of you had actually put in writing.

Leila

My offer was for two shops, with somebody available to watch what happened. We added the rest of the branches before that trial had taken place. I was preparing to support a limited exercise; I wasn't authorising the same arrangement everywhere.

Dev

There's also the confirmation email. It says the request has been accepted, which the system can establish. Whether somebody has actually found the book is another matter. We need to separate those messages. But changing the wording won't create the time for staff to check the shelves.

Leila

Exactly. The requests themselves aren't difficult. It's interrupting a customer at the counter, checking the shelf, and then finding that the stock record doesn't match what's there. That work had to fit into someone's shift, and it was being treated as though it would happen in the gaps.

Nora

I knew there would be extra checking. I don't think I understood that it would interrupt the existing work to that extent. Did your earlier email make that clear, or did we all leave too much implied?

Leila

I attached the staff rota and said we couldn't add that work on Saturday with the people listed. I didn't ask you to cancel the whole launch. But I wasn't in the later discussion where the date was confirmed, so I couldn't tell whether the warning had been considered or simply filed.

Dev

Then we shouldn't solve this by asking technical checks to cover everything. I can test the messages and trace a request. I can't certify the staffing from that. If we make ready mean whatever the next person needs it to mean, the word stops helping anyone make a decision.

Nora

I could have paused the launch. Instead, I treated your warning as background information and assumed someone would find a way to manage it. That's a decision I made, even though I didn't announce it as one. I don't want us to lose that point in a discussion about clearer emails.

Leila

And I don't want the answer to be a committee approving every small change. The warning existed. What was missing was a place for it in the launch decision, with someone able to say whether it had changed the plan. More people copied into a message wouldn't necessarily give us that.

Dev

Could we use a decision log? Nothing elaborate. Name the person deciding, say what evidence they've considered, and keep the unresolved concerns beside the decision. At the moment, somebody reading the thread later would struggle to distinguish a technical update from permission to proceed.

Nora

Possibly. Though another document could become a box we tick after the important conversation. How would that help us when we still disagree?

Dev

It wouldn't make disagreement disappear. That's rather the point. The record could say that a concern remained when the decision was taken. Signing that the discussion has been recorded shouldn't mean signing that you endorse the outcome. Otherwise we're just manufacturing agreement in a different format.

Leila

For now, closing everything would give customers with requests in progress another problem. I'd keep handling those and stop adding branches. That contains the extra work while we find out what's actually involved. It isn't a vote to continue with the whole plan unchanged.

Nora

Agreed. No additional branches this week. I'll tell the branch managers that existing requests will still be handled. We can review the messages and the actual workload before I decide whether to extend it. A quieter few days won't automatically trigger the next stage.

Dev

I'll examine what's entered the support queue. A lower number there wouldn't prove the problem had gone away; people might simply have stopped asking. I want to look at the cases and where they stalled, alongside the requests that appeared to go through normally.

Leila

I'll ask the shops about the time spent between receiving a request and sending a useful reply. Some of those steps aren't visible in your records. That should give us something more concrete than a general statement that staff are finding it difficult.

Nora

I keep the final launch decision, then, but that means explaining the trade-off I'm making. I can't announce that the team decided if what happened was that I heard different views and chose to proceed. The record needs to show that difference, including concerns I haven't resolved.

Leila

And operations needs to be in the sign-off meeting, not invited afterwards to make an announced plan workable. I can state what we can support and on what conditions. If the plan goes beyond that, it shouldn't appear in the record as an operational approval from me.

Dev

That works for me. I'll be specific about the technical checks and what they leave unanswered. We don't need a single declaration that everything is ready. We need enough detail for the person making the decision to know what they're taking on.

Nora

I'll arrange that meeting once we've gathered the information, rather than putting a launch date in the invitation. And I'll write up today's decision about existing requests and expansion. That gives the shops something definite to work from while we investigate.

Leila

Good. I'll send the managers a short note about what we need from them. They shouldn't have to guess whether a request for information is another instruction to increase the service. We've given them enough of that sort of guessing already.