Lesson 6 of 6 · Communicating decisions under pressure
Communicate a decision others can act on
8 minute lesson · 3 checks along the way
Your goal for this lessonBuild a concise operational report that distinguishes evidence, uncertainty and recommended action.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
A clear report carries the reasoning
Time pressure increases the value of concise, precise language. A useful operational report states the observed condition, its time and confidence, the consequence for the next activity and the recommended action. Technical detail matters when it changes a decision; unexplained acronyms and vague reassurance can obscure that connection.
Compare “everything looks strange” with “the latest received temperature is above the expected range for this mode; the packet is three minutes old; the next observation would add heat.” The second report identifies evidence and limitations. It gives other specialists a way to contribute relevant information.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Make the decision and its conditions explicit
An authorization should identify the action and any conditions attached to it. Acknowledgement helps establish that the instruction was understood, but execution and outcome still need their own evidence. This distinction is especially important when several teams, shifts or organizations share responsibilities.
In a fictional rehearsal, a controller recommends delaying an observation until a thermal trend stabilizes. The decision record should state what “stabilizes” means in that exercise, who assesses it and when the team will review the state again. Otherwise different people may apply different unstated thresholds to the same instruction.
Alan Shepard, left, and Walter C. Williams monitor Mercury-Atlas 9 from Mercury Control Center on May 15–16, 1963. Headsets and documents connect the visible participants with a wider operation. The photograph does not reveal the exact words or confidence of any particular report.
Look closely
What would let a historian reconstruct a specific operational exchange?
See what to notice
A timestamped voice record, log or decision document can establish the exchange’s content and context. Visible headsets alone cannot supply the spoken message.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Leave a record that can be reconstructed
Logs and handovers support later reconstruction of what the team knew when it acted. Include uncertainty and dissent that affected the decision rather than editing the record to resemble hindsight. A later diagnosis can be more confident than the original real-time assessment without making that earlier uncertainty a mistake.
Practice a short report using a fictional missed contact: “The scheduled pass produced no valid packets. The last confirmed state is from the previous pass. Ground and spacecraft explanations remain open. The team is checking the contact chain before recommending recovery commands.” It gives a shared starting point while avoiding an unsupported claim about what has failed.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.