Non-violent communication
Cross-functional conflicts can quickly become heated when team members feel their work or ideas are under attack. A developer may snap "This design is impossible to build in our timeline!" while a designer fires back "You always say that without even trying!" Such heated exchanges derail progress and damage team dynamics. These emotional reactions often mask valid concerns that need proper discussion.
Non-violent communication (NVC) provides a practical framework to defuse tension through 4 concrete steps:
- Start with observable facts: "The animation requires 5 new interaction states we haven't built before."
- Then express feelings professionally: "I feel concerned about the technical complexity."
- Next, identify needs: "I need to understand which parts of the design are most critical for user experience."
- Finally, make a specific request: "Could we break this design into phases, starting with core interactions?"
When receiving heated feedback, pause and apply the same framework. Instead of defending or attacking, respond with: "I hear this is technically complex (observation). I'm worried about compromising the user experience (feeling). I need to balance user needs with technical constraints (need). Can we map out complexity levels for each interaction? (request)"