Mistakes and Lessons - Communication in Decentralized Teams

So earlier today, I good friend of mine that is working with me on Gamer's Life Convention 2013 sent me a message to catch up about GLC2013 again. Although GLC is about as much as from Lachlan as it is from me, I felt that I was probably doing something wrong for him to specifically arrange to meet up with me to get updates regarding our plans for the event.

Since the last time we had chat, there have been a few developments. Although these developments were clear to me as I regularly update my notes in my GLC notebook, these developments were unknown to my team members. I had forgotten to keep a clear and regular chain of updates and information to my own team. I had made a mistake with how informed I should keep my team.

Almost everyone in my team was specifically chosen because they contribute a specific set of skills, connections and experience.We were a team with me acting as the team leader to guide the actions of the group. I made a mistake in that I believed I was the only one that needed all the information as I would be making many of the fundamental decisions to the event. Although true for the organisation of the first Gamer's Life Convention I had wanted GLC2013 to have a greater contribution from my team and the community. This one message from a good friend of mine highlighted the fact that when working in an increasingly decentralized team there becomes a need for a greater flow of information between members.

So to solve this problem, I have decided it that I need to include a time during my daily procedure to forward on any updates from that day to some centralized information hub (in this case, posting it in a private Facebook group). Additionally, I've decided to create a list of relevant questions and points of discussion (such as what new activities should we add to the event) on to the central information hub. A to-do list is another good function that should be included as well.

This all makes sense to me now, that people produce and work exceedingly better than average when paired up with tasks and jobs which truly interest and motivate them. In a team that wants to be increasingly more decentralized it's important to keep team members informed so they can more actively choose and determine what task they can do, and do well. It also happens to be how great creative organisations tend to be from what I've heard, places such as Valve, Apple and Google.

Anyways, I'm thinking I might keep these "Mistakes and Lessons" short and not elaborate too much more than this much. Long enough to know some background, but short enough to keep it as a concise note. So in summary.

When moving from Centralized -> Decentralized organization

- free up the flow of information by keeping people informed
- build updating team mates into a part of regular routine
- use technology as a way to

• inform team mates
• gather opinions and feedback
• assist with allocation of tasks