Link stories into journeys
"One of the things that makes story mapping so powerful is the ability to
link stories into larger scenarios that cross categories. For example, in
this scenario this user would do a, then b, then c, then d, etc. This helps
validate the completeness of the map as well as the release chunking. If
you deprioritize a story, but then realize it is part of a critical
scenario, you can adjust. Cardboardit allows you to highlight multiple
stories and create a journey from that, but the order is implied and not
Barry Kurtz commented
Having a customer journey by persona mapped on top of a story map is the holy grail of story mapping for me. Superimposing the customer journey map over the backlog shows how the customers interact with the system. Having journeys for each persona and showing and hiding them on the map would be a powerful visualization when explaining why different decisions were made. Here is a 1 minute video I use in my training to illustrate the point:
I really like the way CardboardIt has this implemented. That said, I like the personas in Stories On Board much better.
Having journeys would eliminate a lot of duplication across cards.
An idea from Scott how this could work:
"I would just like a list of journeys displayed to the side/above the board. Selecting one of them will highlight the associated stories on the board.
The journeys need to be prioritised and colour-coded. They should allow for recording of details like target market, target role, use-case. If these could be filtered on that would be cool but not essential.
For me it’s important to understand whether how high priority journeys are covered by our upcoming releases. It is hard to make sure we’ve got everything in development without the journey views. "
Scott Parkin commented
This is critical for release planning to ensure all journeys are captured for early releases. Agree with the OP that CardboardIt has a great first step, but doesn't quite go far enough to be truly helpful.
Dany Poudrier commented
It would definitly help our UX to get onboard of StoriesOnBoard. At the moment they have to create a separate document to identify the different paths of the journey... So by selecting a bunch of cards as one path , I can have multiple path set in the same board.
Agree, super important. As described, in complex softwares, since specific workflows (or "journeys") involves several tasks dispatched in different activities, some workflows share the same tasks.
Would be really useful to be able to "group" some tasks as a "workflow" or "user journey".
One task can be part of one or several journeys. Those journeys can be named.
We can access to the list of the journeys.
Mike Boysen commented
This would tie very nicely into the top suggestion of attaching personas to activities (and I added to subtasks as well) so we can understand the various decision journeys different groups will value