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

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.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...