Skip to main content

A review: Nonviolent Communication: A Language of Life: Life-Changing Tools for Healthy Relationships

Nonviolent Communication: A Language of Life: Life-Changing Tools for Healthy Relationships

by Marshall Rosenberg
ISBN: 978-1-892005-28-1

I was sitting in an Amazon Web Services workshop and, as an after lunch ice breaker, the workshop leader asked us to all name our latest purchase from Amazon. I had no idea what mine was and when I looked it turned out to be Nonviolent Communication by Marshall Rosenberg. I grinned and announced that I had bought after a recommendation from my boss. While true, it still got the laughter I was looking for.

It wasn’t, well at least I hope it wasn’t, recommended to me as I am angry or violent in my communication, but I was certainly struggling with some of the people related parts of my role as a Team Lead of a software engineering team. However, reading the book made me realise that I was struggling with:

  • Observations
  • Feelings
  • Needs
  • Requests

Not just with respect to other people, but for myself as well. The book helped me use these, along with a deeper understanding of what empathy is and how to use it, to understand better what is really being communicated when we talk with people. When resolving conflict we often look for compromise, but the book helped me understand that what is really needed is to find a way for all parties involved to have their needs fully met.

On several occasions I found myself able to relate directly what the book was telling me to situations I have found myself in.

In one of the later chapters there’s a description of two software engineers in conflict over maintaining an old system or replacing it with a new one. Neither engineer was listening to the needs of the other.

When someone tells me a story of something which has happened to them I am usually keen to retort with a similar story of something that has happened to me. The book helped me understand that this is not demonstrating empathy and I am gradually trying to fight the urge.

One of the first things the book teaches is that just because someone does something you don’t like, like cutting you up when driving or making a decision you don’t agree with, you shouldn’t give them a negative label, like idiot or moron. It doesn’t help them and it doesn’t help you. Instead remember that we don’t always understand what is causing someone to behave in that way and that acts we perceive as bad don’t make a person bad.

I am a big fan of The One Minute Manager. At one point I thought that the Nonviolent Communication book was suggesting that One Minute praisings are shallow and manipulative, so I reacquainted myself with them (they’re part of a poster I have on my wall). I discovered that both books are in alignment, because when you praise someone you should be able to clearly explain how what they did met a need you had.

After I finished the book, one of my colleagues asked me if it was one of those self help books which laboured the same point over and over and could have been shorter. While there is a theme throughout, each chapter looks at a different aspect of Nonviolent Communication, with everything from empathy to how to express anger.

 

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...