We use Fibery and Slack for our communication.
Fibery:
Discussions related to Features and Bugs
Daily Check-Ins
Slack:
Discussions related to Product Areas, Teams, Company in general
There are several major patterns.
We usually create a separate channel for every major Feature. For example, f-my-space or f-publish. Channels are open and anyone can join, but mostly they are used by feature teams. We discuss all things about the feature in Slack channel. However, we don't always transfer this information back to Fibery (🦐)
f-my-space
f-publish
We also have channels for most Product Areas, like pa-search, or pa-integrations.
pa-search
pa-integrations
Business process channels, like marketing, hr.
marketing
hr
Knowledge sharing channels: competitors, ted-nelson.
competitors
ted-nelson
Notifications channels just for events broadcasting: git-lab, new-leads, purchases.
git-lab
new-leads
purchases
Just for fun channels: dopamine, cortisol.
dopamine
cortisol
✔️ Partially Solved (we use Fibery for Features discussions): Discussions in Slack are detached from Features or Product Areas. It means we don't have a single shared context.
Partial Solution: Comments in Fibery are quite good now, so we use it for all communication about features and bugs.
Shared knowledge is not accumulated in Fibery and disconnected from Product Areas, competitors, etc. Slack is a good place to share things, but not good to collect and find things.
It is hard to create work from Slack discussions. You have to copy/paste text into Fibery and lose context. It is not always obvious why this work was created and what was the trigger.
We constantly jump between Fibery and Slack. It might sound like a small issue, but in reality it takes a lot of time and cognitive work.
Have a chat right inside Fibery and have discussions right inside our work/knowledge hub. We've released Thread View (experimental, emulates Slack channels) to experiment with that and moved Daily Check-Ins into Fibery. It works pretty good!
Convert unstructured discussions into structured knowledge.
Reduce context switching by having a single collaboration space.
Threads — interesting tool for deep conversations
Slack — some chat
