# Why team chat should link to the work

> Chat and task tools drift apart. See why team chat should link to tasks, how to keep decisions from getting lost in threads and habits that help.

Most of what a team decides is said in chat and most of what it does is tracked somewhere else. Linking the two keeps decisions from vanishing and tasks from going stale.

Web page: https://kansohq.app/guides/team-chat-linked-to-tasks

Updated: 5 October 2026

## The problem with chat on its own

Chat is fast, and that is its danger. A decision is made in a thread on Tuesday. By Friday it is buried, the task still says the old thing and a new person asks the question again. When chat is separate from the work, three things go wrong:

- **Decisions disappear.** They are made in threads that nobody can find later.
- **Tasks go stale.** The card says “in progress” long after the thread said “blocked”.
- **Context is lost.** A new teammate sees a task and cannot see the conversation that shaped it.

## What linking gives you

When a message can point at a task, a page or a release, and show its current status, the conversation and the work share a reference. Open the message to see the task; open the task to find the message. A status shown in chat is always up to date, because it is read from the task, not typed.

## Habits that help

1. **Link, do not describe.** Paste the task into the message instead of retyping it.
2. **Decide in the thread, record on the card.** When a conversation settles something, write the outcome on the task or in the doc, with a link back.
3. **One channel per area.** For example one per product area or per release, not one for everything and not one per person.
4. **Use mentions for requests.** An @mention reaches the person’s inbox. A message in a busy channel does not.
5. **Do not use chat as a task list.** If something needs doing, it becomes a card with an owner.

## Pitfalls

- Too many channels, so nobody knows where to ask.
- Notifications for everything, so people mute everything. Let each person choose all, mentions only or none per channel.
- Long arguments in chat that should be a call or a decision record.

## Naming channels so people can find them

| Pattern | Example | Use for |
| --- | --- | --- |
| By area | billing, onboarding, search | Ongoing work on part of the product |
| By release | release-3-4 | A launch with an end date, archived afterwards |
| By topic | announcements, help | Things everyone should see, or a place to ask |
| By incident | incident-0914 | Handling one problem, then reviewed and closed |

## A routine from thread to task

1. A question or problem comes up in a channel.
2. Someone links the related task or page, so the thread has something to point at.
3. The thread settles on an answer.
4. The person who owns the work writes the answer on the task or page, and replies with a link.
5. If new work is needed, it becomes a task with an owner and a date, linked back to the thread.

Five steps, and the knowledge is on the task, where the next person will look.

## Habits that save everyone time

- Put the question and the context in one message, so nobody has to ask “what do you mean?”.
- Say what you need and by when: “Can you review this by Thursday?”
- Reply in the thread, not the channel, so the conversation stays with the question.
- Use a reaction to say “seen”, and keep replies for when you have something to add.
- Move long discussions to a page or a call, and link the result back.

## Chat that links to the work in Kanso

In [Kanso Chat](https://kansohq.app/product/chat.md), paste a task and the message shows its current status, not the one it had when it was sent. Channels and direct messages link to any task, page or release, replies stay in place, and an @mention lands in the person’s [inbox](https://kansohq.app/product/inbox.md). Because chat sits in the same workspace as the [board](https://kansohq.app/product/boards.md), there is nothing to sync.

## Questions

### Why should team chat link to tasks?

So decisions are not lost in threads and tasks do not go stale. A link shows the task’s current status inside the conversation, and the conversation is one click from the task.

### Can you use Slack or Teams instead?

Yes, many teams do, and link out to the tracker. The cost is that the two drift apart unless people keep them in step by hand.

### How many chat channels should a team have?

As few as work: usually one per area of work or release, plus a place for announcements. Too many channels leave people unsure where to ask.

### How do you stop chat becoming a task list?

Turn anything that needs doing into a task with an owner and a date, then link to it from the thread.

## Keep reading

- [How remote software teams stay in sync](https://kansohq.app/guides/remote-software-teams.md): How remote and distributed software teams stay in sync: write things down, make status visible, use chat well and keep meetings for decisions.
- [How to take meeting notes your team will use](https://kansohq.app/guides/how-to-take-meeting-notes.md): Good meeting notes record decisions and actions, not a transcript. Learn a simple structure, who takes notes and how to make sure actions happen.
- [Project management for software teams, explained](https://kansohq.app/guides/project-management-for-software-teams.md): Project management for software teams in plain words: what to manage, a light system that works at any size, the rhythm to keep and the mistakes to avoid.
- [Meeting notes template: decisions and actions | Kanso](https://kansohq.app/templates/meeting-notes.md): A meeting notes template that puts decisions first, then actions with owners and dates, then discussion and parked topics. Copy it, or start it in Kanso.
- [Decision record template (ADR) to copy | Kanso](https://kansohq.app/templates/decision-record.md): An architecture decision record (ADR) template with the decision, status, context, consequences and revisit condition. Copy it, or start it in Kanso.

## Parts of Kanso used

- [Kanso Chat](https://kansohq.app/product/chat.md): Channels and direct messages that link straight to the task, page or release being discussed.
- [Kanso Inbox](https://kansohq.app/product/inbox.md): Mentions, messages and work assigned to you, one line each, in the order it arrived.
- [Kanso Boards](https://kansohq.app/product/boards.md): A board for each piece of work. Cards carry a priority, an owner, a due date and the criteria that say when they are done.

[Kanso home, with plans and prices](https://kansohq.app/index.md)