A couple of weeks ago, I had an evening out at the opera. I’d never encountered this on previous visits, but throughout the performance, there was a lady at the side of the stage translating the sung words into sign language. At the time I thought it rather odd – why would deaf people come to the opera at all? In any case, the words were displayed in English text over the top of the stage. Was this accessibility gone mad?
That prompted me to do a little research, and to realise that there are many reasons why there might be deaf people in the audience: from the obvious-if-you-think-about-it possibility that they might be with partners who are not deaf, to the much more important facts that most deaf people have some hearing and may well enjoy music (and even if they have no hearing, may find musical enjoyment in feeling the vibrations), and the more profound realisation that for some deaf people the English spoken and written around them may be ‘foreign’ compared to sign language.
Assumptions
All too often, we make assumptions about how other people see things. In this case, the conflict between my assumptions and the evidence led me to investigate, and find out that my assumptions were wrong, but much of the time our assumptions go unchallenged, and so un-investigated. In change projects, this is a particular danger. People who are feeling threatened or alienated by a change may be unwilling to point out that wrong assumptions are being made, even if they are not assuming that “management must have thought of that – it’s not for me to say”. Change managers must try to unearth conflicts like this by building relationships widely, and giving people at all levels encouragement to bring their concerns into the open. Change projects often fail, at least to some degree. I wonder how often that is because the manager did not realise, or bother to find out why, the assumptions were in conflict with the evidence. [contact-form][contact-field label='Name' type='name' required='1'/][contact-field label='Email' type='email' required='1'/][contact-field label='Website' type='url'/][contact-field label='Comment' type='textarea' required='1'/][/contact-form]
The unexpected death this week of Bob Crow, leader of the RMT Union (which represents many London Underground train drivers amongst others) has prompted quite a bit of media comment over the last few days. Tributes from industrial and political leaders have expressed sincere sadness, despite what his militant public persona might have led you to expect.
I never met Bob Crow, but it seems to me that he grasped more clearly than many that what most people want in their leaders is passion and an appeal to their emotions. At a time of generally falling Union membership, he doubled RMT membership, and then doubled it again, over a decade. I doubt that he could have done that by making a careful rational case. Stack that up against managers who – as public servants, charged with careful management of public money – are obliged to make their arguments rationally. Can you imagine what would have happened if politicians had incited Londoners to picket RMT headquarters when the tube went on strike? It is hardly surprising that he made an impact.
Recalling other powerful Union figures of the past – Arthur Scargill, say - isn’t that instinctive understanding of emotional leadership and the power of passion something they had in common? And perhaps the reason we now have a much less unionised and strike-prone world than we did is in part because union leaders have become less demonstrably passionate.
We need leaders who are passionate about their cause – whether in politics, in industry, or in unions – because passion is what galvanises the led. Whichever side of the argument you are on, we need more leaders who do that, as Bob Crow did.
[contact-form][contact-field label='Name' type='name' required='1'/][contact-field label='Email' type='email' required='1'/][contact-field label='Website' type='url'/][contact-field label='Comment' type='textarea' required='1'/][/contact-form]
A recent client experience came to mind when I read the following blog post:
http://sethgodin.typepad.com/seths_blog/2013/12/broken-english.html.
Seth says “you will be misunderstood”, and broadly speaking I agree with him: we all interpret what we hear in the context of our own experiences, however careful the speaker, and those experiences are all different. But I think is important to remember that there are degrees of misunderstanding; not all misunderstandings are equal.
My client had started a change project which was running into difficulty. As I started to talk to his staff, it became clear that they all had slightly different understandings of the objectives of the project. Not only did that mean that there was confusion about where they were trying to get to as a whole, but it also meant that the various workstreams were unlikely to join up.
You won’t be surprised to hear that there was not much formal documentation for the project. I’m sure my client felt he had explained what he wanted very clearly – and if he had been on the receiving end, I am certain that he would have understood himself perfectly. But his audience was not him, and he had not taken the additional step of asking his audience to play back to him to check their understanding.
One of the most important tasks for any project manager is to make sure that project objectives are defined clearly, and that everyone understands them. A key skill for project managers is therefore to be able to put things into simple, unambiguous language that fits the background and culture of everyone in the team. They must be good translators: there may still be some misunderstandings, but if they can’t reduce them to a very low minimum by adapting their language (and their listening) to their different audiences, they will not be effective. Just look what happened at Babel!
[caption id="" align="alignright" width="240"] Central London Traffic (Photo credit: oatsy40)[/caption]
Driving through London a day or two ago, I was amazed to see in front of me an advertising van unlike any I had ever seen before. Half of the back of the van was taken up with a large screen, repeatedly showing a short advertising video clip, obviously in full view of the drivers behind. It certainly got my attention!
Call me old-fashioned, but this seemed to me to be an innovation too far. Driving in London is hard enough, with heavy traffic, bicycles, pedestrians, buses stopping and starting, complex road layouts etc. to pay attention to, without adding advertising which is so clearly going to distract drivers. Health and Safety rules have a bad reputation, but this seemed to me to be something they really should apply to.
But it did remind me that if you want something to grab someone’s attention, you should make it move! Years ago (even before the first PCs), I was a University Lecturer, and had to put on a display of some research for an open day. Nearly all the displays people made were static. Even though my subject was hard to make exciting for the public, and though my animated display on an early computer screen was small and very crude (in those days anything more would have been very hard), the fact that it moved and had a very simple coordinated sound track attracted far more visitors than most other displays.
Change gets peoples' attention!
Change is like that too. It moves, so it gets peoples' attention, unfortunately more often negatively than positively – like the advertising van did for me. But if you can find a way to make people curious, and if possible engage them in the exploration of the change, the results can be quite different!
[caption id="" align="alignright" width="300"] English: neck of bottle of champagne (Photo credit: Wikipedia)[/caption]
What? Don’t you mean success?
Well, no – although that is worth celebrating too.
I came across the idea that you should celebrate failure recently in “Co-active Coaching”[1], and it makes a lot of sense. People rarely fail at things because they didn’t really try – or at least not at things that matter. First they had to find the courage to attempt something which they knew might to expose them to failure. Then, wanting to avoid failure, they tried hard, probably attempting things they had never done before. Finally they had to admit they had failed - even though in the process they had probably achieved more than they ever thought possible. All of those things are difficult, and worthy of celebration in themselves.
But there is more to it than that. Failure is an excellent teacher! When you fail, you have to face up to things you tried which did not work. Often you will want to understand why they did not work, and this may lead to more success next time.
There is also a less obvious reason. When we are criticised, blamed and shamed for failing, it usually has the desired effect of making us very keen to avoid failing again. Unfortunately, the consequences of that very understandable urge are not necessarily to make us try harder. We are very likely to learn to avoid taking the risky option in the first place, or to limit the options we consider only to the ones which appear ‘safe’.
You can’t stop failure hurting, but instead of adding to the hurt, celebrate failure – the courage, the effort, the learning involved – and at the same time create a culture in which even risky options can be seriously considered.
[1] “Co-Active Coaching” By Henry and Karen Kimsey-House, Phillip Sandahl and Laura Whitworth
How often have you found yourself having a conversation, and it gradually dawning on you that the person you are talking to thinks the conversation is about something quite different to what you thought? It happens to us all from time to time, and normally it causes at worst mild embarrassment as one of you says, ‘hang on a minute, I thought we were talking about x’ and the other looks bemused. Sometimes though, miscommunication can cause real problems.
E-mail Fireworks
Perhaps the most common place for miscommunication to cause problems in the working world is in e-mails. Maybe the relationship is a bit sticky already, or perhaps the subject is emotive. You write an e-mail, for example telling someone what you are going to do. Writing the message down gives you a chance to choose the words carefully so that they can’t be misinterpreted, right? Wrong! Within a few microseconds of pressing the ”send” button, you notice that your computer has started to smoke from the heat in the reply that has just clanged into your inbox. You read it – how could they have misunderstood your intentions so wildly? They must be spoiling for a fight! Your emotion finds its way into your reply, and the exchange just escalates. E-mail fireworks are never productive. Why are e-mails so fraught? Mainly, they are too easy. We dash them off with little thought. For straightforward factual messages that is not a problem. The trouble comes when the exchange has some (often unexpected) emotional content. Although they seem like a way of keeping the emotion out and so appear to be an easy option, humans are emotional creatures: we don’t often do purely rational. Be especially careful when you are worried about the reaction, and it feels safer to keep your distance. By omitting the emotional context of the message, which we detect mostly from body language and tone of voice, we take away the very cues which would help the recipient to know whether we meant to be provocative or were just not choosing our words very well. Poorly-chosen words in the context of a friendly tone and an open expression will usually only prompt clarification, but without these, people usually assume the worst. Here are five tips for minimising the risk of e-mail fireworks, and getting things back on track if necessary:- If you think the message might have some emotional content, don’t rely on e-mail if you can possibly avoid it. Start the exchange face-to-face, or at least with a phone call, so that there is an emotional context. Only once the tone has been set should you follow it up with an email.
- If you didn’t think the message was emotional, but the response appears to be – or even just indicates misunderstanding - never send an email reply. Pick up the phone straight away to clarify, or go and see them if you can.
- If you have to send an email which you know may be emotive, save a draft overnight before sending it, and re-read it in the morning. You have a better chance then of seeing how someone else might mis-interpret your words, and stopping it before it is too late. I rarely find I change nothing the next day!
- For really sensitive messages which you have to put in writing, ask someone else to check your words before you send them.
- If an exchange has gone emotional, apologise face to face – even if you don’t think you have anything to apologise for.
[caption id="" align="alignright" width="300"] Queueing for the Proms 2008 on the south steps of the Royal Albert Hall (Photo credit: Wikipedia)[/caption]
I’m sitting on the steps outside the Royal Albert Hall in London. Fortunately today it isn’t raining, but even if it was, I needn’t worry. These days the Proms have an excellent system for managing the queue – rather like the ones on the deli counters in supermarkets. When you arrive, you are given a numbered ticket, which guarantees your place in the queue. Once you have your ticket, you can wander off for a coffee or a snack, or take shelter if it rains, knowing that everyone will be admitted in the order they joined the queue regardless. It is not particularly sophisticated – but it is a simple system, and it works.
Simplicity is hard-fought-for: it does not happen by accident. Once a complex process or system is in place, changing it to remove unnecessary complexity is hard, just as all change is. Even stopping a simple system getting more complicated needs constant vigilance: otherwise, it is likely to gather exceptions and special cases, as well as extra checks that seem important, but which have a cost which is frequently overlooked. Just as nature dictates that the disorder of the Universe (or a teenager’s bedroom) increases with time, and that this can only be reversed by the input of work, so it is with organisations.
Why does it matter? Because a simple system is inherently more efficient and less error-prone. Have you tried to explain your organisation’s processes to a new joiner? If so, how easy do you find it to explain the judgements required if the process has branches (if this, then that, but if not, then the other), and how quickly do people learn to make them properly? Good governance depends on people following the rules. Complexity makes it more likely that people will make mistakes, and also makes it harder to spot when people deliberately try to get round rules. For an extreme example of what happens with complexity, think about tax codes: with complex rules and many special cases, expert advisers earn a good living, which must be at the expense of either the tax-payer or the tax-collector or both. While that is good for the experts, does that not make its complexity bad for the rest of us?
A few years ago, I spent a fascinating week travelling around Europe. I was trying to put together a consortium to bid for funding from an EU industrial research programme. I was selling a vision. It was one of those “if its Wednesday I must be in France” trips, where after a couple of days my brain’s language processor gets so confused it just gives up attempting anything except English. Fortunately (but as usual), my hosts all put me to shame by speaking excellent English to me.
This trip taught me a very important lesson about selling a vision which I have used many times since. No organisation wants to be the first to commit to partnering when all they have is an outline description of the objectives of the partnership. They feel they need to know who else will be a part of it, and what the content of the programme will look like. Without this, they don’t even really want to share their ideas of what they might contribute or what benefits they might receive. On the other hand, until they do share their ideas it is impossible to put together a realistic programme. So where do you begin?
I describe what I did as “Castles in the air”. Think of the project as a fairy-tale castle floating above the ground. You have to be able to describe in some detail what this castle looks like from a distance. Of course, no-one can actually get to it to look inside, so much of the detail does not need to be filled in, but the description has to be convincing enough that everyone believes it is a real castle, not an illusion. In particular, they must never think that there is nothing holding it up!