The Bearing

The weekly meeting is the most important recurring event in any operation and it is almost universally run badly. Status updates from each function, discussion of what happened last week, some conversation about what is happening this week, maybe a decision or two, an hour gone. Most participants leave unsure whether the meeting was worth their time.

The problem is structural, not cultural. The meeting is trying to do four things at once — status reporting, retrospective, forward planning, and decision-making — and doing none of them well. Status updates consume the first thirty minutes, which means the decisions that actually require human judgment get crammed into whatever time is left.

The Bearing is designed from the ground up to eliminate this. One question drives everything: what requires human judgment this week that is not already handled? Status is not on the agenda because status is handled by the Pulse. What happened last week is not on the agenda because it is already in the record. The Bearing is forward-pointing, specifically and deliberately about decisions that cannot be made by anyone except the humans in that room.

The Bearing has three sections, run in the same order every week.

Section one: Relays since the last Bearing. A Post escalated something to a human. What is the resolution? This is the primary signal from the agent layer to the human layer, and the Bearing is where that signal gets processed. If a Post is Relaying repeatedly on the same trigger, the question is whether there is a Groundwork update needed or whether the trigger is working correctly and the resolution is the point.

Section two: Obstructions. What is in the way of the Waypoints this week? Specific things that have been Flagged and need a Clearing decision. Who is Clearing this and by when? Not a detailed analysis. A decision about who owns the resolution and what the timeline is.

Section three: Waypoint status check. Binary: on track or off track. If off track, why and what changes. If on track, acknowledge and move on.

Thirty minutes for a well-run operation. Forty-five if there are significant Relays. If the Bearing is running ninety minutes, the meeting is doing the wrong job.

The L10 starts with a segue and a scorecard review. The Bearing starts with Relays — direct signal from the agent layer about what required human judgment since last week. The L10 treats the scorecard as the primary health signal. The Bearing treats Relay volume and pattern as the primary health signal, because in an AI-native operation the agents are producing the majority of operational output and their escalation patterns are the most informative diagnostic.

The L10 has IDS as its core problem-solving mechanism. The Bearing has Obstructions and Clearing. Obstructions are pre-Flagged before the meeting — they arrive already identified and ready for a Clearing decision. IDS often involves identifying the issue during the meeting itself, which consumes time that could be spent on resolution.

The Bearing is not anti-EOS. Teams running EOS can adopt the Bearing format by adding Relays as the first agenda item and replacing the scorecard review with a Pulse summary. The L10 structure is good. The Bearing extends it for teams where some of the work is being done by agents.

The Bearing is the fastest way to install the Waypost vocabulary into a team. Run it with the framework language from week one. Process the Relays, name the Obstructions, check the Waypoints. Every week, the vocabulary is used in the context where it matters most: a real governance meeting with real decisions on the table.

Start with a published agenda: Relays, Obstructions, Waypoints. No other sections. No status updates. If someone tries to add status, redirect: that is a Pulse item, bring it to the Bearing only if it requires a human decision.

The first two or three Bearings will feel short because the team is still learning what qualifies. By week four, the meeting will be full. By week eight, the team will not be able to imagine running without it.

The single biggest improvement most teams experience is the elimination of the decision backlog. Decisions that used to stall for days because there was no defined moment to make them now have a guaranteed slot. The weekly rhythm creates a decision cadence that keeps the operation moving even when the environment is chaotic.