Async standup updates on Slack

It’s OK if you like the safety of a ritual to get your standup digest. That’s ok. There are ways to do this while being asynchronous. You need to implement a two-part solution.

  1. Automate the standup. With IFTTT and Zapier, you can automate pretty much everything these days. However, I have two out of the box solutions for you. If you use Jira and Slack, then you can try Geekbot. If you’re using Trello, then the Butler functionality on it can help you create a standup workflow. In fact, my current team does all its standup updates on Trello, courtesy Butler. Whatever you do, make sure that all the updates go to one place - e.g. a #status channel on Slack, or a specific list on Trello so people can control how frequently they get notifications.

  2. Agree on team commitments. An async standup is pointless if people don’t post their updates within a reasonable timeframe and if no one reads these updates. Depending on how distributed you are, your agreements will be different. That said, it’s important to agree on a time by which everyone will post their updates and a time by which everyone will read them. 

That’s it, no biggie. You just need to follow through with your commitments from that point on. And by the way, if you don’t use Jira, Slack or Trello and your company doesn’t allow you to use IFTTT or Zapier, there are other ways to do this. A shared collaborative document, or a form connected to a spreadsheet, can do the trick as well. Tools like Basecamp and Fellow allow for automated standups and you’ll encounter specialised tools like Range too. The world’s your oyster - find your own adventure!

Previous
Previous

Drop the sprint planning meeting

Next
Next

Avoid communication blasts