March 19, 2024

Stop using slack for everything

Stop using slack for everything

Slack is perfect for asking ๐—ฅ๐—ฒ๐—ป๐—ฒฬ ๐—น๐—ฎ ๐—•๐—ฟ๐—ถ๐—พ๐˜‚๐—ฒ where heโ€™s planning to grab lunch, or to notify people about something via a dedicated channel,

BUT the knowledge itself should NEVER live inside of slack. Thatโ€™s a hard rule we have set at Stockly.

1.ย Communications must be asynchronous by default (via Notion for us, but could be via e-mail for other companies)

2.ย The knowledge should be stored in our knowledge base, inside a ticket or in a cold documentation for instance.

It doesnโ€™t prevent you from sending the project page link via slack to your colleague to ask them to have a look if something is urgent for instance.

Or you can use Slack to announce a new documentation / a new process, but the documentation / process itself should live inside your knowledge base, not in the slack announcement.

This way the information is structured, stored in the right place, accessible to everyone, editable by whoever has the rights to edit, easy to share ...

I think it's extremely important to ensure there is always only ๐—ผ๐—ป๐—ฒ ๐˜‚๐—ป๐—ถ๐—พ๐˜‚๐—ฒ ๐˜€๐—ผ๐˜‚๐—ฟ๐—ฐ๐—ฒ ๐—ผ๐—ณ ๐˜๐—ฟ๐˜‚๐˜๐—ต in an organization.

Iโ€™m convinced that this kind of concept is key to make a modern organisation efficient from scratch.