Conflict resolution

Conflict in cross-functional teams is natural and, when handled well, can lead to better solutions and stronger relationships. Consider a common scenario where design priorities clash with technical constraints. Instead of becoming frustrated, team members can use the "GROW" method (Goal, Reality, Options, Way Forward) to find balanced solutions. For example, "Our goal is a user-friendly feature that performs well. What are our current constraints? What options do we have? How can we move forward together?”

Prevention is as important as resolution. Teams can establish early warning systems for potential conflicts using friction logs where members note emerging tensions before they escalate. Regular alignment checks can help surface differences in expectations or understanding — such as weekly priority reviews where team members share their top 3 focuses and discuss any misalignments.

It’s also helpful to have clear escalation paths so team members know how to proceed and who to reach out to (ideally a neutral party) if an issue becomes too challenging to resolve directly, ensuring conflicts don’t stall progress.