Storyboarding is very useful for showing how interactions occur. It is outlines scenarios, tasks, stories or other requirement formats in a way that captures intended interactions.
To do storyboarding, you start with all possible scenarios for interactions and consider everything involved for each scenario. When addressing these scenarios, remember to apply “Avoid Waste” by handling the most likely and most valuable scenario (or the “happy path”) first.
Use some method to illustrate the solution and interactions. For systems, this could be something like Wireframes showing what screens look like in each step. There could be other methods depending on the nature of the tasks involved.
Finally, take all of those elements and combine them. The key here is to remember this can be used as a collaboration tool, meaning, review it with stakeholders, revise and ultimately validate it before turning this over to the delivery team.
Storyboards can be revisited and revised up to when they are in delivery.
Use Storyboards when prototypes are too expensive, but there is a benefit to having an illustration of the process. For example, these are helpful to collect more feedback before development. Also, they are a great tool to illustrate multiple variations. Storyboard variations can be independently prioritized in order to bring the most valuable variants first.
The context is Understanding the Customer and the audience is Internal Teams.
Storyboarding provides a conceptual level to make things less abstract when discussing with stakeholders. And that engages them in more realistic discussions.
But be careful to keep track of the why instead of just how things are done. Also, it’s important to remind stakeholders the delivered product will look similar but different than the storyboard.