Class 1 - Personas
The subject of the first workshop was to understand about developing empathy for the potential users of the UX problem we plan to tackle.
To help get us in the correct mindset, we were tasked with creating 2-3 personas and presenting them with appropriate information.
Personas are fictional users of a proposed product that can represent the diversity or the "average" from the proposed target audience. Details you create are based on your empathy for a particular person's plight as they battle with the current state of affairs that your proposed product is to make better.
My UX Problem
I plan on solving an issue I face every day. I am not alone. My target audience potentially covers every FE and HE tutor and student. That's the potential for massive impact. Even if the end product is not revolutionary, it will hopefully be at least evolutionary.
I, like many tutors, conduct personal tutorials with my students. This formalises the formative feedback process and helps the student plan their next move. This could be something as small as a detail of project they are working on, to something as massive as a decision to switch subjects (slightly pastoral).
Currently we use a paper-based tutorial system but it's terribly outdated, inefficient and even ineffective. This is demonstrated by the following personas (full versions available on Adobe EdEx):
Development & Reflection
After watching Mark Shufflebottom's video on what a persona is and how to create one I started thinking about how to best capture the information I need to generate empathy and demonstrate a user-centred understanding of the problem outlined above.
I broke the core data down into qualitative and quantitative - just like when you're conducting primary research (i.e. surveys). You need both to gain an appropriate understanding on both a technical and emotional level.
The qualitative data comes in the form of both an overview (or background) and some scenarios. The idea was to understand the needs of the user firstly though a personal look at the situations and environment they face the issues connected with my proposed UX solution.
The quantitative data consists of a goals vs. pains descriptor - a look at their behavioural traits and a suggestion to their needs and requirements.
I started the process by first creating a script in a text editor to remove all visual distractions which enabled me to focus on the data: