Learning

Boundary jumping!

“Encounters between people who are very different from each other but prepared to trust and cooperate are where the interesting stuff happens.”

Lynda Gratton

One of the most useful and thought-provoking ideas I have come across recently is the idea of what I call boundary jumping. In a recent book Lynda Gratton refers to “jumping across worlds”. In Debra Ancona and Henrik Bresman’s book X Teams they suggest that highly successful teams “manage across boundaries” and focus at least as much attention on external activities as they do on internal team dynamics. Recently I also undertook accreditation in Cognitive Edge methodologies during the course of which we dug quite deeply into the dynamics of what happens at the boundaries between the simple, complicated, complex and chaotic in organisational life.

Lynda Gratton is based at the London Business School and has been researching and writing about individuals, teams and organisations relationship to work for over thirty years. In her most recent book, entitled Glow: How You Can Radiate Energy, Innovation and Success she tries to describe the most significant characteristics of the people she and her fellow researchers have encountered when they have been investigating highly successful teams. Most of the book, frankly, seems to me to be a bit of an exercise in stating the obvious and runs the risk of being taken as a readymade recipe for success.  In the section on “jumping across worlds” however she uses a simple illustration to make what I think is an important point. She says:

“… when your work is complex – as it often is – then cultivating diverse networks trumps staying close to your own group who are similar to you.”

She illustrates this by suggesting that in any given situation each of us will bring our own set of heuristics or rules of thumb. That is our own unique perspectives, ways of seeing and interpreting, of generating solutions or ways forward and of anticipating what we think will happen next. Gratton argues that the number seven here is significant as there is evidence to suggest that this number plus or minus two is about the limit of the number of ideas, heuristics etc that people can effectively hold in head and use. So my heuristics, as we begin a conversation in which we seek to work out what actions to take next, might be:

A B C D E F G

On the other hand yours might be:

C D E F G H I

When you and I come together in this conversation to negotiate what we will do and//or account to each for what we are doing and generally work out how to “go on” together in a certain direction or towards a certain end, we will have five shared heuristics and each of us will bring two unique heuristics (at least for this situation). I’ll bring A and B and you will bring H and I. The simple point of course is that the more perspectives or possibilities we have to work with the better. The fine print, of course needs to say that, at some point, if there isn’t enough similarity, it’s going to be very hard for us to work together. The question naturally arises, then:

What do we do when we do this – when we collaboratively negotiate and account to each other about joint action?

Recent research and thinking in a range of fields: ethnomethodology, conversational analysis, and social constructionism suggest some possibilities.

  1. As we communicate for a purpose we both value and “take” turns to speak. This isn’t always sweetness and light, however. Often we need to compete for a turn and are forced to “construct” and negotiate rights and obligations in this process. We make turns for ourselves by asking questions, seeking advice, clarifying issues, expressing opinions and so on.
  2. As we take our “turns” in communication we naturally have expectations of each other. Significant among these expectations is the anticipation that as the communication goes back and forth the responses will bear some relation to and association with what was said previously. We also expect others to display a level of competence and reasonableness in their communication. Ultimately we hold each other morally accountable for our actions. This is as true of our communicative action as it is of any other. If we can find no relationship between what we said and the response from another then effectively there is no meaning in the exchange.
  3. Some of the structure that we can recognise in communicative action seems to be a product of the patterns of categorising, segmenting and sequencing that emerge in and through the process itself. We categorise people and their rights to involvement in the conversation, we sequence the flow of conversation around a particular topic based on what are termed “adjacent pairs” – question and answer, request and response, invitation and acceptance and complaint and response. Much of this patterning of categorisation, sequencing and segmentation opens up questions of the power dynamics of particular conversations.
  4. In communicative interaction we also use what might be termed “rhetorical devices”, as another way of responding to each other and linking our practical activities. So we might use “directive” or “instructive” forms of expression to advocate for a particular way of going on together. These “rhetorical device” articulate our noticing of and draw the other person’s attention to, aspects of their speaking and make reference to their context. We agree or disagree, we sympathise or fail to do so and so on, through not only the content but also the form of our speaking.

So, what is practical in all of this?

Three things I suspect:

  1. Firstly the simple reminder that we all, most of the time, come to everyday communicative interactions each with a more or less varied set of operating heuristics and that there are advantages (that can be amplified) and disadvantages (that can be damped) to this.
  2. Secondly the recognition that the way in which we engage in communicative interaction is so much a part of what we do (our practice as people working in organisations) that we are largely unaware of it. But it is something we can be more attentive to.
  3. Thirdly, as a starting point we can be more attentive to particular aspects of our communicative action:
    • How we take turns in particular conversational settings.
    • What we anticipate as appropriate responses and what we do when that doesn’t happen.
    • How our conversations are sequenced.
    • How we categorise people in particular settings and how that patterns the sequencing and segmenting of conversations.
    • How we make use of particular rhetorical devices and what impact that has.

It seems highly likely that just by paying attention and noticing we will change what we do and how we do it and, of course, that could have a ripple effect.

  1. Reblog this post [with Zemanta]

PublicSphere – Government 2.0

Web2.0 mosaic

All tools have intrinsic politics and technology is the tool of now.

Godfrey Reggio

On Monday I attended the PublicSphere Government 2.0 conference hosted by Senator Kate Lundy at Parliament House. I went along because I have recently become interested in how Web 2.0 tools might be helpful in supporting engagement within and between government agencies. I was also interested to experience a conference/meeting that was organised in this way: 150 participants in the room, others watching the live stream from all over Australia (at least), lots of speakers giving 15 minute presentations, live Twitter and blog feeds up on the screen as people spoke. Mark Schenk from Anecdote pretty well summed up my (mixed) reaction in a post on their website on Tuesday. Here’s what he liked and didn’t like with a few square bracketed editorial comments from me.

He liked:

  • 15 minute presentation format – this forced [most] speakers to have a few clear messages
  • The diverse technologies available meant there was something for everyone [but the organisers apparently learned a lot about getting reliable wifi access in somewhere as secure as Parliament House and people trying to watch the live stream from behind organisational firewalls were quite frustrated]
  • Meeting some very interesting people [yes!] and catching up with some people that I haven’t seen for ages
  • It was very well organised and all up it ran pretty smoothly [but perhaps wasn’t as well designed as it could have been]
  • Seeing the passion in Kate Lundy’s eyes for getting this stuff happening [and listening to the enthusiasm among speakers and participants for the opportunity this presents to enable more people to have more of a voice]

He didn’t like:

  • The constant stream of presentations with no provision for discussion. It appeared that the organisers thought that electronic interaction via twitter and commenting on the live blog obviated the need for people to speak to each other. Exacerbating this was the preference for eating into the few breaks to make up time.
  • Realising that he couldn’t cope too well with the multiple inputs while attempting to build a mind map of things that resonated (and watching others appear to handle it with ease) [I was merely trying to take notes and watch the Twitter feed]. He did learn a lot about twitter on the day. [I learned a lot about my own struggle to pay attention to multiple inputs!]

When I sat down to write this post I had in mind that I wanted to say something about the tools we use and how they enable and constrain at the same time. This was a conference format that enabled vast amounts of information and comment to be “transmitted” very quickly. For me it was a fascinating example of a “polyphony of unmerged voices”! One of the gurus (apparently) of this kind of stuff, Clay Shirky author of the book Here Comes Everyone talks about publishing first and filtering second. This conference was a wonderful example of that. Lots of people speaking at once, using whatever location and medium they found easiest – on the understanding that they would individually and collectively then find a way of “making sense” of what was said later.

This TED presentation from Clay Shirky sums it up pretty well for me:

Do I think this Web 2.0/Government 2.0 stuff has potential to change the way we work. Absolutely!

Will it be easy? Absolutely not!

Like all tools these ones aren’t easy, they are no more of a silver bullet than anything else and there is the usual risk that people will be tempted to throw the baby out with the bathwater.  But they clearly provide ways in which more voices can be engaged and they clearly can enable us to do our own sense making before, during and after the event. As such then they provide an interesting way of maintaining multiple conversations across time and space.

Reblog this post [with Zemanta]

The “Point of Contact”

Rock climbers in Yosemite National Park
Image via Wikipedia

“Not knowing what to do, we start to pay real attention.”
David Whyte – The Three Marriages

In his most recent book The Three Marriages: Reimagining Work, Self and Relationship poet and management consultant David Whyte tells of a time in his life when he was teaching rock climbing. He describes the way in which it seemed to him that everyone who was a beginner was bound to put their foot on the rock face in such a way that it was almost inevitable that they would slide off.

Reading his description it seems clear that people really struggled to orient themselves to the mountain, and more specifically to the small piece of it they were climbing, in a way that felt unnatural. Surely in order to be safe from falling the best place to be is as close to the rock as possible? What David points out is that this puts your feet at a downward angle and thus makes it all the more difficult to maintain contact with the mountain. More importantly, it makes it difficult to have a “point of contact” that is secure enough to push off from.

Here is how he generalises the idea of a “point of contact”.

“The point of contact is what allows us to take the next step. Sometimes the point of contact is through the next necessary small task completed; sometimes it is through understanding the depth of our exile, the disenchantment experienced in the here and now, the impossibility of it all. Eventually we realise that not knowing what to do is just as real and just as useful as knowing what to do. Not knowing stops us from taking false directions.”

I really like this metaphor because it reminds me of the need to slow down and of the variety things that I could do when I next find myself, a team I am in or a whole organisation drawn to move forward but unable to know where to go and what to do next.

What follows isn’t an exhaustive list, nor is it in any particular order. It is simply what has occurred to me in this moment.

  • I could pay close attention to where I am and what is going on in the landscape that is my work or my life?
  • To do this I could heighten my attentiveness, especially to those things that are familiar.
  • I could ask myself – does this way of thinking or doing still work for me?
  • I could ask myself – what kind of a challenge it is that I’m facing? Is it, for example, a challenge based on the need to:
    • Understand and work with competing commitments or a contradiction in values?
    • Cultivate new capabilities?
    • Transition from one pattern to another?
    • Protect and sustain something that is at risk?
    • Do something that I’ve never attempted before?
    • Respond quickly in a time of crisis?
  • I could “Hug the Bear” – walk straight at that which scares me most and embrace it for what it will teach me.

The reality is, of course, that each person, team or organisation’s “point of contact”, the leverage they need to move forward (onward and upward if I stick with the mountaineering metaphor) is unique.

This reminds me that I won’t necessarily find that point by rushing about, by doing only what feels safe or by repeating existing patterns. I will find it by paying attention to all that is around me and discovering something that is already there, but which I have not yet noticed.

Reblog this post [with Zemanta]

“Everything we do is subject to error.”

If you have been following what I have been writing recently you will be aware that I have been reading Mary Catherine Bateson’s book, Peripheral Visions. I’ve also been thinking a lot about the practical ways we can proceed when we can’t predict with any certainty what lies ahead or when the landscape around us that sets the context for our work, is uncertain and changing rapidly. This extended quote from the book pretty well sums it up for me.

We are engaged today in a rapidly improvised mortal dance with our planet, in which we have to work out ways of protecting the natural environment without full information – without, for instance, certainty even of the degree or significance of global warming. All behaviour has potential impact. It is not possible to sit on the sidelines, saying, I can’t dance. Our dealings with the planet have always included actions taken before the results could be predicted, and this is unlikely to change, in spite of the achievements of science. Rather than assume everything could be mapped out beforehand, we might be do better to develop rapid and fluid styles of midcourse correction. Little that we do is without risk, but not all risk is culpable. Assuming that all risks should be controlled in advance may lead us into danger rather than the reverse. Everything we do is subject to error.

Mary Catherine wrote these sentences sometime in the 1990′s. How easily they could apply now to the “global financial crisis”. Equally they are recognisable in relation to all sorts of complex, adaptive challenges.

What I’m noticing quite a lot though is a sort of paralysis as people wait for “leaders” to tell them what to do. As well, many managers, and policy makers still seem to be trying to map things out in detail beforehand and eliminate the risks. When they can’t do this with confidence they often freeze – feeling as if they cannot act, because the risk of moving forward is too great.

The development of a practices that allow for, and indeed facilitate “rapid and fluid midcourse correction” seem to me to be not just a good idea but absolutely essential if we are to tackle some of our bigger challenges.

But what might this kind of practice look like?

Here is one idea. Last night I watched NCIS with my kids. (My apologies to those who aren’t regular viewers!) As part of the quirky character development in the show Tony (not usually the “boss”) was put in charge of the case. When they got stuck or things got tough he called a “campfire”. Everyone wheeled their chairs into the middle of the office and they figured out what to do next.

This reminded me of something I read recently about agile processes in software development call the “scrum”. It goes something like this. A team (the originators of this process recommend 7 plus or minus 2 people as particularly workable) is formed to tackle a particular development task or project. Each month the team meets in a “scrum” and decides what work it can achieve in the next “sprint” (30 calendar days). A “daily scrum” takes place in which the team members do what the developers call “synchronisation and status exchange”. Otherwise the team is left to self-organise. Here is how they describe what usually happens

… as the team realises it has the full responsibility to do whatever it deems necessary, a sense of liberation and empowerment (that usually trite phrase) occurs. The team start talking, drawing designs on whiteboards, figuring out what work needs to be done. People start defining what work they’ll do, and what help they need to do it. Some people ask to do work that they’ve always wanted to learn, signing on for additional work to offset their learning curve. The team collectively simmers, brainstorms and works to meet its commtments.

Here’s the bit that struck me as intensely practical. The daily scrums are designed to last no longer than fifteen minutes. In that time everyone answers three questions:

  1. What have you done since the last daily scrum?
  2. What will you do between now and the next daily scrum?
  3. What’s getting in the way of you doing your work?

As a way of reflecting on this you might like to pay attention, over the next month or so, to how long goes by before your team considers these questions. You could also test what happens if you inject those questions, or ones like them into your conversations at more frequent intervals.

If you are interested in reading more about the SCRUM idea go HERE.