Getting into the #23things habit – team update

img_3141I’ve been writing quite a bit for the #23things course, some of the posts were about my personal experience, while others included reflections on my experience of taking part as a team together with my colleagues.

My first post about this shared venture is dated 16 September, so it’s been over two months since we started and we have been participating pretty much every week since.

We have taken a very flexible approach as a group, giving everyone express permission to take part in whatever manner they see fit. We have a shared scratchpad (Google doc) and at our weekly team meetings we talk about one of the 23 things, usually picked by one of the team who have a particular interest and questions. We have also had a guest or two join us for these discussions and that’s been particularly interesting (special thanks to Ewan!).

However, while each week is different and sometimes we spent more time and others less, there is one particular impact that I am delighted about: we have started to get into the habit. The weekly spot in our team meeting agenda has become part of what we do as a group, the conversations becoming more lively and wide-ranging as we share our different perspectives and questions. It’s quite surprising to come upon topics where some know much and others have questions.

As a┬áteam we have become more comfortable at being challenged by topics we know little about or tools we haven’t tried. It’s a lot of fun for me personally to be part of the process, because in a leadership position and as everyone’s boss I don’t always get a lot of time with my colleagues in that kind of context.

So, whilst there are plenty more things to discover in the course itself, I am also thinking about how we can expand on the 23 things to maybe a weekly thing, a topic or question or tool or technology we can talk about. The kinds of interactions the course has prompted us to have regularly are definitely a habit I want to keep.

Leave a Reply

Your email address will not be published. Required fields are marked *