The Translation That Changed the Meaning
Your team receives a verbal report through a trusted community contact who speaks limited English. The contact says a group is 'planning something at the site next week, maybe Thursday, they have keys.' You relay this to the operations manager, who acts on it by changing the site's lock schedule and briefing staff that a break-in is expected Thursday. On Thursday nothing happens. On Friday the operations manager confronts you: the intelligence was wrong, staff were alarmed for nothing, and the lock change cost overtime. The contact, when re-interviewed, says they meant the group had keys to a storage unit, not the site, and 'next week' meant the week after.
1. Where did the process fail, and how do you handle the operations manager's complaint?
Read the worked answer
The failure is not that the intelligence was 'wrong.' It is that an ambiguous verbal report was converted into a specific, actionable claim without a validation step.
Failure points:
- No clarification loop. 'The site,' 'keys,' and 'next week' were all ambiguous. A single follow-up question would have caught the storage-unit meaning.
- No confidence or caveat in the relay. The operations manager received a claim, not an assessment. They had no way to know it was low-confidence and unverified.
- Action outran assessment. Lock changes and staff briefings are high-visibility responses to low-confidence reporting.
- No feedback loop. Nobody checked back with the contact before Thursday.
Handling the complaint:
- Own the process failure honestly. Do not blame the contact or the language barrier.
- Explain the distinction: the report was not false, it was imprecise, and the response was disproportionate to its confidence level.
- Acknowledge the real cost (overtime, staff anxiety) without over-apologising into defensiveness.
- Propose the fix: a validation step before any operational action, and confidence labels on all relays.
Model answer: accept the process failure, explain the distinction between imprecise and false, and fix the relay process.
2. How should the original report have been relayed to the operations manager?
Read the worked answer
It should have been relayed as an assessment with explicit uncertainty, not as a fact.
A better relay:
- Source: community contact, limited English, previously reliable but this is a single uncorroborated report.
- Content as stated: a group is 'planning something' at a location the contact described as 'the site,' possibly Thursday, and they 'have keys.'
- Confidence: low. Key terms are ambiguous - location, timing, and the meaning of 'keys' are all unclear.
- What we are doing: re-interviewing the contact with a translator to pin down location and timing.
- Recommended action now: no visible operational change. Increase passive monitoring and confirm the lock and key inventory. Hold the lock-schedule change until the report is clarified.
Principles:
- Distinguish what the source said from what we assess it means.
- Attach confidence to every relay.
- Match response cost to confidence level - cheap passive measures now, expensive visible measures only on corroboration.
- Close the loop with the source before acting.
Model answer: relay with source, content, confidence, actions in train, and a proportionate recommendation - not a bare claim.