-
At my team, we have been pushing for async collaboration and communication. Here are some findings of sharing information, decision making and collaboration 👇Permalink On twitter.com
♻️ 2 Retweets ❤️ 8 Favorites Mood +1 🙂
-
This Taxonomy, from @TammyBjelland, applies to the experience I'm having when applying more async communication and collaborationPermalink On twitter.com
-
1. Async Dailies work well when you have a good format and expectations on what you expect people to share. Use a template that everyone follows. Ours is: We combined ASYNC and SYNC Dailies for some time until we found that we were informing in the right way to gain experience.Permalink On twitter.com
-
2. When introducing Pairing, we missed share information about the decisions and we realized of those "late" as a team. We introduced the KickOffs, a session that when as a Pair or Individual picks a User Story from the TODO List, we host a session to share and debate decisionsPermalink On twitter.com
-
3. Informing async takes time. We use three tools: - Slack - Miro Board as Information Radiation. This one, it to share anything we want as a team. From our ceremonies, current challenges, literally anything. It's not well organized, but it's our place to go to find stuffPermalink On twitter.com
-
3.1. - Confluence. We aim to put all the info as documentation here. Sometimes, we copy-paste and refactor Threads of Slack to not lose them after 2 - 3 days of chatting there The docs don't need to be good, need to be useful. Sometimes, they are about recalling a conversationPermalink On twitter.com
-
4. Communicate the criticality and importance of your messages. We start the informing messages with a header like: [ Not Critical / Important ] Decision About X It helps people to know how they should react to the message. Like stop and attend this, or check it later.On twitter.com
-
5. Decision-making is hard. People expect them to happen in meetings. Even though there's no decision being made, there's the feeling of they still happening but not involving the team. Be explicit in which format the decision happensPermalink On twitter.com
-
5.1. Share explicit when the decision is ASYNC or SYNC. Aim to not make all the decisions SYNC, it creates a feeling of FOMO when you're not attending a meeting since there is where the decisions happen and you want to give your input.Permalink On twitter.com
-
5.2. Create a habit for decision-making in phases async and sync. 1. Information gathering. ASYNC 2. Noting down pain points and what needs to be decided. ASYNC 3. Create a meeting with the expectations clear and who needs to attend and why 4. SYNC Meeting to take the decisionPermalink On twitter.com