The Power of Nonviolent Communication in Software Testing

Nonviolent communication in tech teams enhances team dynamics. With its four components - observations, feelings, needs, and requests - this approach improves interaction by fostering clear and blame-free dialogue. By making thoughtful adjustments to language, teams can foster better understanding and collaboration. This method isn't just theoretical; it offers practical value in everyday testing environments. By focusing on communication improvements, teams can achieve more effective interactions, ultimately leading to enhanced productivity and harmony within tech environments.

Podcast Episode: The Power of Nonviolent Communication in Software Testing

In this episode, I talk to Maroš Kutschy, a QA technical lead passionate about automation testing and self-improvement. We go into the topic of nonviolent communication and its impact on tech teams. Maroš explains its four core components: observations, feelings, needs, and requests. We discuss how simple changes in language can greatly improve team dynamics and communication. For example, he illustrates how expressing yourself without blame opens up clearer dialogue.

"So yes, there is a lot of communication for testers." - Maroš Kutschy

Maroš is QA Technical Lead at Ness Košice, Slovakia. His hobby is automation testing. He likes leading and mentoring colleagues, learning new automation testing framework and helping people to enter the world of testing. In 2022 he was speaking at ‚Testing United‘ in Prague, ‚Nordic Testing Days‘ in Tallinn, ‚Tacon‘ in Leipzig, ‚HUSTEF‘ in Budapest, and ‚Test Dive‘ in Cracow. In 2023 he was speaking at ‚Software Quality Days‘ in Munich, 'HalfStack' in Vienna, 'SEETEST' in Bucharest and 'SANAE BEER.EX' in Bratislava. He likes self-improvement and leadership books, stoic philosophy, and exercising in the gym.

Highlights der Episode

• Nonviolent communication enhances team dynamics.
• Expressing without blame opens clearer dialogue.
• Language changes can improve communication.
• Four core components: observations, feelings, needs, requests.
• Practical applications benefit everyday testing scenarios.

Transforming Team Dynamics: The Power of Nonviolent Communication in Software Testing

Why Communication Matters in Testing

Software quality doesn’t begin and end with code—it lives and breathes through people. In the latest episode of Software Testing Unleashed, host Richie sits down with Maroš Kutschy, a QA technical lead and passionate advocate for automation testing, to discuss a topic that might surprise some: nonviolent communication (NVC). While it’s easy to focus on technical skills or automation frameworks, the reality is that every tester’s daily work is shaped by how we talk—and listen—to each other.

Maroš believes that the ability to clearly and empathically communicate isn’t just a “nice to have,” but critical for test engineers striving for real impact within tech teams. He draws inspiration from Marshall Rosenberg’s nonviolent communication model, outlining how it can smooth difficult conversations, improve feedback, and drive stronger team collaboration.

The Nonviolent Communication Model: Four Steps to Clarity and Empathy

Rosenberg’s NVC method breaks down into four components: Observations, Feelings, Needs, and Requests. The approach challenges us to communicate honestly while also tuning into the needs and feelings of others. According to Maroš, NVC isn’t just about expressing yourself; it’s about how you listen too—being fully present and open in conversations.

1. Observations: Sticking to the Facts

The first step, observation, is about describing what you see or hear without judgment or evaluation. As testers, it’s easy to slip into evaluation—labeling a developer as a “procrastinator” if code always arrives late. But Maroš points out that this can feel like an attack, leading to defensiveness instead of dialogue.

Practical Example:Instead of, “John procrastinates,” try, “During the last three sprints, you provided your code for testing on the final day.”This allows your message to focus on observable facts, making it less likely to trigger a negative response.

2. Feelings: Naming Your Emotions

Many in tech are used to keeping communication strictly objective, but NVC asks us to share our genuine feelings. The challenge? Distinguishing actual feelings from disguised judgments (“I feel ignored” is really an evaluation, not a raw emotion).

Practical Example:Swap “I feel ignored in our backlog meetings,” for “I feel frustrated during backlog refinement meetings.”Stating your emotion creates an opportunity for empathy and understanding, without blaming others.

3. Needs: Taking Responsibility

Feelings are linked to needs, and this third step is about articulating what you really need—without shifting responsibility onto others. Rather than saying, “You disappointed me by not coming to the meeting,” Maroš explains, you might say, “I was disappointed because I needed to discuss some open questions with you.”This subtle shift keeps the focus on your own experience and motivations.

4. Requests: Clear, Actionable Outcomes

All too often, requests are vague or implied, leading to confusion and missed expectations. NVC encourages clarity—specifying exactly what you’d like to happen.

Practical Example:Instead of, “I’d like to receive reports more often,” try, “Could you send automation reports every Monday, Wednesday, and Friday?”Clarity here is just as crucial as it is in software requirements!

Applying NVC in Real Tester Life

Implementing NVC isn’t automatic. Maroš admits it’s easy to fall back on old habits, especially under pressure. But by pausing—even briefly—to reflect before reacting, testers can radically shift the tone of their interactions. He keeps reminders in his workspace, reading over NVC principles before challenging meetings, and encourages others to do the same.

Richie highlights that, just as testers demand clarity from user stories and requirements, we owe the same precision and openness in our communication.

Empathic Listening: The Other Side of the Conversation

Beyond expressing ourselves, NVC pushes us to listen with empathy. That means fully focusing on the speaker, resisting the urge to interrupt or shift the topic to your own experiences. Sometimes, just being truly present—without jumping in with solutions—makes all the difference in building trust.

Conclusion: Better Teams Through Better Communication

Nonviolent communication won’t get rid of all conflict, but it can make team disagreements more constructive and less personal. For anyone in software testing, adopting these techniques can help unlock smoother collaboration and greater mutual respect—key ingredients for teams aspiring to build not just quality software, but healthier workplaces.

So, next time you’re about to give feedback or face a tricky team dynamic, pause and take a page from Maroš and Marshall Rosenberg: observe, feel, need, request—and watch conversations begin to shift.