Project Management with Tags

Where and How to Use Tags

Sprints and deadlines.
Label iterations (for example, #january_sprint or #C5). This makes retrospectives easier: just open the tag to see everything completed during that period.

Knowledge base.
Tags like #guidelines or #design_system help new team members quickly find what they need.

Priorities and processes.
Use tags to mark urgency (#urgent, #important) or responsibility areas (#HR, #marketing, #procurement).

Client work.
Group tasks by customer or project: #client_JPMorgan or #project_renovation.

Working in the business chat interface

1. Click “add tag” in a task, topic, or comment. Choose an existing tag or create a new one directly in the search field.

2. In the “Tags” section, labels are automatically sorted by popularity. Filters allow you to show only topics, requests, polls, or comments. The “My” tab shows tags you use, while “All” displays tags used by the entire team.

3. Any tag can be expanded to see everything related to it: tasks, topics, polls, and comments.

Common Tagging Mistakes

Too many tags.
50 tags for a team of 10 is usually overkill. When there are too many, people stop understanding which to use and abandon tags altogether. If a tag is used less than once a week, you probably don’t need it.

Overly specific or overly generic tags.
#tasks_for_Ivan_on_Project_Alpha_Q1 is almost useless - just like #work, which fits everything.

Inconsistent naming.
#urgent, #ASAP, #срочно - a direct path to chaos. Agree on one language and format and stick to it.

No cleanup.

Projects end, clients leave, but tags remain. Review your tags quarterly: delete outdated ones and merge duplicates.

Well-organized tags help teams spend less time searching for information and more time doing real work. Start with 5–7 core tags and expand only when necessary.