Health to the Web

 Love this: https://www.netmeister.org/blog/software-engineering-laws.html #11 rotfl

  User Story Mapping is a way to have everyone on the team collaborate on discussing and brainstorming the problem domain. It starts with the big picture: who are the users and what do they want to do. Then drills down into more detail leading to stories which can then be prioritized and organized into releases.  User Story mapping fosters shared understanding. It helps the team understand the big picture. It is an active process where everyone is involved. It is a pattern for making sense of the whole product or feature and works by breaking down large into smaller and smaller pieces. "we're building a map that lets us tell a really big story about the system".  User Story Mapping involves a hierarchy of: Users Activity - something a User needs to do Task - steps within activity Stories - broken out from Tasks It's arranged in a hierarchy top down, left to right. You could use a tool like Figma (even trello?) or just post its on a white board. The content and the pro