Article

There are different strategies for managing conflicts, which are usually learned in childhood and are triggered automatically. Categorizing conflict styles enable learning and appropriate usage of these styles.


Owl

Collaboration – I win, you win

+ Both sides get what they want without negative feelings, resulting in mutual trust, positive relationships, and commitments.

– Time and energy-consuming.

Owl

Shark

Competition – I take charge

+ Quick decisions without compromise which can be correct as well as incorrect = win or lose resolutions.

– The shark may seem hostile and arouse resentment.

Shark

Fox

Compromise – I bend, you bend

+ Cares about relationships and goals when solving complex issues without simple solutions, where all parties are equal in power, 50/50.

– Compromise may create less than optimal outcomes resulting in game playing.

Fox

Turtle

Avoidance – I leave

+ Maintaining relationships by not escalating a conflict can result in late and difficult conflict resolution.

– Conflicts remain unaddressed and unresolved, overusing may result in being walked all over.

Turtle

Teddybear

Accommodation – I give in

+ Accommodating when outmatched to maintain relationships, and minimize injury.

– May be taken advantage of, not be productive, breed resentment, and exploits the weak.

Teddybear

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.