About the scenarios.
We based the scenarios on our personas, introduced in last post. Whereas the personas focused on the target users themselves, the scenarios takes us to hypothetical situations the user is most likely to use our product.
We decided to do two scenarios, instead of three (one for each persona), simply because the student and the high schooler’s personas doesn’t differ that much.
The student’s scenario
Truls is taking a new course in his second year, and the first assignment is a group project. Truls doesn’t know anyone yet from this particular course and has no idea who the people he has ended up with in the group are or how to recognise them during classes. This stresses him, because he doesn’t like to waste time having to look them up on social media and initiate contact there. Fortunately, he has their names, so he logs into the LMS, types in their names in the chat bar and starts a group chat with them, where they agree to meet up in the hallway outside the auditorium at eleven o’clock and discuss their ideas further.
The teacher’s scenario
Jan Kåre has gotten the opportunity to involve digital technology in his lectures, but the software needed is quite new and requires a licence for money. He proposes his idea to the school administration, and they agree it’s an exciting idea. They buy a school licence, and the software is added as a plugin feature on the school’s LMS, easily accessible to Jan Kåre’s pupils.
As we can see, the teacher has a far more mod-esque role than the student.
Now, lets try to visualize these scenarios in a storyboard, shall we?