Hello again,
This week we started planning out our prototype. We aim to have a somewhat high fidelity design which should be able to be used in an interactive way, for this we plan on using the online tool ‘Invision’. We’ve reached out to our stakeholders and booked a meeting with them so they will have the opportunity to test our design first hand. We hope to discover if our design has an easy to understand and simple to use interface, is enticing and time efficient, relates information about the Streets for People program and the planned changes in a useful way and, lastly, collects feedback appropriately.
To do this we need to create pictures, or so called slides, depicting how the interface should look like. For example we need a welcome screen, a map over Jesmond showing where the locations are, a location slide with information and ways of feedback, a slide showing previous comments, and an ending slide providing the sticker. All of these will then be uploaded into Invision where they will be linked together so as the user could use it in an interactive way.
For our user testing we will divide the stakeholders to try out the prototype on individual screens, with each one of us as a personal guide assisting/monitoring their progress. We will after this ask some prepared questions one on one before joining together for a group discussion about the prototype and design. Hopefully they will give us an unique insight of how the design is perceived by a user.
Hello team, a brief post but that’s perhaps fair enough for the prep task. First of all, it’s good to see you are approaching the prototyping task with a clear goal in mind (based on what you like to test in week 10). You could have perhaps elaborated this to greater details. Without understanding your prototype and your project, I would not know what kinds of user paths you like to test with users for example; and in relation to this what kinds of approaches to prototyping you considered (e.g. why Invis.io app).
Some other notes: (1) what needs prototyping to high quality, what needs prototyping to lesser quality; (for example, what about the stand you have been considering building). (2) How have you decided to allocate prototyping tasks and were the roles suggested by the Sprint book useful or did you find a different arrangement?
As for the user test, I spoke with Tony and he was noting that he hoped for a consultation tool. While this is likely not possible to implement a functional prototype by the time of the prototype demonstration; is there any way in which you can use your prototype as a discussion prompt, still collate responses, and practice the handing out of tokens to public participants? This aspect might need some discussion somewhere in your reflective log.
Onwards. Sebastian