Does Social Networking makes your brain grow?

With thanks to Rob Cubbon http://robcubbon.com/sync-up-your-social-media-and-increase-your-tweets/ Ten year ago, we were hearing that London Taxi drivers have an enlarged hippocampus because of their encyclopedic (or should that be atlassian?) knowledge of London's roads.

Now the same research team in UCL are questioning whether social networking has a similar impact although the researchers do confess:

It's not clear whether using social networks boosts grey matter or if those with certain brain structures are good at making friends.

...so perhaps slightly cyclic reasoning?

I've wondered for a while whether we have a finite "namespace" in our brains, and once it's full (see why I didn't make it as a neuroscientist!), it starts to overflow and we forget people's names.

I can testify that changing my work relationship pattern from a single slowly-evolving large corporation to short assignments in 100 client organisations over the last 6 years has certainly helped to fill it up. My wife reports similar name-overflow challenges working a supply teacher.

Or perhaps it's just that we're just getting older!

Knowing, Telling, Writing, Acting.

I've had a couple of workshop events with clients in recent weeks where we have gone back to some of KM's first principles, using some foundational quotations. Polanyi's "We know more than we can tell" is a great one to explore, and I like David Snowden's build "..and we tell more than we can ever write down".

When it comes to KM having a real business impact though - actually changing something to generate value and/or create improvement - which after all, is the reason we do KM - then I think it's incomplete.

I'd like to add a third part to the picture (if I might be so bold as to stand on the shoulders of giants).

So here's the first viewing of a Polanyi/Snowden/Collison triptych.

We know more than we can ever tell,

we tell more than we can ever write down,

and we write down more than we ever act upon.

Posters. Yes, posters. Surprisingly effective social media!

Sometimes I come across organisations which have a way of working which naturally encourages the sharing of knowledge – so naturally, in fact, that they don’t realise that the way they operate is different from most other companies.

Posters – perhaps the most effective (and overlooked) social media?

I spent most of last week with a knowledge-friendly Swiss company which has developed a “poster culture” over the past 5 years.  Corridors, office walls – pretty much every piece of available  wall-space has a poster describing a project, initiative, programme, summary of an event, description of a team and its responsibilities.  Every corner you walk around, you pause and think “hmmm, that’s interesting!”.  They prompt interaction and conversation.

It’s a surprisingly simple low-tech thing, but it goes a long way to helping people discover what’s going on. No surprises. No closed doors.  It puts clear labels on the silos. (see my earlier post – “in defence of silos”)

The same company ran a workshop/conference to update the group on progress on several projects. Rather than using PowerPoint, went to the trouble (and expense) of producing large posters so that people could be walked-through their story.  I joined the groups who were circulating between different poster sessions, found myself reflecting on the dynamics.

Yes, in many cases, the posters looked a lot like several PowerPoint slides arranged side-by-side.  But even where that was the case, as the reader, I was still in control of which ones I read.  Whilst the presenter was talking, I could still flick my eyes back to the material she had just covered, and get a sense of what was still to come. If she’d showed me exactly the same slides, but in the more conventional linear sequence, projected on a screen, driven by the presenter - it would have been different – and I would probably have lost the plot.  In the poster environment, I had more control over my own journey through the story.  Pointing and asking “could you just clarify what you meant in that bit”, is much easier than interrupting the flow with “could you go back 4 slides – I think it was 4, perhaps 5 – no one more...”

In other cases, the poster-makers took full advantage of their canvas, and drew timelines, rollercoasters and journeys to illustrate their talks, and provided pockets of depth and detail in parts of the poster.  You just can’t do that with a conventional 4x3 slide.

Did it cost more?

Yes – $100 per poster – and large posters are unwieldy, require space and take time to put up.  Most companies don’t have 2A0 chart-plotters/printers in house – but don’t let that stop you.

Did it add more value?

Disproportionately yes, I would say.  Spend the money.  Plant some trees to offset the extra paper. Revel in the fact that you don't have a projector in the room.

Did it make best use of the knowledge in the room and encourage dialogue?

I hardly need to answer that.

Yes.  After my poster renaissance moment last week in Switzerland, it’s a +1 from me for this form of social media.

In defence of silos

Are we being too hard on silos? I regularly hear clients describing their workplace as being siloed. It’s common in public, private and third sector.

Sometimes people mean that their organisation is structured in silos.  Sometimes they mean that their information is managed in silos.  Sometimes they mean both.

As KM professionals, we can be a bit militant in our language when it comes to silos.

They have become our public enemy number one – we need to demolish silos, tear silos down, break silos up, eradicate silo working...  you get the picture!

A wise leader once challenged me with a simple question.  I was being evangelical about knowledge management, sharing and networking and painting a picture of how the company could be different if it was restructured with knowledge in mind. His thoughtful response was:

“That sounds really good Chris, but can you also tell me what we would lose?”

It’s easy to slip in to a mindset whereby we view our organisations as completely dysfunctional, and “only radical KM surgery can save them”. Of course that’s never true – and raises the dangerous prospect that in our quest to find knowledge-enabled improvement, we fail to recognise what’s good and working well, and how our actions can impact that.

So is the presence of silos always a bad thing?  They seem to work well for managing grain! Are there areas in your organisation where you need to collect, protect, store, securely develop, and preserve things of value for future use by others?

Perhaps it’s not the presence of silos which is the real issue, it’s their invisibility, anonymity and unnecessary impenetrability! The problems arise when people don’t know where the silos are, whether they are empty or full, how to access the content and who is working on them.  In which case, there will be times when smashing them down isn’t the solution.  It will be more appropriate to discover and  recognise them, map their existence, understand their contribution, check that there’s no duplication, open them up for access and/or contribution by others (inside and outside?) and finally  to communicate how others can get the benefits.

Here’s a quote from the Organisational Learning Strategy at TEAR Fund, who I had the pleasure of working with earlier this year.

We have a great deal to learn from each other across teams and groups, and so we need to reframe the idea of breaking down our silos, to one of opening them up.  We should be continually finding ways to build bridges between and within our teams and groups.  Silos are used to store grain, and our groups and teams need to nurture their learning, and then communicate it with others.

I think there's much more than a grain of truth in that.

Fifteen minutes of.... Reflection.

I secretly love the moment when the air stewardess utters those magic words:

"as we prepare for take-off, please turn off all electronic devices..."

 

Actually, I think the whole plane breathes a collective sigh of relief. Fifteen minutes of enforced separation from the electronic world of work.

Fifteen minutes at the downtime oasis between the instant your iPhone/Blackberry goes off, and the moment your laptop is allowed to be switched on. We're so always-on, info-stimulated, response-charged that it's a bit of a shock to the system. Once I've leafed through the in-flight magazine and perused the safety card, I confess I sometimes find myself nodding off!

Fifteen minutes. That’s the time typically allocated for After Action Reviews (AARs), at least for informal AARs, pioneered by the US Army and now a widely used knowledge management approach. Let’s take a deeper look at this classic, simple process and see why it provides such a welcome quarter of an hour of reflection and learning for a team.

Firstly, the name can create a level of confusion. Informal AARs take place immediately after an event or activity and are designed to provide a safe, honest, space for a team to review performance and identify the learning. In that respect, they are really a tool for learning-whilst-doing. You wouldn’t use this kind of AAR to review a major project in order to generate detailed narrative, lessons and recommendations for the next team. There are other KM methods in your toolbox for those situations – such as Project Reviews, Retrospects and Sensemaking techniques.

The climate for an AAR is important. The US Army describe those fifteen minutes as a “rank-free zone”. University College London’s “Learning Hospital” (to be featured in a future edition of Inside Knowledge), which is training hundreds of its staff as AAR facilitators describe the technique as making it possible to “speak the truth to power”. The ubiquity of AARs in the hospital make it safe for a junior technician to comment on and challenge the actions of the most eminent surgeon, because everybody understands the need for a climate of honesty when patients’ lives are at stake.

Having clarified the name and the climate, let’s take a look at the four simple questions which comprise an AAR. Simple enough to be remembered without a crib-sheet, and familiar enough that people know exactly where they are in the process.

AAR - 4 simple questions
AAR - 4 simple questions

Question one:“What was supposed to happen?” focuses on the facts This may sound surprising, but sometimes it can be difficult to even get agreement on the answers to this question!

Question two: “What actually happened?” – the US Army calls it “ground truth” – again, this is purely a statement of facts about what happened – not an exchange of opinions. Sometimes there are unexpected, positive things which happen in addition to the expected outcome – note these down too, as you might want to repeat those elements in the future.

Question three:“Why was there a difference?”. This is the time when the team can move from stating facts to giving their opinion as to the reasons for any differences; the facilitator uses the time wisely to ensure that contributions are made from as many team members as possible, and discussed where necessary.

Question four: “What can we learn from this?”. This is the most important question, as it is the one most likely to identify what needs to change. It moves the team from reflection to action, and make a difference to the next time they attempt a similar task.

So that’s it. Four simple questions, addressed rapidly by the team with the facilitator (a team member) capturing a brief record on a flipchart to keep the focus on shared opinions and actions. All in all, a straightforward technique. The power of AARs comes in the structure; the slowing-down effect of the four questions. Let’s face it, as intelligent professionals, we like to think we have a pretty good idea about what the learning points are, even before we’ve discussed it. AARs are designed to stop people just like us from bypassing steps i, ii and iii and jumping to conclusions as to what the learning was, without having verified that there is agreement about what actually happened.

In our always-on world, where we re-tweet things around the globe before we’ve even read them, and connect with people we barely know – fifteen minutes to slow down, reflect and think – together - is invaluable. Now... where did that duty-free magazine go?

Taken from the Consulting Collison column in the next edition of Inside Knowledge

Speed Consulting

Have you ever wondered what it would be like if you combined speed dating and knowledge-sharing? I can’t own up to any firsthand experience of the former, but I’m told by friends who do, that you participate in a merry-go-round of three-minute exchanges on a room full of tables-for-two.  When the bell rings you move around to the next person.  If you like what you’re experienced, you make a note on your score-card, and, if the feeling was mutual, you take the next steps together. Tremendously efficient and less emotionally risky than the traditional approach - at least for most people!

To save a praying mantis experience, there are websites full of interesting questions that you might ask during your 3 minutes – for example:  “What luxury item would you take on a desert island?” and “What are your favourite words and why?”. Incidentally, “knowledge management” is not a good answer to the second question. So if speed-dating is designed to reduce the emotional investment, embarrassment and risk of failure  of finding a potential partner – what can we learn from that room-full of tables which we could apply in a KM context?

In my work with communities of practice and networks over the years, I have observed that when someone asks a question in a network, people are sometimes reluctant to offer up suggestions and ideas because they don’t have a complete answer or a polished response.  The longer the silence lasts, the more risky it feels to contribute.  People hold back, worried that they might be the only one to respond and that their idea will be perceived as being too trivial or too obvious – how embarrassing! If your community feels like this, and you have an opportunity to meet face-to-face, then let me recommend a simple “Speed Consulting” exercise which can help groups to break these bad habits.  (I’m indebted to my friend and consulting colleague Elizabeth Lank for introducing me to this technique).

A quick guide to speed consulting.

Identify some business issue owners In advance, identify a number of people (around 10% of the total) with a business challenge which they would like help with – they are to play the role of the client who will be visited by a team of brilliant management consultants. Business issues should not be highly complex; ideally, each issue could be described in 3 minutes or less.  Brief the issue owners privately coach on their body language, active listening, acknowledgement of input etc.  Remind them that if they are seen to have stopped taking notes (even when a suggestion has been noted before); they may stem the flow of ideas.

Arrange the room You need multiple small consultant teams working in parallel, close enough to generate a “buzz” from the room to keep the overall energy high. Round tables or chair circles work well.  Sit one issue owner at each table. Everybody else at the table plays the role of a consultant. The issue owner will remain at the table throughout the exercise, whilst the groups of “visiting consultants” move around.

Set the contextExplain to the room that each table has a business issue, and a team of consultants.  The consultants have a tremendous amount to offer collectively – from their experience and knowledge - but that they need to do it very quickly because they are paid by the minute! They have 15 minutes with each client before a bell sounds, and they move on to their next assignment. The time pressure is designed to prevent any one person monopolising the time with detailed explanation of a particular technique.  Instead, they should refer the issue owner to somewhere (or someone) where they can get further information.  Short inputs make it easier for less confident contributors to participate.

Start the first round Reiterate that you will keep rigidly to time, and that the consultants should work fast to ensure that everyone has shared everything that they have to offer. After 15 minutes, sound the bell and synchronise the movement to avoid a “consultant pile-up”.

Repeat the process Issue owners need to behave as though this is the first group and not respond with ‘the other group thought of that!’. They may need to conceal their notes. Check the energy levels at the tables after 45 minutes.  More than three rounds can be tiring for the issue owners, but if the motivation is particularly high, you might manage 4 rotations.

Ask for feedback and reflection on the process Emphasise that the issue owners are not being asked to “judge” the quality of the consultants!  Invariably, someone will say that they were surprised at the breadth of ideas, and that they received valuable input from unexpected places. Ask members of the “consulting teams” to do the same. Often they will voice their surprise at how sharing an incomplete idea or a contact was well received, and how they found it easy to build on the ideas of others.

Transfer these behaviours into community life Challenge them to offer up partial solutions, ideas and suggestions when a business issue arises in a community.  Having established the habit face-to-face, it should be far easier to continue in a virtual environment.   The immediacy and brevity of social media helps here – perhaps the 140 character limit in Twitter empowers people to contribute?

So perhaps I should have just tweeted: @ikmagazine http://bit.ly/speed_consulting boosts sharing in communities #KM @elank and waited to see what my followers would respond with! To be published in the next edition of Inside Knowledge.

KM Tools: Creating a River Diagram...

I'm often asked to explain what a "River Diagram" is, and how they can be used to shape knowledge management strategy, and as a way to help communities share and learn.  Geoff Parcell and I wrote a couple of chapters in "No More Consultants", but some how it's one of those topics always has me grabbing a sheet of paper, a whiteboard or a napkin to work through the steps in a more visual way.I'm sure that the guys at Commoncraft will do a great job on it one day...

So for now, in the spirit of vlogging, and with thanks to Geoff for the use of his green screen, here's a quick YouTube tutorial on "How to Create a River Diagram".

Preserving knowledge. Jam tomorrow?

Have you ever been given a pot of homemade jam?  (Jelly to my American readers!) Perhaps you won some as a prize on the tombola stall at a school fair, whilst secretly hoping for that champagne bottle?

It usually comes in a recycled jar, carefully labelled by hand – often in the spidery handwriting of somebody else’s Aunt Agatha.  If you’re anything like me, you’ll smile dutifully, and put it away in the dark corner of a kitchen cupboard for a few years.  One day you’ll rediscover it, and put it straight into the bin (or if you’re unscrupulous, offer it to the tombola stall at the next school fair).

The trouble is, I don’t know Aunt Agatha.  I’m sure she’s a very nice lady, who thought she was doing a wonderful job of preserving those blackcurrants for the future.  However, I have no idea about her jam-making prowess, whether she thoroughly checked the ingredients for bugs or mould – or whether I’ll I reach the bottom of the jar and discover her false teeth. No thank you.  I’d rather stick with a new pot of Bon Maman™ from the supermarket.  I like it, I know exactly what I’m getting, and I can return it if there’s a problem. You know what the truth is?  Don’t tell her, but as much as she loves to make it, nobody ever eats Aunt Agatha’s jam... We’re in the throes of a global recession, and on the edge of some pretty severe job reductions, particularly in the UK public sector. As this becomes a reality, I have no doubt that many enlightened but embattled managers will recognise implications for corporate memory, and look for “knowledge harvesting” solutions.  This is where alarm bells start ringing for me.

Why the alarm?  Well, I fear that management consultants and KM specialists can give false hope to organisations, and in the worst cases, prey on the fears and insecurities of managers.

“Don’t worry – we’ll interview all your key members of staff, and give you a nicely packaged product on a memory stick which represents each person’s knowledge, experience, relationships, favourite references etc.  You can relax – your worries are over.  The corporate knowledge is safe for future generations.”

In ‘Learning to Fly’, I described these kind of personal knowledge capture activities as “knowledge salvage”.  I’m speaking from experience, as a consultant who has tried these techniques, and as a former corporate employee who has used them.  Yes, there are some practical steps you can take in an emergency situation for a key individual small number of retiring staff - but you need to recognise that it’s a damage limitation exercise at best.  All is not lost – but most of it is.

No matter how skilled and prepared the interviewer is, no matter how much you involve colleagues and networks in formulating the questions and iterating the content, no matter how slick and media-rich the final product is, and no matter how much you can persuade the “survivors” to actually use it...  it’s a salvage operation.

Large scale downsizing is brutal.  Surgery is usually carried out with a blunt instrument and valuable knowledge will be lost forever. Fact. I think it important that we face up to the limitations of KM, and manage expectations.

We know how it works.  After a painful period of reduction and redundancy there is a period of adjustment as things begin to stabilise and the downsized world becomes a reality.  After a couple of years management attention will turn back towards future growth  - at which point the organisation will usually  look to the outside for transformational leaders with fresh thinking to begin its new chapter. Doesn’t that sounds more like a future taste for Bon Maman™, and less likely that a jar of Aunt Agatha’s 3-year old preserve will be savoured?

So what should we do when faced with downsizing on a large scale?  Nothing at all?  Just let that knowledge walk out of the door carrying its redundancy package?

I’m not saying that - but I do encourage a healthy dose of pragmatism.

  • Don’t structure knowledge around an individual.  In two years time, nobody will remember who they were, what they achieved or which context they were working in.  Identify which topics are critical to continuing current operations.  Capture any key points against these topics. If you come across a memorable story or anecdote which illustrates the point, then take note of it.
  • Focus where knowledge is technical or procedural, and can be captured as guidelines, checklists and recommendations.  Embed these in a process or policy if you can.
  • Pay attention to ‘know-who’, but remember that you can’t capture a relationship – all you can do capturing contacts and a small amount of background context.  Relationships will have to be re-built from scratch by the new job-holder.
  • If the pace of the downsizing allows it, place the emphasis on knowledge transfer methods to staff likely to remain.  Examples include the use of future retirees as mentors, buddying, shadowing and participation in communities of practice.
  • Work with HR to find creative ways to remain connected to leavers. It might be better to divert that knowledge retention budget towards securing ongoing knowledge access.  The ability to access an alumni network, or to have a timely telephone call or meeting with a former employee will  easily outweigh the effort required to anticipate all possible questions, capture the answers up-front and bury them in SharePoint.

Above all, challenge yourself with the question:  “If this knowledge is important to the future, what is the best can I ensure that it’s actually used?”.  That will stop you, or your consultant, from getting too carried away. I don’t believe that you can be a meticulous corporate historian and an effective corporate strategist at the same time; you’ll only end up in a jam.

With apologies to Aunt Agatha.  Taken from my upcoming column in the next edition of Inside Knowledge.

BP Oil Spill, Knowledge Management and HBR

Tom Davenport posted an interesting blog in the HBR site this week, entitled: If Only BP Knew Now What it Knew Then where he asserted a relationship between the BP Oil spill, and the reduction of its knowledge management programme.

It's something which Geoff and I have receive many questions on, so I thought it might be helpful to cross-post our responses to Tom's blog here:~

As the other author of “Learning to Fly”, let me add to what Geoff has written, which I agree wholeheartedly with.

It’s been desperately, desperately sad to see the unnecessary loss of life. Tragic to see the environmental impact. Shocking to see the commercial impact. Disturbing, yet understandable, to see the media, political and public reaction.

Being good at knowledge management doesn’t make you immune from making a poor decision, but being put on a pedestal for long enough can give you vertigo. I’m sure Toyota, another veteran of Knowledge Management would agree. As Larry wrote – all that any of us can do is work to improve the odds. I believe that BP’s knowledge management and organisational learning efforts have diminished in recent years, and what was once an almost instinctive culture of learning and sharing between peers has become diluted. I think Tom’s allowing himself some poetic licence in his use of the word ‘relic’, but I don’t disagree with the thrust of his argument. Like Geoff, I’ve been away from BP for too long to offer an informed view as to how much sharing and learning was going on around its operations at the time of the events in Tom’s post.

Clearly something went very wrong.

Hopefully we will learn the what, why, when, how and who of what went wrong over the coming months or years of review and inquiry. Perhaps we’ll find that there are positive knowledge-sharing and collaboration stories which also emerge, showing how competitors, partners and individuals joined with BP to work to remedy the situation. Possibly we’ll discover will be some Apollo 13 paragraphs within this Challenger story? After the final traces of crude have been dispersed, the food-chain has purged itself of the pollutant effects, the rightful compensation paid and livelihoods restored – what will the legacy of learning be for the oil industry? I really hope that the genuine learning is surfaced and shared, and isn’t drowned out by the noise of the legal machinery.

TS Elliot famously wrote: “Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" Perhaps today he would have added: “Where is the learning we have lost in litigation.”

Now that might make another interesting article, Tom.

Geoff Parcell

I am one of the authors of “Learning to Fly” and I have been watching the response to the oil spill in the Gulf of Mexico with a mixture of anguish, sadness and concern. It is almost 9 years since the first edition of “Learning to Fly” was published, and more than 5 years since I left employment with BP, following a period of secondment to the United Nations AIDS agency UNAIDS. I don’t feel in a position to judge whose fault it was, whether the response was adequate, or whether sharing and learning was adequate within BP. I’ll leave that to others.

However there are three main themes on the topic of knowledge management that seem relevant to this story:

1. What knowledge and information are we basing our views on? 2. What sort of environment has been created for collaborating and learning? 3. How well have the risks been managed?

Let’s deal with these in turn.

1. Most of the information we have to base our views on are directly from the media - television, the internet and the press. My Member of Parliament in the UK, David Heath, recently wrote a press article on the future of political reporting.

“I am very worried about the standards of political and other reporting. If we need new politics, then perhaps we need a new journalism too.

Much that is written in the national newspapers is sloppy and under-researched. A lot of it comes from press releases and chats over lunch rather than looking for facts. As a result, much of it is drivel. On top of that you have a layer of unconcealed prurience masquerading as incisive investigation, concentrating on celebrity and trivia over substance, and the whole edifice looks remarkably shallow.”

I have some sympathy with this point of view. The press has moved from reporting news events to providing instant analysis and answers, assigning blame, searching out the high numbers (of casualties, demonstrators or barrels of oil spilt.) Accuracy is not the aim, finding the highest number someone is prepared to state is. In addition, the internet reinforces extreme views by replication, which has the effect of seeming more convincing even though there is no more information.

At the same time BP is providing its own information - video feeds of the well head, video explanations of each attempt to cap the well and stop the flow. Some think there is a bias to that information.

We make our judgements based on the information provided, coupled with our own knowledge, biases and values.

2. One of the biggest barriers to learning the lessons from mistakes is the litigious society we have created. Learning and sharing takes place in a trusting environment. So many incidents - from train crashes, to fires, to conflict situations, to explosions -are subject to litigation that people are afraid to open their mouths. Even for minor car crashes our insurance companies instruct us not to admit liability even when our instinct is to explain our actions and assumptions to others involved. There are few reports of collaboration for this response. BP did acknowledge cooperation between various government agencies and itself. Other oil companies have provided knowledge, experts, equipment and advice to support. I’d have liked to have seen much more cooperation especially with the US government to fix the problem and clean up first, then learn the lessons, and only then address the issue of who pays and who if any is negligent. What I saw and read was a mix of assigning blame, politicking and maintaining reputation; hardly the environment conducive to listening and learning from each other. What are the chances of really learning the lessons so that we can prevent something like this occurring again?

3. We need to manage the risks and for that we need knowledge. As individuals we rarely avoid risks altogether else we’d never get out of bed. We all handle risks not avoid them. When we assess the risk we judge the probability of occurrence, the impact if it happens and the amount of control of influence we have to mitigate the risk. It does come down to judgement and that judgement comes down to having the relevant knowledge.

Malcolm Gladwell in “Blink” shows examples where only a small amount of knowledge is required to make a decision. People who are risk averse often seek more and more knowledge rather than make a judgement. We need less knowledge than we think to make a decision, rather we need the right balance of knowledge and judgement according to our tolerance to risk. What concerned me was not that BP took risks but the response plan to mitigate the risk did not seem to be operational.

The basic principles of Knowledge Management outlined in “Learning to Fly” are as relevant as ever and are being applied within and between many organizations around the world. It is the application of the techniques that matters and the actions taken once you have the knowledge.