An impact map helps the delivery organisation maintain a strong focus during delivery, and helps to prioritise and define activities related to improving or assuring quality. The role of testing becomes to prove that deliverables support desired actor behaviours, instead of comparing software features to technical expectations. If a deliverable does not support an impact, even if it works correctly from a technical perspective, it is a failure and should be treated as a problem, enhanced or removed.
