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…

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to KanbanFrom High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important. 
Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate. 
Context: A Delivery Team started with Type A Scrum with 2 weeks Sprints. After a while, they deploy their …

New Organisational Model For Project Based Companies

Elliot Goldratt suggested a Strategy Tree for project based companies. While that may work for some companies, it will not work for knowledge based workers or Software Development Companies, or Digital Agencies. On the other hand traditional resource planning and resource allocation is also not effective despite all the effort one put into it to make it less of a command and control model - Here I assume we know who are knowledge workers and how their productivity works, Peter Drucker has a fantastic article about Knowledge Workers that I highly recommend you to read, if you have not read it yet: http://www.forschungsnetzwerk.at/downloadpub/knowledge_workers_the_biggest_challenge.pdf
Also, it has been proven that stable teams work better together on long term projects in software development. However, almost majority of software development companies or digital agencies break teams and reassemble them based on new projects or clients. This creates unnecessary complication and waste w…