Showing posts with label truth. Show all posts
Showing posts with label truth. Show all posts

Friday, 5 January 2018

You wish to point and sneer? How will that help, precisely?

There have been recent news reports about leaks on-board the new British aircraft carrier, HMS Queen Elizabeth.  The ship is currently undergoing sea trials, during which all systems and crew will be tested before being declared fully operational.

The purpose of the trials is to check that the ship is fit for purpose, and to familiarise the crew with both it, and each other.  In knowledge management-speak, this is part of what is known as 'learning before'.

High-performing organisations invest time and resources in deliberate learning before (i.e. through KM planning), during (i.e. through Peer Assists) and after (i.e. through Retrospects and Knowledge Harvesting Interviews) key activities, to identify key knowledge that can be reapplied in the future, thereby saving time, money and improving performance, quality and safety.

Is the ship meant to be fully operational yet?  No.

Are the crew meant to be fully trained on it yet?  No.

Have time and resources been allocated to enable this 'learning before' to take place? Yes.

Are these so-called 'leaks' normal in ships at this stage of their life?  Yes.

Are they attended and reduced so that the risk is as low as reasonably possible? Yes.

Is highlighting a so-called leak like this helpful in any way?  No.

Does the media care?  Of course not.

In his book, 'Just Culture' (reviewed on this blog here), Sidney Dekker sets out the tensions between learning and accountability and reminds us that the clamour for 'heads to roll' after each and every mistake and oversight almost always has the opposite, unintended effect.  Instead of encouraging others NOT to make mistakes, such caterwauling merely warns others to cover up their errors, thereby ensuring learning does not take place and performance does not improve.

Pointing the finger when things appear to go wrong, finding someone to blame, using words like 'fault' - these are all evidence of a workplace culture that is anything but 'just'.  In such places, learning from experience is all but non-existent and performance way below where it could be.

For a chat about how to develop a workplace culture where learning from experience, before, during and after key activities, please contact me direct or via the Knoco website.

Friday, 10 February 2017

Anonymity vs. Attribution


In an earlier post, we looked at the importance of accountability to good knowledge management (KM).  Accountability underpins the effective management of anything at all – money, people, safety and definitely knowledge.
I’m now going to examine two related opposing concepts and how they can affect KM – namely, anonymity and attribution.

I’ll first look at each concept in turn, pointing out its effects and how those can be both positive or negative, depending on the context.
Then, I’ll look at how good KM is helped or hindered by them, with some suggestions on when one should be preferred over the other.

Anonymity

A piece of work is anonymous when its author’s identity remains unknown to us, the readers.  This has two important effects:

1.       The author can write whatever they like, released from the consequences that might otherwise result from that such freedom might have if we knew their identify;

2.       We, the readers, are forced to judge the piece of work based on its content alone, and not the identity or background of its author.

We can consider either of these effects positively or negatively, depending on the situation:

1.       Consequences

a.       Positive – a ‘whistle-blower’ is able to raise concerns about wrongdoing or crimes, protected from possible coercion from those involved;

b.       Negative – social media ‘trolls’ can abuse or threaten people online, or can spread lies or other misinformation, without consequences;

2.       Content alone; no context

a.       Positive – biases, prejudices or other ‘mental models’ cannot act as filters, which open us up to reading content we might otherwise miss;

b.       Negative – we have no way of knowing whether the writer is experienced or qualified, let alone credible and may simply be wasting our time.

Attribution

A piece of work is attributed when its author’s identity is known to us, the readers.  This also has two important effects which are of course the ‘flip side’ of those relating to anonymity, above:

1.       The author is no longer free to write whatever they like, for they remain tied to the consequences that might flow from our knowing their identify;

2.       We, the readers, can now judge the piece of work in context, not solely on its content but also by taking into account the identity or background of its author.

Again, these effects can be positive or negative, depending on the situation:

1.       Consequences

a.       Positive – attributed works are generally more likely to be considered, responsible and thoughtful, since favourable reception enhances the author’s reputation;

b.       Negative – there is a risk of euphemism, obfuscation or even dishonesty, as people seek to protect themselves from negative reactions were ‘the truth’ to come out;

2.       Context applied

a.       Positive – contextual consideration helps us to understand and judge a work; focusing on those from people with credibility and expertise; as well as enabling us to follow up with the author, asking questions or offering further insight;

b.       Negative – ‘group-think’ may occur, as fewer sources are considered, thereby increasing the risk of missing a perspective that might be valid but never gets heard.

How do these affect KM?

I’ll now run through a list of KM interventions or tools, highlighting the use they make of anonymity or attribution:

·        KM Assessments – at Knoco, our assessment and benchmarking service involves interviewing people drawn from across the client organisation, to understand how they work with knowledge and identify areas for improvement.  The output, either a written report or slides, or both, contains anonymised quotes from these interviews help to bring the report to life and show what things are really like.  For example, whilst the report might state refer to ‘silos’ and ‘inter-departmental relationships’, a killer quote really makes the point far more vividly, thus: “Tribalism is a problem here still; everyone knows this but it's not acceptable to say so publically; it's an undiscussable. It persists because top management do nothing to address it.”  Here, anonymity gives senior management an insight that normal, open reporting channels would not permit.

·        Knowledge-harvesting Interviews – these are a very effective way of getting knowledge out of people’s heads and into a form that can reach far more of their colleagues than would be possible face-to-face.  We would almost always recommend that the output be attributable, so that readers can follow up with the interviewee if they have questions or comments.  Also, it means that the output is more credible because the readers know who it came from – usually an acknowledged expert in a particular field, hence the interview.  When attributed interview transcripts are typed up and distributed or posted online, the interviewee should always have the right to review and edit the output for the simple reason that others will not engage if they hear that they might be misquoted or have their words used against them in some way.

·        Knowledge Assets – these are often created with reference to many different interviews and other KM capture activities and, as with interview transcripts, should generally be attributed, for the same reasons.  Providing the contributors’ name and contact details enables users to get in touch and offer further insights or feedback – something that is not possible if the content is all anonymous.  Also, anonymous content, unless it has gone through an established and credible validation process, will always lack the credibility of its attributed counterpart.  People need to know where the guidance and advice is coming from, otherwise they will be reluctant to use it.

o   Case-study – Some years ago, working as an analyst for the British Army’s newly-formed Lessons Exploitation Centre, I helped to produce a series of ‘Good Practice Guides’, full of anonymous insights and advice gleaned from Post-Operational Reports and Interviews.  It took time for us to earn a reputation as a credible source of knowledge and, with hindsight, I think we should have retained the source and author of each ‘nugget’, in order to show its provenance and enabled readers to follow up.

o   By contrast, a Battlegroup from my Regiment (The Rifles) produced a very helpful and credible post-tour handbook, full of insights, advice, tactics and case-studies – each of which was fully-sourced and attributed, enabling readers to judge the validity for themselves.

·        Lessons – At Knoco we help organisations capture lessons at the end of projects through the Retrospect process – a facilitated discussion between project team members, to identify learning points and make recommendations for the future.  Facilitation is needed to help participants examine events in a structured way, and this outsider, with no direct knowledge of the project, can ensure that lessons are written for the benefit of future users as opposed to recording events merely for posterity.  Lessons will be written up so as to balance the candour needed for effective reflection whilst protecting participants from direct quotation.  Like with interviews, draft lessons are returned to a project team member for review and editing, to ensure accuracy whilst reassuring future participants.

·        Knowledge Exchanges – these events bring people together to focus upon and discuss one particular topic, to facilitate the creation or update of a Knowledge Asset (see above), or to enable direct transfer between those with knowledge to those in need of it.  As with any KM activity, Terms of Reference help to ensure that all participants understand the event’s purpose and approach.  Notably, some events may use what are termed here in the UK as ‘Chatham House rules’, which means that formal capture and publication of any content may be allowed, but only without attribution.  The aim of such an approach is to enable speakers to do so more freely than they otherwise might, if they thought their every word would appear in print in due course.

·        Discussion forums – available across the internet as well as within medium or large organisations, these enable users to raise questions or start a discussion on a particular topic.  Most internet forums enable users to use an anonymous ‘handle’, thereby leading to honesty that may be painful, the ‘trolling abuse’ mentioned above, as well as running the risk that contributions are either unhelpful or even mendacious.  Some forums nowadays enable users to score both individual users and their contributions based on how ‘useful’ they have been.  Over time, this enables users to acquire ‘credibility’, thereby addressing, albeit partially, the issue of whether users should trust advice from an anonymous source.  Internal forums usually retain users’ identity, to enable subsequent follow-up and offline discussion, as well as ensuring that debate remains, for the whole part, civilised.

o   Case-study – Mumsnet is a well-known parenting forum where users can seek help or ask for insights on virtually any topic, albeit with a domestic bias.  99.9% of users have anonymous handles and debate is forthright.  Interestingly, users can and do change their name at any point and many do so, temporarily, in order to offer contributions that they feel unable to make from behind their (still anonymous) online persona.  Proof perhaps that sometimes we don’t like having to remain accountable for things we say, even amongst people whom we have never met.

A final observation – I used to work as a trained Samaritans volunteer, something I’ve mentioned before with relation to KM, here.
There are a number of factors that combine to enable Samaritans to do their job, which is to provide emotional support to people in crisis, including those that may be feeling suicidal.  However, the most important one, in my view, is the fact that callers and visitors to Samaritans centres can be 100% anonymous if they wish, and can share as much or as little about their lives as they wish.

This freedom means there is no comeback.  Which means they can be 100% honest – something they can’t be with their husbands, wives, partners, friends or colleagues.  It’s very hard to let those to whom we are closest see us at our most vulnerable but, somewhat paradoxically, it’s far easier to do so with complete strangers, to whom we shall probably never speak again.

I hope I have shown that neither anonymity nor attribution are always appropriate.  What matters is the outcome that we as KMers are trying to achieve – if we need warts and all honesty to understand truly what happened, then anonymity will help but we run the risk the output may not be wholly credible. 

Conversely, if we want to enable feedback and continued engagement with credible sources, attribution will be needed, with the understanding that there may not be full transparency, at least not until trust has been established.

For a conversation about anonymity and attribution and how they affect KM, please contact me direct or via the Knoco website.

Monday, 21 November 2016

Do you want to learn for the future? Or blame someone? You can't do both

This article, published yesterday on the Guardian website, argues that the Chilcot Inquiry (i.e. examining UK involvement in the run-up to the 2003 Gulf War and blogged about by me on its day of publication here) was set up to 'focus on lessons and avoid blame'.
It goes further, reporting that this was all about 'not holding people accountable'.

So far, so very typical of the media.

To report in this way is to make a category error because you can either investigate in order to hold people accountable and find out who is to blame, or you can seek to identify lessons for the future.  You can't do both - at least, not as part of the same process you can't.

In his excellent book, 'Black Box Thinking', which I reviewed here, Matthew Syed writes about the 'blame game' and the way it prevents people, teams and organisations from learning about past performance, thereby depriving them of valuable learning opportunities for the future.

He writes,
"...if professionals think they are going to be blamed for honest mistakes, why would they be open about them?  If they do not trust their managers to take the trouble to see what really happened, why would they report what is going wrong, and how can the system adapt?" (p. 240, Black Box Thinking)
Readers may recall my review of the great Sidney Dekker's book, 'Just Culture', in which he examines the dilemma of balancing openness (and learning) with accountability (and blame).
Dekker relates a powerful story of a nurse who volunteers the information that she made a mistake which contributed towards the death of child, with the result that she loses her job and is prevented from nursing again. 

In such an environment, and with such consequences, how likely is it that other healthcare professionals will volunteer insight into their own mistakes?  Or is it more likely that they will seek to cover them up?

Back to the media, and the campaign groups, and the families of the deceased - such people need to ask themselves, what outcomes do they seek?  Do they want to learn what happened and reduce the likelihood of recurrence?  OR, do they want to hold people to account and blame them for their decisions and actions? 

They can't have both - not from the same process, at any rate.

If you run lessons capture meetings, use a structured process to examine past events and identify lessons for the future, including actions that, if implemented, will help to improve performance.

You need to ask:
  • What did we expect to happen?
  • What actually happened?
  • Is there a difference between these and if so, why?
  • What have we learned?
  • What will do differently next time?
  • What actions do we need to take to embed this learning?
  • What was the impact of this issue?
Please don't ask 'Who?'  Even when examining 'what happened' and 'why', I am always very careful to ensure that no-one uses words like 'fault' or 'blame', and that we talk about 'actions taken' rather than 'he or she doing this or that'.

It may sound as though we're avoiding the hard questions and seeking an easy life, and it is certainly the case that organisations that have such processes hardwired into their projects and programmes are more comfortable with providing answers to questions that might be uncomfortable for others that are less familiar with this approach. 

However, the aim of such meetings in particular, and of knowledge management (KM) in general, must be to improve performance through the sharing and re-use of knowledge.  Other processes exist to 'hold people to account' and they must be kept separate from KM in order to encourage people to talk freely, without fear of consequences.

Can and should politicians and civil servants and generals be 'held to account' and 'blamed' for their decisions?  Where appropriate, absolutely. 

But an inquiry set up to identify lessons for the future is not the place for such motives and it is wilfully naïve of the media to expect both aims to be achieved through the same process.

Thursday, 13 October 2016

Leading the way - latest Knoco newsletter - KM and leadership

The latest Knoco newsletter on the relationship between Knowledge Management (KM) and leadership is now out!

Follow this link for:
  • How does leadership affect KM?
  • What do good and bad KM leadership look like?
  • How to manage leaders in lessons capture meetings
  • How to win leaders' support
  • The power of the 'CEO video'
  • KM tools to deliver good leadership
  • News from around the Knoco family
For a conversation about KM leadership, please get in touch direct or visit the Knoco website.

Thursday, 25 February 2016

Culture - a self-inflicted wound (or how the BBC and Nokia hurt themselves and how KM can help)


Today, the former judge Dame Janet Smith published her report into the culture and practices of the BBC in light of allegations of abuse by the late Jimmy Savile, during his time as a DJ and TV personality there.
The full report is available here.

Some may recall my writing about this sordid episode before (here and here).
Some key quotes that struck me:

·        “…the management culture in the BBC did not encourage openness in these respects and did not recognise the sense of insecurity which inhibited staff from speaking out.”

·        “An important feature of the culture of the BBC during the period with which we are concerned was the reluctance of staff to complain about bad things which happened to them or to raise concerns about bad things which were happening within the organisation.”

·        “…organisations both large and small find it almost impossible to inculcate a culture where people feel able to report a complaint or raise a concern without fear of adverse consequences for themselves.”

·        “…most staff (other than those who had been in the higher echelons) felt that the management culture was too deferential and that some executives were ‘above the law’.”

·        “…the culture in the BBC and the BBC’s management style did not encourage the reporting of complaints or concerns.”

·        “…fear of reprisal, fear of losing your job, fear of being known as a troublemaker and fear of not being promoted [are the] reasons why complaints might not be made.” 
Now, let’s turn to another well-known organisation – the telecommunications company, Nokia. Formerly the dominant force in the mobile phone market, Nokia sold its mobile devices division to Microsoft in 2013, having been unable to respond to the market challenges presented by Apple and Samsung over the previous 6 years.
This article here, makes a compelling case that it wasn’t Apple or Samsung that damaged Nokia but its very own culture.
Again, some key points:

·        “the company’s top managers had a terrifying reputation, which was widely shared by middle managers….some members of Nokia’s board and top management [were] “extremely temperamental” who regularly shouted at people “at the top of their lungs”….it was thus very difficult to tell them things they didn’t want to hear. Threats of firings or demotions were commonplace.”

·        “Fearing the reactions of top managers, middle managers remained silent or provided optimistic, filtered information.”

·        “…the information did not flow upwards. Top management was directly lied to….There were situations where everybody knew things were going wrong, but we were thinking, “Why tell top managers about this? It won’t make things any better.””

·        “Nokia’s ultimate fall can be put down to internal politics. In short, Nokia people weakened Nokia people and thus made the company increasingly vulnerable to competitive forces. When fear permeated all levels, the lower rungs of the organisation turned inward to protect resources, themselves and their units, giving little away, fearing harm to their personal careers. Top managers failed to motivate the middle managers with their heavy-handed approaches and they were in the dark with what was really going on.”
Two organisations with different purposes and structures but with a common problem – a culture that did not encourage openness and honesty, where only ‘good news’ gets passed on up and whereby senior management don’t have the full picture, forcing them to make decisions based on partial information.
Why?  Because of the culture that they themselves have allowed to take hold. 
But these are extreme cases, right?  That sort of thing doesn’t happen everywhere, does it?
Well, how about we delete ‘sexual abuse’ or ‘touch-screen phone’ and insert, ‘project delays’ or ‘cost over-runs’ or ‘performance issues’ or ‘safety concerns’.  Or any of the other ways in which performance can end up not quite how we had intended.  Are these reported upwards in full?  Or do we only talk about the good stuff? 
In short, many organisations are places where leaders are making decisions whilst not knowing what has really happened and, perhaps more importantly, why.
So what can they do about this?
Good knowledge management requires (amongst other things) the creation of processes to help people talk about how things are going and how they can be improved:

·        After Action Reviews get people in teams to talk openly about how things have gone  and learn from each other;

·        Peer Assists, Knowledge Exchanges and Handovers get different teams to explore issues and come up with solutions that can be embedded into everyday ways working;

·        Retrospects help project teams explore how the project (or stage thereof) went, what has been learned and what can be done differently next time;

·        Knowledge Harvesting Interviews get critical knowledge and information out of the heads of a few experts and available for others to use.
These tools and others can reveal much about what things are really like inside an organisation and, for their potential as learning techniques to be realised, senior management have to show leadership and send out the message that messengers will NOT be shot if they tell the truth.
Leaders must lead by example – which means being brutally honest about their own shortcomings, to send out the message that it’s okay to do so.  Moreover, that to do so is expected and is the essential thing that will lead to better performance – lower costs, higher profits, safer workplaces, motivated employees, better quality products.
For a chat about KM tools or how to create a learning culture, please get in touch or via the Knoco website.

Wednesday, 30 December 2015

Seven things I learned in 2015

·        ‘Not invented here’ remains the default response of too many people in too many organisations to any initiative;
·        Leaders are more powerful than they themselves realise – not because of what they say but what they do, and how!
·        Initiatives survive and prosper when we first agree on the effect we wish to achieve, and then work backwards on how to do it;
·        Good knowledge management needs both the ‘push’ from those that have acquired knowledge and the ‘pull’ from those that need it;
·        ‘Lessons must be learned’ continues to be trotted out by the media, politicians, chief executives and football managers alike – almost all of whom do not know what it means or requires;
·        Brevity helps;
·        Time spent understanding the client’s needs and desires is seldom wasted.

What will 2016 bring??

Tuesday, 20 October 2015

It’s always what we do that matters, not what we say (Part One)

We’re all individuals, keen to be treated as such but, put us in big groups and I’ll wager we’re most of us all the same. 
Why do I say this?
This weekend I was meeting a friend of a friend who had heard what I do for a living but wanted to know more; so I explained briefly what knowledge management is.  My new acquaintance asked me, “Do you enjoy what you do?” and I replied, “I love it.”  He asked me why and so I said, “Because what I do brings me directly into contact with the human condition.”
His frown showed I needed to explain what I meant and he seemed interested enough to hear my take on what.
“Because basically, no matter what we do for a living, where we live or how old we are…we’re pretty much all the same.  We want to be respected, to feel like we make a difference.  We want to be rewarded and we want security, as far as possible.  Most of us prefer to be popular than unpopular and we don’t like hurting other people, or even merely embarrassing them.  We want people to think well of us and most of us avoid conflict whenever possible.”
He nodded along and then said, “So?”  So I continued, “So, when faced with a situation that we fear will put these things at risk, we all do the same thing.  We minimise embarrassment for ourselves and others; we avoid awkwardness and far prefer choppy waters to be smoothed than stirred up even more.  We mostly tell people what we think they want to hear or, at the very least, will pull our punches so as not to make things any worse.  In short, we won’t tell anyone what we really think or how we really feel unless we feel 100% safe and secure and whoever feels like that at work?”
Again, he asked, “So?” “So…if we are ever going to improve anything, if we are ever going to learn from the past and make the future better, we need to know all that there is to know about whatever problem we face.  We need people to be honest, which means we need to let them feel it’s okay to be honest, which means they mustn’t fear demotion or the sack if they tell the truth, or even just embarrassment for offering a different point of view.  That takes time and effort and real, brace leadership from those at the top.  They need to show by what they do and say that they value integrity and honesty and moral courage because otherwise all they’ll get, indeed all that most organisations get is defensiveness, dishonesty and fear.”
I pulled out a pen and piece of paper and drew this picture of 2 stick-men with ‘speech bubbles’ representing their conversation and ‘thought clouds’ above each man’s head.  “Most problems in the world are down to poor communication, with people either unable, or downright refusing, to express what they think and feel. This is because they’re unsure what they think or feel or because they know all too well what they think or feel but are uncomfortable with sharing that with others.  Now, we tell each other the things in the speech bubbles and yet everything we do is shaped by what is in the thought clouds. Getting people to share those inner thoughts and feelings is at the heart of what knowledge management and organisational learning is all about.  It’s incredibly difficult and, quite frankly, a thankless task but, when it works, if only briefly, it’s very rewarding.”
He smiled and bought me a pint.
To be continued….