Replying to @coderbyheart

Here is a typical cause for a conflict:

  1. I am experienced, so I want my team members to follow my lead.
  2. They should however question my decisions, because I could hold an outdated
    view. There is no way that a collaboration can work without a conflict, it's
    built in.
Sat, 23 Feb 2019 16:14:44 UTC93

4 replies

Replying to @coderbyheart

A system like a business who wants to continuosly improve will always have this
conflict: working based on past experiences is efficient, going a different
route costs more energy but can lead to innovation. Now I know that conflicts
are inevitable and a useful process.

Replying to @coderbyheart

The issue I see with my past handling of conflict was that I saw them as an
avoidable exception and they needed to be resolved as quickly as possible.
Instead I think I should spend much more time on using conflicts to advance the
"state of knowledge" within a project.

Replying to @coderbyheart

I never reseatched a lot about that aspect of my work and how to make conflict
resolution a learning experience. I know of teams that have written down
conflict resolution workflows, which is something that I imagine to be very
helpful, because it increases everyone's awareness.

Replying to @coderbyheart

It would be super interesting to know of you have this at your workplace and if
your receive regular training on conflict.

Is conflict institutionalised or ignored at your workplace?

What do you think about this topic?