| I really like the idea around "ambient awareness". I'll look into it. Currently, I've built a slack bot for personal use that integrates with my calendar where I can create stretches of times as "Focus" events and during that time, the bot helps me establish an async communication model. The bot sets my status to "Do Not Disturb" during the event and if somebody tries to message me, they get a message that I am in heads down mode. They can then leave a note on why they were contacting me or if I they need me urgently, they can click a button and I get an immediate notification. When my focus time ends, I get a list of notes from my team on why they needed me and I can answer them one by one. Effectively, I've found that once a team moves to Slack, all internal communication moves to Slack (instead of using slack for urgent sync and email for other async), and this brings back email like async model to Slack for the times when you need it. You can try out the slack bot at https://slack.com/apps/A5MJB641F-oliv In full disclosure, I've build the bot for my personal usage and don't intend to monetize it. It's just my way of giving back to the community. It's not very polished and doesn't have an onboarding flow, so if you need any help in using it, contact me at ishan.chhabra [at] gmail.com. I'll be happy to help. |