72% of you filled in the recent organisational analysis survey (thank you!)* - we looked at some of the initial data yesterday in the unconference sessions, and wanted to share more broadly here for others. The results can show us a lot about how Status operates, interacts and communicates as an organisation.
A good example is this view - focused on who we share information with:
In this map, the Embark and Nimbus teams are clear clusters with critical nodes (Iuri and Jacek respectively) that share information between the teams and the rest of Status.
You can view the network maps for 3 broad questions here:
There are a bunch of options to filter & modify the networks based on multiple criteria - feel free to play around with them (please share any interesting findings).
In our session yesterday, we discussed:
- Identifying critical nodes to the organisation (with the insight that they may also be at risk of being overloaded)
- The unique challenges that remote working brings to an organsation likes ours - where we may miss out on the “watercooler” moments that help create cross team connections.
- How to create more connections between teams/groups (especially where none seem to exist) - and the role that Slack & Desktop have played in creating or breaking some of the connections.
- The risk posed by having “critical” nodes in our network (i.e an over-reliance on one person) and one potential solution being a “documentation week” where we try to document all process etc to ensure continuance when a team member is sick/on vacation/leaves.
- The hope that the week in Istanbul will strengthen connections across teams, and how we should/could schedule similar events to continue to develop the connections. BUIDL week was cited as a good example.
Further comment/insight welcome!
*If you haven’t filled in the survey, you still can do, and I can update the network maps.