This week we had a short lecture and then completed storyboards in groups.

Reflection - This week started off with a short explanation of what a storyboard is and then straight into storyboard creation with groups. I love the group work in this class it was engaging and fun, and it was a good way to not take it so seriously. I also enjoyed seeing what others created with the same directive, especially the more fun that had with the story. It helped also realise there is more than booking and arriving, there is a whole ongoing story.

Storyboarding is defined as ‘storyboard communicates a story through images displayed in a sequence of panels that chronologically maps the story’s main events’. We use it to explain who, what, and why we are making a choice or a concept would work. There are three things to consider before starting.

1. Scenario - they are based on a person or story so it has to be outlined to explain the user story and the storyboard as a whole.
2. Visuals - the level of visuals will depend on who it is to be explained to, as when it's for the designer it can just be very ruff but if it is for a stakeholder you should consider doing it in a lot more depth.
3. Captions - each slide should have an explanation, that should be straightforward, clear, and doesn't confuse the reader.

There are lots of reasons to use a storyboard

1. Usability - as you have been working on a project you have grown to understand and know a lot through the research but the people you're showing this to have not got the same understanding so it gives them an explanation and shows the usability.
2. Context - while displaying the story it helps you understand all the steps and the whole story creating a more in depth understanding that you can show, which is easily seen in creating empathy for the story
3. Prioritisation - when creating and showing the storyboard you and a team can decide what's most important making sure that nothing is added unnecessarily.
4. Ideation - they make you see the whole story together and what you can create with it, creating a more positive user experience.
5. Memorable - a storyboard will be remembered more than just a story of a user, people like visuals, that will stand out and make investors or clients have faith in it.

https://www.nngroup.com/articles/storyboards-visualize-ideas/#:~:text=Definition%3A A storyboard communicates a,for your team and stakeholders.

This is a good example of a very clear storyboard, that is easy to understand and isn't confusing. It was created by Cheryl Platz a designer, I really like this storyboard, it just needs a short explanation beside each slide.

Site maps are a great way of understanding everything that is needed in the UI, breaking it down into understandable areas. There are other benefits to using site maps.

1. Hierarchy - the site map will help you understand where pages will be, the layout, and what will be accessed on each page.
2. Users - a site map will help you see it from a user's perspective and how they navigate through the UI.
3. Mistakes - help understand areas you have missed or aren't accessible or if are there multiple pages.
4. Explain - to others how you will use the interface and help justify decisions.