A couple of weeks ago I attended a short workshop on nonviolent communication, and for me the root of it wall was the link between needs and feelings (see basic cycle below)
My mind started wondering around how can this be useful and interesting in the context of software testing.
First thing that came to mind for detecting dark patterns (more here). This is an obvious usage since dark patterns usually cause negative emotions while we as testers need to be observers.
Second approach to using this was testing something like emotion user journeys. This is a little bit on the opposite of the dark patterns facet., since when designing a user journey in a product or service, the UX designer can target some user emotional states, and as testers these intended emotional states should also be targeted as things to test. So, the questions can be “What feeling would I associate with the user journey so far? Is this in sync with the intended one?”
Third usage scenarios I see is around writing testing findings in a more empathetic way or even for defects that have not visible and obvious technical ground, but they just “feel wrong”. When I say this I have in mind those defects that seem obvious on a human and emotional level, but have no technical ground, things like “i just feel this is wrong, but why?”. In this scenario, I believe the nonviolent communication model can help, as it puts a flashlight on the feeling-needs pair.
Of course, I might be wrong, and things could be added, but this is what I see and believe now 🙂