After initial discovery and planning, the user story map serves as an excellent that supports ad hoc day to day conversations about the system, its functionality, its users, and the typical lifecycle of use. The stories contained in a typical story map may be high level - they type used in initial backlog formation and planning. But the story map works just like a physical geographical map allowing you quickly find the "place" in the system's workflow where the specific story you're working on is located. Once you've found that location in the story map, a wealth of context comes in with it such as the primary user involved, secondary users and stakeholders important to the process, the goals of the user involved, the work they're engaged in, as well as what they were doing before, and what comes next.