March 19, 2024

What should be used for communications inside a company?

What should be used for communications inside a company?

If not using Slack / instant messaging for everything, what should be used for communications inside a company?

๐“๐ข๐œ๐ค๐ž๐ญ๐ฌ ๐ŸŽŸ๏ธ๐ŸŽŸ๏ธ๐ŸŽŸ๏ธ๐ŸŽŸ๏ธ๐ŸŽŸ๏ธ !!!!!

Each team at Stockly owns a ticket table, where other teams can go and request basically anything.

To make it smooth and efficient the key concepts of our tickets tables are the following.

Each ticket has a Severity from 1 to 5. 1 means the whole company is about to explode. 5 means thereโ€™s nothing urgent about the request.

Most tickets are templated. For instance if you request a day-off you create a day-off ticket, you simply input the necessary info and then the HR team will make sure everything is done properly (all the steps being directly documented inside the template).

As all tickets table are Notion databases (of courseโ€ฆ) you can create specific views (filters, sortings, etc.) to make sure you see the right stuff in the right context.

Some tickets can also be created automatically or triggered by a certain workflow.

This allows overall:

1.ย Very efficient asynchronous communications

2.ย Clear SLAs and reliability

3.ย Traceability of all topics

We documented very precisely all the rules about how to manage tickets at Stockly, ๐—น๐—ฒ๐˜ ๐—บ๐—ฒ ๐—ธ๐—ป๐—ผ๐˜„ ๐—ถ๐—ป ๐—ฐ๐—ผ๐—บ๐—บ๐—ฒ๐—ป๐˜๐˜€ ๐—ถ๐—ณ ๐˜†๐—ผ๐˜‚ ๐˜„๐—ฎ๐—ป๐˜ ๐—บ๐—ฒ ๐˜๐—ผ ๐—ต๐—ฎ๐˜ƒ๐—ฒ ๐—ฎ ๐—น๐—ผ๐—ผ๐—ธ ๐—ฎ๐˜ ๐˜๐—ต๐—ถ๐˜€ ๐—ฑ๐—ผ๐—ฐ๐˜‚๐—บ๐—ฒ๐—ป๐˜๐—ฎ๐˜๐—ถ๐—ผ๐—ป, ๐—ต๐—ฎ๐—ฝ๐—ฝ๐˜† ๐˜๐—ผ ๐˜€๐—ต๐—ฎ๐—ฟ๐—ฒ ๐—ถ๐—ณ ๐—ถ๐˜ ๐—ฐ๐—ฎ๐—ป ๐—ต๐—ฒ๐—น๐—ฝ ๐—ผ๐˜๐—ต๐—ฒ๐—ฟ๐˜€!