The 'What' of Data Driven Decisions
Next week, I will present my talk “Data Driven Decisions in Testing” at my first conference of the year, Agile Testing Days USA 2023.
I’ve given this talk a few times now and once those people have thought about the presentation more in the weeks that follow, they come to me with more questions. They want more examples of how they can start asking questions in their teams to get more data driven decisions happening. This is good! This is the whole idea behind this talk.
So, I’m going to split my answers to this into a mini blog series:
- The “What” (this post!)
- The “Where”
- The “Why”
- The “Who”
- The “When”
- The “How”
I like to start conversations around data gathering with questions like:
- What does the user care about with this feature and how can we measure that?
- What does success of this feature look like in numbers? - Usage statistics, financial goals, new sales, reduced abandonment rate, better app store reviews, reduced number of errors
- What can we measure currently?
- What data would we like to track?
These questions are essentially all asking the same thing but the framing of them is different depending on my audience. They all boil down to:
What number do we care about the most as an outcome for this?
Have you tried asking any of these questions in your team? What did you learn?
I’d love to hear from you!