Exploratory testing is supposed to be unscripted, but that does not mean one shouldn\u2019t use any patterns \/ heuristics to \u2018explore\u2019 better<\/p>\n

There are a couple of techniques you could use, risk-based testing is one of them.<\/p>\n

There are quite a few recommended practices & activities, one of the I learned recently was to ask others to give their suggestions.<\/p>\n

Think of ideas like a tree with fruit, we have a couple of methods to get that fruit, but sometimes shaking the tree also helps<\/p>\n

In our context, it\u2019s about getting those untapped ideas which I might not be considering<\/p>\n

A good way of doing that is to get help from a person or group of people in a time-boxed session:
\n– Provide some context to the problem
\n– Some oracles and reference material
\n– Giving a time-boxed window to think about all possible risks<\/p>\n

Often you might come across some which you might not have think of.<\/p>\n

Nothing novel here, but \u2018collective\u2019 thinking like this had not been a priority for me before.<\/p>\n

Reference link in first comment<\/p>\n<\/div>