Analysing and Summarising Slack Discussions

This guide covers how to read Slack activity and turn it into something useful for the user.

What makes a conversation worth surfacing?

Surface it if:

• A decision was made or a direction was settled — even informally ("yeah let's just go with X")
• An open question is being actively debated and hasn't resolved
• Someone announced something shipped, launched, or completed
• There's a blocker, escalation, or something that needs the user's attention
• Context has emerged that affects how a project or initiative should be understood
• There's a pattern across multiple channels (same topic coming up in eng, product, and customer channels → probably important)

Useful even if low-drama:

• What people are working on and what's blocking them — a quiet digest of team activity the user doesn't always have time to read
• Customer signals — feedback, questions, complaints that reflect real usage

Skip it if:

• It's purely logistical with no informational content (scheduling, room booking, lunch orders)
• It resolves immediately with no substance ("anyone seen X?" "yeah it's in the drive")

How to present discussions to the user

Be scannable. The user reads the daily note quickly. Lead with what matters.

• One line per item — state the substance, not the meta-description. "Decision: delaying beta by one week (thread in #product)" not "There was a discussion in #product about the beta timeline."
• Link to the source — always include a deep link to the Slack message or thread so the user can click in and read the full context if needed. Use the permalink field from the API.
• Flag open questions — if something is unresolved and might need the user's input, say so explicitly.
• Group by channel or topic — whichever makes the digest easier to scan. Usually topic-grouping works better when there's cross-channel activity on the same thing.

Daily note format

Add a ## Slack section to the daily note. Structure it like this:

## Slack

**Last checked:** 2026-03-21T09:00:00Z

**Channels checked:** #team-engineering, #decisions, #product-discussion

### Decisions & announcements
- Feature X now working across all environments — close to merging. [→](https://your-workspace.slack.com/...)
- Decision in #product: beta delayed one week, integration not ready. [→](https://your-workspace.slack.com/...)

### Active threads to watch
- #team-engineering: concern raised about approach — 5 replies, unresolved. [→](https://your-workspace.slack.com/...)

### Team activity digest
- Alice: wrapping up feature X
- [others as relevant]

List the channels checked so future check-ins can scan the note and know where to start.

Updating the KB

Most Slack activity belongs in the daily note, not the KB. Push something to the KB when:

• A decision materially changes the understanding of a product area, project, or process
• An announcement marks a project as complete (flag as archive candidate)
• A discussion surfaces durable domain knowledge (a definition, a competitive insight, a customer pattern)

When in doubt, put it in the daily note and let the user decide.