Trying to follow geopolitics right now feels like trying to drink from a firehose while someone’s shaking it.
The hose is on fire, and the water is also on fire.
You get a dozen breaking news alerts, a thousand hot takes, and zero actual clarity on what's happening, let alone what it means. The noise is the product.
Which is why Daniel’s prompt this week is so timely. He’s asking us to explore structured formats for synthesizing information in fast-moving situations. He specifically highlighted the SITREP format for its precision and high signal-to-noise ratio compared to mainstream news, and he wants to know if there are other reliable, well-defined formats that can help interpret complex events accurately.
We’re talking about building a mental filter. An antidote to the chaos. By the way, today’s script is being powered by deepseek-v3-2.
Oh, the friendly AI down the road sent over a draft? Hope it got the bit about my photogenic side.
I’m sure it’s captured your essence. It sounds military for a reason.
Because it is. That’s the origin. It’s a formalized method for cutting through fog, and I think the reason Daniel is asking about this now is that the mainstream news cycle has become almost purely additive. It adds speculation, it adds punditry, it adds emotional framing. It rarely subtracts or clarifies.
It’s designed to keep you watching, not to give you a definitive understanding you can act on. A SITREP has a very different goal: create shared situational awareness so a decision can be made. So where do we even start with this?
We start with the structure itself. Because the magic isn't in the acronym, it’s in the enforced discipline — the way it makes you answer specific, uncomfortable questions before you’re allowed to offer an opinion.
Okay, so before we even get to the letters, what’s that fundamental discipline? What’s the first, most important rule?
Separate observation from assessment. It’s the core of all intelligence tradecraft. You must state what you see, separately from what you think it means. The moment you blend them, you introduce bias and confuse the picture for everyone else. The format enforces that separation structurally.
That discipline shows up in the SITREP format, which forces you to cover four core areas: Situation, Mission, Execution, and Administration. The "Situation" part is the meat of it — what do we actually know? Not what we think, not what we feel. Known facts, verified enemy activity, friendly force status.
This is where the source qualification comes in, which Daniel specifically mentioned. It's not just "Reuters reports." It's "Reuters, citing two U.officials familiar with the matter, reports a troop movement near X." You grade the source. You note the time of the report. You separate the raw signal from your own analysis.
The format originated in military contexts during World War Two, as a way to get clear, standardized updates from the front lines up the chain of command. Its effectiveness is in its brutal simplicity. It answers, in order: What's happening? What are we trying to do about it? How are we doing it? And what do we need to keep doing it?
What makes it uniquely effective compared to, say, a beautifully written narrative analysis in a magazine?
It inverts the priority. Narrative analysis often starts with a thesis and finds facts to support it. A SITREP starts with the facts and only then allows for assessment. So when Corn asks about practical application—say, to Taiwan Strait tensions—we're already working from that grounded foundation. The structure minimizes noise by excluding unverified speculation and maximizes signal through observable events.
So break down that "Situation" component for me. What does it look like in practice when you're applying it to the Taiwan Strait tensions from a few months back? Not the military version, the analyst's version.
Right, applying the framework. So for the analyst, "Situation" becomes a forced inventory. First, you list all known, confirmed facts. In late February, that was: The Chinese Coast Guard had established a new, regular patrol pattern within Taiwan's twelve-mile contiguous zone. Satellite imagery from Planet Labs showed a twenty-percent increase in PLA Air Force sorties near the median line over the previous week. Taiwan's Defense Ministry had publicly confirmed these incursions.
Let me push on that for a second. “Satellite imagery from Planet Labs” – that’s a great example. But how do you, as an individual, grade that source? What makes it a good fact?
That’s a critical follow-up. Source grading has layers. First, the sensor: Commercial satellite imagery is generally considered highly reliable for visual, observable events. It’s a primary source. Second, the interpreter: Is it Planet Labs’ own analysis, or an open-source analyst like Damien Symon? You check their track record. Third, corroboration: Are other satellite companies, like Maxar, showing the same thing? A single-source fact is noted as such. A multi-sourced, sensor-verified fact goes to the top of your list. It’s about building a chain of custody for information.
No speculation about Xi Jinping's intentions. No "what this means for the U." Just the observable, reportable events.
The second part of "Situation" is the enemy activity assessment, which for an analyst becomes "adversary activity." Here you state what the other side says it's doing. So, Chinese Foreign Ministry statements asserting their right to patrol "sovereign waters." PLA Eastern Theater Command press releases about "combat readiness drills." You present their stated position without endorsing it.
Right, you’re treating their statements as facts about their position, not as truths about the world.
It’s a data point of their narrative. And then friendly status?
For an analyst, that's "our position" or "the defended position." So: The U.Seventh Fleet had the USS Ralph Johnson on a scheduled freedom of navigation transit through the Strait. Taiwan's President had given a speech reaffirming the status quo. Japan's Defense Ministry issued a statement of concern. These are all discrete, verifiable data points. The magic is in the assembly. By laying them out side-by-side, the actual picture emerges without you having to narrate it. The tension is in the data itself.
That's the signal maximization. You're not adding commentary, you're just arranging the verified pieces so they talk to each other. The noise minimization comes from what you leave out.
Which is everything else. No "experts fear," no "this could be a prelude to," no historical analogies about Munich or Kosovo. Those might come later, in an assessment annex, but they are structurally barred from the core SITREP. It creates a clean baseline that everyone, regardless of political viewpoint, can agree on as the factual starting point.
That's where it fundamentally outperforms traditional news formats. A cable news segment has to fill time, so it starts with the one fact and immediately layers on three pundits, historical context, market implications, and partisan finger-pointing. The signal gets buried in the first thirty seconds. A SITREP forces delay of that gratification.
It's a discipline of patience. The "Mission" component then asks: What is our analytical goal? Are we trying to assess likelihood of invasion? Predict economic fallout? Defining that mission upfront prevents scope creep. You're not trying to solve every question at once.
How do you avoid picking a mission that’s already biased? Like, if my mission is “prove that China is preparing for an invasion,” I’ve already poisoned the well.
The mission should be a question, not a conclusion. “Assess indicators of preparation for a blockade versus an amphibious invasion” is a valid mission. “Prove invasion is imminent” is not. The format helps, but it’s not immune to a bad actor. The discipline is also for the team—someone should be able to challenge a poorly framed mission.
"Execution" is your plan for answering it.
What intelligence indicators are we watching? Diplomatic cable traffic? And "Administration" is logistics: What sources do we need access to? Who needs to be on the distribution list for this report? It sounds bureaucratic, but that's the point. It replaces panic with procedure.
What's the trade-off? The format can't be perfect.
The main trade-off is speed and adaptability. A proper SITREP takes time to compile and verify. In a truly breaking, minutes-matter scenario, the full format can be too slow. That's why you have formats like the "Flash SITREP" or "Spot Report" for initial contact. But even those enforce the core discipline: source, time, location, observed activity.
The other trade-off, it seems to me, is narrative power. A purely factual, dispassionate list can fail to convey urgency or meaning to a decision-maker who's not immersed in the details. The "why we should care" can get lost.
That's a fair critique. Which is why in military practice, the SITREP is often followed by an assessment or recommendation. But the assessment is built on the SITREP, not mixed into it. The structure ensures the recommendation is grounded in shared reality, not just gut feeling. For an analyst reading the news, it's the same. You build your SITREP first, then you allow yourself to form an opinion. It reverses the default human, and definitely the default media, impulse.
The Taiwan Strait example. If my mission was to assess the risk of a kinetic incident within forty-eight hours, my execution would focus on specific, real-time indicators.
You'd be monitoring for specific things: a shift in PLA rocket force readiness states, the scrambling of Taiwanese air defense batteries to actual intercept positions, not just shadowing, a halt to commercial air traffic over the Strait. The SITREP format forces you to be that specific. You're not just "watching nervously." You have a checklist derived from your mission. It turns anxiety into a search protocol.
I can see why Daniel finds this appealing. It's a tool for regaining a sense of agency, or at least comprehension, when the world feels like it's spinning into chaos. You're not just consuming the chaos; you're processing it through a filter you control.
That's precisely it - an analytical coping mechanism for the information age. And the beautiful part is how the format itself becomes the antidote to that additive noise we've been discussing.
Right, so SITREP gives you that stable, verified baseline. Which makes me wonder - since Daniel’s prompt also asked about other well-defined formats, what else is in the toolkit besides this one?
The most famous companion is probably the OODA Loop. Observe, Orient, Decide, Act. It was developed by Colonel John Boyd in the nineteen fifties, based on his experience as a fighter pilot. It’s less about reporting a static situation and more about the cycle of decision-making in a dynamic, competitive environment.
It’s for when you’re in the fight, not just observing it.
The goal is to get inside your opponent’s decision cycle, to act and change the situation faster than they can comprehend it. It’s a framework for creating chaos for the other side, while managing it for yourself. The Ukraine conflict last year offered a textbook case study of this in the information domain.
Take the Ukrainian drone operations against Russian oil refineries in early twenty twenty-five. The Observe phase was constant ISR — intelligence, surveillance, reconnaissance — using commercial satellites, local spotters, and signals intercepts to identify vulnerabilities. The Orient phase was the crucial twist: they understood that Russian air defense was layered but predictable, and that the psychological impact of striking deep, symbolic targets outweighed the pure military damage.
They oriented on the cognitive effect, not just the physical blast.
Then Decide: they chose a wave of low-cost, modified maritime drones to strike at night, from unexpected vectors. Act: they executed. But then they immediately cycled back to Observe — monitoring Russian state media reaction, Western energy market fluctuations, and internal Russian security shifts to gauge the effect and plan the next strike. They were running dozens of these micro-OODA loops per week, while the Russian response was stuck in a slow, bureaucratic decision cycle. They were inside it.
That’s a great case study. But let’s get a bit geeky for a second—what’s a common misunderstanding about the OODA loop? People throw the term around a lot.
The biggest mistake is thinking it’s just “be faster.” The heart of it is the Orient phase. Boyd called it the “schwerpunkt,” the schwerpunkt. It’s your mental model of the world—your culture, genetics, previous experience, new information. It’s where you make sense of what you Observe. If your orientation is wrong—if you’re using an outdated map—you’ll decide and act quickly, but into a wall. The Ukraine example works because their orientation included a sophisticated understanding of Russian bureaucratic politics and Western market psychology, not just drone specs.
Compared to SITREP, OODA is more… competitive and iterative. SITREP is about establishing a shared picture. OODA is about shattering the other side’s picture.
SITREP supports decision-making; OODA is the decision-making engine. One is a snapshot, the other is a continuous feedback loop. For an analyst, the choice comes down to your goal. Are you trying to understand a complex situation with clarity? Are you trying to predict or outmaneuver an adaptive adversary in real time? Think in OODA loops.
Then there’s the After Action Review, the AAR. That’s the post-mortem format.
Which is arguably just as important. The AAR is a brutally structured debrief. What was supposed to happen? What actually happened? Why was there a difference? What do we sustain, and what do we improve? It forces learning. The key is that it’s blameless and focused on process, not people. In the commercial world, tech companies do post-mortems after outages. In the intelligence world, they’re done after an operation or a failed prediction.
Can you give a quick, non-military example of an AAR in action? Something listeners might relate to.
Imagine a small company launches a new product feature that flops. A bad meeting would be the manager asking “Whose fault is this?” An AAR would structure it: “Our plan was to attract small businesses with this simplified interface. The result was a 5% adoption rate and negative feedback about missing functionality. The difference was we tested with power users, not our actual target audience. We sustain the rapid development cycle. We improve by changing our beta-test recruitment protocol.” It’s systematic, not personal.
We have SITREP for the present picture, OODA for the ongoing fight, and AAR for the historical lesson. That’s a pretty complete lifecycle.
And the through-line is structured questioning. Each format is just a set of mandatory questions that prevent you from skipping to a lazy conclusion. Mainstream news coverage, by contrast, has no mandatory questions. Its only mandatory element is engagement, which leads to the additive chaos we started with.
Let’s make that comparison concrete. A major network covers the same refinery strikes. What’s their format?
They open with dramatic footage, real or stock. Then a anchor voiceover: “Ukraine strikes deep into Russia, escalating the conflict.” Then they cut to a panel: a former general, a energy analyst, a diplomatic correspondent. The general speculates on Putin’s response. The energy analyst talks about global oil prices. The diplomat wonders about NATO unity. Twenty minutes later, you have a dozen opinions, but you still don’t know the basic facts of the attack vector, the drone model used, the precise damage assessment, or the Russian military’s specific failure mode. You have noise, not signal.
Because they never forced the “Observe” part. They jumped straight to “Orient” and “Decide” on what it all means, without establishing what “it” is.
They’re running a broken OODA loop on your behalf, and orienting you based on narrative conventions, not observable facts. A SITREP-style approach from an analyst would first compile the verified facts: time, coordinates, number of drones, type of drones, claimed responsibility, satellite imagery of damage. Then you could layer on analysis of implications.
The practical implication for an analyst or a policymaker is to consciously choose your format based on the problem. And to recognize that the default media format is designed to bypass all of them.
That’s the insight. If you’re on a team monitoring a crisis, you might start your day with a shared SITREP to align. As events move, you shift to thinking in OODA loops about your adversary’s and your own next moves. After a key development, you pause for a quick, informal AAR: “Our prediction was X, reality was Y, why?” It turns reactive chaos into a structured process. For a lone analyst, it’s a mental check against being swept away by the narrative tide. You literally have a list of questions to answer before you’re allowed to have a take.
It’s the discipline of the checklist, applied to thinking. Seems simple, almost trivial. But that’s why it’s so powerful when everything else is working against it. And that’s exactly what makes it practical for anyone—not just military intelligence cells.
The million-dollar question for our listeners is, how do you actually use this? You're a person trying to understand the world without losing your mind. What's the first step?
Pick one ongoing event you're following. The next time you see a headline, stop. Open a blank note. Force yourself to answer the SITREP questions in order. Situation: What are the confirmed facts? Go find the primary source—a government statement, a Reuters ticker, verified geolocated footage. Write only those. Mission: What are you trying to figure out? Is it "Will this trigger a wider war?" or "How will this affect energy prices?Execution: What will you watch to answer that? A specific official's travel schedule? A commodity futures index? Administration: Where will you get that data? Bookmark the direct source pages.
The key is the forced pause. You're building a tiny intelligence product for yourself. It takes five minutes, but it breaks the scroll-and-react cycle.
And you'll quickly see which "news" reports are just repackaged speculation. For the OODA Loop, the switch is about dynamism. If you're following a fast-moving negotiation or a market disruption, ask yourself: What would Observe look like here? What data would indicate the other side's next move? How can I Orient faster—what mental model or historical pattern applies? You're not just predicting; you're simulating a decision loop. This is especially useful in business or competitive hobbies.
Like chess, or even fantasy football. You’re observing your opponent’s past moves, orienting based on their strategy, deciding your counter, and acting. It’s the same feedback loop.
It demystifies it. It’s not magic; it’s just disciplined attention.
As for resources, the gold standard is still military field manuals, which are publicly available. Army Field Manual six dash zero covers commander and staff organization and includes SITREP templates. For OODA, Colonel Boyd's original briefings, "Patterns of Conflict," are dense but transformative. For a modern, applied take, the War on the Rocks podcast and articles frequently dissect current events using these exact frameworks.
For a purely civilian, analytical approach, I'd recommend the website "The Analyst's Cookbook." It's run by former intelligence officers who break down open-source investigation techniques. They have excellent primers on source grading and building your own SITREP-like trackers. Which actually leads me to Daniel's next question—can a military-derived format like SITREP work outside of geopolitics?
In a corporate merger, or a tech rollout—does that same structured discipline hold value? The adaptability question feels key here.
I think it can, but you have to translate the components. "Situation" becomes the verified market data and internal metrics. "Mission" is the board's strategic objective. "Execution" is the playbook for the deal team. "Administration" is resource allocation. The rigor of separating confirmed facts from leadership's hopeful projections is universally valuable. The noise isn't just cable news pundits; it's corporate PowerPoint decks full of aspirational slides.
I’ve seen a version of this in product management, actually. They have a “State of the Product” memo that’s very SITREP-like: Here are the key metrics (Situation), here’s the quarterly goal (Mission), here’s the roadmap to get there (Execution), here’s the team and budget (Admin). It aligns everyone on reality before the brainstorming begins.
The format travels well because the enemy—confusion, bias, assumption—is the same everywhere.
The future implication has to be AI. Not to replace the analyst, but to turbocharge the format. An AI tool could instantly scrape and grade every source mentioning an event, tag them as fact, claim, or analysis, and auto-populate the first draft of a "Situation" section, with citations. It turns the analyst into a verifier and a commander, not a drudge.
That's the next frontier. An AI-augmented OODA loop, where the "Observe" phase is continuous, global sensor feed, and "Orient" is aided by predictive models of adversary behavior. The human decides and acts. The structure prevents the AI from just being a noise generator. It has to answer the checklist.
Here’s a fun, slightly terrifying tangent: What happens when adversaries use AI-augmented OODA loops against the information space? Could that lead to a new kind of hyper-chaos?
It absolutely could. We’re already seeing primitive versions with deepfakes and bot networks. A sophisticated AI could run millions of micro-OODA loops, testing disinformation narratives, observing social media reactions, orienting based on engagement, and deciding on the next variant—all in real-time. The defense against that isn’t a faster AI; it’s a more grounded human using a slower, more disciplined format like SITREP to establish an unshakeable baseline of truth.
That’s a powerful note to end on. The antidote to algorithmic chaos is human-imposed structure. Which brings us to the end of another one. Thanks, as always, to our producer Hilbert Flumingtop for keeping the gears turning. And thanks to Modal — their serverless GPUs power the pipeline that lets Daniel send us these weird prompts in the first place.
This has been My Weird Prompts. If you found this useful, leave us a review wherever you listen. It helps more people find the show.
Until next time.
