Better way to think about conflicts

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. Hammock driven developmentagentic-coding
  2. Peculiar ways number three fits into our funny little brains
  3. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  4. How I write essays in 2026writing
  5. Authority in the guise of evidencecritical-rationalism
  6. Map is not the territoryphilosophy
  7. Self hypnosis as a manifestation ritualmeditation
  8. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  9. How I prepare for tough negotiations nowadaysnegotiation
  10. When should we steelthread somethingproduct-development
  11. How to become a polyglot
  12. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  13. Healthy conflict in teams have a tipping point
  14. Deslopify AI writing
  15. How I started building softwares with AI agents being non technicalagentic-coding
  16. Read raw transcriptsknowledge
  17. Legible and illegible tasks in organisationsproduct
  18. L2 Fat marker sketchesdesign
  19. Writing as moats for humanswriting
  20. Beauty of second degree probesdecision-making
  21. Boundary objects as the new prototypesprototyping
  22. One way door decisionsproduct
  23. Finished softwares should existproduct
  24. How I periodically rank my rough draftsobsidian
  25. Flipping questions on its headinterviewing
  26. Vibe writing maximswriting
  27. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  28. How I build greenfield apps with AI-assisted codingai-coding
  29. We have been scammed by the Gaussian distribution clubmathematics
  30. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  31. I was wrong about optimal stoppingmathematics
  32. Thinking like a ship
  33. Hyperpersonalised N=1 learningeducation
  34. New mediums for humans to complement superintelligenceai-coding
  35. Maxims for AI assisted codingai-coding
  36. Personal Website Starter Kitai-coding
  37. Virtual bookshelvesaesthetics
  38. It's computational everythingtrends
  39. Public gardens, secret routesdigital-garden
  40. Git way of learning to codeai-coding
  41. Kaomoji generatorsoftware
  42. Copy, Paste and Citeai-coding
  43. Style Transfer in AI writingai-coding
  44. Understanding codebases without using codeai-coding
  45. Vibe coding with Cursorai-coding
  46. Virtuoso Guide for Personal Memory Systemsmemory
  47. Writing in Future Pastwriting
  48. Publish Originally, Syndicate Elsewhereblogging
  49. Poetic License of Designdesign
  50. Idea in the shower, testing before breakfastsoftware
  51. Technology and regulation have a dance of ice and firetechnology
  52. How I ship "stuff"software
  53. Writing is thinkingwriting
  54. Song of Shapes, Words and Pathscreativity
  55. How do we absorb ideas better?knowledge
  56. Read writers who operatewriting
  57. Brew your ideas lazilyideas
  58. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  59. Compound Interest of Private Notesknowledge
  60. Conceptual Compression for LLMsai-coding
  61. Meta-analysis for contradictory research findingsdigital-health
  62. Proof of workproduct
  63. Gauging previous work of new joinees to the teamleadership
  64. Task management for product managersproduct
  65. Beauty of Zettelswriting
  66. Stitching React and Rails togetherai-coding
  67. Exploring "smart connections" for note takingknowledge
  68. Deploying Home Cooked Apps with Railssoftware
  69. Repetitive Copypromptingwriting
  70. Questions to ask every decadejournalling
  71. Balancing work, time and focusproductivity
  72. Hyperlinks are like cashew nutswriting
  73. Brand treatments, Design Systems, Vibesdesign
  74. How to spot human writing on the internetwriting
  75. Can a thought be an algorithm?product
  76. Opportunity Harvestingcareers
  77. How does AI affect UI?design
  78. Everything is a prioritisation problemproduct-management
  79. Nowlifestyle
  80. How I do product roastsproduct
  81. The Modern Startup Stacksoftware
  82. In-person vision transmissionproduct
  83. How might we help children invent for social good?social-design
  84. The meeting before the meetingmeetings
  85. Design that's so bad it's actually gooddesign
  86. Lessons learnt interview prepping for product rolesinterviewing
  87. Obsessing over personal websitessoftware
  88. English is the hot new programming languagesoftware
  89. Better way to think about conflictsconflict-management
  90. The role of taste in building productsdesign
  91. Dear enterprises, we're tired of your subscriptionssoftware
  92. Products need not be user centereddesign
  93. World's most ancient public health problemsoftware
  94. Pluginisation of Modern Softwaredesign
  95. Let's make every work 'strategic'consulting
  96. Making Nielsen's heuristics more digestibledesign
  97. Startups are a fertile ground for risk takingentrepreneurship
  98. Insights are not just a salad of factsdesign
  99. Minimum Lovable Productproduct
  100. Methods are lifejackets not straight jacketsmethodology
  101. How to arrive at on-brand colours?design
  102. Minto principle for writing memoswriting
  103. Importance of Whytask-management
  104. Quality Ideas Trump Executionsoftware
  105. How to hire a personal doctor
  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 Ageing with Mehdi Yacoubiinterviewing
  120. Future of Tacit knowledge with Celeste Volpiinterviewing
  121. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  122. Future of Equity with Ludovick Petersinterviewing
  123. Future of work with Laetitia Vitaudinterviewing
  124. Future of Mental Health with Kavya Raointerviewing
  125. Future of unschooling with Che Vanniinterviewing
  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