One Named Channel, and What Belongs In It
Several half-used channels are worse than one. How to pick it, what goes in and what deliberately does not.
three things · two reached them · the room side is not counted
What a week looks like once somebody is actually doing this.
A team with four channels, each used for some of the same things, has no channel at all for the person who is not in the room. They have to read all four and still miss things.
The missing context described in “One Named Channel, and What Belongs In It” is an operating-process gap. Teams considering what to examine when choosing monitask pricing for monitask pricing can attach clearer time and project evidence to work already being discussed, provided decisions, reasons and corrections remain visible to people who were not present.
One place, named, with a stated purpose, is worth more than any amount of tooling.
The questions raised by “One Named Channel, and What Belongs In It” can also be compared with Catchafire skills-based volunteering. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
Why multiple channels fail specifically here
Because people in the room do not depend on any of them. They have the room, and the channels are a supplement; whichever one is nearest to hand gets used.
For somebody outside, the channels are the entire supply, and a supply scattered across four places with no rule is a supply they have to search rather than receive. The cost of that search falls entirely on one person, which is why nobody else notices the problem.
Choosing which one
Whichever the team already uses most. Introducing a new tool to solve this is the commonest mistake, and it produces five channels.
The choice matters far less than the naming.
What belongs in it
Decisions, changes of direction, anything another person needs in order to not do the wrong thing, and the fact that something is open.
Four categories, stated once, written down somewhere visible.
The four categories, stated once and written somewhere visible:
- Decisions, with the constraint that forced them.
- Changes of direction, including small ones.
- Anything somebody needs in order not to do the wrong thing.
- The fact that a question is open and unresolved.
What deliberately does not
Discussion. A channel that carries both announcements and conversation becomes unreadable, and the person who most needs it is the one who has to read all of it.
Keep the conversation elsewhere and put conclusions here.
Why that separation matters
Because the value of the channel is that it can be read in two minutes after two days away. Anything that makes it longer makes it less useful to exactly the person it exists for.
A channel with forty messages a day is a channel somebody has stopped reading, and they will not tell you they have stopped.
The rule that keeps it short
If it would still matter in a week, it goes in. If it is a question, an aside or a reaction, it goes somewhere else.
One sentence, repeated whenever somebody forgets.
Who maintains the discipline
The manager, visibly, by moving their own messages when they put one in the wrong place. Correcting other people works badly; correcting yourself in public works.
It takes about two months.
The read-receipt temptation
Resist any mechanism that tracks whether somebody has read the channel. It converts a supply into a compliance measure, and the person being measured is the person the channel was built for.
If you want to know whether it is working, ask them.
Time zones and the reading of it
Where the person outside the room is in another time zone, the channel is read once a day rather than continuously, and anything that depends on being seen within the hour is not going to work.
That is an argument for the channel carrying conclusions rather than questions: a conclusion read nine hours late is still a conclusion, while a question read nine hours late has usually been overtaken.
Searchability
The channel has to be searchable and it has to have an archive somebody can scroll. Something that disappears after a week is a notification system rather than a record.
This rules out several things teams use for exactly this purpose.
The summary at the top
A pinned list of the current state — the live decisions, the open questions, the current priorities — updated weekly. It is the first thing somebody returning after a week should read.
Without it, the channel is a stream and streams have to be read in full or not at all, which means in practice they are read in full by nobody. A pinned summary is what turns the channel into something somebody can actually catch up on.
Who writes the summary
The manager, weekly, four minutes. Not delegated and not skipped in busy weeks, because busy weeks are when the drift is largest and the summary is worth the most.
A missed week is the beginning of its ending.
What a channel cannot do
Make anybody write in it. The channel is a destination and the problem has always been supply: the decisions that never get written down are not sitting in some other channel, they are nowhere at all.
Naming the place is necessary and it is the easy half. The hard half is the habit of writing, which is covered in the two notes before this one, and no amount of tooling substitutes for a named person doing it within the hour. A perfectly organised empty channel is the most common outcome of this exercise.
Next door
- The One-to-One That Is Not a Status Report
- Rotation: the Meeting, the Work, the Seat
- Saying Out Loud That Something Has Been Decided
- Why the Deliberate Invitation Feels Staged
- What Each Mechanism Costs, in Minutes
- What to Stop Doing in the Room
- Writing the Decision Down Within the Hour
- Writing the Reason Beside It