Week 14: Presentation & Card-sorting testing

April 13 — April 19, 2020

Jiyoung Ohn
Index Project Challenge
5 min readApr 19, 2020

--

📊Evaluative research Presentation

This week we presented our evaluative stage presentation. We worked on our presentation flow from Saturday, so we were able to be better prepared for the presentation. The following is the link to our third presentation.

https://docs.google.com/presentation/d/1dbdNms1rtaYUpf6-HrkkJuWnH4u3iTVd-fFF1439pMY/edit

We had a lot of things to cover to explain the system and product we have designed. So the presentation got longer then we have expected. Also, we got a lot of comments to develop a way to communicate the story and idea in a more succinct and effective way. We decided to focus on how to make a good story for our final presentation.

Getting feedback from Peter

📊Planning for the next steps

We meet on Wednesday to review all the comments we got and plan our next steps. Overall, we got good comments on the direction we are going. After the presentation, my team took the time to write down lists that we should consider based on the feedback we got. We made sure to make all the comments into actionable items so that it’s easier to think about how to incorporate them into our project.

  • Business model- buy-ins — how are we justifying/ensuring data taker compliance? Sofia feedback: Activist campaign? Civic pressure? Our direction: Policy regulation, incentives for data takers. Look into GDPR and why Google in complying without backlashes. Or is there a backlash?
  • Onboarding- use of visuals, wireframe, workflow simplification, reduction in intellectual burden
  • Dashboard- components, use of interaction elements
  • Service entry-point (and think of narrative)
  • How can we learn more evaluation methods by applying them to our project?
  • Understanding and applying iOS guidelines
  • Accountability question?
  • How can we leverage this to create more awareness about the issue?

For our next step, we decided to do card-sorting testing. We thought this testing is necessary to finalize our information tree because currently, we have a lot of features in the concept. Through user testing, we are trying to figure out how users group and name the features and what features they prioritize over others.

In terms of the final deliverable, we are thinking of making a short video explaining the new feature, something like advertising. Then we are trying to create GIFs of a few users flows to help users understand the use cases. For now, we are thinking of doing it in a presentation format, but we are also considering making a mico-website.

Based on our plans, we made a calendar as follows.

📊 Card sorting testing

We have watched a bunch of videos to understand how to conduct card sorting activity.
https://www.youtube.com/watch?v=TNvdgXCqEvM
https://www.youtube.com/watch?v=FTzHeYPB9c8

Based on the videos, we designed the testing prompt as following. We started to write down all the features that we want to include in the system on the cards. We intentionally mixed the positions of the cards so that participants can rearrange them from scratch.

Card sorting prompt sequence
Card deck

Link to Card sorting results: https://docs.google.com/presentation/d/1ngPi47yFa_TMpnKZOGAfXfTY6rNP4SrHUj5BzQ3CCCs/edit#slide=id.p

Conducting a card sorting activity with users

📊 Synthesize the testing results

On Sunday, we met with the card sorting testing results and shared what we learned from the session. From the discussion, we were able to synthesize the following insights.

  • Pop-up notifications- urgent actionable items
  • Link devices: is not needed because all settings would by default be synced if someone is logged in from the same id on any apple device
  • Export and Import policy in one to combine as a Share button
  • View Requests from services that I’m not using isn’t required, instead, I’d prefer seeing recommendations to choose from
  • View Data footprint and erasure requests shouldn’t be on the same level, maybe data related requests can be accessed through data footprint
  • “View my entire policy” and “Change setting” can be together
  • All updates on policy (my own or of the services) should be under one single tab
  • History/Logs: of policy changes or my data requests
  • If a service is not a good match with my policy, how can I modify the settings for that service to bring it closer to my preferences

Based on the insights, we revisited the card deck and started to rearrange. We decided to combine my data and my policy to create ‘My page’ where the user can review all the things related to individual privacy. ‘Privacy match’ is where you can review all your apps to check which is matching your policy and which not. Last page ‘Community’ is a social page where users can discuss with other users about policy, and also ask questions to the policymakers.

Finalized information tree

We still had a few things that need to be discussed further (Pink colored boxes)

  • Restore settings to an earlier date
    : Is this needed? Where should this be situated?
  • Modify app settings of services that aren’t a good match but the user wants to continue using
    :
    Where should this control be provided? How does this app connect to individual apps?
  • Edit Notification Settings
    : Since we have been removed settings, where should this control be provided? Under iOS settings?

--

--