Situation Awareness

Knowing every fact that happened this week and knowing where things stand are two different mental operations. A complete list can nail the first one and still fail the second.

Title card reading 'Situation Awareness' in green type on a large cream circle, framed by abstract organic shapes in terracotta, gold, dusty blue, sage, and cream on a textured cream background

A weekly brief lands in the inbox: twelve tickets shipped, three deals closed, one customer call flagged a bug, a competitor quietly raised prices. Every line is accurate. Nobody misreported anything. The reader finishes it and still can't say whether the week was good or bad, or what any of it means for the week coming next. A complete list of what happened and an understanding of where things stand were never the same document, and no amount of making the list more complete closes that gap.

Listing what happened is not the same operation as knowing what it means

These are two different mental jobs, not two versions of the same job at different levels of effort. Noticing that twelve tickets shipped is one operation: pulling individual facts out of a stream of activity. Understanding what those twelve tickets add up to, whether they cleared the actual blocker customers were hitting, whether they shipped faster or slower than the team's real capacity, whether "shipped" this week quietly means "reopened" next week, is a second, separate operation performed on top of the first. A list can get the first job perfectly right and still leave the second one completely undone, because nothing about correctly noticing twelve facts forces anyone to correctly combine them.

There's a third job stacked on top of both, and it's the one a reader actually wants answered: given what happened and what it adds up to, what does that imply about what's coming. A brief can nail the first two jobs, an accurate list, a correct read on what it means right now, and still say nothing useful about next week, because knowing where things stand today doesn't automatically tell you where they're headed. Each of these three jobs can fail on its own, even when the one before it went perfectly.

Where this gets its name

Human factors research has a name for exactly this three-part structure, developed to explain why a pilot or an air traffic controller with all the right instruments in front of them can still misjudge a fast-moving situation. In 1995, Mica Endsley published "Toward a Theory of Situation Awareness in Dynamic Systems" (Human Factors), defining situation awareness as three distinct levels that build on each other but don't guarantee each other. Level one is perception: noticing the individual elements actually present, the instrument readings, the radio calls, the blips on a screen. Level two is comprehension: integrating those separate elements into what they mean together right now, not just that an altitude reading changed, but that the aircraft is descending toward terrain. Level three is projection: extrapolating from that understanding to what's likely to happen next, if nothing changes, in enough time to actually act on it. Endsley's point wasn't that any one level is hard by itself. It was that an operator can be flawless at level one, perceiving every instrument correctly, and still fail entirely at level two or three, and that failure looks, from the outside, exactly like having all the right information and still getting it wrong.

The honest limit: this was built for real-time operators, not weekly documents

This is a borrowed framework, not a literal transfer, and it's worth being precise about where the borrowing stops. Endsley was modeling operators monitoring a system continuously in real time, where a missed projection can mean a plane hits terrain in the next ninety seconds. A weekly brief is asynchronous and much lower stakes in the moment, nobody's read of Tuesday's summary determines what happens by Wednesday afternoon the way a pilot's situation awareness determines what happens in the next minute. What transfers isn't the urgency. It's the three-level structure itself: the same clean separation between noticing, understanding, and projecting holds up as a diagnostic for a written brief as much as for a cockpit, and the same failure mode applies, a document that's flawless at level one and silent at levels two and three will read as informative while telling the reader almost nothing useful.

The other honest limit is that level three doesn't get easier just because levels one and two went well. Projection is the most cognitively demanding of the three levels, since it depends on the first two already being correct and then extrapolating into a future that hasn't happened yet. That's not the same as saying it's the level most likely to fail in practice. David Jones and Mica Endsley's follow-up study, "Sources of Situation Awareness Errors in Aviation" (Aviation, Space, and Environmental Medicine, 67(6), 1996, pp. 507-512), examined real aviation error reports and found the opposite: the large majority of documented situation-awareness failures happened at level one, simply perceiving something correctly, with level-three failures the rarest of the three. What stays true regardless is narrower: a correct projection is still a claim about an uncertain future, and getting comprehension right earns the right to attempt one. It doesn't make that projection certain.

Where this fits at Brief

Read against that three-level structure, most of what a product organization tracks day to day sits at level one: what shipped, what closed, what a customer said, what a competitor changed. The structural gap the theory describes is real regardless of any specific implementation: a system that only accumulates level-one facts, however completely, hasn't done the level-two or level-three work a reader actually needs from something calling itself a brief. Weekly Brief Agent's own documented description, synthesizing the whole picture into the one read that tells a team where things actually stand, is stated as a level-two promise, understanding what the picture adds up to right now, not a level-one one. This post can't speak to how that promise gets kept today, or whether the read it produces also attempts level three. What it can say is that even the documented promise is the harder one, and no amount of level-one completeness fulfills it on its own.

Read your team's last weekly update again. Does it tell you what happened, or does it tell you where things actually stand, and are you sure those are the same sentence?

Frequently asked questions

What is situation awareness? A three-level model of understanding a changing situation: perceiving the individual facts present, comprehending what those facts add up to right now, and projecting what they imply about what happens next. The levels build on each other but don't guarantee each other, an accurate perception of every fact doesn't automatically produce a correct comprehension or projection.

Where does the model come from? Mica Endsley's 1995 paper "Toward a Theory of Situation Awareness in Dynamic Systems," developed to explain how skilled human operators, pilots and air traffic controllers, correctly or incorrectly track fast-moving situations with all the right instruments in front of them.

Why can a report be factually complete and still not useful? Because completeness is a level-one property, every relevant fact got noticed and included, while usefulness depends on levels two and three, whether the facts were correctly combined into what they mean and correctly extrapolated into what comes next. A report can hit level one perfectly and still leave the reader to do levels two and three themselves.

Does understanding what's happening now guarantee a correct read on what happens next? No. Building a correct projection takes more than getting the first two levels right, it also means reaching into a future that hasn't happened yet, and no amount of accurate comprehension removes the real uncertainty in that reach. That demanding shape doesn't translate to "most error-prone" in practice either, aviation error data actually shows the opposite pattern, failures cluster earliest, at simply noticing something correctly. A well-earned projection has still done the hard part. It hasn't done the impossible part of making an uncertain future certain.

GET TLDR FROM:
← Back to Blog