PEIC Level 5 (C2) study materials
PEIC Level 5 (C2) study resources

What the Manager Didn't Say

PEIC Level 5 (C2) · Put your knowledge to work in context.

All case studies

What the Manager Didn't Say

You are listening to a six-minute recording of a project team meeting. The manager says: 'I'm not saying the deadline is impossible, but I'd be surprised if we got sign-off by Friday.' Later she says: 'If it were down to me, I'd probably pause the launch.' A junior analyst asks, 'So should we pause?' The manager replies: 'Let's not put words in my mouth - I'm just thinking aloud.' Near the end she says, 'We'll revisit after the audit,' and 'I'd like options by Thursday.' The team must produce minutes and a short action list. Two team members leave the meeting with different impressions: one believes the launch is paused; the other believes only the deadline is at risk. You are asked to interpret the manager's meaning, decide what belongs in the minutes, and prepare one question for the manager before the next meeting.

1. What does the manager most likely mean by 'I'd be surprised if we got sign-off by Friday'? Identify the implicature and one reason a literal reading would mislead.

Read the worked answer

The implicature is that the manager expects sign-off to be late or unlikely, but she is not willing to state that as a decision. 'I'd be surprised if...' functions as a hedged prediction, not a factual prediction about her surprise. A literal reading ('she has no information about Friday') would mislead the analyst into treating the deadline as safe. The second sentence, 'If it were down to me, I'd probably pause the launch,' is a conditional recommendation: it signals a preference for pausing while denying that she has made the call. 'Let's not put words in my mouth' reinforces that she is not authorising a pause. The hearer should infer: the deadline is at serious risk; a pause is under consideration; no decision has been made; the manager wants options, not a decision from the team.

2. Write two bullet points for the minutes: one recording a decision, one recording an action. If something is not a decision, say so explicitly.

Read the worked answer

Minutes should record only what is attributable and actionable.

  • Decision: No decision was taken to pause the launch. The launch timing remains under review pending the audit. Record the manager's words as 'launch timing to be revisited after the audit', not 'launch paused'.
  • Action: Options for the launch timetable to be submitted to the manager by Thursday. Owner: project team. Record 'options' rather than 'recommendation', because that is the word she used.

I would not minute 'the deadline is impossible' or 'the manager wants to pause', because both overstate what was said. If the chair needs certainty, the minutes should flag the ambiguity explicitly.

3. Draft one clarifying question to ask the manager before the next meeting. Explain why your question is likely to get a useful answer.

Read the worked answer

Question: 'When you said you'd be surprised if we got sign-off by Friday, do you want us to treat Friday as a fixed constraint, or should the options include a later date?'

This is likely to get a useful answer because it offers two concrete alternatives rather than asking 'What did you mean?'. It tests the operational consequence of her hedge. A closed question with two options is easier to answer than an open request to explain intent, and it gives her a way to clarify without admitting that she was ambiguous. I would ask it in private if possible, because a public clarification can feel like a challenge to her authority.