How to keep a decision log in team chat
Decisions disappear unless they live where the work lives. A choice left in a direct message, a meeting note, or a thread nobody scrolls back to leaves the channel looking undecided. The next person asks again, or starts from the last version they can see.
A decision log is a short entry in the team channel, written the same way every time: what was decided, who owns it, by when, and where to find the context.
The usual way
The record sits apart from the channel the team is already reading.
Two people settle a channel question in a direct message. The channel still shows the open question. When DMs hide the decision is that pattern. The log is the line you post so everyone else can see the choice.
A meeting ends in a doc or a slide deck. The person who picks up the work on Thursday was pointed at the channel, and the sentence never arrived there.
By Friday, Tuesday's decision sits under updates, links, and a side question. Nothing marks the deciding line, so people keep scrolling.
The next person asks and gets an answer from memory. One version names an owner. Another names a date. The team is working from two versions of the same agreement.
Four fields in one message
Use the same four labels every time, so a search for "Decided" lands on the log.
- Decided. One sentence, the choice itself. "We ship the shorter headline."
- Owner. One person, by name. "Sam owns the swap."
- By when. A day, or the words "no date" when nothing is scheduled. "Soon" is a deadline nobody can check.
- Where to look. The thread, the doc, or the message that holds the context. If this message is the context, write "this thread."
Decided: we ship the shorter headline. Owner: Sam. By Friday. Where to look: this thread.
A date change uses the same shape: "Decided: the launch date moves to November 3. Owner: Priya. By Wednesday. Where to look: the thread under Maya's question this morning."
Write the labels for the person who was not in the room. Those opening words are what a later search finds.
Habits that make the log stick
Post in the channel the work already uses. If the question lives in the launch channel, the entry lives there too. The working channel is the log, because that is the list people read.
One thread per decision, or one pinned log. Reply in the thread so a single choice sits under the discussion that produced it. For a channel that makes many small calls, pin one message titled "Decision log" and add a line each time something is settled. Say which pattern the channel uses, in the topic or in the pin.
Check the log before related work starts. Search the channel for "Decided" before a new thread opens on the same topic. If a line exists, reply under it or link it. When the search comes back empty, write the next entry in the new thread.
Post a new line when the choice changes. Name the new decision, the owner, the date, and the earlier message it replaces. Leave the old message in the history. The newest "Decided" line is the one the team treats as current.
Close the entry in the same place. When the owner finishes, they reply on that entry: "Done. The shorter headline is live." The log then holds the choice and the outcome.
Write the four fields before the conversation ends. A log that waits on a later write-up turns back into a meeting note.
How Bullpen fits
In Bullpen, the bullpen is the team's space. A decision posted in the shared channel sits in the same list as the question it answers. Walk-in voice rooms stay open beside the channel, so the short talk and the written log share one place.
Wren, an AI helper, posts notes and action items from a walk-in voice room back to the channel that room belongs to. If the note runs long, reply under it with the four fields so the log line stays easy to scan. Recaps that land in the channel covers how those notes arrive.
Scout, an AI helper, answers from what was said and links the source message. Mention Scout in the channel and ask what was decided about the headline. The reply cites the log entry, so the next person opens the sentence that was posted. Searchable team chat is why that link matters.
Nix, an AI helper, sets reminders in the channel. When the entry names a day, mention Nix in that thread and ask it to remind the channel then. The reminder lands next to the decision, where the owner and anyone else on the work can see it. How to keep track of follow-ups in team chat is that routine on its own.
The log entry, the voice note, and the reminder are channel messages. Scout points at the entry.
Write the next entry before you leave
The next time a thread, a direct message, or a walk-in voice room settles something other people will act on, post four fields in the channel before you move on.
Decided. Owner. By when. Where to look.