Archive

Therapy

Testbash Dublin and Organisational Psychotherapy

As I mentioned in my previous post, I’m just back from presenting an interactive session on Organisational Psychotherapy at Testbash Dublin. Some folks seemed confused as to the relevance of Organisational Psychotherapy to testers and the world of testing, so I’m happy to explain the connection as I see it. (And please note that many of my previous posts on Organisational Psychotherapy may also help to illuminate this connection.)

I’ll start by riffing on something Rob Meaney said during his presentation:

“Significant quality improvements [aren’t] driven by testing. They [are] driven by building relationships and influencing the right people at the right time.” ~ @RobMeaney #TestBash

Quality (and other) improvements come from improved relationships. This has been a theme on this blog for some years now. For example see: The Power of Humane Relationships.

I asked a key (for me) question during my session (several times):

“If we accept that (as per the Marshall Model) it’s the collective mindset of the organisation that determines its relative effectiveness, how do we propose to support the organisation if and when it choses to do something about its mindset?”

Unsurprisingly perhaps, I heard no answers, excepting my own proposal for a means to that end: Organisational Psychotherapy.

I wonder how many folks involved with testing ask themselves and their peers the question “How can our organisation become more effective at testing?”. Or, using the #NoTesting frame, “How can our organisation become more effective at delivering quality products and services?”

Fellowship

Organisational Psychotherapy is not just about improving product quality, however. Through improved relationships, and a shift in how the organisation relates to its people (i.e. from Theory-X to Theory-Y), the quality of life at work also improves. Put another way, we all have more fun, more job satisfaction, and get to realise more of our potential at work. Further, for all the folks that matter, their several needs get better met. And, as a bonus for the organisation itself, it gets to see its people more productive and engaged. What’s not to like?

Incidentally

I’ve also written elsewhere about using the Antimatter Principle in practical ways during software development. For example, during development we eschew requirements gathering in favour of incrementally elaborating hypotheses about the needs of all the folks that matter, and then conducting experiments to explore those needs. I can envisage teams that still need testers adopting a needs-focused approach to driving testing. For example, putting into place various means by which to answer the question “how well does our product meet the needs of the people that matter to us?”.

Practical Applications

On a related note, some folks asked me about practical applications of Organisational Psychotherapy in their day-to-day work as testers. Here’s just a few applications which immediately come to mind:

  • Improving communication with the people that matter (i.e. developers, fellow testers, management, stakeholders, customers, etc.). I find NVC (nonviolent communication) skills and practice particularly useful in this context.
  • Clarifying what works and thus what to do more of (Cf Solutions Focus). This can improve team retrospectives.
  • Helping the people that matter (including ourselves) feel better about what we’re doing (Cf. Positive Psychology).
  • Understanding each other’s strengths, with a view to having the right people in the right seats on the bus (Cf. StrengthsFinder).
  • Eliciting requirements (if you still do that) (Cf Clean Language).
  • Building a community (such as a Testing CoP or a multi-skilled self-organising product team) (Cf Satir Family Therapy).
  • Improved cooperation with higher-ups (empathy, Transactional Analysis, etc.).
  • Dealing with blockers to changing/improving the way the work works.

Invitation

I’d love to hear if this post has helped put my recent Testbash session in context.

– Bob

Testbash Dublin

I’m just back from presenting an interactive session at Testbash Dublin. I enjoyed conversations on the topic of the session – Organisational Psychotherapy – as well as conversations around e.g. #NoTesting. Indeed, I noted a common theme running through many of the sessions from the more seasoned testers presenting: a grumbling low-key disaffection with the notion of testing as a path to quality.

No Testing

A number of folks engaged me in trying to better understand what I might mean by #NoTesting. Such conversations generally start out with “What do you mean by ‘testing’?”. My time in Dublin has allowed me to see through my discomfort in avoiding this question (yes, I generally choose to avoid it). I’m loath to get into semantic arguments from the get-go. I find they rarely lead to productive mutual exploration of such topics.

The bottom-line, is: It doesn’t matter one iota what I mean by “testing”. Whatever YOU mean by “testing”, that’s what I’m talking about when I mention #NoTesting. It’s an invitation for YOU to pause awhile to consider how life would be different if you stopped doing “testing” (whatever YOU choose to understand by that term) and did something else to address the same ends.

Ends Over Means

There’s an idea from therapy which might help you understand this perspective. In eg Nonviolent Communication (and some other therapies), human motivation is assumed to stem from attempts to get our needs met. That is, our behaviours and actions result from the strategies (means) we choose in order to meet our needs (ends). Any particular strategy affords us a limited palette of behaviours and actions. Aside: Often, we have little or no conscious awareness of either our ends or our chosen means.

“Testing” (whatever YOU choose to understand by that term) is a strategy you (or someone else) has chosen – almost always, implicitly –  for getting your or their needs met. And other folks’ needs, too, in the general case.

There are always other strategies (means, options) for meeting folks’ needs. Yet rarely do these other strategies receive any consideration. Maybe some of these other options offer a way to better meet folks’ needs. How would we ever discover that, without considering them, becoming aware of them, exploring them?

So that’s what I’m talking about with #NoTesting (amongst a raft of #No hashtags) – an invitation and reminder to actively consider whether your default means (strategy) are best serving your ends (needs), whether your first and automatic choice of strategy is the most effective way to attend to your – and other folks’ – needs.

– Bob

What If #4 – No Answers

What if we refrained from inviting answers, at least until we had sought our own? What if we refrained from providing answers, at least until someone had unequivocally asked?

“I don’t understand this” is a pretty common admission. Although not perhaps as commonly admitted as it is thought or experienced. And what do we do when our friends, peers, colleagues, loved ones make this admission to us? We jump to fill the void. To provide some answers. To help them in their understanding. Helping people to understand is a natural human reaction. But how helpful is it, really?

How often do we tell ourselves that we’re helping someone to understand, when we’re actually just helping them adopt our interpretation?

And what if we helped them to understand something and they came to their own understanding of it? An understanding at odds with our own? How would we feel then?

Personally, the joy I find in helping people understand something is as nothing compared to the joy I take in folks finding their own understanding. Even, and perhaps especially, when it differs from mine.

There are occasions when someone asks me directly. “Just tell me the damn answer!”. On these occasions I mourn for the loss of opportunity. For the lost chance to explore together. For the missed joy we might both have taken from finding answers together. And yet most times I’ll accede to the demand. Albeit with a heavy heart.

What if we refrained from inviting answers, at least until we had sought our own? What if we refrained from providing answers, at least until someone had unequivocally asked us? What if we just tried to listen, to hold the space, to empathise, and to do what we could to relate to people as fellow human beings, walking together for a while, as we each pursue our journeys?

NB. I’m not looking for answers here – at least, until you’ve found some of your own.

– Bob

Further Reading

What Is Clean Language? ~ Marian Way

Other Posts In This Occasional Series

What If #1 – No Management
What If #2 – No Process
What If #3 – No Telling
What If #5 – Continuous Improvement Is Useless
What If #6 ~ Agile Nirvana
What If #7 – No Work
What If #8 – Agile Never Happened