Better way to think about conflicts

06 Feb 2024

Shreyas Prakash headshot

Shreyas Prakash

What’s the hardest conflict you’ve ever encountered at your work?

It’s hard to avoid conflicts, but there are various ways in which we could mitigate conflict as much as possible. As a product person, apart from keeping the team running, working with stakeholders, shipping successful products, you’re also tasked with resolving conflicts. As Feynman once said, ‘Imagine how much harder physics would be if electrons had feelings’. While dealing with people and emotions, It takes time and effort to identify conflicting situations in advance, and to nip them in the bud if possible. And this requires expertise maneouvring the field space of ‘feelings’.

My first line of thinking was to look at conflict in two major buckets. You have task conflicts. These are arguments over specific ideas and opinions (eg. “What should we eat for dinner?”). The second bucket can be termed as a relationship conflict. These are personal feuds and arguments (eg. “You are mean!”). Task conflicts are almost always beneficial, and can help the business lead to better outcomes, but they might also tread the path of turning into relationship conflict. This is when it gets ugly. I’ve struggled in the past deciphering events before they turn ugly, and was looking for examples from how product leaders approached it.

Recently, while researching about design patterns surrounding conversational AI, I came across this unique pattern called as conversational implicature. It’s an example wherein humans don’t always mean what they say, or say what they mean. A lot of it is implied, and in the context of a conversation, the AI should draw the larger context of the entire chat thread, before making an observation. For example, if customers are complaining: “I’m not able to get online”, as well as “I think my internet is broken”, they’re indicating that “lack of internet is a problem”. While researching about this pattern of human behavior, I realised that we are good at “knowing” what the other person wants. We don’t need people to use a specific set of words for us to understand. A lot of conflict resolution is around “knowing” what a person wants or needs.

Graciously borrowing ideas from Paloma Medina and Sasha Laundy, I use the BICEPS framework for identifying budding conflicts. This serves as a checklist to understand and prepare for the worst case scenario, especially when there is an important change, knowing how this might affect people is important.

How might this change upset people?

Core Needs: BICEPS
There are six core needs researchers find are important for humans (both at work and in our personal lives). Each of us have a personal hierarchy for the six however: You might find that equity and belonging are most important to you, but choice and status are most important to your employee, your partner, your child.  Getting to know them is a shortcut to better communication, as well as greater inclusivity at work. 

Paloma Medina https://www.palomamedina.com/biceps

In these scenarios, I run it through the BICEPS list:

Belonging

  • Do team members feel a sense of community?
  • Is there a focus on overall team well-being?
  • Are there strong connections between team members?

Improvement

  • Is there visible progress towards important goals?
  • Can team members see how their work impacts others positively?
  • Are there opportunities for personal growth and skill development?

Choice

  • Do team members have flexibility in their work?
  • Is there clear ownership and autonomy in specific areas?
  • Can team members make decisions about matters important to them?

Equality/Fairness

  • Is access to resources (time, money, space) equitable?
  • Is relevant information shared transparently with all team members?
  • Are support and reciprocity balanced among team members?
  • Are decisions made fairly, with equal consideration for all?

Predictability

  • Is there certainty about available resources?
  • Are timelines and schedules clear and consistent?
  • Can team members anticipate and prepare for future challenges?
  • Is the overall direction and strategy stable?

Significance

  • Does the work have a clear sense of purpose?
  • Can team members see how their work contributes to larger goals?
  • Do team members feel part of an important, positive movement?

While drafting an email consciously thinking of ‘How might this change affect people’, I go through the BICEPS list as a checklist to anticipate preventable core need button jabs.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Stop arguing, and start drawing circles togethermathematics
  2. The whole world is just the snake eating its own tailmental-models
  3. Life lessons and hot takes from my 30slifestyle
  4. Building a skill for coherent science illustrationsscience
  5. My agentic engineering workflow (step by step)agentic-coding
  6. Every darn thing is a kekulean loop if you notice itdesign-thinking
  7. Hammock driven developmentagentic-coding
  8. Peculiar ways number three fits into our funny little brainsmental-models
  9. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  10. How I write essays in 2026writing
  11. Authority in the guise of evidencecritical-rationalism
  12. Map is not the territoryphilosophy
  13. Self hypnosis as a manifestation ritualmeditation
  14. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  15. How I prepare for tough negotiations nowadaysnegotiation
  16. When should we steelthread somethingproduct-development
  17. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  18. Healthy conflict in teams have a tipping pointteam-building
  19. How I deslopify AI writingwriting
  20. How I started building softwares with AI agents being non technicalagentic-coding
  21. Read raw transcriptswriting
  22. Legible and illegible tasks in organisationsproduct
  23. L2 Fat marker sketchesdesign
  24. Writing as moats for humanswriting
  25. Beauty of second degree probesdecision-making
  26. Boundary objects as the new prototypesprototyping
  27. One way door decisionsproduct
  28. Finished softwares should existproduct
  29. How I periodically rank my rough draftsobsidian
  30. Flipping questions on its headinterviewing
  31. Vibe writing maximswriting
  32. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  33. How I build greenfield apps with AI-assisted codingagentic-coding
  34. We have been scammed by the Gaussian distribution clubmathematics
  35. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  36. I was wrong about optimal stoppingmathematics
  37. Thinking like a shipmental-models
  38. Hyperpersonalised N=1 learningeducation
  39. New mediums for humans to complement superintelligenceagentic-coding
  40. Maxims for AI assisted codingagentic-coding
  41. Virtual bookshelvesaesthetics
  42. It's computational everythingtrends
  43. Public gardens, secret routesdigital-garden
  44. Git way of learning to codeagentic-coding
  45. Style Transfer in AI writingagentic-coding
  46. Understanding codebases without using codeagentic-coding
  47. Vibe coding with Cursoragentic-coding
  48. Virtuoso Guide for Personal Memory Systemsmemory
  49. Writing in Future Pastwriting
  50. Publish Originally, Syndicate Elsewhereblogging
  51. Poetic License of Designdesign
  52. Idea in the shower, testing before breakfastsoftware
  53. Technology and regulation have a dance of ice and firetechnology
  54. How I ship "stuff"software
  55. Writing is thinkingwriting
  56. Song of Shapes, Words and Pathscreativity
  57. How do we absorb ideas better?knowledge
  58. Read writers who operatewriting
  59. Brew your ideas lazilyideas
  60. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  61. Compound Interest of Private Noteswriting
  62. Conceptual Compression for LLMsagentic-coding
  63. Meta-analysis for contradictory research findingsdigital-health
  64. Proof of workproduct
  65. Gauging previous work of new joinees to the teamleadership
  66. Task management for product managersproduct
  67. Beauty of Zettelswriting
  68. Stitching React and Rails togetheragentic-coding
  69. Exploring "smart connections" for note takingwriting
  70. Deploying Home Cooked Apps with Railssoftware
  71. Repetitive Copypromptingwriting
  72. Questions to ask every decadejournalling
  73. Balancing work, time and focusproductivity
  74. Hyperlinks are like cashew nutswriting
  75. Brand treatments, Design Systems, Vibesdesign
  76. How to spot human writing on the internetwriting
  77. Can a thought be an algorithm?product
  78. Opportunity Harvestingcareers
  79. How does AI affect UI?design
  80. Everything is a prioritisation problemproduct
  81. How I do product roastsproduct
  82. The Modern Startup Stacksoftware
  83. In-person vision transmissionproduct
  84. How might we help children invent for social good?social-design
  85. The meeting before the meetingmeetings
  86. Design that's so bad it's actually gooddesign
  87. Lessons learnt interview prepping for product rolesinterviewing
  88. Obsessing over personal websitessoftware
  89. English is the hot new programming languagesoftware
  90. Better way to think about conflictsconflict-management
  91. The role of taste in building productsdesign
  92. Dear enterprises, we're tired of your subscriptionssoftware
  93. Products need not be user centereddesign
  94. World's most ancient public health problemsoftware
  95. Pluginisation of Modern Softwaredesign
  96. Let's make every work 'strategic'consulting
  97. Making Nielsen's heuristics more digestibledesign
  98. Startups are a fertile ground for risk takingentrepreneurship
  99. Insights are not just a salad of factsdesign
  100. Minimum Lovable Productproduct
  101. Methods are lifejackets not straight jacketsmethodology
  102. How to arrive at on-brand colours?design
  103. Minto principle for writing memoswriting
  104. Importance of Whytask-management
  105. Quality Ideas Trump Executionsoftware
  106. Why I prefer indie softwareslifestyle
  107. Use code only if no code failscode
  108. Self Marketing
  109. Personal Observation Techniquesdesign
  110. Design is a confusing worddesign
  111. A Primer to Service Design Blueprintsdesign
  112. Rapid Journey Prototypingdesign
  113. Visualise detailed file structures on CLIcli
  114. Do's and Don'ts of User Researchdesign
  115. Design Manifestodesign
  116. Complex project management for productproducts
  117. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  118. Pedagogy of the Uncharted — What for, and Where to?education
  119. Future of Equity with Ludovick Petersinterviewing
  120. Future of Ageing with Mehdi Yacoubiinterviewing
  121. Future of Tacit knowledge with Celeste Volpiinterviewing
  122. Future of Mental Health with Kavya Raointerviewing
  123. Future of unschooling with Che Vanniinterviewing
  124. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  125. Future of work with Laetitia Vitaudinterviewing
  126. How might we prevent acquired infections in hospitals?digital-health
  127. The why to endure any howentrepreneurship
  128. Design education amidst social tribulationsdesign
  129. How might we assist deafblind runners to navigate?social-design