Connecting the dots…

  • You’re in your blind spot

    We’re all biased. It’s the way evolution has shaped us, and it really isn’t (always) such a bad thing. These cognitive biases developed for good reasons, namely helping us to survive and thrive as a species. But the issue is that these biases are more suitable for the African savannah than for the urban jungle. These biases (also called heuristics or mental shortcuts) are part of what Daniel Kahneman describes in his book “Thinking, fast and slow” as System 1, or the “fast thinking” part of our cognition. System 2 is the slower, more deliberate form of cognition that we use to make complex decisions. There are loads of biases and they’re fascinating to learn about, especially because you realise you encounter them everywhere, all the time! Because of the sheer number of them, there’s been an effort to categorise them into the problems that they try to solve, which might be seen as the following:

    1 – Too much info

    Our senses are constantly bombarded with information. However, we really need to know what information is critical. Take, for instance, that gold-coloured flicking tail just sticking out of the grass on the savannah. Ignoring that might be limiting. But we would come to a standstill if we had to try to process all the information we receive. So we don’t. We use all sorts of techniques to filter this information to find that which is relevant or important.

    2 – Not enough meaning

    Even though we have all this info flying at us, it’s often not connected and doesn’t make that much sense. So we impose our own meaning on it. We string together stories that link the information and then we act on that. Sometimes this can be very powerful, sometimes not so much. Often we simply climb up the ladder or inference.

    3 – The need to act fast

    When we see that flicking tail in the grass, it’s important to act fast. We’ve developed all sorts of shortcuts to facilitate with fast decision-making to ensure our survival. But these same shortcuts can have very detrimental effects when we really need to take the time to think before acting.

    4 – What should we remember?

    With all this information, we have to decide what’s important for us to remember. With your survival on the line, it’s best to remember the colour and shape of the root that might poison you. We tend to generalise to make it easier to remember things, but by generalising you can often miss important details.

    The first step to any problem is to gain knowledge, so to understand what we’re dealing with, here are a few of the cognitive biases that I find play out often in the coaching space and are important to be aware of.


    Bias Blind Spot

    Probably the most important bias to know about is this one. The bias blind-spot is the ability to easily spot the proverbial speck of sawdust in someone else’s eye, but fail to notice the log in your own. This is also something that coaches are as prone to as others. Not me though – only other coaches. But seriously, if you can’t admit you have biases, you may as well flick to another website now. There’s no hope for you.

    The Curse of Knowledge

    Here’s another one that coaches struggle with. The curse of knowledge is the inability to take yourself back to the place and time before you had the knowledge you have. You can no longer see the world like you used to and you can’t understand how others can’t see the world as you do now. This can be fatal for a coach. How are you supposed to help people change if you can’t understand where (and indeed when) they are?

    The other way this manifests is in our communication of ideas and concepts. We use jargon, lingo and industry-specific acronyms, which can have the unintended consequence of pushing your clients away from you, not bring them closer.

    The Dunning-Kruger Effect

    It may have a fancy name, but you’ll know this one. Those with the least knowledge of some topic are the ones spewing forth wisdom on that topic. They’re the same people that read a blog post about agile and the next day walk around the office telling everyone they should be having 15 minute ‘scrums’ if they want to be agile.

    What’s quite ironic is that there is an opposite effect called Imposter Syndrome, where those that are the most qualified feel like they don’t know enough and that any minute they’ll be found out. I guess somewhere in the middle we’ll find the balance.

    Confirmation Bias

    When you believe something to be true you can bet you’re going to find lots of evidence to prove it and avoid any evidence to the contrary. Google is great fuel for this particular bias. We find those articles that complement our beliefs but shun any articles that don’t.

    Semmelweis Reflex

    Your clients want to go agile. But they say: “It won’t work here. We’re different. Our circumstances are special. We’re not [fill in the agile company name here]. They don’t have legacy systems like ours.” Welcome to the Semmelweis Reflex. People reject concepts, technology and any new ideas that don’t fit into their current paradigm. Don’t get me started on the DevOps pushback!

    Stereotyping

    Probably the most common bias of them all. We simply have to put people in boxes – we can’t help it. How often have you heard the developers talking about ‘business’ and how they just don’t get it? They push and push, they’re always trying to get more work into the Sprint, etc. And what do the business people say about developers?

    Law of the Instrument

    You know that story about having a hammer and seeing every problem as a nail? We do that too. Take Scrum. We hammer that in everywhere. Doesn’t matter if it’s really suitable or not, godammit it’s agile!

    Actor-Observer Bias

    Observer: I was driving to work the other day and this idiot cut in front of me! What was he thinking! He shouldn’t be allowed on the road!

    Actor: I was driving to work the other day and I accidentally cut in front of someone. It wasn’t my fault – there was a glare from the car next to me and the damn coffee I was drinking was too hot (I’ve told that barista a hundred times not to make it so hot!) and it burnt my tongue, making me spill it over my new shirt!

    Yeah, when it’s someone else, it’s their fault. When it’s you, it’s still someone else’s fault. Go figure.


    These biases are just the tip of the iceberg. There are many other ways your brain takes shortcuts. So what can we do about it? (see how I used ‘we’ there and not ‘you’?) Well, it’s a bit like the 12 steps in the AA – you’ve gotta admit to having these biases first before you can move forward. However, just like alcoholism, you’ll never get rid of cognitive biases. You can become better at spotting them and stopping yourself from acting out, but your system is wired to play out in this way.

    Here are some tips that might be of use.

    1. Stop. Think. It’s really basic, but it can work. Before you act out, take a few moments to calm yourself and think. Usually just getting over the initial emotional flush can help you deal with situations better. Take a few deep breaths. Then take a few more.
    2. Ask questions. This is an extension of the point above in that it also allows you a bit of extra time to gather yourself. By asking questions you potentially have more knowledge and information at hand and could make better decisions.
    3. Create Tripwires. A tripwire is a mechanism that you set up for yourself before a potential situation occurs, that will trigger when that situation is reached. If, for instance, you know that it’s difficult to back out of a project once you’re too far in (the Sunk Cost fallacy), set up an agreement with your colleagues to review the project at regular intervals with exactly this issue in mind.
    4. Find a devil’s advocate. You may not like her, but that colleague that always has a different opinion is actually good for you. If you allow yourself, you might see things from her perspective, opening up other ways of thinking and potential options. Don’t surround yourself with ‘yes’ people.
    5. Create a backlog. You’re probably thinking, like, ‘duh’! But the practice of managing a prioritised list of tasks will force you into System 2 mode and stop you from being reactive and playing into System 1.
    6. Avoid Group-Think. Not as easy as it may seem, but powerful once it becomes second nature. Some people are just really good at this and are contrary just to be different or prove a point. This can be a really good trait as it can help you see situations from a different perspective. Cultivate it.
    7. Consciously break down stereotypes. This may seem a bit forced, but a good way to break stereotypes is to place images of non-stereotypical people or events in your everyday path (how about a pic of a gorgeous ginger…). You should try to enrich the stories you tell yourself of those around you as much as possible to make them less 2D and more 3D and alive.
    8. Get feedback. You can’t see yourself as others do, but you can certainly ask them to tell you what they see. It’s not easy hearing about your blind spots, but knowledge is power!

    This isn’t an easy journey. We’re human and we’re born with an operating system full of strange programming. With a bit of discipline and lots of self-observation we can learn to harness the best of ourselves.

  • Quote of the day

    “Like most people who go on diets, most companies that go lean fool themselves into thinking that the change effort is a time-bounded exercise. The company just needs to eat less and exercise more for now. It doesn’t understand that if it is to stay lean, a company, like a person, has to live lean … forever. It is literally about resetting the corporate metabolism, even restructuring its DNA. That cannot be done just by shifting a process, implementing a methodology, or running a change program. Real systemic change has to happen at a company’s core, with its people. Most critically, it needs to be embodied in the company’s leaders.”

    – “The Toyota Way to Lean Leadership: Achieving and Sustaining Excellence through Leadership Development” by Jeffrey K. Liker, Gary L. Convis –

  • Quote of the day

    “Questions you cannot answer are usually far better for you than answers you cannot question.”

    “21 Lessons for the 21st Century” by Yuval Noah Harari –

  • Quote of the day

    There are 2 things I don’t like: change, and the way things are now.

  • Learning vs not

    I’m going to take a break from the series I’ve been writing for the last few posts. It’s not that I’m getting bored with it, but rather that I’ve had another realisation after attended another Servant Leadership course. And here it is.

    The 2 models that are contrasted in Servant Leadership are unilateral vs mutual learning. The key word for me in that is learning. It feels to me that the unilateral model doesn’t allow the individual to learn from others. Their position is right and everyone else is wrong. Perhaps there is some learning involved, but it certainly isn’t done willingly. Rather, it is more likely a forced learning.

    Mutual learning believes that there isn’t a right or wrong, but rather differences that can help us understand the world better. When we are presented with someone else’s perspective we have the opportunity to grow and integrate that perspective into our own. This is a learning experience.

    What’s fascinating for me is that these 2 a completely different mindsets. They represent fundamentally different ways of viewing the world. When I’m unilateral, I have an anxious, closed view of the world. There are clear boundaries around me. I have a view of how things are and how I want them to be. These views and perspectives are within my boundaries. Anyone else’s views are outside the boundaries and in order for me to feel safe within my boundaries, I have to see your perspectives as ‘wrong’. This creates distance between us. This reinforces the ‘us’ vs ‘them’.

    When I’m mutual learning, I’m filled with an open sense of curiosity. I want to know more about you. I see the things I know as simply a small part of a much bigger whole. The things I know or have experienced are the edges of my boundaries and I feel a hunger to stretch those boundaries further and further, to learn more, experience more and bring that into a more fuller ‘me’. With this mindset, every interaction is an opportunity to learn more, become more, experience more.

    Unilateral values the finite. It’s a scarcity mindset. Mutual learning celebrates the infinite. It revels in abundance.

    Which do you choose?

  • Quote of the day

    There is no normal. Simply the relentless cycle of change. – Seth Godin.

  • What is agility?

    Agile is on everybody’s lips these days. Everyone’s talking about ‘going agile’ or ‘being more agile’. But what does this actually mean?

    Perhaps a bit of the history of agile is on order first. The term ‘agile’ started to emerge around the turn of the century in the software development community.  After many failed attempts at delivering software following the engineering principles & practises used in tradition engineering (the Waterfall Model),  they soon realised that the way they were developing software wasn’t working and that they needed to change. Thus was born the many variants of agile methodologies and practices that we see today, such as Scrum, Kanban, SAFe, LeSS, etc. What’s really critical here is that we don’t focus on the methodologies but rather on the fact that these luminaries understood their customer’s needs and the environment in which they were working and adapted accordingly.

    This is the crux of agility:

    …being able to quickly respond to changes.

    The first ingredient for agility is customer delight – being able to satisfy the customer’s needs as quickly and as often as possible with valuable products and services. Customer’s needs change regularly in this complex, digitally connected world and businesses need to be able to adapt and change in step with them. When we focus instead on the inner workings of the business we fail to notice when the customers takes a left turn. We we finally look up we’re surprised that the customers aren’t there anymore.

    The second key ingredient to agility is to reduce complexity by descaling work. In a VUCA world, we generally have the best success when we deal with small, manageable problems one at a time, and then moving on. Trying to deal with a massive amount of moving parts is a recipe for disaster.

    The third ingredient is a recognition that the organisation is a system and that agility needs to be embraced organisation-wide. Each part of the system is inter-related and needs to works together, so if one area changes, all areas need to change. This isn’t someone else’s problem – if you’re part of the system, you need to be part of the change.

    Underpinning all this is probably the most important ingredient of all – a culture that supports and nurtures learning, change & growth. Leaders need to hold the space, giving permission for and accountability to people to figure out the best way to delight customers, knowing that the efforts may not always work, but supporting them in their efforts to learn, grow and adapt from their experiences.

    Put all these ingredients together in the right quantities, provide the right cultural environment to allow for growth, and you’re on your way to true business agility. But don’t expect it to be easy – change is difficult and you’ll be challenged at every turn. But with change comes growth. 

    “The world as we have created it is a process of our thinking. It cannot be changed without changing our thinking.” ― Albert Einstein

  • Quote of the day

    “Be stubborn on the vision, but flexible on the details.”

    —Jeff Bezos

  • For example…

    One of the issues that often arises in teamwork is that of terminology. You’re in a meeting explaining yourself using what you think are perfectly understandable words but after a bit of back and forth you realise that the others aren’t understanding what you’re saying in the way you mean it. Or worse, you don’t realise that there’s been a misunderstanding and you leave the meeting thinking everything is sorted, only to discover a while later that the team has gone off on the wrong path.

    Thus the 3rd Ground Rule is:

    Use specific examples and agree on what important terms mean.

    This rule is all about specifics – specifics in situations and specifics in language usage.

    Situational specifics

    Abstract thinking may be great for philosophy, but when we’re trying to communicate in a high-performing team and we need action, it’s so much easier for us to relate to specific concrete examples. This is especially true when we’re trying to resolve issues in the team. In these instances, a clear situational example of what happened when and by whom helps to set the context within which further discussion can take place. If you’re trying to air a grievance and you start with “you always do [insert that thing they do here]”, there’s a big chance that the person can deny your grievance, as it’s almost impossible for someone to do something all the time.

    Language specifics

    One of the first artefacts I try to establish during any project is a glossary. Besides the usual role of clarifying the meaning of terms, I often find that the glossary is also used to define the single term that the team agrees to use whenever there are multiple terms are in use in the organisation. I know it might sound silly to go to the trouble of clarifying the words we use in a project, but you’ll save yourself quite a bit of time and frustration in the long run.

    This is a relatively simple rule, but it’s surprising how easy it can be to get it wrong!

  • Flow the info

    In the last post I wrote about assumptions and their effect on team performance. One of the most basic assumptions you often encounter in teams is that others have the same information you do. Hence, the second principle:

    Share all relevant information

    Let’s take an example – the traditional requirements gathering phase. The Business Analyst sits with the business person while they explain what they want this new system to do. The analyst takes notes and documents what they believe the business said. They then take this documentation back to the business, who, when reading someone else’s interpretation of what they said, realise that there were quite a few things that they forgot to mention that were in their head that would’ve made their requirements clearer.

    When these docs are signed off and given to the developer to build from, the developer looks on in amazement at the analyst, wondering where all the detail they need is. So the analyst and developer make a trip to the business to get the info they need. The relevant information here is that which the developer needs to turn the requirement into a system.

    The Agile solution to this problem is to remove unnecessary handoffs and potential miscommunication by simply having everyone work together full-time through the entire process. This way the team can make it clear what information would be relevant to them to help each other start sharing it more.

    A key point to make is the use of the word ‘relevant’. Oversharing is not constructive. If it doesn’t need to be said, don’t say it. Only share what is needed to progress the discussion or the work at hand. Anything more is waste.