In using story-work to build a brand, engage employees, or for one of its many other purposes, organisations nearly always focus on storytelling. The meme is strong because the act of storytelling is so powerful. But to focus solely on this one aspect of story-work severely limits the benefits. The most valuable application of this technique combines storytelling with story-listening and story-triggering. Together, these processes create the conditions for enduring and healthy change.

Story-listening

Back in 2005, I introduced the readers of the Anecdote blog to the concept of story-listening (it might even have been the first time the term was used). Story-listening is the process of eliciting and collecting stories, helping groups to draw meaning from those stories, and then, most importantly from a business perspective, creating opportunities for the stories to inspire employees to take positive, transformational action.

Story-listening may sound passive, but it does not involve people merely sitting back and listening to their company's stories in the same way that they might enjoy their favourite podcasts. It is all about helping those who can most influence change understand what's really happening in their organisation, and then inspiring them to do something about it. All good business story-work is purposeful.

Let me give you an example. Earlier this year, one of Australia's biggest accounting firms contacted Anecdote for help. They'd just done their employee engagement survey, and while many parts of the business were in good shape, there were several areas that revealed a need for improvement. The problem, however, was that the survey results didn't make it clear what might be creating the lower engagement scores. Broad themes like reward and recognition, communication and leadership behaviour had been flagged, but the organisation remained uncertain as to exactly which behaviours needed changing - or, for that matter, which behaviours were working nicely.

We started the project by collecting stories from a good cross-section of the firm and managing them in our Zahmoo story bank. We then assembled a group of influential employees from across the business and ran a workshop to help them work out for themselves the patterns of behaviour they wanted to reinforce and the conduct they wanted to correct - the stories we'd collected gave the employees many concrete examples of specific behaviours that either helped or hindered employee engagement. Once the important patterns where identified, we helped the group to design targeted interventions that would prompt constructive, lasting change.

All the stories you hear at work reflect your organisation's culture. You cannot change this culture without changing the stories being told and retold in your workplace. Then, once you've initiated new behaviours, new stories will flow. Story-listening helps you become aware of the current corporate narratives - it helps you to clearly hear the dominant stories, the prevalent archetypes, the repeating plot lines. Most importantly, because you are working with stories, your feelings are engaged, and these feelings inspire you to take action. Story-listening gives you the essential ingredients for change: decisions makers who both understand what's going on AND who are emotionally moved to make a difference.

Story-triggering

We all act in accordance with our beliefs, attitudes and values, which together form our view of life - or in terms of organisational culture, our view of work. This view is shaped and reshaped by what happens to us and how we interpret those experiences, and we reinforce those interpretations by telling ourselves stories and acting in accordance with them.

One of the first projects we did at Anecdote was to investigate the issue of trust in a bank's call centre. The call centre manager told us that when she'd first joined the section, she'd held the strong belief that all she had to do to get something done was to simply ask someone to do it and get their verbal agreement. But within her first week on the job, a colleague pulled her aside and advised her that, to get anything done, she should really email the person she was tasking and document her request, cc-ing all the relevant managers to ensure there was an obvious paper trail. At first this seemed crazy to the manager, and it offended her belief in the personal, friendly and trusting management style she had cultivated over many years, so she refused to adopt this approach. However, within another three weeks, after a series of incidents, the manager was emailing all of her tasking requests.

The dominant story at this call centre was that if you just relied on face-to-face requests, your words would be twisted or ignored and the job wouldn't get done, so you needed to maintain a paper trail as evidence. The centre's manager lived this negative story, multiple times, and eventually adopted it in place of her optimistic personal conviction. This was a sign of a very unhealthy workplace. What needed to happen here was that the employees needed to be subjected to new experiences that generated a fresh, positive governing story, and this is exactly the objective of story-triggering.

The simplest way to trigger such stories is for an organisation's leaders - that is, leaders in the broadest sense of the word - to do remarkable things, things that other people will remark on. We saw this happen at another bank we worked with. The bank's new CEO had noticed that most of the meeting rooms in the company's headquarters were occupied all the time, but that a handful were usually empty. On closer inspection, he noticed that the empty rooms each had a sign on the door which read, "This room can only be booked by a General Manager." The CEO asked around to see if this was necessary and quickly decided it wasn't. He then personally went to each GM meeting room and tore down the notices, triggering a story that flew around the organisation.

This might seem like a small act and a trivial story. But, in fact, it fed into a much bigger narrative that the CEO was creating, which went along the lines of: "We are flattening our organisation and resources will be allocated to whoever needs them to deliver business outcomes, regardless of their level in the company."

The first step in successful story-triggering is for leaders to be mindful of their actions. Such purposefulness is easier said than done. Often a leader's intent doesn't match the lived experiences and perceptions of her colleagues. She might want to foster collaboration yet is seen as acting in ways that create competition. She will only be able to tell if she is on the right track by becoming aware of the stories that are being told about her; some story-listening might be required here.

The next step is for leaders to identify or engineer opportunities to do something remarkable, and to do it conspicuously. This might be as simple as a leader telling an authentic story that reveals something about them - in particular, something about how they really feel, rather than what they think. If this sounds wishy-washy, it isn't. In his book The Political Brain, neuroscientist and political pundit Drew Westen puts it this way, using the context of political campaigns:

"Campaigns aren't won with bags full of anything [e.g. policy promises]. They are won by candidates who can convince voters, through their words, intonation, body language, and actions, that they share their values, that they understand people like them, and that they inspire the nation or save it from danger."

One CEO we worked with punctuated each sentence of a sustainability policy he was presenting by smacking the projection screen with the back of his hand. By the end of the presentation, no-one was left in any doubt as to the fact that sustainability was important to him.

The psychologists Robert Kegan and Lisa Laskow Lahey point out in their book Immunity to Change that we can also apply the idea of story-triggering at the individual level, helping people to create new stories for themselves which fulfil the prerequisites for behaviour change.

The usefulness of this approach became clear to me while I was conducting a workshop with 80 professors at an Australian university on ways to improve collaboration. As I began to make the point that two important behaviours for good collaboration were to make and keep promises and to speak your mind to colleagues with respect and good intent, I noticed a woman sitting at the back of the room. She had her arms firmly crossed and was shaking her head, clearly very unhappy with what I was saying. So I stopped my presentation and asked the woman if she would like to share what she was thinking with the rest of the group. Practically before I had finished my request, she said, "There is no way in the world you can be open and honest with a senior professor around here." Before I could comment, she went on to tell a mini story: "I once did what you are suggesting and I had to move departments."

Now, no amount of clever argument or telling of familiar stories would have changed that person's mind. She had obviously had an incredibly bad experience. The only way to help her gain a new insight would be to create an experience with a different result to what she was expecting, and to do this many times over. She would then have a new story that would in turn guide her future behaviour.

Storytelling

There are many ways to apply storytelling to your work setting. You can help your leaders to become better storytellers, and you can also begin to share stories of customer service or safety, or stories that convey your values, brand, service or product. But there is one particular type of storytelling that I'd like to focus on here, that which will help you bring your strategy to life.

As I've said in my paper, How to make your strategy stick with a strategic story [http://www.anecdote.com.au/whitepapers.php?wpid=23], the sad reality of strategies is that considerable effort is expended to create them, yet it's often the case that few people in an organisation know them. As a consequence, it is practically impossible for people to act strategically. Without the company strategy in mind, people won't know what to focus on, or what to say 'yes' or 'no' to, and they will become reliant on their managers for direction which, depending on the quality of the manager, can really curtail innovation and effectiveness. This is where strategic stories can help.

There are some misconceptions about strategic stories that we should clear up. Firstly, some people think that a strategic story is merely an immutable single story that must be conveyed unchanged in each telling. Of course, this common misunderstanding is far from the truth. One of our associates once helped a large postal service develop their strategic story, but before he'd had time to organise some sessions to explain how to use it, the story had found its way to the head of the parcels section, who promptly said there was no way he was going to parrot 'this script' or read it out to his guys. Our associate assured him that that wasn't the intention. Rather, the story had been designed to convey the meaning of the postal service's strategy via a mixture of context, emotion and facts, and with that meaning in mind, leaders would be encouraged to tell their own stories to illustrate the company's strategic directions.

A good strategic story is a framework of meaning that explains why an organisation's strategic directions have been selected. But it's also like a chord progression used by a jazz musician, in that within that progression, the musician is free improvise and adapt the music to suit their needs and the desires of the moment.

Another misconception about strategic stories is that they are crafted by the CEO and her team and communicated to everyone much like Moses heralded the Ten Commandments. On the contrary, it's important that the development of a strategic story is a participatory process that involves as many people as possible, both in its initial crafting and in the sharing of new stories about how the strategy is subsequently being lived out by employees.

Once you've developed a strategic story, you'll find that it wields tremendous power in clarifying a new strategy. Even if you already have a strategy in place, the strategic story process will often reveal misunderstandings about what the strategic directions actually mean, or disagreement among your leaders on what they should be. When we conducted separate interviews with each of the senior partners of a large consulting firm, we found them mostly in agreement about the company's strategic directions. During the strategic story process, however, we discovered major differences of opinion between them which required resolution before the process could be completed. Through some difficult but important conversations, the leaders reached agreement and now have an even stronger resolve to pursue their strategy. Unfortunately, too many organisations avoid these tough discussions or just lack the trigger and then the process to pursue them effectively. Instead, they mistakenly continue working with a completely misaligned view of their strategy.

A strategic story is memorable, adaptable and imbued with meaning. It helps everyone in an organisation to make sense of what's happening in the business. Done well, a strategic story provides a real competitive advantage.

Bringing it all together

The combination of story-listening, story-triggering and storytelling magnifies the impact of story-work far beyond that achieved through the use of a single story approach. Organisations often start with story-listening, to find out what's really happening in the workplace and to help employees work out what they need to do. Then storytelling is used to increase the ability of leaders to connect with their colleagues and inspire them. While we are all natural storytellers - I'm writing this in a cafe and the guys at the next table are sharing one story after another - we often need to build our confidence to tell stories in a work setting. This is because we've become used to merely voicing our opinions at work, rather than showing our hearts. But employees want to know what their leaders stand for, and those leaders' actions and stories are a useful guide. Once an organisation knows what is happening within it, albeit with an awareness that you can never know it all, then story-triggering is used to prompt the telling of new stories that will pave the way for a new means of acting.

If you're already applying a story technique to your organisation, then you're well placed to broaden your approach and gain the benefits of using all three story-work modes. If you're just starting out, then you have a great opportunity to distinguish yourself from your competitors by using a comprehensive story approach to improve the way you work. You'll be amazed at the business results.

How do you get your people to think about what the future could be, in a way that inspires them and starts to spark action, but also takes into account the simple fact that the future is unpredictable?

I was reminded of this challenge, yet again, last week.

We were working with a client on developing a session for a two day leadership conference focussing on bringing their strategy to life. As we were throwing round ideas on the types of things we could do, someone suggested an exercise that involved the participants spending time writing a magazine article about how things are for that organisation in 5 years time.

This triggered a recollection when we did a similar thing when I was working in the UK for the Royal Bank of Scotland (RBS). I was involved in planning and running a series of workshops for the management population of my division, working with American management guru Noel Tichy to bring his concept of " cycle of leadership to life. These were 2 day courses, and we ended up running them for nearly 5000 leaders, over a two year period in 2006 and 2007.

On day two there was an exercise where everyone had to draft a magazine article, for the leading business magazine The Economist, with these instructions:

You are assigned to write a cover story for the Economist - dated September 21st, 2012. The story is about the dramatic transformation of RBS, and how through your leadership and outstanding execution, RBS is achieving unprecedented success. The article should be written as if it were 2012 and should discuss the challenges RBS has overcome, how that was done and what the business now looks like.

Now to understand the rest of this story you need to know that RBS during that time was one of the biggest and most successful companies in the world. In 2005 it announced a profit of $A10.27bn, up 14% from the year before, and in
2006 the profit increased another 16% to $A13.69bn. By 2007 the profit stood at a very impressive A$15.33bn and the share price stood at $A8.94.

It was held up as a major success story in the UK corporate world, and its Chief Executive, Sir Fred Goodwin, who had been knighted in 2004, was a darling of Wall Street and the city in London. The feeling was that we could do no wrong, the business would just keep growing and growing, and become even more and more successful.

People spend an hour crafting these beautiful magazine articles talking about RBS and its success five years in the future. They then worked in three's sharing each other stories, before three or four of the best ones were shared with the whole group. I remember they talked about things like how RBS now had 500,000 staff (up from its 120,000 at the time), that its market share has gone through the roof (i.e. its share of the credit card market was now 80%, up from 20%), that the world's most innovative companies came to RBS to learn how to do it, and that its profit had just hit A$30bn a year.

At the time I thought the exercise was very useful. It created energy in the room, made people feel good about themselves and the organisation and all of what was mentioned seemed realistic and achievable.

On the 19 January 2009, RBS announced a loss of AS41.65bn, the biggest ever annual loss in UK corporate history. On that same day the British Government increased its holding in the bank to 70%, and the share price stood at less than 14 cents. Tens of thousands of people lost their jobs, businesses within the RBS Group were sold and Sir Fred resigned, he was vilified by the British press, and his house was even attacked by angry protestors.

There is no way in 2006 or 2007 that we could see this downfall happening. It was completely realistic to think of continued success and global domination. The exercise seemed to do exactly what Tichy had wanted it to do, and people were still talking about months after the events. But every single prediction that 5000 people made about the future proved to be wrong.

How do you get your people to think about the future, and what it could be, but which also takes into account its unpredictability? How do you manage and deal with that paradox? Was the exercise we did at RBS 'wrong', or did it achieve what it wanted, if its purpose was to get people excited about RBS' future, and reinforced to them why they wanted to be there. Is it more of an engagement technique than a strategic visioning exercise?

I would really like to hear your views on exercises like this and your experiences of dealing with the challenge of trying to envisage a rapidly changing, unpredictable future and the value in doing so.

What would you say is valued in this organisation?

A company that values 'fun' should be teaming with 'fun' stories. It's a little difficult, however, to have 'fun' stories without fun experiences.

We've developed a story-based approach for embedding values. Send us an email if you would like to explore using this approach in your organisation.

My engineering friends would say it like this...good intentions are a necessary but insufficient condition for success.

In my working life I have only ever met a handful of people who deliberately set out to humiliate, disempower, demotivate or otherwise disengage staff. Yet these are exactly the effects that many managers/leaders have. How can this be?

The answer, of course, is the 'knowing-doing gap'. Its the difference between what we intend as a result of actions and the impact that we have on people. But, can managers really be so lacking in self-awareness?

Apparently the answer is yes! In this article (registration required to access it) Lucy Kellaway from the London Financial Times describes an 18-month survey asking CEOs to list their 3 worst features. A staggering 97% list weaknesses that are really strengths, like 'I'm too trusting and accessible'. Lucy's conclusion is that the three worst traits of chief executives are a lack of self-knowledge, a lack of self-knowledge and a quite extraordinary willingness to give themselves the benefit of the doubt.

The Economist recently published this story:

So, step 1 needs to focus on getting leaders to acknowledge their faults and to focus on their impacts rather than their intentions. This is the first objective in our leadership programs. We expose participants to an equal number of positive and negative examples around engagement and the impact of manager behaviour. Participants are asked to identify what they think are the best examples and the ones that are worst. We also ask them to identify any examples where, as a manager, they have done this themselves or something like it. They identify these anecdotes by placing a blue dot on them.

The results are spectacularly conclusive. Over 75% of the blue dots are placed on the positive examples. Another way of saying this is that the participating managers consider themselves nearly four times more likely to generate positive experiences than negative ones. If this assessment were accurate it would probably be a pretty good place to work and employee engagement would be high. Unfortunately, in all four cases, employee engagement was moderate at best (between 40% and 60% of staff being ‘engaged’).

Our next step is to show these leaders a tag cloud (produced using Wordle) of the tags for all the examples collected in their organisation. A tag cloud of the aggregated data is shown below.

As the tag cloud shows, on average staff relate four times as many negative experiences as they do positive ones. This is almost the inverse of the managers' self-assessment. For many leaders this comes as a revelation - they need to change their behaviour for staff engagement to improve. They need to look past their intentions and focus on the impact they are having in the workplace.

The data has been collected from over 250 leaders from four large organisations between 2008 and 2011.

Is really listening to someone about your listening abilities, or is it about your motivation to listen? Is it about the 'skills' of listening or is it the desire to want to listen that makes the difference?

I have been running a series of workshops lately where we do a very simple listening exercise that gets the participants to actually feel what it is like not to be listened too. The exercise takes it from being a purely rational/logical thing (i.e. "I know that not being listened too isn't nice") to one where they actually feel the anger, frustration and almost diminishing sense of self worth that comes when you are not being listened too.

At the end of the exercise I do a de-brief and one of the questions I ask is; "What do you think is more important when you listen - your ability to listen, or your desire to listen?" You can see people have this light bulb moment as they realise it is not the ability side of listening that they are struggling with, it's the motivation to want to listen in the first place.

When asked they can all tell you what you need to do to be able to listen better, from a skills perspective - mirror body language, lean forward, make eye contact, avoid distractions etc. etc. A good outline of some of these were covered in a blog Shawn did in May last year.

However, these things only become useful if you want to listen in the first place.

For me listening, really listening to someone, is an issue of motivation first and foremost. Once I want to listen to you, then my skills and abilities to listen can really kick in.

We have been using narrative approaches for many years to help organisations with employee engagement. This 4 minute youtube video gives some insights into some of the things we've notice working in this field and some examples of behaviours that can build or undermine engagement. In 2009, we also posted a detailed description of how narrative can be applied to this challenge.

I stumbled across a blog post yesterday from Bob Sutton where he referred to the 'Otis Redding Problem'.

This is where you put in place too many metrics to measure individuals, teams, or business units. meaning they can’t even think about all of them at once. They therefore end-up doing what they believe are important or that will bring them rewards.

This is based on the line from the famous Otis Redding song Sitting By the Dock of the Bay; “Can’t do what ten people tell me to do, so I guess I’ll remain the same.”

This triggered a thought for me about how you could potentially use musical artists, lyrics or song names in an exercise.

Say you wanted to explore levels of engagement within a team or department. Asking straight out is unlikely to get you an accurate picture, depending on the culture, environment, who is present etc.   

What you could do is get groups to come up with, say, a written 'Playlist' of songs that sum up levels of engagement for them within the team. Or you could give them an iPod and get them to actually create one and play it back to the room.

Maybe instead you could introduce them to the 'Otis Redding Problem' and then get them to come up with their own examples within the team, based on song lyrics.

I just think this type of method allows people some safety and security to "discuss the undiscussable". It allows them to distance themselves from openly expressing how they feel, and the dangers that presents, just as archetypes or metaphor exercises might allow. It also creates a bit of fun, and lets people express some of their creativity and musical knowledge!

Anyone ever used anything like this and wanted to share how it went? Or does anyone have their own ideas on Problems/Dilemmas/Scenarios in the 'Otis Redding Problem' vein? Love to hear your thoughts.

When we collect stories in companies one of the most common anecdotes is the one about the boss who fails to recognise their staff's work. People want to be thanked, appreciated, recognised regardless of their level in the organisation or their level of skill or expertise.

Dan Ariely conducted a simple experiment described in his latest book, The Upside of Irrationality, which shows that a simple nod of appreciation is more than a nicety, it's a business necessity.

This is how it worked. Imagine a room where you might have a university exam--hopefully this doesn't send chills down your spine. Sitting up front is the invigilator keeping an eye on your every move and ready to collect your paper at the end. In this case each person collects a single sheet of paper from the invigilator that's covered in words. Your task is to circle any two letters that sit side-by-side and are the same. When you finish one page you return it to the invigilator and get another sheet until you can't be bothered doing it any more.

There are three groups in this experiment.

For the first group when they return their sheet the invigilator gives a friendly smile and a nod of thanks.

People in the second group returning their paper are ignored. The invigilator doesn't even look up. Their sheet is turned faced down onto a pile and without a word a new sheet is given.

The invigilator for the third group takes the sheet and without looking at the contents shreds it in front of the participant before handing them another sheet of paper to work on.

On avergae the first group that gets the nod of appreciation complete 9.03 sheets. Not bad for such a boring task.

The third group are ritually humiliated by the invigilator by shedding their work complete on average 6.34 sheets.

So what do you think happened for those people who were ignored? Are they somewhere in between groups 1 and 3?

Group three who received no feedback completed on average 6.77 sheets, very similar to those people who were practically abused as their efforts were destroyed before their eyes.

It would seem that authentic appreciation for a job well done goes along way to boost productivity and if you are one of these bosses who figures, "hey, they're smart people who know what to do. They don't need my praise." think again. You could be really holding them back.

I have just finished The Power of Positive Deviance: How Unlikely Innovators Solve the World's Toughest Problems by Richard Pascale, Jerry Sternin and Monique Sternin) a book I have been waiting for some time to come out. I am very glad to say the wait has been well worth it.

Positive deviance has received a lot of attention since the concept was laid out in a series of articles way back in 2000 – one in the Harvard Business Review and the other in Fast Company. The concept has recently received a new boost since it was covered in both Influencer: the Power to Change Anything and by Chip and Dan Heath (where they called them ‘bright spots’) in Switch: How to Change Things When Change Is Hard.

Positive deviance is based on the observation that in every community or organisation, there are certain individuals or groups (the ‘positive deviants’ or ‘bright spots’), whose uncommon but successful behaviours enable them to find better solutions to a problem than their peers. Positive deviance identifies these individuals or groups, who have access to exactly the same resources and face the same challenges and obstacles as their peers, and examines their behaviours and attitudes, which help them avoid problems that plague the rest of their community.

The concept of positive deviance is therefore relatively simple. It involves the identification of people who manage to thrive in a situation where most fail; figuring out what those people are doing that is different from the majority; and then getting everyone to engage in the same actions, thereby solving the problem. Sounds simple enough right? The book shows the challenges encountered in trying to use positive deviance to make a difference to a wide range of seemingly intractable problems.

The book is based around six in-depth case studies (a chapter each) on the use of positive deviance to address childhood malnutrition in Vietnam, stopping female circumcision in Egypt, reducing hospital infection rates in the US, reducing infant mortality in Pakistan, boosting sales within the pharmaceutical firm Merck, and helping reintegrate girl soldiers in Uganda.

Each of these chapters is an in-depth analysis of the power and limitations of positive deviance and how they have learnt and adapted the approach as they have gone along. These case studies really bring to life the context, situation and challenges they faced in each scenario. They are detailed, have a lot of information in them, and I've gone back and re-read most of them a number of times, and each time something new has jumped off the page for me.

Some of the key lessons I've taken, or had reinforced, from these case studies include:

1. We focus too much on the ‘what’, and not enough on the ‘how’.

We are drawn to the 'technical' stuff – the 'what', the specific practices and tools that make the individual positive deviants successful;

“That's the easy part – and only 20 percent of the work. What matters far more is the 'how' – the very particular journey that each community must engage in to mobilize itself, …discover its latent wisdom, and put this wisdom into practice.” This point really made me think about the number of articles I have articles about positive deviance, and how the vast majority of them focused on the ‘what’ the solution – not on the ‘how’ the solution was found and integrated into a community – from my experience the hard stuff.

2. The danger we bring as ‘experts’ in the change process:

As the authors say: “The greatest barrier to the success of positive deviance approach comes not from the members of the community themselves but from the “experts” who seek to help them...” There is fantastic story of how a suggestion around the use of tongs for Fried Chicken fundamentally changed an expert’s view on how to deal with, and beat, MRSA

3. Creating compelling and concrete portrayals of the problem at hand.

I absolutely love the story of using chocolate pudding to bring to life MRSA and its impacts in the VA Hospital in Pittsburgh

4. Change starts with changing practices

The conventional wisdom is that knowledge changes attitudes and attitudes change practice. Positive deviance reverses that. It starts with changing practice. As people see that changes make a difference, their attitude changes and they internalise the knowledge.

As the authors say; “its easier to act your way into a new way of thinking, than to think your way into a new way of acting… Once positive deviance behaviours have been discovered, the design must provide those who seek to learn with both the opportunity and the means to practice the new behaviour. A focus on practice rather than knowledge has proven to be a key element in bringing about lasting behavioural change...”

5. Use Deliberate Practice to practice the new behaviour

There is a lovely sidebar headed ‘choreographed conversations’ about training positive deviance participants in Egypt to start conversations around female circumcision. It is a great example of some of the key elements of deliberate practice.

6. Positive deviance is not the same as ‘Best Practice’

What comes out of the positive deviance process should not be confused with ‘best practices’ that we all are familiar with in our organisations. ‘Best Practices’ are typically identified by those at the top and then presented to everyone else for adoption. Positive deviance, on the other hand, is based on discovery by the practitioners themselves, which promotes buy in, acceptance, and change.

The book finishes with some absolute nuggets in how to undertake positive deviance work in a section called the ‘Basic Field Guide to Positive Deviance’. It provides a step by step guide (as much as you can within a process as fluid as that of positive deviance) on the key activities within a positive deviance initiative, as well as some really practical tips they have picked up during all of their work. My favourite one is; “Let silence speak! (Pause for twenty seconds after asking a question. That’s long enough to sing happy birthday!). Try it, you’ll be amazed how long twenty seconds actually is!

Overall, I have thoroughly enjoyed The Power of Positive Deviance (http://tinyurl.com/2vykgaz). It is detailed, it’s in-depth, and provides a huge amount of information about positive deviance and the challenges to apply it to solve real world problems. It did take some effort in parts to relate the chapters back to my world. Not always easy to link stopping female circumcision in Egypt with and the challenges that I face in creating change within organizations, but the links and the lessons are there.

Lastly, a word of advice. If you want to easily understand the concepts and principles of positive deviance and get excited about it and how it has been used – start with Influencer (http://tinyurl.com/yuvg54) and Switch (http://tinyurl.com/37bnsoz). If you need to get senior stakeholders and sponsors excited about the concept, do the same. If you then want to try and use positive deviance in making a difference to the challenges you face, read The Power of Positive Deviance (http://tinyurl.com/2vykgaz).


About the authors:

Richard Pascale is an academic at Oxford University, and author of numerous books including Surfing the Edge of Chaos (http://tinyurl.com/334ceb3). Jerry Sternin was the world's leading expert in the application of positive deviance before his death in December, 2008. Monique Sternin has been an equal partner in these efforts and now heads the Positive Deviance Institute (http://tinyurl.com/kmqjb9) at Tufts University.

Digital Habitats: Stewarding Technology for Communities by Etienne Wenger, Nancy White and John D. Smith

I’m often the technology steward for communities of practice (CoP). I create the Ning spaces and configure ‘em, I setup the email lists, I work out whether we should have a wiki or a blog or a discussion forum or some other combination of communication technologies. As you can see I’m quite a geek: I really do love it.

And whenever I get stuck I’ll contact my friends at CPSquare: Etienne, Nancy and John. And while I know they all have a deep understanding of CoPs I tend to ask Etienne the theory questions, Nancy the technology questions and John the group dynamics questions. Together they are a formidable team. Sadly I think their new book, Digital Habitats, will give them strong cause to suggest I should RTFM: Read The Flipping Manual.

Digital Habitats (DH) has a single goal: to help the reader understand the role of technology steward in cultivating a community of practice: what is it, why you would do it, are you are cut out for it, how to do it and where to find help. But it is not a shoppers guide nor a roadmap for technology selection.

There is a lovely photo of Etienne, Nancy and John in the preface and I feel that reading DH is like have a friendly conversation with them on a sunny balcony. They provide the context, a little theory, then lots of practical tips supported by real life stories to ground it and make it memorable.

For me there are three ideas in this book I have already put into practice with great effect.

Experience shows us that all know that communities of practice are different, and sometimes poles apart. DH introduces the idea of community orientations to help us understand where the emphasis might lie and therefore what technologies make most sense.

There are 9 orientations: meetings, open-ended conversations, projects, content, access to expertise, relationships, individual participation, community participation, serving a context. With my engineering communities, for example, I’ve asked the members where they see their current orientation and then ask them to identify where they would like to be. A community might start off very content focussed but realise that the real benefits will come from providing access to expertise. By understanding this orientation gap the technology steward can start introducing tools to facilitate the future orientation needs.

The second idea I find useful is how my friends (I was going to say ‘the authors’ but it didn’t feel right) describe the range of activities a community might be engaged in. The axis range from informal to formal and learning from to learning with. This diagram helps me ensure I’m thinking about the full range of possibilities when helping communities members design their CoP.

DH envisages three types of readers: deep divers, attentive practitioners and just do it-ers. The just do it-ers are directed to chapter 10 which contains an action notebook. It is a series of checklists to help you think about the role of the technology steward. What I love about chapter 10 is that I can jump in and start learning about the role by doing things and then come back to the descriptions contained in the rest of the book when it is more meaningful for me. DH makes the job of finding the relevant descriptions in the other chapters easy through a multitude of cross-links from chapter 10 to the relevant book section.

There are very few practical community of practice books available (I can think of 3 others) and Etienne has already had a hand in writing one of them. So Digital Habitats is a valuable addition to this exclusive club. It’s highly readable and practical and will definitely help make a difference to the quality of your technology support for your community of practice.

Late last year, a company approached us on the topic of employee engagement. They’d received the results of their biannual engagement survey and, as with previous years, realised that the data pointed them to strengths and potential weaknesses but didn't help understand what was really going on, or what to do about it. The data might show that 63% of staff agreed or strongly agreed with the statement 'I am proud to work for this company' and this might be down 6% from the previous survey. On its own however, the data doesn't help with the question "what does this mean and what should be done? "

Narrative approaches are excellent for exploring these sorts of issues and helping organisations find out what is really going on, and what actions they can take to reinforce things that are going well, and improving things that need work. The survey data is vital 'targeting information' but on its own it is an insufficient basis for planning. Thus, exploring employee engagement is a natural marriage of traditional approaches such as surveys and the emerging practice of narrative.

Our approach to staff engagement looks like this:

• Employee engagement surveys often focus on areas such as: do people say positive or negative things about the organisation; their intent to stay with the company; and whether they are motivated to strive to do the best they can for the company. In preparing for the narrative project, the survey data is examined to identify the themes to be explored, the geographic or structural areas to focus on and the people to involve in the project. Key stakeholders are also asked for their views on the survey results and the things that are of most concern or surprise to them.
• We use anecdote circles during the 'discovery phase' of these projects to collect a large number of examples (anecdotes) of how staff at all levels in the organisation experience issues on a day-to-day basis. The anecdote circles are an intervention in themselves as they get groups of people sharing their experiences; people value the opportunity to be listened to and participants learn from each other about how things get done. Recently, during an anecdote circle, a participant related how he received a call early one morning from his manager asking if he’d heard about the severe storm warning for his area (he hadn't). The manager was worried about him driving to work in the storm and requested that he work from home that day. The guy telling the story was really impressed by the phone call. This was a great example of how small actions can really help build employee engagement.
• In the sensemaking phase a significant and diverse groups of influencers are exposed to a cross-section of the collected anecdotes and are facilitated to engage in dialogue with each other to identify issues and themes regarding the current situation. The idea of sensemaking is to develop a rich and common understanding among these influencers of the current situation and its history. Exposure to the anecdotes provides participants with insights into what really goes on in the organisation; this can be quite confronting at times. Nonetheless, sensemaking is a vital step as the individual and collective understand it provides is the springboard for deciding what action to take. The sensemaking workshop takes between 4 hours to a full day and one of its valuable side effects is that individuals will often change (deliberately or sub-consciously) their behaviour back in the workplace as a result of the new understanding they’ve developed. This is an important step as one of the key actions to improve staff engagement is to 'stop doing things that piss staff off.'
• Complex problems cannot be 'solved' in any traditional sense and the way to make progress is to try things and see what happens. Using the deep understanding developed during the sensemaking phase, we involve the influencers in identifying the actions that can be taken to move the situation in a desirable direction. Our approach to this stage (which we call initiative design) is strongly influenced by the characteristics of complex problems meaning we encourage the organisation to identify lots of small scale actions that can be implemented at an individual or team level, based on the knowledge that with complex problems, little things can make a big difference. We also encourage the development of a 'continual improvement process' that aims to get these changes embedded in the fabric of the organisation.
• The final stage is to monitor what happens as a result of the actions taken - reinforcing the patterns that are beneficial and disrupting the ones that aren't. This is achieved through the embedding process developed during sensemaking and by using techniques such as most significant change. A planned monitoring regime is important as it helps detect changes - it also works as an incentive to implement the actions identified during intervention design

Since the initial approach, several other unrelated opportunities have emerged to work with companies to explore their employee engagement outcomes. Our extensive work in leadership/management development also has a strong link to employee engagement (as the main roles of a manager can be summarised as 'driving performance' and 'building engagement'). It looks like employee engagement is a growing area for us to apply narrative approaches.

Last year I wrote about how the skill to apologize will become even more valuable as the world get even more complex and speedy. Things will go wrong.

Well it looks like some books are being published on the topic. Here's what Tom Peters has discovered.

In What Got You Here Won't Get You There: How Successful People Become Even More Successful, Marshall Goldsmith proclaims: "I regard apologizing as the most magical, healing, restorative gesture human beings can make. It is the centerpiece of my work with executives who want to get better."

All I can add is:

Amen!

I believe that skill at Apologizing is nothing short of a "strategic competence"!

"Strategic competence"? Absolutely! Customers lost for want of a timely and sincere "I'm sorry. My fault" number in the billions, from restaurant diners to aircraft engine purchasers.

And now there's an entire book on the topic arriving May 1, Effective Apology: Mending Fences, Building Bridges, and Restoring Trust, by John Kador.

Read a whole book on the topic?

Yes!

Damn it!

Stra-te-gic-com-pe-tence!

In addition to being an excellent "how to" guide, the book also captures hard evidence. For example, with a new policy on apologies, Toro, the lawn mower folks, reduced the average cost of a claim from $115,000 in 1991 to $35,000 in 2008—and the company hasn't been to trial since 1994. The VA hospital in Lexington, Massachusetts, developed an astonishing approach to apologizing for errors (forthcoming—even when no patient request or claim was made). In 2000, the overall mean VA system malpractice settlement was $413,000. The Lexington VA hospital settlement # was $36,000—and there were far fewer per patient claims to begin with.

To paraphrase Annette Simmons, "People wont listen to you until they know who you are and what you want." And one of the best ways to introduce yourself and answer these two questions is to tell a story that reveals something about your character and experience.

The challenge for many people, however, is to find and tell a story that doesn't sound like you are just blowing your own trumpet. One approach is to take the spotlight off yourself and make someone else the lead. You can then play the supporting role.

When I introduce myself to a new audience I often tell the story of how I got started in storytelling by meeting Dave Snowden. Dave is a world leader in knowledge management and narrative techniques and is an impressive speaker and storyteller.

At this point you might want to have a look at this video where I tell the story of how I met Dave. After you've watched the video, and before you read on, please jot down what you inferred about me after hearing the story and pop your answer in the comments. This will help illustrate a key point to this approach.

For those of you that didn't watch the video, here's the basic plot. Dave comes to Canberra and presents at a seminar I organise. He captivates the audience for the whole day with stories and new ways of seeing the world. I'm so taken with the performance that I resolve to do similar work one day and that night write a story and send it to Dave. He admonishes me for missing the whole point of his work, which is to help organisations make sense of their own stories, not to craft stories. We become friends and I join to lead his research centre on complexity in Australia and New Zealand. Then I leave IBM to set up Anecdote in 2004.

So Dave is front and centre in this story. He is the star but I play a significant supporting role.

When I ask the participants of our storytelling for business leaders workshops (which I'm giving in London in June) about what they infer about me after hearing this story (I tell the story at the beginning of the day and ask for their feedback in the afternoon), they say the following:

• you are passionate about storytelling
• you are willing to take risks
• you have large organisation experience
• you've worked for a highly respected company
• you are confident to share your mistakes
• you are experienced in storytelling

I never get the sense that they think I'm a poser (mind you, that might not be saying). To the contrary, it feels like we make a connection quickly and the workshop is off to a good start.

So think about those times when you'd lent a helping hand, where you'd help create the conditions for others to succeed, and tell these stories to introduce yourself and build rapport. These stories speak volumes about who you are, what drives you and they reveal your character; the pre-requisites for trusting collaborations.

To change the way we work we need to change our mental models, and that requires insight.

In The Neuroscience of Leadership David Rock and Jeffrey Schwartz describe how our improved understanding of the brain is helping to reorient how we design organisational change initiatives.

The article recommends leaders create situations where their people get a new insight into how they view things: what is the dominant mental model?

One of the most effective technique to help create this insight is archetype extraction. It involves collecting anecdotes from people in the organisation on a theme such as customer service and extracting the archetypes from the many stories.  

An archetype is a embodiment of the organisation's culture in the form of a complex yet familiar character. An archetype is usually partly good and partly bad; a complex mix of traits. Not to be confused with a stereotype, which is typically an oversimplification based on simple categorisation or role: "Oh, he's a librarian."

We take these anecdotes into a workshop of 10-20 thought leaders and influencers who could benefit from an alternative perspective.

The workshop participants identify the characters and their character traits from the collected anecdotes on customer service and using a facilitation process they morph into the archetypes, which are often drawn by a cartoonist for greater visual impact.

The cartoons in the post depict some of the archetypes that illustrated the culture of a large Australia organisation. Once the archetypes are identified people can then use them to discuss some of the un-discussables without getting personal.

Most importantly the participants will have obtain a new insight on how the organisation views itself or another group.