Shallow Disagreements

Stick long enough in context-driven testing, and you will hear the term “shallow agreement” one time or another. A shallow agreement happens when we forget to confirm our understanding regarding a user story before starting to work on it, and find out during the Sprint Review – or worse: later – that the functionality did not meet the expectations of our ProductOwner or end-user. Shallow agreement happens when we find out too late that we seemed to agree on something, but really weren’t. We didn’t check our assumptions, and usually both parties end up being disappointed by each other.

Last year, I realized there is also something like shallow disagreements – and I am not sure whether these are worse than shallow agreements.

What’s a shallow disagreement? With the description of a shallow agreement given in the introduction, a shallow disagreement happens when we seem to disagree, but are not. Shallow disagreements happen when we argue for hours about a particular design, and no one of us used code to clarify that, we find out after implementing the first approach that we had the same picture in mind, but could not get along with each other – for whatever reason.

Shallow disagreements happen if we fight with each other over a matter where each of us theorizes about the objectives of the other party, and never check our assumptions. Shallow disagreements happen when we fight over thoughtleaders’ approaches without diving into their teachings or visiting one of their courses. Shallow disagreements happen when we engage in a twitter fight, and don’t realize that the brevity of 140 characters does not provide us with enough communication bandwidth to get certain points across.

Personally, I think that shallow disagreements drown our energy, since we put so much of it into a fight that does not need to be a fight if only we could stop for a minute, and actively listen to the thoughts of the other. If only we would stop, and open our mind for the point, and try to understand their position. Shallow disagreements happen when we shot down our empathy for the sake of fighting with each other.

But what causes a shallow disagreement? I think it’s not lack of empathy to start with. Virginia Satir’s communication model taught me that it’s a lack of understanding the other party. Schulz von Thun taught me that it’s caused by a difference in argumentation levels. If I argument on the context level, and you only listen on the relationship level, then we are more likely to disagree with each other. Or as one of my colleague put it: if your thinking is no longer constraint by logic, you probably can only be reached by emotional argumentation.

What causes us to argument on different levels? What causes us to listen on different levels? Personally, I think a lack of trust can result in over-listening on the relationship level. Also a low self-esteem can result in being picky about the relation that the other one is trying to enforce on you. If you perceive a threat by the content of the message, you are also likely to react on a different level than the speaker tries to connect to you.

How can we dissolve shallow agreements? We have to ensure that we reach the same level of communication. Non-violent communication achieves that by making sure to address the crucial pieces of a conversation: the self, the other, and the context. The same applies to congruent communication based upon Virginia Satir’s model. Also some kind of empathy is necessary to notice for the individual speaker that he’s currently not reaching the same level as the other is hearing on. With that awareness, I found that I can more easily change my communication style to make sure that I reach the correct level in that other person.

What’s worse? Shallow agreement or shallow disagreement? I am probably biased here, but I find unnecessary fighting is dragging much energy from myself that I could otherwise use to bring value to others. Of course, shallow agreements are terrible. And I think that discussions and agreement are not binary. They are more on a fluent scale. That said, there is a thin line between checking assumptions to avoid shallow agreements, and over-checking assumptions and creating a shallow disagreement. If we miss to reach out to that other person on his or her level, then we are most likely to engage in a energy-drowning shallow disagreement that does not lead to new conclusions.

So, next time, you find yourself in a fight, check whether you have a shallow disagreement by varying your message to reach different levels of listening on the other person. Only if you find an unshallow disagreement, engage in the fight to avoid shallow agreements.

  • Print
  • Twitter
  • LinkedIn
  • Google Bookmarks

3 thoughts on “Shallow Disagreements”

  1. The arguing of shallow disagreement may be annoying to you, but I think you are wrong to suggest it has little value. Lots of things are happening when you argue. Your relationship is evolving. It can be dangerous, but it can also create trust, depending on how you handle it.

    You must keep in mind that you can’t know that a disagreement is shallow until you go through your tiring process of hashing it out. If you turn away from that process you risk leaving a big bug in your thinking and big trouble in the team.

    Many times I have heard people moan about how they don’t want to have an argument… but I wonder what they think they have when they don’t argue? I doubt that what they achieve is great work.

    1. Thanks for that comment James. And me replying to your comment probably also acknowledges that fact.

      Based upon Patrick Lencioni’s model in the five dysfunctions of a team, I tend to disagree with disagreement creating trust. According to Lencioni, a lack of trust leads builds the basis for a fear of conflict – and therefore for disagreement, and fighting that out in a respectful way. So, trust builds the basis – according to Lencioni – for a fruitful disagreement.

      Just to make the picture from Lencioni complete, in Lencioni’s model, what creates trust is to overcome the perfection thinking, and fear of failure. That said, I think you add more to a conversation by stating that you might have been wrong, and trying to understand the counter-argument.

      Don’t get me wrong, I like to have arguments. And I like to have them in a constructive manner where idea piles on other ideas, and we can shed light on different perspectives.

  2. Markus,

    First, it was nice to finally meet you at CAST 2014!

    I was researching “shallow agreement” and came across your blog. How nice!

    As I was reading your definition of “shallow disagreement”, my first thought was “this often happens to me on Twitter!” And then I read a few more sentences and found, “Shallow disagreements happen when we engage in a twitter fight, and don’t realize that the brevity of 140 characters does not provide us with enough communication bandwidth to get certain points across”. 

    You said (in the blog post and comments):
    “If only we would stop, and open our mind for the point, and try to understand their position.”
    “I think you add more to a conversation by … trying to understand the counter-argument.”
    While at CAST, I (and many others!) witnessed James Bach and Doug Hoffman passionately debating a certain topic. Later, I was fortunate enough to talk with Doug, and I asked about the earlier exchange that he had with James. To me, the most interesting part was the “stopping heuristics” that he and James had developed to help them deal with these debates. As I understood it, it requires that one (or both) can adequately explain (to the other’s satisfaction) the other’s viewpoint.

    For example, if Doug can see James’ point of view, and can explain it to James’ satisfaction, and *agrees* with James’ point of view, then the debate is done. There is no need for James’ to continue to argue his point (“beat a dead horse”) since they can now both see the same thing and agree that it is so.

    Or, if Doug can see James’ point of view, and can explain it to James’ satisfaction…AND James can see Doug’s point of view, and can explain it to Doug’s satisfaction, but they still *disagree*, then the debate is over. There is no need for them to continue to debate since there is no misunderstanding but just an opposing viewpoint.

    These “stopping heuristics” seem to align with some of your comments above, so I thought I’d share.

    Cheers!

    (and thanks for the iPhone cable!)

Leave a Reply to James Bach Cancel reply

Your email address will not be published. Required fields are marked *