<aside> 💡 Slack stands for Searchable Log of All Communication and Knowledge (yes, really). At Juro, we use Slack as a complementary repository to our official knowledge stores (like Notion, JIRA, Salesforce etc.).
</aside>
Slack is used at Juro as a way of bringing agility and transparency to help with effective communication across the organisation.
This means that asynchronous conversations happen in Slack. There is no guarantee of an immediate response. If it’s urgent, you may need to pick up the phone or log a ticket in one of our systems (e.g. with Customer Support or Engineering).
Slack supports 4 types of conversations in different types of channel:
With over 100 users and 500 channels it can be confusing to know what can be posted, where messages should be posted, how information can be found and if there are any best practices.
Many of us find ourselves slaves to the endless notifications, which affects productivity. Some of this is because we don’t follow best practices.
To try and help make Slack even more useful we have taken inspiration from the teams at Slack, Zapier and many other organisations and consolidated the best bits into our own set of guidelines.
<aside> 💡 Our must-do top 5 are listed here (with the detail in the table below), follow these and slack becomes more usable with less notifications and more searchable data.
</aside>