This document discusses exploratory testing (ET) and provides guidance on how to plan and execute ET. It explains that the goal of ET is to discover new bugs, reduce testing time, and satisfy curiosity. While the requirements analysis and test design techniques are similar to scripted testing, ET involves designing test charters rather than formal test cases. The document then provides examples of different types of ET techniques like scenario-based testing, bug-based testing, and heuristic-based testing. It suggests sources of information to guide ET when requirements are not available, such as user documentation, forums, and blogs. The overall message is that testing is an art and ET involves learning about the product through exploration to discover issues.