Storyboarding will help you create an understanding of what occurs when a user is first triggered the need for a Job to be done through to when they complete that Job.


There may only be parts of the story that occur within one or many systems. On one or any devices. And may contain many separate tasks.

For example, if the story was to catch the train to work in the morning – you’d need switch your alarm off, get ready, check the arrival time of your train, commute to the station and board the train.

Using stories in some form or another is a well-established practice in software design, so much so that there are many meanings of the term “stories.” For instance, in agile processes, there is a concept of “user stories,” which are very basic units of expressing functional requirements: “As a user, I want to receive notifications when new applications are submitted.”

In their book, Storytelling for User Experience, Whitney Quesenbery and Kevin Brooks offer these benefits of using stories in software design:

  • They help us gather and share information about users, tasks, and goals.
  • They put a human face on analytic data.
  • They can spark new design concepts and encourage collaboration and innovation.
  • They are a way to share ideas and create a sense of shared history and purpose.
  • They help us understand the world by giving us insight into people who are not just like us.
  • They can even persuade others of the value of our contribution.
  • Whatever they’re called, stories are an effective and inexpensive way to capture, relate, and explore experiences in the design process.

Great longform explanations: