Storyboard (Extra) of SIA

Here is the storyboard of SIA in today’s presentation and here I will explain it in detail.

Our aim is to introduce the treasure hunter game to the young children within the community and the idea is to enhance the neighbourhood relationship within the community. Treasure hunter game will be a team work. Children will be set up into groups with 2 or 3 members. It is better for the game as well as knowing each other. Firstly the treasure hunter game will be started from the gate of nearby park or a street the community. The start point can be vary but the concept is to relate to the community, but need to consider the safety of players as there will be many people gather together in a place. Secondly, there is a function called ‘Map’ on the app and players can use it to find locations they need to go next. First place’s location will be give to the player and use the map function to find the place. The clue of the location can become harder step by step. Thirdly, when reach a location, take photos and the player’s QR code will be scanned by the staffs. Volunteers and parents will become stuffs in the game and the QR code is in the ‘My Account’ function and players using cellphone to take photos so easier to upload the photos later in the App and the key idea is to let players know each place in the community better. After that players have to go to all locations shown on the map, take photos, let the QR code be scanned. Finally the finish point of the game will be at the Arthur’s Hill. After the game players can upload their photos taken during the game and give some interactive feedback of the game, for example, what activities you would like to see in the Arthur Hall.

This is the general idea of the storyboard.


Week Log 10 – NUTC

This week we met with Ali, Mark and John who we had decided would be our user testers. We finished our prototype last week so wanted to test it firsthand with stakeholders who could give us an honest opinion on how successful they believe our prototype to be. We completed this test at the civic centre, gaining a lot of very helpful feedback. And decided to leed our user test with the 5 act interview and by giving each one a computer to test and respond with no exterior influence.

Some examples of the feedback were:

  • “We don’t have any strong, clear messages so that’s what I really like, something that’s hard hitting and to the point, talking to driving rather than alternatives.”
  • “Will grab peoples attention”
  • “Directly targets people” – especially the travelling public
  • “Really likable”
  • “Very positive way of reaching out to the people.”
  • “Way of seeing how people feel in a positive sense not just always the negatives”

This was all very helpful as it gave us a lot more confidence in the prototype we have made and it was nice to hear how the council liked our idea and found it believable even thinking of a way they could make our project a reality. The only concerns brought up were the fact that traffic administration people only allow signs in relation to road safety. Although they liked our idea so much they began to think about and suggest to us ways it could become a reality through the likes of roadside signs instead or using modes of transport to display the signs.  

Later in the week we had a workshop on business modelling by Steve Bowden. This  helped us understand how to better our pitch for the proposition of our idea. And taught us how to make a Business Model Canvas.

Business model canvas are based on key partners, key activities, key resources, value proposition, cost structure, customer relationships, channels, customer segments. We figured while doing ours and talking to Steve, that we would have customers (City Council) and users (Heaton Road passers-by) and we could both see our design as a service or product.

Next week we plan to finalise our presentation more, adding the final information with the prototype test feedback, and correct it based on the last presentation feedback, to get it ready ready to present the week after, and to start bringing our blog posts together into a final log for for assignment due dates.


Week 10 – Team 2

This week we began our prototype testing process. We met with Clare Ross, from Gateshead Council at the Civic Centre to show her the PowerPoint presentation prototype of our app for Chase Park. As Clare is one of the stakeholders in our project, it was essential we gained feedback from her for the prototype to ensure we had fulfilled the project goals which were based around the stakeholders’ requests.

Overall Clare responded very positively to our prototype. She was especially impressed with the volunteer hours log section and explained how the volunteers currently use Whatsapp for this, but having this facility on the app would improve communication, make the volunteers feel that they were part of something and make volunteering more sociable. Clare also highlighted that having a public log for individuals’ hours, this could encourage volunteers to complete more hours as it may result in competitiveness. This would have a positive impact on the park and the log could be submitted to the Heritage Lottery Fund as proof of the volunteer hours completed. Clare also gave positive feedback regarding the location service and the ability to share photographs of the park within the app.

Clare only had two concerns about the app. Firstly, she suggested we label the options on the main menu rather than only using symbols; to avoid confusion or doubt of what the symbols meant. Clare also highlighted the obvious issue around safeguarding. Safeguarding is something we need to discuss further as a group and find the most effective way of using security measures within the app without taking the fun out of it.

Clare used the prototype as we intended and we asked her to think out loud as she did. This was useful as we gained feedback from her regarding every aspect of the app. Overall, this prototype test left us feeling positive about our progress but highlighted that we need to think further about the clarity of the visuals and explore the best measures we can introduce for high levels of security and safety.

Our next step will be to hopefully meet with Alan from the Friends of Chase Park to also test our prototype with him and gain feedback from another of our stakeholders.


This week we focused on getting the prototype test scenes done. Since we do not have the technology of the sensor (to identify the thumb up or down), we chose to do the prototype in a powerpoint presentation, we believe this method will be most efficient to display our ideas and present them in the most realistic and interactive way.

The slides show a scene sequence explaining how our design works and what would be the order we imagined it displaying, starting with a newspaper ad, followed by a street viewer scene and the drivers view of the traffic light. Then the different signs are shown and a voting system in powerpoint allows the user to actually vote as it would happen in real life. Depending of the users choice, a different sign or the Twitter handle will follow.

The scenes were made using Canva, Photoshop and Balsamiq, to create the signs layouts and the slides scenes, and a decision map was made explaining how the order the signs would be shown depending of the vote.

We have arranged to meet with Mark, Julie and Ali to test our prototype and see if they approve of our designs. We plan to do this within the civic centre which will be a fairly formal setting but very appropriate as this is where elections sometimes take place or ballots involving the public. We aren’t planning to ask questions during the prototyping but to explain our ideas more and how did we prepare the presentation so they understand when we expect them to actually interact and vote, so we can let our testers have a play around with our project to get to know it a bit better.

User Test Plan:

We believe our prototype is more a service than an actual device and we expect to find out if our users believe it would be effective for Heaton. We also want to find out if after testing it they agree that it would be a good method to introduce the idea that cycle routes are beneficial.

We know the ideal participants would be Heaton road passers by and residents such as Julie herself. But due to Ali’s wishes for us to keep this out of the public as much as possible, we decided to include her, Mark and third party to test it also.

We intend to start the testing with 5 act interview, welcoming the users, asking what kind of travellers are they, if they normally pass by Heaton road… Then, introduce the prototype, explain what it is and how we expect them to interact (after the scenes start voting). Fourthly, task – get them to carry out tasks on the presentation. Fifth, quick debrief to confirm whether they believe it is effective and would be successful.

For this testing we will only need a computer with the presentation and the users. We believe it will be very accessible and easy to perform the testing.


Week 8 Log – NUTC

Log week 8

This week, we started to polish our prototype ideas and which softwares will we use to accomplish our prototype design. We decided to use Balsamiq, Invision, Photoshop, InDesign, Sketchapp and Powerpoint. We have interpreted an interactive prototype as something visual where the people themselves can follow the storyboard that we will present, compared to as if they would play a video or computer game.

For our prototype, we decided to do a scene presentation explaining how would it work from the drivers or pedestrians vision. We intend to create the signs design and to explain how would the entire process work. As we have explained on the previous logs, the prototype is a informative digital sign with a sensor, which the participant after reading a fact would respond with a thumbs up or down to then get a Twitter handle or another fact. On our presentation we hope to be able to show exactly what would be presented to the passers-by, and what their next move would be.

Our group is currently refining the final ideas and trying to get to a final key concept to present in the end of this module. We have divided the work by taking different roles, that is, maker, stitcher, writer, collector and interviewer. Although, we decided that the group will work together and be apart of any role, in order for everybody to be on the same page during the whole process. But we do keep in mind that some of us are more skilled in some of the roles, for instance Gabriela has created the latest visuals for the final presentation, while the others have been collecting information and researching facts about the benefits with cycling as a transportation mode. We have not yet decided who is going to be the interviewer during the final presentation, as well as who to invite for it (but we intend to make Ali, Mark and Julie part of this).

Next step is to continue further with the research about the sensors and how they would work for our interactive signs. We will also continue to read on the different example projects (Australia for Vote etc.) in order to be able to back up our project as well as possible during the final presentation.

These pictures below show the creative process of some of the visuals that we are planning to use for when presenting the final prototype. These were made on Balsamiq and Photoshop.

The visual part of our presentation will be composed by, besides an introduction of the project and example research, introductory scenes that shows the storyboard from different perspectives, for example Heaton Road looking from the “outside” and from a “car view”, signs, thumbs up and thumbs down, responses and a phone with the twitter hashtag #thumbsupheaton.

For the prototype completion we would need more pictures, and the final designs of the facts signs and the Twitter handle sign, in order to include the whole story board that we have created earlier. Combining the new examples and the further research with the prototype designs we believe the we would be able to start with the final presentation.



User Testing – Blog 9 

Who will test it?

For our user testing plan we aim to find out both the successes and failures of our design from the key stakeholders in our project. We want to invite Katrina, Nigel and also potentially some youths living in the area whom Katrina may have some connections to, to also invite, as our design is focused around giving the youth an opportunity to explore their area and create a link between them and 250 Philip Street.


Our test will be conducted in the Wingrove area as this is the base context for our design intervention therefore we would be able to receive genuine feedback of how well the explorer/game works within the setting.

We will need a smartphone for the interface and we thought about including paper charts with factors which we would ask users to rank from high to low, in terms of the games; ease of use, engagement, how well it responds to the brief, the longevity of the game and the overall enjoyment and fun element.

As for team numbers, we decided only 2 or 3 people in our group will take part in the user testing so we avoid the potential for us coming into their community and intimidating the users to respond positively. We want the testing to be as natural as possible as if we were not testing at all, with us occasionally prompting users to ensure we get all our questions answered as Herzum (2016) suggests, for instance:

  1. What would you do next?
  2. How would you use the navigation tool?
  3. Encouraging them to think aloud and ask why they did a certain thing.

We want to achieve “rich verbalisations…by employing relaxed thinking aloud” with the aims of gaining a more insightful response to usability problems and successes (Herzum 2016).

Prior Questioning 

Before testing the prototype however, we want to gain insight into the users’ knowledge of the area now, if they know about events and get involved in them and also their current digital abilities, as some may have little experience with a digital interface. This is one reason why we wanted a simple prototype with obvious navigation features.

Key testing elements

Running briefly through the testing, the participants will engage in the navigation feature and explore their area, completing tasks and activities. We want them to explore the routes and experience the active side to the game. We would also want them to interact with the background features of the calendar, chat, picture albums etc. to determine the success/failures of these as well.

In terms of measures of a ‘good’ design, we want to capture the users view on the ease of use, the durability of the game, and ratings of the ‘fun factor’ etc.

We will document all these through media images, basic charts and stickers, and written statements from users.

We want to ensure the design is a good idea and if it would actually help the community to improve the social connections within the area. The design we are proposing is a unique social explorer into the Wingrove community. At the beginning of our task, the digital scene was scattered with unused Facebook pages, Watsapp group chats and website events. We are aiming to combine all these features and create one interface in which Wingrove residents can check events, interact with one another with regards to these events, with a focusing on the youth as our target users as during our user research many mentioned the need for a youth program in the area. This explorer could be the start of the beginning to bringing the youth into community events, with use of 250 Philip Street, a building which was once a youth club itself.

We want users, particularly the youth, to progress this narrative and allow them to engage with their area through active exploration.


Hertzum, M. (2016). A usability test is not an interview. Interactions, 23(2), 82– 84.

Week 9, Team 2

Blog week 9-

This week we looked at user testing in order to provide a successful app. It is important that we get feed-back in order to improve the app for Chase Park users before we submit our final design. When planning what testing would entail, we think it would be useful to get Alan and Ken from Friends of Chase Park, Claire from Gateshead Council and a number of children from Front Street Primary School to trial our prototype which would be in the form of a power point. A way of carrying out the testing would be by conducting a 5- Act Interview. Firstly, a friendly welcome. Secondly, context questions- asking whether they use Chase Park, how often they go, if an app would be relevant to them etc… Thirdly, introduce the prototype, explain what it is. Fourthly, task – get them to carry out tasks on the app e.g. can you tell us an event or find and create your secret group. Fifth, quick debrief, get their feed-back about the app. When using the app and carrying out the tasks stated above we would get them to think out loud in order to understand the process through new eyes. When it comes to carrying out the user testing it will involve myself, Laura and James. Louis was heavily involved with creating and providing the prototype so as a group we feel it best that he isn’t involved in the interview/testing process. In order to make the app realistic for our testers we are going to be using power-point which will show the images of the app. Hyperlinks will be in place to allow movement between the app pages.

Week 8 Log – Greening Wingrove

Week 8 Log 


What is an interactive Prototype? 

Interactive prototypes aim to show how the interaction will work in practice. This is a much better way to evaluate design. Commercial prototyping software allows you to define clickable areas, transitions and events, in order to produce an interactive prototype that captures the user flow process and demonstrates interactivity, without having to write a single line of code. Basic programs such as PowerPoint and Keynote can be used to create such prototypes. You can use interactive prototypes in user tests before any code has been written. The whole point of having an interactive prototype, and prototypes in general is to ensure that the proposed design will work effectively in practice before spending money, time and effort developing code. 

Our Prototype  

This week we began to work on our prototypes for our Wingrove Community explorer application. The prototyping tools we have decided to use for this project are in a 2D digital format through the use of Microsoft PowerPoint. Our application has two primary uses for its user. The first is to easily and effectively communicate with other residents, which is achieved through the use of a contacts search bar whereby the user can message other people to organize community events and gatherings. It works the same way as your contacts on your phone. The application also includes a calendar to pin community events that are of interest to the user, which is followed by a map which shows the locations of various events organized by the Wingrove Community in the local area. In practice, the map will be interactive giving the user the ability to tap and select locations on the map that they wish to explore. Once a location has been selected the user will see a picture of the location on their screen, and from there, they will have the option to select and search for activities within that vicinity or building. This is where our idea then overlaps with the creation of an interactive form of leisure for the local community. We have done this by implementing an activity section whereby the user can take part by completing tasks designated to various locations e.g. taking a picture of a community landmark within a certain area to prove that it’s been visited, or carrying out some kind of community activity and evidencing it with a picture. Though this feature was designed with primary and secondary schoolchildren in mind, anyone can use it. The whole purpose of our application is to provide community information on the go in a compact and simplistic format, whilst giving the user ways of interacting with and contributing to the local area, or simply keeping in the loop with other residents in the area. In terms of what still needs to be done to complete the prototype, we just need to add some finishing touches that explain and display all the features we intend to include within the application, such as the treasure hunt game. Our idea is basically a social media app for the local community to increase the participation and awareness of local residents.  


Week 8 – Chase Park

This week we looked at prototyping and made a start on creating our own interactive prototype. An interactive prototype is something which is ‘real’ for the user to look at and use. For example, they would be able to navigate around an app clicking on buttons which then moved to a different page etc. so that it feels the functions are real.

We have decided to use PowerPoint for our prototype of our app. PowerPoint is a simple tool for creating a prototype, but it is a tool which we are most familiar with and think it will be able to perform all the necessary functions that we need on our app. We will show our prototype by getting people to go through the prototype app on the PowerPoint by simply beginning the slide show and then the user can click on the buttons, such as a ‘main menu’ button or a ‘home button’ to go back to the main menu, these will be linked with a hyperlink which will make it interactive and give it a feeling of ‘realness’ because things will happen depending on which icon or button you select. We still need to complete a few more interfaces of different pages to the app before it is complete, but below are a few pictures of what our current prototype looks like.


SIA Storyboard (Extra)

This one is the extra post of SIA’s storyboard blog and this is Zhaodong. This is the storyboard of the Greening Wingrove Community App and it is a little bit late to post it to the blog because of my personal issues so very sorry about that.

Basically the idea of the App is to provide a stronger connection between the community and one of our previous ideas was to make a treasure hunter game within the community and now we put the idea into the App which let it become a part of the App.  Apart from the front page the App has four basic functions: Chatting, Calendar/Activities, Local Map and ‘My Account’. On the front page you can see the local temperature and weather today as well as the news and announcements within the community. The treasure hunter game is set as the latest news here and can be clicked for mor info. and we made some analysis on it (you can open the picture attached and have a look). The chatting function is similar to the iMessage but apart them a new function is designed called ‘Moments’. You can share your own special events happen around you here and let your friends to look and make comments. Calendar/Activities function looks like the calendar on your phone but also shows the activities that will take place as well as the activities that you will attend and show you the location of the activities. For the Local Map function, the location with schemed activities will be marked and able to be clicked and you can see different activities within the area and these are related to the Calendar/Activities function. ‘My Account’ is very easy to understand: manage your personal account, make self-introduction to others, add more friends and precious pictures into your album. More infomation of the App can be seen in the picture attached within this post.