Channels hold conversations; tabs hold the instruments of the work. A tracker, a wiki page, a live board — pinning the right ones turns a channel from a chat into a cockpit. Each tab is a choice that needs upkeep, though, and the wrong ones linger quietly because nobody complains about a tab.
Pin what gets read; automate what gets tedious
Two categories of tools solve different problems.
- Tabs — surfaces people open during work. The current brief, the release checklist, the on-call roster. One screen, one purpose, renamed to what its job actually is.
- Connectors — feeders that post when something changes. A build finishes, a form lands, a ticket escalates. The value is in fewer tab switches; the risk is noise.
Field note
Every automation needs a mute switch and an owner. When the feed posts twice for the same event or goes quiet for a fortnight, someone must notice and adjust — otherwise the channel learns to ignore it, and the next real alert drowns in the same silence as the last false one.
The dashboard graveyards
Every workspace eventually accumulates tabs nobody opens — last quarter’s retro board, a chart that died with its owner, a page titled “Untitled page”. Two habits fight the rot:
- Renaming the tab tells the truth about its function — “Contract — current draft” versus “page 2”.
- Unpin what nobody could open in six weeks; the channel and the search will outlive it.
A channel with two good tabs is a workplace. A channel with fourteen tabs is a museum — and museums are quiet because nothing moves through.
