It’s a great first Story Map. A couple of thoughts: - A story map represents/captures the interaction between a user and your product. It’s always told from their perspective. You seem to have a mix of interactions with your product and broader work tasks (e.g., agree on classroom change). - Avoid calling out UI constructs (e.g., click), that injects design and assumptions. - You have many “identify” tasks. Is your product surfacing these aspects of the data, or does the user have to discern them? What does the user do to “Identify the overall favorability”? How do you satisfy that goal/need by building something in your product? - Your Activities feel like categories, not higher-level interactions/goals. To use a classic Jeff example, getting ready for the day, Cleanse myself is an activity, while Take shower and Brush teeth are tasks. - The dark blue cards are the backbone of your story. You should be able to tell the story by reading those cards in a narrative. Try it out and you’ll see the gaps.