Accéder au contenu principal

How to keep a disagreement from becoming an argument

Welcome the disagreement.

Remember the slogan, "When two partners always agree, one of them is not necessary". If there is some point you haven't thought about, be thankful if it is brought to your attention. Perhaps, this disagreement is your opportunity to be corrected before you make a serious mistake.

Distrust your first instinctive impression.
Our first natural reaction in a disagreeable situation is to be defensive. Be careful. Keep calm and watch out for your first reaction. It may be you at your worst, not your best.

Control your temper.
Remember, you can measure the size of a person by what makes him or her angry.

Listen first.
Give your opponent a chance to talk. Let them finish. Do not resist, defend or debate. This only raises barriers. Try to build bridges of understanding.

Look for areas of agreement.
When you have heard your opponents out, dwell first on the points and areas on which you agree.

Be honest.
Look for areas where you can admit error and say so. Apologize for your mistakes. It will help disarm your opponents and reduce defensiveness.

Promise to think over your opponent's ideas and study them carefully.
And mean it. Your opponent may be right. It is a lot easier at this stage to agree to think about their points than to move rapidly ahead and find yourself in the position where your opponents can say: "We tried to tell you, but you wouldn't listen".

Thank your opponents sincerely for their interest.
Anyone who takes the time to disagree with you is interested in the same thing you are. Think of them as people who really want to help you and you may turn your opponents into friends.

Postpone action to give both sides time to think through the problem.
Suggest that a new meeting be held later that day or the next day, when all the facts may be brought to bear. In preparation for this meeting, ask yourself some hard questions : Could my opponents be right ? partly right ? is there truth or merit in their position or argument ? Will my reaction drive my opponents further away or draw them closer to me ? Will my reaction drive elevate the estimation good people have of me ? will I win or lose ? What price will I have to pay if I win ? Is this difficult situation an opportunity for me ?

Quoted from "Bits and Pieces published by The Economic Press, Fairfield.

Commentaires

Posts les plus consultés de ce blog

Summary of 'Words are windows, Introduction to nonviolent communication' by Marshall Rosenberg

Summary of 'Words are windows, Introduction to nonviolent communication' by Marshall Rosenberg “Words are windows” is an introduction to non violent communication (abbreviated as NVC). Marshall Rosenberg presents in this book the process that allows us to communicate more serenely with others as well as with ourselves. This mode of communication allows us to become more and more caring, authentic, and empathic with others. It can therefore be used in all interactions of everyday life: as a couple, with our children, at work … NVC is proving to be a very effective way to manage conflicts, and also to better identify our own needs. At the source of Non Violent Communication NVC has 4 four key components: Observation – specific facts/data, no evaluation/judgment Feeling – state how we feel (many failure modes here) Need – the need underlying this feeling Request – must be specific action to address need First we observe what is really happening in a given situatio

Summary of 'Clean Architecture' by Robert C. Martin

Summary of 'Clean Architecture' by Robert C. Martin Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software. Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book. Clean Architecture leaves me with the same feeling, even if it’s pushing the development world to do better, has some good stories and present robust principles to build software. The book is build around 34 chapters organised in chapters. Programming paradigm After some introduction, there is an overview of three paradigm of programming: structured programming which imposes discipline on direct transfer of control object oriented programming which imposes discipline on indirect transfer of control functional programming which imposes discipline upon assignment Uncle Bob tells us

Le développeur incompétent est un mythe

Sous ce titre complètement arbitraire et très clairement provocateur, je vais passer un contre pied aux derniers articles que j'ai lus sur le métier de développeur. Par exemple : http://patricelamarche.net/2011/05/24/lincomptence-des-dveloppeurs/  http://blogs.codes-sources.com/tja/archive/2011/10/04/etre-un-bon-d-veloppeur-c-est-aussi-une-question-d-attitude-personnelle.aspx  Ça tombe bien c'est juste avant la soirée du Paris JUG sur le métier de développeur ! Et comme on se plaint que les présentateurs ne sont pas de vrais (?) développeurs, je vais en profiter pour donner mon avis. Alors voila, d'après ces articles, un bon développeur connait ses fondamentaux. Ok soit mais quelle est cette liste de fondamentaux ?  Chez certains, c'est les maths et l'algorithmie pure, d'autres c'est C++ par coeur et savoir retourner une chaine de caractère en moins de 3 instructions et une seule allocation mémoire, d'autres c'est Java JEE, ses 100 jsr et fra