Well…#wolweek (“working out loud” week) didn’t quite turn out as I’d anticipated, when I optimistically wrote a post last week about intending to participate.
Day 1-2 I was mostly offline, madly finishing a work piece to support a huge organisation-wide ERP project. Not quite sure what happened the rest of the week…but I never managed the flurry of tweets and blog posts of updates on work in progress and half baked thoughts I’d imagined at the week’s beginning. I was reflecting on why this was the case, and I think it comes down to the simple fact that it takes more than just intentions to change behaviour. Although I had the intention to participate, I didn’t actually think about how I’d do it. Starting a #wol habit and participating actively in #wolweek involves actively participating in a community. This starts with consciously and habitually checking the feed, responding to other’s updates as well as sharing your own – and integrating this behaviour into your work day. This is the challenge of any new behaviour change.
As Jeff Merrell pointed out on my previous post, #wol isn’t just about sharing publicly, but sharing and being open with anyone you’re working with. Yes, I was in ongoing communication and shared work in progress with stakeholders in the project (something I am consciously working on getting more comfortable with – and have found that early sharing of incomplete work or initial ideas- can be very helpful). But – were there also moments when sharing what I was working on with the broader network outside of my immediate work group could have helped me? Definitely.
Some of these moments included:
- trying to figure out how to link internally to a set of html files from a page in an elearning authoring tool. Googling it brought up a number of promising looking links – but they were all to the vendor’s (CLOSED) community. When I tried joining the community to access the forum posts, the activation email didn’t work. I gave up, and eventually called the vendor’s support where I eventually got the information I needed to make it work. It was a frustrating experience that could possibly have been short circuited by directly consulting my network. Did I even think of this at the time? No. (This goes back to not having thought about the sorts of things I’d share during #wolweek, and when).
- toying with the idea of a structural change to the online comms/awareness piece I was working on. I ended up leaving it in the end but at that point when you’ve looked at something 1000 times and lost all objectivity, getting feedback from someone with no background or prior knowledge can be helpful.
- researching how to develop & deploy an ipad app (scoping the specs so still have a chance to get help on this)
So…although #wolweek is just about over, and didn’t go quite as I’d intended, I’m hoping my reflections on why, how and what i could have done will help keep #wol front of mind for me, and trigger a response to share what I’m working on and learn from others. And at least I’m getting more comfortable with blurting out quick posts.
I’ve also got a bunch of old drafts that I will publish…likely over the next week (as it’s after midnight now and I don’t have the energy to do anything other than post this one!).