Paper-prototypes

Low-fi prototype ideas

Fredrik:

Suhanyaa:

Main Screen of the stationary infoboard

Main Screen with focus on map 

Main Screen when "Tourist Attraction"-Button clicked

detailed description to selected tourist attraction

Edvin:

Henning:

Emil:

Jonas:

Prototype meeting

Meeting 14/10-15

We met up to further discuss our design idea and to start creating a  prototype. We gathered our design ideas and created sketches of our concept(first sketches). When the meeting concluded we agreed that for our next meeting, everyone in the group should reflect on the sketches made and the ideas discussed and then create individual paper-prototypes based on that. The different solutions will then be used to make a low-fi-prototype using either Flinto or Invision. 

Next meeting is taking place on the 28/10-15

A possible design for the front page

First sketches of the stationary info-screen

After the brainstorming, we decided to focus on one of our two project proposals: Improved ticket machine with ability to print a map with directions (and ferry/bus/trail stations)
However, we realized during further ideation sessions, that a ticket machine will not match our requirments that we extracted from the field studies. Our users want to find their route on an easy and fast way. If users can buy their ticket at the same machine, it is more likely that users have to spent a lot of time on the machine, while other potential users have to wait. Furthermore we do not want our concept to be dependent on SL or other companies. Our infoscreen should not only help people that want to use public transportation, but generally everyone (mainly tourist) who wants to find a route from A to B. Therefore, we moved away from the idea of creating an improved ticket machine to creating a stationary info-screen that helps people to plan their route from A to B in an very easy, intuitive and fast way. The info-screen is fitted to the needs of our target user group, the tourists. It also provides the possibility to print individualized map with the chosen route information.

Some of the first sketches of our solution.

Design of the physical device

Main screen

initial screen to animate user to start interaction

main screen with tourist attraction button clicked

choose languages (appears, when flag sign on main screen clicked)

Our Evaluation Method (from seminar 2)

Requirements

Primary Requirements
   - Fast
   - Easy to use
   - User not required to have internet connection
   - Provide all relevant travel information

Secondary Requirements
   - Sustainabilty
   - Fun to use

  

Evaluation Framework

Using the DECIDE framework

Determine the goals
- Does the solution solve the task/ fix the problem?
- Does the proposed solution fulfil the requirements?

Explore the questions
- How long did it take to fulfil the task? (Was it fast?)
- Did you find all the information needed:
- How to get from A to B
- Which transportation means to use
- Cost of travel
- Route
- Where to find the stations
- Travel duration
   - How clear was the information the user got?
- Was it easy to use? 
   - Did any complications occur during performing the task?

Choose evaluation methods 
   - Thinking aloud: controlled setting, user involved
- Analytics: Fitt's Law

Practical issues
   - We have no budget, so it cannot cost us anything
   - ???

Ethical issues
   - Printing papers can damage the environment.

Final evaluation   
   - To make sure the data is trustworthy, we can use triangulation

Feedback

Further define what we mean with "controlled environment":
   - Whom do we use as user?
   - Do we controll all variables? 
   - Where do we perform this?
   - etc...

Notes Seminar 2 - Jonas Masko

Evaluations, the DECIDE framework (cha 13):

1. Goals
   The target group and what they want with the product. This is critical to be able to evaluate the final product.
2. Questions
   Break down the major goal into smaller parts by continually asking "why", giving a set of questions to be answred by gathering data. Which leads to finding a...
3. Method!
   A suitable method to evaluate the product. This needs to be adjusted to the context it is used.
4. Practical Issues
   Budget questions? Are the group of people participating gin user studies relevant? Enough time? Expertice sufficient? etc...
5. Ethical Issues
   Mostly targeted towards the participants. Have they been treated correctly, paid enough, kept their anonymity, contract signed? etc...
6. Final Evaluation
   Time to evaluate the data and result. The result and data should also be able to be presented at this point. Key aspects to evaluate are: biases, reliability, scope & validity.

Different evaluation methods (cha 15):
Analyze the results without a user using heuristic evaluation or walktrough can be done consulting an expert. Walkthrough can involve both expert and user.

Heuristic evaluation evaluates EVERYTHING (real world correlation, standards, consistent, error avoiding, efficiency, memory...). First you brief the participant what is gonna happen and what is evaluated. Experts can initially show "how it's done".

Analytic: Analyzing the user using secret logging (can be an ethical issue...) and then analyzing it afterwards.

Notes on seminar 2

Chapter 13. Evaluations.

Its important to evaluate your work, both with yourself and with a user, so you get many different viewpoints. This helps to understand the users requirements, which takes time for the designers to find out what exactly these are. Things that limit evaluations are tight schedules, low budgets or limited access to users.

The DECIDE framework is a good one, a checklist.

· Determine the goals

Who wants it and why? Let the goals guide the evaluation.

· Explore the questions

Find the questions relevant to the goals, break them down in further questions. Continually ask why, why, why?

· Choose the evaluation methods

Finding the right method is important, so you don’t choose something that does not fit with the issue at hand, for example doing observations on the natural behavior of something, but in a controlled environment. If it’s not their natural habitat, their behavior will not be natural.

· Identify the practical issues

Its helpful to do a pilot study at first, to see the largest issues. Other questions to ask yourself is: is this the right people to participate, do we have the time or the budget for this, do we have the expertise needed?

· Decide how to deal with the ethical issues

Should the participants be anonym? How do we protect their information? Have they signed a consent form if we are to use their info? Have we been honest with them?

· Evaluate, analyze, interpret, and present the data.

Decide how reliable your data is, if its consistent or makes sense. Is the person you interviewed a reliable source? How valid was your evaluation method, now in hindsight? If it effects the environment, or if the environment effected your evaluation, is it relevant? Are we or any of our participants bias? Is that relevant?

Its common to not follow this strictly linearly, but rather jump back and forth, since reality is rarly this simple.

 Chapter 15 Evaluation: Inspections, analytics, and models

Deal with different kinds of evaluations.

Walkthroughs, a expert help the participant.

Heuristic evaluation: Factors like Visability of system status, how it corrilates to the real world, how much freedom do the user has, how good are the standards, is it consistent, how do we avoid errors, is it efficient to use, are important, and its also important to think about that the users should recognize things, minimalistic design, and give them good help.

You start a Heuristic evaluation with a briefing session so they know what to do, then you do the evaluation, where the expert does it first, then the evaluators do it, then finish with a defreafing season.

Cognitive walkthrough, you simulate the users problem solving in each step.

Pluarstic walktrhought.

Several evaluators take on different roles,

Questions for us: What model should we use, shall we follow the decide framework?