Have you ever found something surprising while testing and didn’t know how to bring it up?

scottkenyon
Thu, 08 May 2025 13:27:00 +0000
Discussions

Sometimes in testing, you spot something that’s not exactly a bug, but it doesn’t sit right either. It makes you pause and think “What’s going on here?” These moments are worth sharing, but how you share them can make all the difference in whether your team leans in with curiosity or misses the value in what you’ve spotted.

Here’s a small activity to help you practise framing those findings in a way your team can act on.

The Task: Share a surprising finding

1. Think back to a time something didn’t behave as expected. Doesn’t have to be a bug, just something that made you go “eh?”

If you don’t have a real example, imagine a scenario like:
"The password reset option on a login form only appears after three failed attempts.”

2. Write a short message (3–5 sentences) you could send to your team to describe what you noticed.
You might find it helpful to structure it with SBI framework (Situation, Behaviour, Impact) :

Situation – Where/when you saw the behaviour

Behaviour – What actually happened

Impact – Why it stood out or might matter

3. Reflect on your message by answering the following:

What tone did you aim for?

Who did you imagine your audience to be, and how did that shape your message?

What questions might they ask in response?

What might you do next?

6 posts - 6 participants