Skip to main content

Management & Leadership - How Do you Manage Conflict?

A manager asked me this question in an interview. I answered very brief, But found it a good topic for blog :)
1. I look at the Conflict as a positive and natural event, Why?
Simply because people are from different environment, families, societies, cultures, ideologies. People have different personality and different way of thinking and different way of communicating.
So it is natural for two or more people to see one topic, situation or problem from different angle and it is GOOD :)



Observing a conflict as a positive event which should/may/must happen will let you to think rationally about the situation and let you make decisions BETTER.
2. I clarify with myself what I want in that event, relationship, communication, conversation or meeting.
I may ask myself the following:
  • What is the Goal of this event, meeting, or process?
  • What do I want out of this processes?
  • What dose the other person want?
  • What would I do if I was in his/her shoes?
  • What is the least I will accept out of the process?
  • What the problems could arise?
  • How will I deal with each problem, and, If possible, turn it into benefit for the other person?
  • How will I bring the process to a conclusion?
3. I speak the language of the other person based on his/her personality and communication behavior. As you may now most of the conflict arise when two or more people speak about the same thing in different ways. One talked with facts and figures the other laugh and make fun, one orders and asks direct questions, and the last guy sits silence and tries to calm down the situation by not intervening!
I do this by using DISC model. You may get more information about DISC by looking to my previous blog “http://blog.kavehkh.com/2009/03/management-four-common-mistakes.html’ part “Stop criticizing, Give FEEDBACK only.” or Google it, Bing it or Search for it in Internet or Email me to give you more details.
I think that’s it , If you have a feedback please feel free to share it with me.
2 comments

Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…

Collocation is not the silver bullet for success and agility

To collocate or not to collocate? Most companies that are new to agile have been "consulted" by a "Scrum" Agile Coach, who suggested that they must break their organisation and have cross-functional teams to sit together in one location. Is that the recipe for success?.. Is it really?

Even though collocation has its benefits, it is not the necessary condition for a successful delivery team. Collocation as a dogmatic view may hurt you more than you think, and will not necessarily help you to deliver more successful products.

I am neither for nor against collocation, but I have experienced and worked with both approaches. And each sometimes worked very well and sometimes failed. All the variations of teams geolocation (collocated, fully-dispersed, partially-dispersed, or distributed) can work. It all depends on how the collaboration model is setup, what is the context and conditions, and how much the team and organisation are aware of each other, and are aligned.

Ha…