At the exercise we finally entered into the cycles of prototyping by dividing into two smaller groups and then creating one design idea each. This is called “Parallel design”. We listed our pain points, personas and scenarios and created a design with that as starting-point.
Group 1 chose the following base:
Pain Point: Zone System
Scenario: Buying single ticket
Persona: Busra Mirzaie (See earlier post)
The result was the folllowing sequence of post-it notes with clear instructions of each step in the buying process:
Afterwards we sent the design around and everyone got to criticize it. These are some of the critique that came up:
· We need more language options.
· From should autofilled with where we are located at the moment.
· The confirmation screen is unnecessary?
· First step – Larger sign so you can see the machine.
· Pick zone at the top and ”to” and ”from” at the bottom.
· There is no ”back” buttons. You are not able to go back and fix faulty things.
· Should the starting language be english?
· Take away ”Or choose zone”?
· Take away the map?
· You should be able to choose how many zones you are going to cross.
· Information about that children under 7 years travel for free.
Group 2 had the following as their base:
Pain Point:Instructions
Scenario: Buying paper ticket
Persona: Hans Zimmerman (See earlier post)
Group 2 zoomed in on what the first screen the user sees should look like. They came up with lots of different options including one design with a small helper in the corner that would help people that are extra lost. Here is the result:
The critique was as following:
-The little helper shouldn’t be necessary if we our design is simple and intuitive enough. The ultimate goal is that no questions should be asked. Also, no one liked the Microsoft Word helper.
-The design with lots of languages and illustrations of the paper ticket and the acess card is the easiest one to understand.
Conclusion
We then combined both ideas and formed a first design draft for our prototype by choosing the best start screen from group 2 and adding to group 1’s design. We should of course not forget that the scope was narrowed during this exercise and that we should consider a lot of other things when creating our next design. Everyone in the group is happy and are looking forward towards creating the first low-fidelity prototype.
Inga kommentarer:
Skicka en kommentar