Skip to content
Not in the Room

Saying Out Loud That Something Has Been Decided

The room has to be told it is no longer the record, repeatedly, by somebody with standing to say it.

What the team needs to knowIn the roomSent out
The decision, written down5 sent
The reason, written down2 sent
That you were thinking of themnone sent
Dense: the room supplies it, uncountedSparse: each mark is one deliberate actNo channel carries it at all

three things · two reached them · the room side is not counted

What a week looks like once somebody is actually doing this.

Home / On purpose

On purpose · Practice

A room will go on being the record until somebody with standing says, out loud and repeatedly, that it is not. Written mechanisms do not replace the room by existing; they replace it when the room is told they have.

The practical lesson in “Saying Out Loud That Something Has Been Decided” is that visibility must be designed rather than assumed. For teams exploring employee time tracking, see the current solution overview can add consistent time and project context when the purpose is explicit, access is limited and managers review exceptions with the people involved.

The telling is a separate act and it is the one most often omitted.

Additional sector context for “Saying Out Loud That Something Has Been Decided” is available from Pro Bono Australia nonprofit news. Check broad guidance against the team’s mission, funding obligations, workforce and jurisdiction.

Why the mechanism alone is not enough

Because the room keeps working. Decisions keep being made in it correctly and quickly, and the written version is an additional step with no immediate payoff for anybody present.

Nothing about having a channel changes that calculation.

What has to be said

Three things: that the room is no longer where decisions live, that anything not written down did not happen, and that this applies to everybody including the people who were present.

Said once, it is a policy. Said monthly, it is a practice.

The three things that have to be said, and keep being said:

  1. The room is no longer where decisions live.
  2. Anything not written down did not happen.
  3. This applies to everybody, including the people who were present.

Why repetition rather than announcement

Because an announcement is absorbed as an intention and then forgotten. The practice decays silently within about three weeks, and nothing signals the decay.

Repetition is not nagging; it is maintenance of a thing that mechanically runs down. A manager who finds themselves saying it for the ninth time has not failed to communicate: they have understood the shape of the problem.

Who can say it

Somebody the room will not quietly ignore. In most teams that is the manager, and it does not transfer to whoever cares most about the issue.

The person outside the room cannot do this at all.

Why they cannot

Because when they say it, it is a request about their situation. When the manager says it, it is how the team works.

Expecting the person it benefits to be the one who maintains it is the commonest structural failure in this whole subject.

The sentence that works in the moment

"That is a decision — who is writing it down?" asked in the room, immediately, every time.

It is mildly irritating, it works, and after two months somebody else starts asking it.

Saying it to new people first

Anybody joining the team learns how it works in their first fortnight and keeps that model for years. Telling them on day two that decisions live in writing and that the room is not the record costs nothing and sticks.

A team that says this to every joiner needs to say it to everybody else less often, because within two years half the team learned it as the way things are rather than as a correction.

The moment to catch

The point at which a conversation stops being exploratory. It is usually audible: somebody says "right" or "okay, so" and the tone changes.

Interrupting at that moment is the single most effective habit available, and it requires only that you be listening for it.

Naming the cost openly

Saying that this costs the room something and buys something for somebody else, plainly, without pretending it is free.

Teams accept a stated trade far better than an unexplained requirement, and the pretence that a practice is costless is detected immediately by the people paying for it.

What not to say

That it is about everybody being able to find things later, when the real reason is that one person is not in the room. The general justification is weaker and everybody knows it is not the reason.

Say the actual reason.

Why the actual reason is better

Because it is checkable and it is finite. A practice justified by a specific person's situation can be reviewed when the situation changes, and it does not expand into a documentation regime.

It also treats the team as adults who can be told what the problem is.

Handling the objection

Somebody will say that the overhead is disproportionate to one person's benefit. That is a legitimate position and it deserves an answer rather than a frown.

The answer is usually that the overhead is a minute a day and the alternative is a colleague working from stale information for a quarter, and that the trade has been considered rather than assumed.

What saying it cannot do

Make the room stop deciding things in passing. People will keep agreeing things in corridors and at the kettle, because that is how working together functions, and no amount of repetition changes it.

What repetition changes is the proportion that gets restated afterwards, and that proportion is the whole of the available improvement. A manager who expects the room to become a place where decisions are only taken formally will be disappointed and will give up; one who expects to recover half of what the room settles informally is aiming at something achievable and will still be doing it in a year.

Next door