How do founders keep track of decisions made in Slack threads?

What the job actually is

Founders keep track of decisions made in Slack threads by writing each call out of the thread the same day: what was decided, who owned it, and why. Let's go with Option B plus three thumbs-up is a conversation. It is a record only after someone writes the call down where the team will look in two weeks.

Founders and CEOs at companies of about 5 to 50 people live in Slack. They are the bottleneck. Product calls, hiring calls, and pricing calls land in threads while they are in a meeting. Two weeks later someone asks what we actually decided, and the founder spends a quarter hour scrolling.

Asana's Anatomy of Work Index, which surveyed over 10,000 knowledge workers, found they spend 60% of their time on work about work, including searching for information and chasing the status of work. The same index found the average employee uses 10 different apps every day, and 88% agree that time-sensitive projects and large initiatives have fallen behind or through the cracks. Slack says more than 4.7 billion messages are sent each week on its platform. A thread that held the call is one of them.

The buying prompt collapses four jobs: catch up on the thread, extract the call on demand, keep a durable log with an owner and a why, and follow up on the work the decision created. Promises typed as I'll send that tomorrow are a neighboring job, on the chief of staff software page. The agency-owner version of team promises in client Slack is on the chief of staff page for agencies. Client requests buried in threads are another, on how consultants keep requests from getting buried.

Which tool wins which job

Fund the row that matches the leak. A recap, an extracted list, and a durable log are neighboring jobs.

A recap is not a decision log

A recap compresses what was said. A decision log is only the calls that still stand, with an owner, a date, and a why. Summarizing every Slack message gives you a shorter thread. The founder needs what the team already settled.

Slack says Slack AI saves its pilot customers an average of 97 minutes per user a week, by its own internal analysis. That is time saved reading, not calls closed. A recap can mention Let's go with Option B and still leave Friday empty. Jason Morita, a product owner at ProService Hawaii, told Slack he gets over 100 messages on various Slack channels a day. Conversation summaries catch him up after meetings. They do not, by themselves, write the log.

Slack recaps land in a Recap view in the sidebar. You add the channels you want and get a new recap every morning of what you missed. Conversation summaries on Pro catch you up on a thread you open. Search finds messages, including with is:thread and has:pin, if you remember a phrase. Slack's own search help calls the archive searchable conversations and decisions. The phrase you need two weeks later is often not the phrase someone typed.

Recal's daily recap is structured: highlights, decisions, blockers, open questions, and action items, in 1-2 minutes. Recal says reading a day's messages in an active channel takes 10-15 minutes. Its action-items page says that in a 50-message Slack thread, 5+ action items are typically buried throughout. It still summarizes a window of messages. You run /recal, or you schedule it. An always-on scan of every channel is a different product, and a different privacy bargain. Recal's Slack page says it only accesses messages in channels where you invoke /recal, never reads private DMs, and does not store full message history. The recap is shown only to the person who ran the command unless they share the link. Catch-up already in Slack is on Slack AI vs a dedicated teammate.

When the log has to leave Slack

Discussion can live in the thread. The call needs a permanent address. Arpit Bhayani's rule, posted in March 2026, is the one operators repeat: never capture a critical decision on chat. Chat is fast. Months later a new hire has to reconstruct intent from a partial thread.

A Slack List keeps the flagged message inside Slack. Hover the message, pick Add to list, and fill the fields. That is the right move when the team already lives in Lists. A pinned message lands in the Pins tab. Pins pile up. They are a pointer, not a log with a why. A canvas tab is the in-Slack document. Right-click the tab and select Show canvas by default so a new person sees the log the first time they open the channel.

Notion is the wiki version of the same job. Use the message shortcut Send to Notion or Create task in Notion on the thread reply itself. The /notion create and /notion task commands only work at channel level, not inside Slack threads. Confirm page creation publicly if you want the channel to see that a page was filed. Manual copy into a doc is the step teams skip when the conversation is still moving.

The work the decision created is a different row. I'll write the spec Friday is a follow-up. We ship Option B is the log. Mix them and the why dies the first time the task is marked done. Outbound promises are on the commitments-from-threads page. A morning list of still-open asks is on the daily summary page.

The caveat that should decide the setup

The failure founders name first is an AI that treats a joke as a call. A half-joking let's just do X can read like a real decision. Recal extracts when you ask. Slack summaries fire when you open the thread. Thumbs-up is evidence that people saw the message. It is not an owner, a date, or a why. If a decision was made in chat and has not been captured somewhere permanent, treat it as still open.

A second caveat is auto-send. A prompt that says draft only is not a send gate. Worst case with a draft is you delete it. Worst case with auto-send is you explaining a recap that named the wrong call. Recal's on-demand recap stays with the person who ran /recal unless they share it. A scheduled recap posted into a Slack Connect channel is visible to the other organization. Keep the shop's log off the thread an outsider can read.

A third caveat is the Free plan's 90-day message history. After that the thread is gone, and search cannot bring it back. Pro keeps unlimited history. On Free, the log has to live outside the message stream or it dies with the history. A human chief of staff still wins the call on people and priorities. Software stores open loops. A meeting recorder wins notes from a call. Write a promise said only on the call into Slack or the log before the call ends if you need it on the same list.

Concrete is an AI employee that works in existing Slack channels. It keeps every promise made in a thread, and every thread waiting on a reply, as a follow-up. Each morning it nudges the owner. It drafts the follow-up as a Send / Edit / Skip card. There is no auto-send mode. Follow-ups survive reboots. After downtime it sweeps channel history, thread replies included. It starts from a ready-made role, including Chief of Staff. It is in design-partner preview; the longer thesis is on the vision page. It does not record meetings. It does not replace a chief of staff. The log of what you decided still needs a page. Concrete keeps the work that page created.

Step by step: write the decision out of the thread

This is the boring version that holds when the founder is still the bottleneck. Pin it before the next Let's go with Option B.

• Step 1: Name the call in the thread. Reply with Decision, the owner, the date, and one line of why. Tick Send reply to this channel so people who never opened the thread still see it. In a multi-person channel, Slack only notifies you of thread replies if you started the thread, replied to it, or were mentioned.
• Step 2: Write it out of Slack the same day. Add the message to a Slack List, drop the same four lines into the channel canvas, or use Send to Notion on the thread reply. /notion create does not work inside threads. Creating a to-do does not set a reminder by default. Do not trust Pins as the log.
• Step 3: Keep one shared log. A personal Later list vanishes when the founder is out. A #decisions channel still depends on someone posting. One canvas, one List, or one Notion database is the address. New hires read that, not scrollback.
• Step 4: Separate the decision from the work it created. The log holds what and why. I'll write the spec Friday is a follow-up with an owner. Knowledge workers spend about 28% of the workweek on email, roughly 11 hours, according to the McKinsey Global Institute, so the same call often has a twin in Gmail. Keep both on lists you will actually open. Email-only chase is on how to stop forgetting emails you promised.
• Step 5: Keep send as a tap. Draft the recap if you want speed. Send stays a tap. A scheduled recap in a shared external channel shows the other side your internals. The list of AI employees for a founder who cannot hire a chief of staff yet is on the roundup.
• Step 6: Sweep threads in the morning. Open Threads and Activity. Channel history hides thread replies unless you open them. A catch-up that reads only top-level messages drops the actual call. Keywords in an unfollowed thread will not notify you.