Pratical Application of The Service Profit Chain
Last week, we looked at the knowing-doing gap and some of the causes behind that. But your mindset is possibly the biggest hindrance in closing your knowing-doing gap. That is what this week’s video is about.
Download The Mindset Checkup Test
Next week, we will have a look at what it takes to change our beliefs.
In my previous blog post, I mentioned that I have decided to switch format in 2018 and try my hand at vlogging. Here is the first video in a new series about learning developing and getting better at stuff.
Next week, we will explore how your mindset contributes to the knowing-doing gap for many of us.
As you may know, I have been blogging on this site for quite a few years now.
Now I decided it’s time for a change. For the rest of the year, I will be producing short 5-10 minute video blogs. Here is the first one that explains what this will all be about.
If you have ideas, suggestions or feedback in whatever form, please let do me know.
Introducing a new videoblog format from Mike Hohnen on Vimeo.
Next week, we will start by exploring the knowing-doing gap.
Sounds nuts, I know, but according to research by psychologist Gary Klein, it’s a great way to improve the actual outcome of your projects.
But before we go into details, there is an additional benefit that fits in with this month’s theme of improving how our top management teams function.
You see if you perform what Klein calls a pre-mortem on your projects, you are also providing a psychologically safe space for your team to voice disagreement or worries without being labelled as negative spoilsports or even worse being seen as disloyal.
So how do you do it? You make a plan for the project in your usual way, or maybe it is just a plan how you are going to execute the day with your team. When everyone is happy that we now have a plan, you announce:
“I am sorry to tell you but it has turned out that project (X) was an unprecedented disaster. Please give me your ideas as what could have happened to derail the project so badly.”
This is a very different question from asking: “So what could go wrong?” When we ask the ‘what could go wrong’ question, voicing your doubts on the team can be much trickier and often decidedly outside the psychological safety zone.
Now, everyone gets out a pad of paper and brainstorms with themselves 3-5 ways that this project could have been totally derailed, or that this day that we planned so carefully ended up a total disaster.
On a whiteboard or a flip-chart, draw a 2×2 as shown below:
Now ask each person to read out their ideas as to why this day/ project went wrong. As they do, note the item in the appropriate square.
Now you have an overview of what problems we might encounter, sorted in a practical way. Discuss how to create proactive solutions where you can see the need and make a backup plan for the issues that you can see could happen under a certain set of circumstances.
You have now achieved two things:
1) You have proactively identified a number of issues that you would probably not have discovered until it was too late.
2) More importantly, you have provided a safe space where it is possible to actually discuss the proverbial elephant in the room. Instead of a messy feedback session loaded with blame and critique, you have made it possible to voice doubts in a constructive way regardless of hierarchies or departmental boundaries.
The method is called ‘prospective hindsight’ and according to Author Karl Weick, it can improve people’s ability to predict the reasons for future outcomes by 30%.
After the reset, then what? We reset the management team and cleared the air using the workshop framework I described in my previous blog post.
Now, the question is what is the one thing we could start doing immediately, that would help us grow stronger as a team. In my view, the obvious answer is to learn how to we deal with setbacks and mistakes. The crucial move is from holding people responsible to everyone taking responsibility.
This may sound theoretical but is not, we can learn how to do that by one simple shift in our behaviour as a team. We need to develop and integrate the practice of the After Action Review, not in the form of the occasional event when something has gone wrong but as a natural part of how we finish ‘things’. The job is not complete until we have not done an after action review.
But nor is the week, the month or the year for that matter. We need to develop a different approach, a culture of not rushing into the next ‘thing’ before we have finished digesting what we just accomplished.
The format of the After Action Review can vary and if you google the term, you will see many more or less complex versions. My favourite fast and dirty is to grab a flip chart, napkin or whatever I can find to write on, I draw this:
Then I ask the team “So what went well (today, this project, or whatever we are wrapping up)?” That goes in the square labelled ‘Preserve’. Here we list things we are happy with, things that went well or even beyond our expectations. Practices worth learning from.
What do we need to get better at or develop in the future? Here we list things that did not go according to plan or turned out different than what we expected. We are not trying to place blame, only to identify what needs to change next time. Think of more as a feedforward than a feedback. Whatever comes up goes into the square ‘Develop’.
What did we do that we wish we had not done? I.e. what should we stop doing in the future? This is a great place for the individual mea culpa. I screwed up and I will try not to do it again, or maybe we all screwed up. What counts is the conversation about how are we going to avoid that in the future. Those items go the square marked ‘Eliminate’.
And finally, I ask what are we happy that we avoided today. Maybe last time we promised each other to keep tempers down even when things get tricky and today we manage to do that, yea! And that goes onto the last of the four squares.
This process can take 10-15 minutes at the end of a shift or it can take a full morning at the end of a larger project. When doing it this way, we create a relatively safe space for everyone to voice their views and opinions. It helps us clear up any friction or misunderstanding that might have arisen during the heat of the action.
Once we develop the habit of doing this as a regular practice, we have also taken the first step toward a more open and honest feedback culture. A culture with a focus on fixing things and learning from our mistakes. It’s a shift away from problem focus and towards to a solution focus. It is a goodbye to the drama triangles.
You can try it out very quickly at the end of your next management team meeting as: “So let’s just do a quick review of how we hold meeting with each other…”, you grab the flip chart, draw the model and ask the question. Easy, you are off to a new start.
Harvard professor Dr. Robert Kegan says:
“Let’s be blunt: In the ordinary organization, nearly everyone is doing a second job no one is paying them for — namely, hiding their weaknesses, looking good, covering their rear ends, managing other people’s favorable impression of them. This is the single biggest waste of a company’s resources.”
And the way I look at it is that the better they are at that second job, the more dysfunctional the management teams become…
So what to do about it? How to stop the madness?
Again, according to Kegan, it requires a different mindset, a culture that goes something like this:
“We hired you because we thought you were good, not because we thought you were perfect. We are all here to get better, and the only way we will get better is to make mistakes, reveal our limitations, and support each other to overcome them.”
And that, says Kegan, is the starting point. That is the basic foundation of how to create what he and co-author Dr. Lisa Lahey have labelled the DDO a Deliberately Developmental Organization in their book: An everyone culture.
In that culture, we would not need to spend time on our second job at all but would use the time more productively to develop ourselves each other and the organisation. This is not as utopian as you might think, but it definitely requires a hard ‘ RESET’ of how the team interacts with each other.
A good place to start might be to go off-site for 2-3 days and agree on a new set of ground rules for collaboration development and growth. There are various ways to do that. One of my favourite frameworks is using Peter Blocks six conversations as the agenda for the retreat.
In my experience, it is well worthwhile to have a person who is not part of the team facilitate these conversations. So that each team member can participate freely without having another job to as well.
On the first evening, I also like to add a Life Map exercise in addition to the Six Conversations. After dinner, each participant takes 15-20 minutes to reflect on the path they have come along in life. They draw that as a graph or map using a template (you can have a copy by simply entering your email below). Once everyone has completed the Life Map, they take turns sharing their story using the life map as the guide. This ALWAYS produces a much better understanding of why each of us is who we are. And ultimately that contributes to higher levels of trust in the group.
Here is a link to a short introduction to Peter Block’s six conversations framework. And if you would like a more comprehensive explanation, read the book: Community The Structure of Belonging By Peter Block
