Your Status Meeting Is a Polling Loop. The Always-On Channel Fails the Same Way.
Watch the video version:
At the Open@Epic keynote in Madison last month, a speaker described apps connected to patient records that check for new information on a timer, every 30 minutes in the speaker's example, whether anything changed or not. That polling costs infrastructure, and health systems, the speaker said, "are definitely noticing the extra traffic."
The fix is notifications. Health systems "can decide which notifications they want to support," so when a patient has a visit, a notification goes out and the app responds to it. The goal, in the speaker's words, is to "build apps that don't need to just constantly ask, is there anything new? Is there anything new?"
That repeated question is the sound of most weekly status meetings. Each person, in turn, on a timer, is asked what changed since last week. Plenty of the answers are "still working on it." Anything that changed on Tuesday waited for Monday's slot.
Ask a room of engineering leaders how to keep a team visible and you hear one of two answers. Hold a regular status meeting, so everyone reports and nothing falls through the cracks. Or kill the meetings and stay responsive: open door, open channel, ping me the moment anything changes. Each is sold as the cure for the other, and most teams have run both.
Neither answers the question underneath: which changes matter, to whom, and how fast. With no rule, the leader picks the trigger by default.
The meeting makes the calendar the trigger. News waits for the slot, so people learn to hold it, smooth it into "on track," and rehearse the bad version. Two engineers whose work collides sit in the same room and route it through the leader instead of turning to each other. I call that meeting The Standup Ghost: a recurring meeting that produces attendance but no decisions.
The open channel makes "now" the trigger. Everything reaches the leader the moment it happens, whether it matters or not, and the leader triages all day. People stop making small calls themselves, because asking up is faster and safer than owning the answer, and every quick question breaks someone's focus on the way. I call that Klaxon: every request treated as equally urgent, because nothing has taught the team the difference.
Both end in the same place. The leader becomes the integration point: the only person holding the whole picture, and the only route between people who should be talking directly. Bad news arrives late or arrives as noise, decisions queue on one calendar, and the team's throughput stops at the leader's capacity. When the leader takes a week off, the meeting gets cancelled or the channel goes quiet, and the work slows to match. That is a cadence and communication failure: a culture where people do not communicate directly or work together, because every connection runs through one person.
Both setups were reasonable answers to a question nobody wrote down. Design the trigger, the way event notifications do. I call it the Trigger Rule, and three lines are enough. Anything that changes someone else's work, such as a slipped dependency, a blocked handoff, or a changed interface, goes straight to the person it affects the moment it is known; the leader hears about it only when those two need a decision they cannot make. Progress and small risks wait for the regular slot, which now exists to close decisions instead of collecting status. Work moving as planned needs no report at all.
Once the team trusts which line an event belongs on, Klaxon has nothing to ring about, and once every slot ends with one owned, dated commitment, The Standup Ghost loses its chair. That rule is the first piece of Communication Infrastructure: information flow designed as a system, so understanding holds when nobody, the leader included, is actively passing it along.
The bar is a team that functions without you and is better when you are in the room. So measure yourself by what happened while you were out. If nothing was decided without you, the team was built around you, not with you. Admit the status meeting is for you. It gives you the comfort of knowing first, and keeping it after the rule exists chooses your comfort over their throughput.
Think of the last full day you were away. Name one decision two people on your team made together, without you, that you heard about afterward. Then count the updates in your last status meeting that were news to someone other than you. If you can name one, your team already runs part of the first line; write it down so it holds. If the first answer is none and the count is close to zero, write the three lines this week with the team in the room, and give the next slot a decision to close instead of a report to collect.
TeamOS™ builds this into your team's operating system. Chapter 1 walks you through the channel map, response-time table, meeting taxonomy, and information routing guide that decide which information goes where, and Chapter 2 names Klaxon and The Standup Ghost and what beats each: https://TeamOS.Coach
Ninety business days from an empty binder to version 1.0 of your team's own operating system: written down, distributed, and acknowledged.
