Better way to think about conflicts
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
2026
2025
- Legible and illegible tasks in organisations
- L2 Fat marker sketches
- Writing as moats for humans
- Beauty of second degree probes
- Read raw transcripts
- Boundary objects as the new prototypes
- One way door decisions
- Finished softwares should exist
- Essay Quality Ranker
- Export LLM conversations as snippets
- Flipping questions on its head
- Vibe writing maxims
- How I blog with Obsidian, Cloudflare, AstroJS, Github
- How I build greenfield apps with AI-assisted coding
- We have been scammed by the Gaussian distribution club
- Classify incentive problems into stag hunts, and prisoners dilemmas
- I was wrong about optimal stopping
- Thinking like a ship
- Hyperpersonalised N=1 learning
- New mediums for humans to complement superintelligence
- Maxims for AI assisted coding
- Personal Website Starter Kit
- Virtual bookshelves
- It's computational everything
- Public gardens, secret routes
- Git way of learning to code
- Kaomoji generator
- Style Transfer in AI writing
- Copy, Paste and Cite
- Understanding codebases without using code
- Vibe coding with Cursor
- Virtuoso Guide for Personal Memory Systems
- Writing in Future Past
- Publish Originally, Syndicate Elsewhere
- Poetic License of Design
- Idea in the shower, testing before breakfast
- Technology and regulation have a dance of ice and fire
- How I ship "stuff"
- Weekly TODO List on CLI
- Writing is thinking
- Song of Shapes, Words and Paths
- How do we absorb ideas better?
2024
- Read writers who operate
- Brew your ideas lazily
- Vibes
- Trees, Branches, Twigs and Leaves — Mental Models for Writing
- Compound Interest of Private Notes
- Conceptual Compression for LLMs
- Meta-analysis for contradictory research findings
- Beauty of Zettels
- Proof of work
- Gauging previous work of new joinees to the team
- Task management for product managers
- Stitching React and Rails together
- Exploring "smart connections" for note taking
- Deploying Home Cooked Apps with Rails
- Self Marketing
- Repetitive Copyprompting
- Questions to ask every decade
- Balancing work, time and focus
- Hyperlinks are like cashew nuts
- Brand treatments, Design Systems, Vibes
- How to spot human writing on the internet?
- Can a thought be an algorithm?
- Opportunity Harvesting
- How does AI affect UI?
- Everything is a prioritisation problem
- Now
- How I do product roasts
- The Modern Startup Stack
- In-person vision transmission
- How might we help children invent for social good?
- The meeting before the meeting
- Design that's so bad it's actually good
- Breaking the fourth wall of an interview
- Obsessing over personal websites
- Convert v0.dev React to Rails ViewComponents
- English is the hot new programming language
- Better way to think about conflicts
- The role of taste in building products
- World's most ancient public health problem
- Dear enterprises, we're tired of your subscriptions
- Products need not be user centered
- Pluginisation of Modern Software
- Let's make every work 'strategic'
- Making Nielsen's heuristics more digestible
- Startups are a fertile ground for risk taking
- Insights are not just a salad of facts
- Minimum Lovable Product
2023
- Methods are lifejackets not straight jackets
- How to arrive at on-brand colours?
- Minto principle for writing memos
- Importance of Why
- Quality Ideas Trump Execution
- How to hire a personal doctor
- Why I prefer indie softwares
- Use code only if no code fails
- Personal Observation Techniques
- Design is a confusing word
- A Primer to Service Design Blueprints
- Rapid Journey Prototyping
- Directory Structure Visualizer
- AI git commits
- Do's and Don'ts of User Research
- Design Manifesto
- Complex project management for product
2022
2020
- Future of Ageing with Mehdi Yacoubi
- Future of Equity with Ludovick Peters
- Future of Tacit knowledge with Celeste Volpi
- Future of Mental Health with Kavya Rao
- Future of Rural Innovation with Thabiso Blak Mashaba
- Future of unschooling with Che Vanni
- Future of work with Laetitia Vitaud
- How might we prevent acquired infections in hospitals?