A friend shared piece of feedback on what I might be missing from my "What is Exploratory Testing" article, and I cannot decide if I feel it is an omission or if it is how I structure what is what. What they shared is:
I believe that exploratory testing is a separate concept of managing exploratory testing.What I miss when ppl say they have used ET is visibility and learnings from it too. we should have debriefs to share what had been tested, what learned and what to do next. Then tester will learn more from other ppl (vs learning from own tests only).— Marko Rytkönen (@_mry) July 30, 2018
Exploratory testing is the idea of skilled testing where learning continuously and letting the learning change next steps is the core. To manage something like that, you end up with considerations like what if you need to convince others that what you are doing is worthwhile beyond reporting discussions starters like bugs or questions? What if you're not given an area you work on by yourself but you need to figure out how to share that area with others?
When I've been trying to understand that line between doing it and managing it, I've identified quite many things some people find absolutely necessary for managing it to a degree they would not be comfortable calling it exploratory testing without it. I've come to the idea that as long as we're not the testers who are like fridge lights only on when the door is closed with bug reporting, any structures around the days of work of tester are optional. They become necessary as there is a group rather than an individual.