One label, and the whole story comes back together
- Trigger
- /tags
- Lands in
- An ephemeral view in Slack
- Setup
- 1 min
- Needs
- Nothing else
Everything tagged “spring launch”
4 pins, 2 decisions, 3 open tasks
- Pins
- Launch checklist, brand kit
- Decisions
- Ship on the 14th
- Open tasks
- 2 owned, 1 up for grabs
- Archived
- excluded
Every row deep-links to its original message, so the roll-up is a map of the work rather than a copy that goes stale.
What one tag pulls together
A tag is not tied to a message type. Put the same label on a pin, a locked-thread outcome, and a task, and /tags gathers all of them under one heading, so the whole picture of a theme arrives at once.
The launch checklist, the brand asset, the link everyone keeps asking for. Tag the pin once and it stays findable long after it has scrolled off the channel.
The debate you closed with an outcome recorded. Tagged, it sits alongside everything else on the theme, so the reason behind a call is one command away rather than lost in the history.
What is still owed, and who owns it. A tagged task shows up in the roll-up with its assignee, or marked up for grabs, so nothing on the theme quietly goes unowned.
There is no folder to file into and no board to maintain. The roll-up is built the moment you ask, from work your team was already doing, and archived items fall out of it on their own.
One shared vocabulary, not everyone's private folders
The reason tagging usually fails is that everyone invents their own words, and the labels drift until none of them find anything. Viably keeps the tag library in one place so the whole team marks things the same way.
An admin curates the list of tags in one place. In Slack, people pick from that list on a pin, a lock, or a task, so the names stay consistent and there is no long tail of near-duplicates like q4, Q4, and fourth-quarter.
A tag can contain spaces and reads however your team talks, so scranton onboarding, spring launch, and board prep all work. Matching ignores case, so nobody has to remember exactly how it was typed.
Remove a tag from the library and it stops appearing in the pickers. Existing items keep their history, and the picker only ever offers labels that still mean something to the team.
Turn it on in 3 steps
Nothing to migrate and nothing to model. Name a few tags, apply them to work you are already doing, and the roll-up is there the first time you ask for it.
Open Tags in the dashboard and add the labels your team works in: themes, campaigns, clients, quarters, events. This is the one place tags are made, which is what keeps the vocabulary shared.
Pinning a message, locking a thread, and creating a task each offer a tag picker. Add one or several from the list and carry on, with nothing extra to open.
Run /tags followed by a name in any channel to pull every pin, decision, and task on that theme into one view, each deep-linked back to where it lives.
Recall a whole theme with one command
Two ways to run it, one to bring the team up to speed and one to remind yourself what themes exist.
/tags name, the shared roll-upRun it with a tag and Viably posts every live item carrying it, the pins, the locked threads, and the tasks, into the channel for everyone to see. It is the fastest way to bring a whole team up to speed on a campaign without calling a status meeting. A tag with nothing on it stays private, so a miss never adds noise to the channel.
/tags, your private indexRun it on its own and Viably shows you the workspace tag library, visible only to you, so you can see which themes already exist before you pick one to apply.
Each pin, decision, and task in the roll-up carries a deep link to its original Slack message, so the view is a map of the work rather than a copy of it that goes stale.
Three things, and they share one library: pins on the Pinboard, locked threads with their recorded outcome, and tasks. Because the same label spans all three, /tags returns the reference, the decision, and the open work on a theme in a single view instead of three separate searches.
The dashboard. An admin curates the workspace tag library there, and everyone else applies those labels in Slack when they pin a message, lock a thread, or create a task. Keeping creation in one place is what stops a team ending up with five spellings of the same idea.
Search looks for words in messages. A tag is a deliberate label your team put on the things that mattered, so /tags returns the decisions and open tasks you chose to mark, not every message that happens to mention the word. It is the difference between a filing system and a search box.
Yes. Tags read the way your team talks, so spring launch and scranton onboarding are valid, and matching ignores case, which means /tags standup still finds an item tagged Standup.
Archived pins, resolved threads, and closed tasks drop out of the roll-up automatically, so /tags always shows what is still in play rather than a history dump. Remove a tag from the library and it simply stops appearing in the pickers, while the items keep their history.
Start tagging today
The first tag pays off the moment a second thing carries it, so pick a live campaign and label the next pin, decision, and task that touch it.
It helps to have them switched on: the Pinboard for references, the Thread Locking guide for decisions with an outcome, and the Task Management guide for the open loops a tag then gathers up.
Open Tags in the dashboard and add your first few labels. From then on one reaction or one task tags the work, and /tags brings the whole theme back.