Example Mapping, a form of structured conversation for a three amigos meeting, where a user story is explored through examples.
This is a form of deliberate discovery, where we Learn along the way and develop a shared understanding. Up front, some business rules (aka acceptance criteria) may be 'known', but there will be many that aren't known. This could be because:
it hasn't been thought about
a business rule can be subdivided into multiple business rules
The act of discovery, through asking questions and proposing examples, helps tease out both known unknowns and unknown unknowns. Ultimately, this technique helps minimise rework, reduces the likelihood of building the wrong stuff (speculative features) and reduces the cost of software development. Testing is clarifying misunderstandings
The answer to the unknowns may not necessarily be answered right away, but can be sought independently and brought back to the team.
Example Mapping for discovering unknown unknowns is one technique that can be applied to perform exploration of a user need.
In Example Mapping, the purpose of an example is to clarify some rule.
Indeed, this can even be done in an Agileway, with discovery techniques such as Example Mapping for discovering unknown unknowns.
When Example Mapping, Rules may be known in advance and presented to the group, or they may be assumed or unknown, only to be discovered through the process.
Because the cheapest way to correct a bug is to prevent it happening in the first place, it follows that having high-quality structured conversations (such as Example Mapping for discovering unknown unknowns) can produce this shared understanding at an appropriate point.
Testing is clarifying misunderstandings and through structured conversations like Example Mapping for discovering unknown unknowns can help tease out the common language.