Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.

How do you engage stakeholders, such as devs & product, with the findings from your exploratory testing session?

20 Mar 2026

In this moment: Richard Adams
Richard Adams asks:

How do you engage stakeholders, such as devs & product, with the findings from your exploratory testing session?

Things that I've found helpful:
  • Establishing an agreement that after every exploratory testing session, a formal debrief will happen. Sometimes group a few sessions and then debrief the group of sessions. Use a call/in person chat to share discoveries. Sometimes this would also be done asynchronously with summarised and detailed testing notes. Or via a recorded video update.
  • During the debrief pitch what I think the recipient/s might be interested in first. While we might have this super bug that we must tell them about pick an interesting observation first to break the debrief ice.
  • Ask what your recipients would like to hear about first. I'd say, "I've categorised my findings as Problems, Questions, Ideas and Praise. Which would you like to hear first?"
  • Keeping sessions short e.g. 30 minutes and max of 90 mins, can still lead to a lot of discoveries. It's hard yet important to not overwhelm devs and product people with so much information. They've already got a lot on their plate! I'd use a value - risks - questions approach to link my exploration back to risks and the value we're trying to deliver with the thing we're building. The aim is to speak in a language of risks.
  • Find allies who welcome your approach. I once had a program manager fascinated by my notes. They couldn't believe what I did as I'd attached them to the relevant JIRA. A developer once told me they appreciated seeing all the smiley faces on my testing notes, those that I'd labelled as "praise".
  • Keep trying if debriefs don't land. Folks might not initially be ready for them and it's easy to feel disheartened. Just keep going for it.

Thanks for your question, Richard. I hope it helps!

FootMoTes
Simon Tomes profile image
Simon Tomes
Community Lead at MoTaverse
he/him

Hello, I'm Simon. Since 2003 I've had various roles in testing, tech leadership and coaching. I believe in the power of collaboration, creativity and community. πŸŽ“ MoT-STEC qualified. I get real joy working with and supporting our wonderful MoTaverse community.

β€œThanks for making me feel so confident about myself.” | β€œI'm so grateful for all you do in the MoTaverse community, I learn so much as a result!” | β€œA simple chat with Simon in person absolutely changed everything.” | β€œSimon is one of the best people that I've ever met to have conversations with. He's so grounded in his way of thinking and articulates his thoughts so well and his feelings and his knowledge about community and everything.”

Open To
Write
Teach
Speak
Mentor
CV Reviews
Podcasting
Meet at MoTaCon 2026
Review Conference Proposals
MoTaverse Team
Attending MoTaCon 🀝
Chapter Lead
Richard Adams
Thanks Simon! Some great ideas to help me with debriefs. I've liked PQIP and is something that I shared with dev teams on exploratory testing.

Simon Tomes
Nice one, Richard. Thanks for reading. Glad to hear it was helpful. If it sparks anything else let me know. Feel free to create a new Moment with reflections or more tips and advice.

Sign in to comment
Explore MoT
Influence, from the other side of the table image
What I learned about influence by becoming a stakeholder
Cognitive Biases In Software Testing image
Learn how to recognise cognitive biases, explain what they are and use them to your advantage in your testing
This Week in Quality image
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Subscribe to our newsletter