There are numerous articles on the topic of mapping which already do a fine job of describing the technique. What I seek to do here in this practice is to provide guides with brief set of instructions.
This Guide is intended to provide a summary of story mapping that is short enough for the instructions to fit on an index card
The story map image is downloaded from Steve Rogalsky’s "How to Create a User Story Map," available in sources.
Identify the “things people do” (User Tasks). Write User Tasks on blue note cards (second row of the diagram).
Move the User Tasks to reflect initial guesses about sequencing/workflow.
Identify User Activities (major categories associated with application workflow). Write User Activities on orange note cards (top row of the diagram in Step 1).
Move the User Activities to reflect what is known about the workflow; rearrange the User Tasks as needed so they fall under their respective User Activities.
Take a step back and see if any User Tasks/User Activities are missing or duplicative.
Write user stories on yellow note cards.
Write the T-shirt size of the user stories on each one. (Or skip this step if you do not typically estimate user stories.)
Have an initial conversation about how to sequence the user stories, where the ones to be done soonest are at the top, and the ones to be done later are further down in the stack.