Better way to think about conflicts
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
- Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
- How I started building softwares with AI agents being non technicalagentic-engineering
- Legible and illegible tasks in organisationsproduct
- L2 Fat marker sketchesdesign
- Writing as moats for humanswriting
- Beauty of second degree probesdecision-making
- Read raw transcriptsknowledge
- Boundary objects as the new prototypesprototyping
- One way door decisionsproduct
- Finished softwares should existproduct
- Essay Quality Rankerobsidian
- Export LLM conversations as snippetsbrowser-extension
- Flipping questions on its headinterviewing
- Vibe writing maximswriting
- How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
- How I build greenfield apps with AI-assisted codingai-coding
- We have been scammed by the Gaussian distribution clubmathematics
- Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
- I was wrong about optimal stoppingmathematics
- Thinking like a ship
- Hyperpersonalised N=1 learningeducation
- New mediums for humans to complement superintelligenceai-coding
- Maxims for AI assisted codingai-coding
- Personal Website Starter Kitai-coding
- Virtual bookshelvesaesthetics
- It's computational and AI everythingai-coding
- Public gardens, secret routesdigital-garden
- Git way of learning to codeai-coding
- Kaomoji generatorsoftware
- Copy, Paste and Citecuriosities
- Style Transfer in AI writingai-coding
- Understanding codebases without using codeai-coding
- Vibe coding with Cursorai-coding
- Virtuoso Guide for Personal Memory Systemsmemory
- Writing in Future Pastwriting
- Publish Originally, Syndicate Elsewhereblogging
- Poetic License of Designdesign
- Idea in the shower, testing before breakfastsoftware
- Technology and regulation have a dance of ice and firetechnology
- How I ship "stuff"software
- Weekly TODO List on CLIcli
- Writing is thinkingwriting
- Song of Shapes, Words and Pathscreativity
- How do we absorb ideas better?knowledge
- Read writers who operatewriting
- Brew your ideas lazilyideas
- Vibescreativity
- Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
- Compound Interest of Private Notesknowledge
- Conceptual Compression for LLMsai-coding
- Meta-analysis for contradictory research findingsdigital-health
- Beauty of Zettelswriting
- Proof of workproduct
- Gauging previous work of new joinees to the teamleadership
- Task management for product managersproduct
- Stitching React and Rails togetherai-coding
- Exploring "smart connections" for note takingknowledge
- Deploying Home Cooked Apps with Railssoftware
- Self Marketing
- Repetitive Copypromptingwriting
- Questions to ask every decadejournalling
- Balancing work, time and focusproductivity
- Hyperlinks are like cashew nutswriting
- Brand treatments, Design Systems, Vibesdesign
- How to spot human writing on the internet?writing
- Can a thought be an algorithm?product
- Opportunity Harvestingcareers
- How does AI affect UI?design
- Everything is a prioritisation problemproduct-management
- Nowlifestyle
- How I do product roastsproduct
- The Modern Startup Stacksoftware
- In-person vision transmissionproduct
- How might we help children invent for social good?social-design
- The meeting before the meetingmeetings
- Design that's so bad it's actually gooddesign
- Breaking the fourth wall of an interviewinterviewing
- Obsessing over personal websitessoftware
- Convert v0.dev React to Rails ViewComponentsrails
- English is the hot new programming languagesoftware
- Better way to think about conflictsconflict-management
- The role of taste in building productsdesign
- World's most ancient public health problemsoftware
- Dear enterprises, we're tired of your subscriptionssoftware
- Products need not be user centereddesign
- Pluginisation of Modern Softwaredesign
- Let's make every work 'strategic'consulting
- Making Nielsen's heuristics more digestibledesign
- Startups are a fertile ground for risk takingentrepreneurship
- Insights are not just a salad of factsdesign
- Minimum Lovable Productproduct
- Methods are lifejackets not straight jacketsmethodology
- How to arrive at on-brand colours?design
- Minto principle for writing memoswriting
- Importance of Whytask-management
- Quality Ideas Trump Executionsoftware
- How to hire a personal doctor
- Why I prefer indie softwareslifestyle
- Use code only if no code failscode
- Personal Observation Techniquesdesign
- Design is a confusing worddesign
- A Primer to Service Design Blueprintsdesign
- Rapid Journey Prototypingdesign
- Directory Structure Visualizercli
- AI git commitscli
- Do's and Don'ts of User Researchdesign
- Design Manifestodesign
- Complex project management for productproducts
- How might we enable patients and caregivers to overcome preventable health conditions?digital-health
- Pedagogy of the Uncharted — What for, and Where to?education
- Future of Ageing with Mehdi Yacoubiinterviewing
- Future of Equity with Ludovick Petersinterviewing
- Future of Mental Health with Kavya Raointerviewing
- Future of Tacit knowledge with Celeste Volpiinterviewing
- Future of Rural Innovation with Thabiso Blak Mashabainterviewing
- Future of unschooling with Che Vanniinterviewing
- Future of work with Laetitia Vitaudinterviewing
- How might we prevent acquired infections in hospitals?digital-health
- The soul searching yearsentrepreneurship
- Design education amidst social tribulationsdesign
- How might we assist deafblind runners to navigate?social-design