What did we do?
For the sprint studio this week, we worked together in groups of three to brainstorm ideas of helping scientists gather species statistics through the public by letting the public report data to the scientists.
We first came up with ideas of environments and animals. My group talked about our ideas before we wrote them on the whiteboard. I came up with the ideas of counting animals on the UW campus, such as bunnies, ducks, crows, geese, etc.
Afterwards, we identified users that will report the data and came up with ideas that attract those users to report the data every once in a while.
For my idea of reporting statistics of animals on UW campus, the users of the report app will be UW students, faculties, and sometimes visitors. A motivation for all users is rewards. For example, we may offer students free visit to some scientific institution or labs if they upload their reports often. Another effective motivation is competition. I liked some ideas of creating competitions among users’ friends. Users will usually be more active reporting data they gathered.
Then my group focused to make a flow chart for navigations within the app. We had a map first to locate the user, then we ask the user to enter data or take a picture of the animals. The number which users enter will be directly sent to the scientists. The pictures will be sent to a medium which is responsible for counting animals within the pictures. Then the medium will report the data to the scientists.
The whole studio period was focusing on brainstorming ideas of users interaction design that will make the users like the app.
I personally love low-fidelity prototyping because I can focus more on the key factors in the project. My goal of many things is doing the least amount of work to get the best result. It requires high efficiency. The studio this week helped me to think efficiently. We looked for key ideas such as specific objectives, users, and motivation. These three key ideas allowed us to prototype efficiently.
In the future, I will use low-fidelity prototyping when I need to create a survey. Again, I will need to brainstorm objectives, users, and motivation for users to take the survey.
Here is an example. Suppose I want to find out what the average time that a UW student had been to a Huskies football game in a season is through survey. The users are UW students. Motivations must be set up because UW students do not always have time to spare to take a useless survey that is not useful for themselves at all. Huskies gears coupons are good motivations. UW students love to show their pride as Huskies, so Huskies gears are very important to them. Also, it will be very helpful if there is a link to job openings within the UW football department. Students can find jobs related to football on campus.
I believe low-fidelity prototyping will help me produce a good survey.