Status meetings are a waste of time for the half spent rebuilding the picture.

Say you run operations for a hotel group with eleven properties, and every Monday at nine the general managers dial in, one after another, to say how the week went. They cover occupancy at the city hotels, the boiler at the coastal property, a wedding party that moved its date and housekeeping running short at two sites over the weekend. By the seventh manager, the first few are answering guests on their phones with the camera off, and the one real decision of the morning, whether to move staff between two properties for a busy weekend, comes up in the last ten minutes, after the call has already run over.

Most of that hour is wasted, though the meeting is doing a job and the job is real. Nowhere else in the group holds the current picture of all eleven properties at once, so the managers rebuild it out loud, every week, from memory. What is wrong is where the picture lives. It could live somewhere people read before they dial in.

What the first forty minutes are doing

Play a status meeting back as if it were a recording and most of what gets said is somebody reconstructing a fact that already sits somewhere else. Occupancy is in the property system. The boiler lives in the maintenance log, and in a WhatsApp thread with the heating engineer that nobody else in the group can see. The wedding moved on a Thursday phone call to the events coordinator. Each of those places holds its fact perfectly well, and Monday's call is the only place they ever meet.

At one property that arrangement works, because the general manager can walk the floor and see most of it before lunch. Somewhere between one hotel and eleven it stops working, and the moment is hard to spot, since the call just gets a little longer each year and everyone puts that down to the business getting bigger.

There is also a cost the hour hides. A manager reporting from memory reports what they remember, and what anyone remembers about a busy week is the loudest thing that happened in it. Often that is a different thing from what the COO needed to hear.

Two failures OCTYN found in its own version

OCTYN ran into the same thing inside its own work. Brain, the planning system OCTYN runs its whole portfolio on, exists because the context of more than twenty codebases had to be rebuilt every morning: what state each project was in and what had been decided about it, including the reason behind a decision that now looked strange. The workspace audited on 24 July 2026 held roughly 34,853 files, with 141 notes across 15 subprojects.

Building it showed two failures that carry straight over to a Monday call. The expensive one was a blended answer. Ask how one project deploys and get a fluent reply that quietly merges the steps of two projects, and the mistake stays invisible until somebody acts on it. On a call, the same failure sounds like "the boiler is sorted", said about the other property's boiler, or about the quote when the repair has not happened yet.

The second was age. The Brain case study puts it this way: a fact that was true in July and recalled in September with no sense of its age is worse than no memory at all. Status said out loud rarely carries a date. A manager who says the weekend is fully staffed might mean it was, on Tuesday, when the rota went out.

Brain has an answer to each. It keeps each project's context separate and will not mix two of them into one answer, and what it recalls can be traced back to where it came from. A line either has a source and a date beside it, or it does not belong in the record. There is a gap in that, and the case study says so. No fixed set of test questions exists for how well Brain picks its context, so the claim that it never blends two projects rests on nobody having noticed it happen. Building that test set is the first thing on its list of what would be done differently.

A meeting that opens on the decisions

For the hotel group, the change starts with where Monday's facts already live. Every one of them gets written down somewhere during the week by the work itself, in the maintenance log, the property system, the coordinator's notes and the engineer's thread. An operations system reads those places as things happen and keeps one current record per property, each line with where it came from and when.

It matters that the work writes the record. A summary somebody has to put together on Sunday night is the status meeting moved into a document, and it goes stale in exactly the same way. The Brain case study says Brain maintains itself as a by product of being used, and calls that the only arrangement that survives.

Then the call changes shape. People read the record before they dial in, and the call opens on the things a person has to decide, like moving staff for the busy weekend or whether the coastal property should replace its boiler or keep paying for repairs. The system can flag what looks off, a property whose maintenance log has gone quiet for a week, say, or two sites both counting on the same relief staff. Moving anyone is left to the managers. Brain has the same rule at its centre: it plans and never builds or deploys, which is what makes it safe to consult, since the worst a wrong answer can do is be wrong. Company Brain is that design, built as one memory for a company's own decisions and records.

The general managers keep the calls only they can make. They know which housekeeper will happily cover a double shift and which one will say yes and then not turn up, and no record is going to know that. They just stop spending Monday morning telling each other what a page could have told them on Sunday.

Where to look first

Sit in on the next call with a notepad and mark every item as one of two things, somebody reporting where something stands or somebody deciding something. Each reporting item points at a place its fact already lives, because the manager had to get it from somewhere before nine. Those places are where a record starts. If you want to count what the hour costs across the group on your own numbers, the page on what a system gives back does the sum.

The wedding party will still want an answer by Tuesday.