I’ve been away:Reflections on a Journey Part 1

Introduction

The blog has been quiet because I have been on the road for 18 days, first to Rome to co-facilitate the second CGIAR/FAO Knowledge Sharing Workshop face to face phase, then on for a quick stop in Prague (cheaper to fly to Israel from Rome via Prague) where I met my pen pal of 40 years face to face for the first time, and finally to my first time in the Middle East in Israel and Palestine.

Four countries, many sets of new and old relationships and a profoundly moving and challenging experience of a new set of complex cultures has left me so much to reflect on that it will take a while. But in the spirit of learning, I wanted to capture some of it here on the blog because it has, for me, profound connections to the work so many of us do around working and communicating across all kinds of lines. And how everything changes, always.

Even as I start typing this at 7 in the morning, I am amazed how it is so dark, for only 18 days ago the sun was up at this time of the morning. How the leaves changed and the last tomatoes gave up any chance of ripening. I was not the only thing changing. Everything changes. As we seek to facilitate change, we are changed.

Interspersed with this reflection will be personal stuff. Political stuff. It is unavoidable when we travel outside our home territories, to become vulnerable and open to new things. So if you read my blog for the more professional stuff, you may either have to skip these posts, or read them with whatever filter you need.

Part 1 – The Power of Doing TOGETHER

I have been doing work with the Consultative Group on International Research (CGIAR) and the Food and Agricultural Organization (FAO) of the UN for many years. This year, I had the pleasure of doing work for them both at the same time as they collaborated on offering the second iteration of a Knowledge Sharing (KS) workshop some of us developed for the ICT-KM project of the CGIAR earlier this year. The workshop is a three phase online/face to face/online offering focused on learning about choosing and applying knowledge sharing tools and methods in the context of real work. Learn, do, revise, learn, do…. This time we had 35 people from around the world join the workshop with a variety of needs, levels of practice and, as always, time available to participate.

We have learned from similar workshops in the past that the mixing of participants from different organizations has provided some specific benefits. The diversity gets us out of any of our own “organizational ruts.” You know — the things we think we can’t do in our own organizations, the barriers that we feel are always surrounding us. We tend to put those aside when we are with others. The diversity of experience and perspectives opens us up to seeing the work in a new way. What is less-than-useful social “chatter” for one is critical trust building process for another. If we can’t see these things at work in a group, we have a harder time understanding their role in our work. We tend to design knowledge sharing processes based solely on our own perspectives and preferences. When we learn about them in a diverse group, we see them in new ways. This was very present in our online and face to face phases. The diversity does present challenges, but with some persistence and reflection, we can process them as a useful part of the learning. Together.

The F2F workshop was three days of learning about knowledge sharing tools and methods while using them. We spent 1.5 days in Open Space learning about a variety of tools and methods. We used video, audio and graphic recording to debrief our Open Space experience. We broke the ice each day with different methods. We learned together while doing peer assists and Samoan circles. We brainstormed and picked topics with Dotmocracy to Speed Geek about new technologies. It is so hard to really get the essence of these tools and methods simply by reading about them or having them presented. But when you do them, and debrief them afterwards, the learning feels richer and deeper. From the informal participant feedback, this seems to be the case. I’ll be interested to learn more as we do the rest of our post-workshop evaluation.

Debriefing and Crystallizing Learnings

I want to call out specifically the importance of the debrief. After each session which used a knowledge sharing tool or method, we took time to debrief both the experience of the method, how it was facilitated and why it was chosen, leading to a brief discussion of when something may or may NOT be useful. We tried to capture all these debriefs in our wiki notes and blogs, and I hope over the course of the next few weeks, we can weave what we learned in the debriefs into the specific tool and method pages on our shared webbased resource, the KSToolkit. Recently there has been a very rich thread on the KM4Dev (development) email list about capturing lessons learned from F2F events. If you are interested in this topic, take a peek. Look for the posts entitled “Documentation: More than Just Minutes.”

My Key Learnings

  • People make meaning through the construction of their own experience so having a chance to try methods like Speed Geeking and Open Space are important moments, even when we have other constraints which might suggest other methods.
  • Give people ownership of their participation. At the start of the workshop I commented that many people had laptops open. I said I was not going to tell people to close or open them, but that they should make choices about their use of their laptops based both on their own needs and their perception of how their choices might impact others. In other words, we are responsible both for our own actions and to be attentive to the needs and actions of the group. This is right in line with Open Space’s “Law of Two Feet.” At the end of the workshop, a couple of people commented on how important this was for them, and how different from the “usual” where we are told what to do and how to do it.
  • As I noted above, the power of debriefing and shared meaning making.
  • Try to have your workshop close to lodgings. It took a lot of energy to get us from our hotels in Rome out 30 minutes to our meeting location. The location and hosting of our workshop by Bioversity was fantastic, but the travel took a lot of energy that could be used elsewhere. You do what you have to do, but just in case you CAN be close, be CLOSE!
  • I’d like to do more participant “capturing of learning” with video, audio and other media. We did this a bit and I think there is a lot more that I’d like to experiment with.
  • We missed time for people to plan their next steps in their work. Last time we spent too much time on this. This time I think we spent too little.
  • Plan a dinner the night before to start the socializing.
  • When doing Speed Geeking, we did NOT have expert practitioners for each station and in retrospect, that would have been a good idea. I loved that people created useful groups around things they wanted to learn, but I think this mixed up too many things and Speed Geeking might be best with just one intent.
  • Find ways to engage the participants in the facilitation. We did this a bit and I’d like to find more ways to increase others’ chances to facilitate.

Amazing Participants and Co-Facilitators

The joy of work like this is the people I get to work with. The participants of the workshop were diverse, engaged and they didn’t just passively take in information, they engaged and challenged us. And as always, facilitation and learning is not a solo sport, and I want to thank Pete Shelton and Gauri Salokhe, my F2F co-conspiritors, and Simone Stagier who supported from afar.

Soundtrack while writing: the guitar playing of Sungha Jung

Learning from our mistakes

Flicr CC Image from David C FosterMichael Krigsman has a good story today on ZDNet about transparency and learning. He analyzes Amazon S3 team’s After Action Review (AAR) process following a disruption in their service. This reminds me of the importance of learning from failures and mistakes, rather than forgetting or covering them up. In fact there is a whole community dedicated to learning from mistakes, The Mistake Bank. Here is a quick recap of the useful practices Amazon deployed when they had a breakdown in their services. I’ve edited out some of the text so as not to cross ZDNet’s copyright, so click into the story for the full details.

Amazon’s S3 post-mortem demonstrates maturity | IT Project Failures | ZDNet.com
THE PROJECT FAILURES ANALYSIS

In analyzing the failure, Amazon asked four questions:

What happened? The first step to a successful post-mortem is establishing a clear understanding of what went wrong. You can’t analyze what you don’t understand.

Why did it happen? After after determining the facts, the post-mortem team should assess why failure occurred….

How did we respond and recover? … A useful post-mortem depends on the analysis team gaining a reasonable level of honesty, insight, and cooperation from the organization.

How can we prevent similar unexpected issues from having system-wide impact? … Planning must also consider the business process and management responses the team initiates when a failure occurs. A complete post-mortem addresses both technical and management issues.

Amazon’s technical failure disrupted its customers’ business and hurt the company’s credibility. However, their open and transparent response to the failure and its aftermath demonstrates a level of organizational maturity rarely found among Enterprise 2.0 companies.

Pulling our mistakes out and looking with them, alone and with the aid of colleagues, is a simple and effective learning practice. But it takes both a personal commitment to productively looking at our warts (rather than simple self-flagellation or guilt) and an organizational culture that values learning along with success. And we all know it… we learn more from our failures than our successes. 😉

Here are a few resources for learning from mistakes and failures (some repeated from embedded links above, but I want to make it easy to scan for the resources!):

Have any to add? Knowledge sharing in action!

Photo Credit: Flickr/CC

Matt and Nancy blather about slow communities

cc on Flickr by by fatboykeWe missed our partner in crime – er- podcasting, Ed (how can life interfere with our podcasts! Alas!) but Matt Moore and I had a fun time yesterday as he recorded our conversation about Slow Communities . We rambled for about 20 minutes, then finished.

Afterwards I said – hm, we didn’t get to any practical ideas about what to DO about volume and speed, and how to be discerning about when to go fast or slow. Matt suggests sending us postcards! 😉 I am copying the whole post here… hm, is that rude of me? I want to annotate the timestamp notes, and this seemed the most efficient way.

Nancy has been writing & talking a lot about “slow community” recently – video, slides & post here & here. Sadly Ed Mitchell couldn’t join us as planned (but we’ll nab him again in the future).

One thing we didn’t tackle in the podcast was the matter of practical tactics: What should community members & coordinators do?

Answers on a postcard please…

Download the mp3

00:00 – Nancy’s conversations about slow communities
03:30 – Matt’s fast community anecdote
* N’s note: what to do/how to respond to unrealistic expectations about speed of community building and expectations of learning through reflection if you don’t take time to reflect!
06:00 – When is slow appropriate?
* and for whom and how do we know if my slow is your fast?
06:30 – The importance of sustainability
* hm, and now that I think about it, also scalability. Is “community” generically scalable? I don’t think so. Does it have costs to sustain? Yup. Are the benefits sufficient and are we willing to pay the freight?
07:15 – Fast is good for social media experiments
* and brainstorming, iterative design, and getting the chores done…
08:00 – We need to learn & reflect
* do leaders role model reflection and learning?
10:30 – Rhythm, pausing & athletics
* I want to dive deeper into this “rhythm” thing…
12:15 – Organisational seasons & hurricanes
14:00 – More is not necessarily better
15:30 – Community obesity
* Oh, I LOVED this one. A Matt Moore gem, for sure. Also Infoluenza…
* Matt forgot to include “community and network speedometers” — what does making the pace visible do to our awareness and subsequent choices/behaviors? A feedback mechanism showing me how many emails I have read/written, groups responded to, blog posts, tweets… and time spent on them? Dunno?
* Multimembership
* How many relationships… and what is the depth/quality of those relationships
17:00 – Networks & communities
* are networks fast and communities slow? I don’t think that is quite it, but something is there…
18:00 – Admitting that you have a problem
* Moi?
20:00 – Mindfulness & self-awareness as critical skills
* It is almost impossible to micromanage in many of our current environments, so self management becomes a critical skill and practice
22:30 – Nancy applies the brakes with meditation
24:00 – What do we really need?

Photo credit, Flickr, CC

view photostream Uploaded on July 14, 2008
by fatboyke

A spot of reflection – shifting from me to we

Dog in the Windo

Window Dog

The dog days of summer are here, and I want to be outside on these glorious, sunny Seattle days. With a long wet winter, we tend to be hyper aware of the magnificence of our Pacific Northwest Summers. Right now there are raspberries and strawberries ripening in my garden. Flowers. Compost to be turned, potted plants luxuriating outside, needing water. The last two days I was up on Whidbey Island, about an hour north of Seattle, sitting on a deck overlooking the water and being blissfully quiet.

Where is the reflection on my work? On my practice. For the most part, right here on this blog. So I wanted to share some of the things I’m thinking about. Today’s is about the shift from me to we.

For the last two weeks I’ve been peeking in and participating peripherally in the South African online event, e/merge. Here is a bit about e/merge for context…

e/merge 2008 – Professionalising Practices is the third virtual conference on educational technology in Africa and builds on the e/merge conferences in 2004 and 2006. e/merge 2008 will take place online from 7 – 18 July 2008 and may include associated face to face events in a number of cities. The conference is primarily designed to share good practice and knowledge about educational technology innovation within the further and higher education sectors in the region, as well as to strengthen communities of researchers and practitioners.

I have been a part the first two e/merges (2004 and 2006). In 2006 we ran a little online facilitation workshop within the event and that was what Tony Carr and I were going to do this year. But through a nice accident, we both were overwhelmed and decided to shift gears to something both simpler and emergent. We decided to host three chats during the two week event around the facilitation of the event, asking the event facilitators and hosts to join us with their thoughts and observations. IT offered not only a simpler structure, but it would provide a little bit of time for reflection within the event. Wow, slowing down!

The chats attracted the event facilitators plus other participants and have been FANTASTIC. The open format with a loose theme somehow created a safe, warm and humorous place where I felt the shift from “me to we” each time. In our last chat today, we talked about how we pay attention to and invite that shift from me to we. Some of the triggers people noticed include:

  • Being acknowledged as a contributor (in a reply, summary, etc.)
  • Getting comfortable (posting, the technology, the people)
  • Having enough space to establish an identity, then letting that go

How do you invite this transition from me to we in your facilitation, online or off? Can you share a story of when you felt or experienced this shift?