Update #7 – Final Recommendations & Reflection

A. FINAL CONCLUSIONS AND RECOMMENDATIONS

Overall, we think that we have successfully validated our proposal, although we have also identified major gaps that need further work. The main idea behind our design was that anyone can feel comfortable reading and sharing political news, although today that activity is commonly perceived as a special interest of a particular kind. We tend to interpret this attitude as something that needs to be changed, rather than a constraint that could discourage further work.

As our experiment showed, our prototype didn’t surpass Reddit overall, however it didn’t fall behind either: no significant differences were observed in performance speed and perceived user satisfaction. As we were putting our prototype next to a fully polished app, used daily by millions of people, the comparison was somewhat not in our favor from the beginning. In that light, we interpret the fact that the prototype finished close to Reddit in terms of performance speed and user satisfaction as a success. We conclude that our proposal is viable, although further development is needed to make it really comparable to existing popular systems.

One aspect of our app that calls for further in-depth study is the moderation process. Based on our experimental results, we concluded that our moderation proposal shows promise, however our subject pool was quite small to understand how moderation will work in real-world scenarios. Therefore, we recommend a further study that would involve a larger pool of participants, as well as a bigger sample of the articles that have to be moderated during the task.

Other recommendations include:

  • Supporting Android as well as iOS: we didn’t have Android support in our experiment, which slowed down several participants with no iOS experience;
  • Make sharing much quicker, available directly from the browser: copying the URL and article headline from one app to another was very time-consuming;
  • Detecting the names of political figures in the article automatically: our participants needed to find those names in each article, which took a lot of time;
  • Including more features in the prototype: it will make the comparison with an existing system more fair.

Crucially, a key insight from our project is that credibility and trustworthiness need to be considered as central design problems when designing digital media. Filtering the stream of news is a crucial feature expected today by many users, and the lack of it could lead to the users being less engaged with a particular medium overall.

 

B. REFLECTION ON THE DESIGN AND EVALUATION PROCESS

We gained a large amount of insight from our users that would not have been predicted based on our own experience and intuition:

  • During the field study interviews, we initially assumed that sharing news would be a more prominent feature.  However, we learned that a large majority of our users were consumers of content, not sharers.  This apprehension towards sharing political news with strangers and acquaintances was not predicted based on our own insight.
  • We considered addressing this issue by allowing users to post anonymously, but the problem of slanderous posting arose.
  • This idea then eventually evolved in into the user moderation of news articles.


In addition to insight about our users, we gained experience with design methods.

  • We conducted multiple brainstorming sessions throughout the entire design process.  These brainstorming sessions provided two key benefits:
    • First, we were able to better conceive novel ideas as a group while sharing our thought processes.
    • Second, we realized which ideas were more popular because of the immediate reactions received.
  • In order to organize the scattered thoughts created during a brainstorming session, we began to use affinity diagrams.
  • Affinity diagrams helped organize the entire group’s ideas into useful themes that could be delved into deeper.  In conjunction with brainstorming, this method was the most useful for generating ideas and coming to a consensus.
  • The pilots provide good feedback that helps avoid collecting useless data during the actual experiment.  They also helped polish the experimental procedure, this aided in making the actual experiment more professional.


Prototyping

  • It was exciting to see our proposal come to life when the prototype was made. It would have been hard to present our ideas to the users in any other way: the prototype is almost universally accessible, and our participants were comfortable sharing opinions about it.


Experiment

  • We used both interviews and questionnaires to gather data during the studies.  We found that interviews were better than the questionnaires in collecting useful data.
  • The participants would interpret the long form open-ended questions on the questionnaire as optional.  This was likely due to sheer laziness.
  • Once asked to provide the same answers verbally, all the participants complied and provided far more rich and useful data.
  • We didn’t find video and screen recordings particularly valuable for gaining new insight about our proposal. It worked ok for documenting the experiment, but we didn’t really gain any new information from the footage.
  • Although they provided rich data, the analysis of video data was far too time consuming and unrealistic.
  • Having an additional interviewer present during the experiment filled in the gap of missing data that one interviewer may not have been able to collect, thus negating the need for video recordings.


What we would’ve changed

  • Perhaps we would avoid fully transcribing user interviews, as that was very time-consuming. An approach that would have worked better is having two interviewers, with one guiding the interview and the other taking very detailed notes.

Update #6 – Experiment Abstract and Materials

A. PILOT TEST

After performing 2 pilot tests of the experiment, our team decided upon a few minor modifications for the experiment protocol and study instruments.

We initially planned on video recording all 10 of the interviews, however we realized that this was not feasible due to time constraints. Instead we video recorded 5 interviews, and in order to make up for the lost data, we also did screen recordings of the entire experiment.

The open-ended questionnaires were too easily dismissed by both the pilot participants, we believe this occurred because of sheer laziness. As a result, we decided to ask participants to elaborate verbally. This seems to have provided far more rich feedback.

The final study instrument which required modifications was the coding sheet.  After performing both the pilots, it was very apparent that the coding sheet was seriously lacking.  We decided to completely remake the coding sheet with more appropriate sections and fields.

Finally, we realized that our interface was not clearing the text fields in between posting stories. This bug was resolved before we began running actual participants.

 

B. EXPERIMENT ABSTRACT

Consuming and sharing news is an essential part of today’s social media landscape. In that setting, numerous issues arise around the credibility of the news, as online activities converge around entertainment and advertising. It is difficult for news consumers to have consistent access to reporting that is factually true, valuable, and unbiased. We propose a mobile app for engaging with real-time political news, allowing the users to interact with information that is crucial for transparent democratic governance. We asked our participants to share a story with the prototype of our app and with a popular existing news app, and found no significant difference in task completion time. No significant differences in user satisfaction were observed. We also found that peer moderation can be an adequate mechanism for filtering out inappropriate stories. We conclude that our proposal is viable and suggest several crucial improvements from a prototype to the actual implementation.

 

C. REVISED SUPPLEMENTARY EXPERIMENT MATERIALS

Update #4 – Experiment Design

a. Revised Experiment Goals

Sharing: Is the process of sharing a piece of news easy for the users, as measured by time and number of mistakes when compared to a similar real world application?

Satisfaction: How satisfied are users with the overall experience?

We have decided to delve deeper into the experimental goal that focuses on sharing, while avoiding the moderation and filtering goals mentioned in a previous blog post, as sharing was a major sticking point among all participants during Milestone II.  We hope to run an experiment which will help us better determine what is required to make sharing an intuitive and well received feature.  We have decided that comparing our sharing/posting feature with another successful real world product, which performs similar features, will provide adequate feedback as to whether our system is successful.  We hope to determine satisfaction levels via a questionnaire that addresses the seven aspects of the user experience honeycomb.

 

b. Experiment Method

Participants:

We plan on recruiting 10 participants from our social circles into the subject pool.  We chose to use the aforementioned approach because our experiment does not have a strict requirement for participants, as the expected user population for our system varies greatly. The ideal candidates for this experiment will have little to no experience with Reddit’s mobile application. We can determine whether this is the case during an intake survey. We hope to find candidates who have little experience with Reddit because we will be comparing our system against Reddit’s mobile application, and if the participants are experienced with Reddit’s mobile application, our system will be at a disadvantage during the experiment.

Conditions:

For the experimental goal of sharing we will use time as a measure of how easy sharing is (a faster time indicating a more intuitive sharing interface) and we will count the number of errors made when the user tries to post an article.  The aforementioned performance data will be collected with an identical task from both a real world product (Reddit’s mobile application) and our application.

Tasks:

The user will be asked to explore the first application for 30 seconds. After this exploration period, the participant will be asked to share the same news stories using our application by posting it through our application.

Design:

Our experiment will follow a basic 2-sample (2 condition experiment) experiment.  We plan on making a comparison between the performance data from Reddit’s mobile application and our system design.

Procedure:

  1. The interview should be conducted by two interviewers involving one participant at a time.
  2. We will first ask the participant to sign a consent form, and brief the participant on the experiment that will follow.
  3. A camera will be set-up on a tripod, without a person behind the lens.  This is a deliberate decision to minimize the awkwardness of introducing a camera to an experiment.
  4. The interviewer will follow the script (4.c) as closely as possible, in order to provide all the participants with a similar experience.
  5. The participants will be asked to complete a pre-questionnaire (4.c) that will gage demographic information, and more importantly previous knowledge about similar systems.
  6. A printed out sheet of tasks will be read aloud and then handed to the participants. This will be done in order to avoid having to remind participants of the task.
  7. Half of the subject pool will be asked to explore Reddit first, and the other half will be asked to explore our system first. This is done in order to avoid bias that may be introduced by having learned the tasks, considering identical tasks will be completed on both applications.
  8. Interviewer 1 will be observing and taking free-hand notes, and interviewer 2 will be filling out the coding sheet (4.c).  We have decided to use 2 interviewer because we feel that a single interviewer may be unable to capture all the small details of the participants interaction with the system.  We also understand that not all interviewers are alike, and some may be more capable of collecting useful data. We hope to minimize lost data by having two interviewers and recording video of the interaction.
  9. Next, the participant will be asked to explore the news feed in the first application for 30 seconds. The participant will then be asked to complete the first task. Which is to post a predetermine story to the system. This interaction will be timed, and an error rate will be determined.
  10. After a quick 1 minute break to regroup, the user will be asked to do the same task on the second system.  A 30 second exploration period, followed by trying to post a predetermined article on the application.
  11. Finally the participant will be asked to complete a post-questionnaire (4.c).  This questionnaire will determine general satisfaction levels according to the user experience honeycomb and any other feedback the participants have.

Apparatus:

  • A camera will be set-up on a tripod in order to record the participants’ interactions with the application for a later, deeper, analysis.
  • In order to ensure that conditions remain consistent between participants, the user will be provided with an iPhone that has both applications pre installed.  The location of the experiment is an informal setting that the user is comfortable in (E.g. the participants’ work area).  This is in order to emulate the location that this application may actually be used in.  We feel that conducting the experiment in a lab setting will be unnatural.
  • The script will be printed out and available to the interviewer if needed.  The tasks will also be printed out, as the participant may need to reference them during the experiment.
  • A laptop will be provided, as it will be needed in order to complete both the pre and post questionnaire.

Independent Variable:

Types of interface

  • MR. JDK’s prototype
  • Reddit’s mobile application

In this experiment, we will compare user performance, on a specified task, of Mr.JDK’s mobile application to the performance of using Reddit’s mobile application.

Dependent Variables:

Participants’ satisfaction level:

  • During post experiment interview, we will ask user to mark their level of satisfaction on the Like-Chart which allows participants to choose the answer on a continuum of numbers from 0 to 100

Time of completing the given task:

  • We will use a stopwatch to keep track of duration.

Number of errors:

  • We will mark each error made by users when they perform the task, and add them up at the time of completion.
    • Definition of error: participants click on the wrong button while completing the task.

Hypothesis:

H1:

Sharing/posting news stories on Mr.JDK’s prototype leads to faster user performance (measured as time to complete the task), compared to the Reddit’s mobile application.

H2:

Sharing/ posting news stories on Mr.JDK’s prototype will be less errors prone than sharing/ posting news stories on Reddit.

H3:

Using Mr.JDK’s prototype generates a higher satisfaction level than using Reddit.

Planned statistical analysis:

There are three factors we are measuring in this experiment: number of errors, time of completion, and numerical form of participants’ satisfaction level. We plan to use both T-test and ANOVA, giving us the options to examine the collected statistics from two different angles.

  • ANOVA: Due the nature of our experiment design, ANOVA will be an ideal statistical analysis tool. Our design experiment is moderately complex, including independent variables and specific value of independent variable. ANOVA allows us to compare means between two or more factor levels within a single factor and determine whether there is a difference between two sample groups. Using ANOVA to compare the relationships between many factors provides more informed results, considering the interactions between factors in our experiment design.
  • T-test: We plan to use two-tailed unpaired T-test in order to establish the confidence level in the difference we will probably find between 2 sample means. Specifically, we will run a between-subjects experiment, where we will count the number of errors under each condition, time the duration of completion and satisfaction level. In order to compare two sets of independent observations, and determine whether if Mr.JDK’s prototype is better than Reddit’s mobile application or not, we as designers need to figure out whether there is a significant difference between the means which T-test can provide valid an answer.

Expected limitations of the planned experiment:

Due to time, and financial restriction, we are only able to recruit 10 participants to conduct our experiment and confirm the quality of our medium fidelity prototype. The limited amount of participants may to lead to less significant difference in data from two sample groups. As designers, we should keep in mind that statistical insignificance does not imply that the difference is not important. We could counterbalance this by taking even trivial difference into account.The fact that we drill down into one aspect of this application – Sharing could lead to a higher error rate due to the lack of horizontal design and the vertical depth in most part of Mr.JDK’s design.

 

c. Supplementary Experimental Materials

Update #5a – Rationale of Medium Fidelity Prototyping Approach

  1. How much horizontal and vertical?

Our medium fidelity prototype will be moderately vertical, with some horizontal aspects. Our prototype will include the ability to browse the news feed and post news stories. We will only have a select few stories that the user will be able to view, and the user will not be able to get out of the boundaries of the story posting workflow. Also, each news story will be either marked as trusted, or not trusted (depending on the news source) this aspect will also be horizontal since it exposes the feature of the app that tells the user whether a particular news source is trusted or not. We will have a horizontal upvote, downvote, and a report button on the bottom of each news story because these buttons won’t be functional. Finally, we will have several tabs at the bottom of the screen, such as “Newsfeed”, “Browse”, and “Share”, which will hint at the other pockets of the application.

  1. What (simulated) functionality must it contain? What can be faked? How specifically, from a technical standpoint, do you plan on doing the faking? The goal should be that the subjects are as unaware as possible that the system is not fully implemented.

The simulated functionality that our prototype must contain is a necessary and sufficient set of features for reaching our experimental goals. One of our goals is concerned with the ability of the users to share news stories within a consistently short amount of time. This question can be answered by exposing the users to the sharing functionality in our prototype, and comparing the outcomes to the user sharing a story on Reddit. Since we are letting users to actually make posts we don’t have to fake this functionality. However, for our second goal regarding the satisfaction of users with the overall experience we must take a more nuanced approach because satisfaction is usually measured by the overall feel of our application, and thus it is dependent on the app offering seamless functionality. Since we will have limited functionality in our prototype, we will be faking other aspects of our prototype by having dummy buttons (I.e. upvote,downvote, report buttons) and other fillers like whether or not a news source for a particular story is trusted. The faking of these aspects is relatively easy to implement in our application because our prototyping tools allow us to put in dummy buttons and other fillers that look real but aren’t functional.

Subjects will most likely be unaware of the faked functionality of our prototype initially, however they will become of it as soon as they try it and see that no results ensue. The task posed to the users will not include engaging with the faked aspects of our prototype. However, the purpose of including the faked features is to increase perceived user satisfaction by making the prototype visually appealing so it looks more like a realistic application.

  1. How important is appearance?

The appearance of our prototype is quite important because one of our experimental goals relies on user satisfaction, and appearance usually plays a big part in a user satisfaction.

  1. If your interface includes physical (non-graphical) elements, is it useful and/or feasible to augment your functional prototype with form mockups?

Our interface will not include physical elements.

  1. Finally, decide which prototyping tools to use. Most likely you will want to use one of the tools available in X360 (this includes all software available on the general CS ugrad lab machines as well software only available in X360: https://www.cs.ubc.ca/ourdepartment/facilities/hci-learning-studio/resources). Use a combination of your group’s skills / comfort level, and the requirements for the prototype to make this choice. IF YOU ARE EXPECTING TO USE A LANGUAGE or TOOL NOT INSTALLED ON x360 COMPUTERS and THAT IS NOT OTHERWISE EASILY AVAILABLE, CONTACT COURSE STAFF FIRST.

We will be using Atomic.

Update #3 – Low-fidelity Prototyping & Cognitive Walkthrough, Proposed Experiment Goals

A. Further updated task examples

The task examples outlined in Blog Update #2 remain unchanged. Please refer to this link for a comprehensive summary of the task examples.

 

B. Low-fidelity prototype(s) demonstration

An annotated version of the paper prototype (in PDF format) is visible here.

 

C. Additional information about the prototype

The prototype was designed to support all three task examples from the outset. We aimed to ensure that the three most salient features, as described in the task examples, were the core of the design; the minimization of bias, the aggregation of multiple news sources, as well as more granular control over the user’s news feed were the guiding principles during the development of the low-fidelity prototype.

To this end, we chose to use a social media news feed/timeline (e.g., Twitter) as our primary design analogy, as many of our participants from the MSII field study expressed a desire for a more real-time way of receiving news. This analogy furthermore allowed us to imitate social media’s core conceit of “following” specific political figures, allowing the user a greater deal of control over the sort of content they would see on their own particular timeline.

In addition, the idea of “user karma” was floated during the brainstorm process as both a means of giving users credibility without compromising their anonymity, and as a guiding framework for user-driven moderation. In this way, many of the issues and concerns regarding user anonymity are addressed. The “notifications” screen now reflects this score in addition to which shared news items are queued for moderation, as well as system messages regarding whether or not a user’s own shared news items were approved/rejected.

In terms of scope, we aimed to communicate a typical user workflow by defining the main screens of the app, but developing the bulk of the interface horizontally without diving into too much detail. As the interface itself was designed from the outset to be a streamlined news aggregator, we didn’t really need an enormous level of verticality to define the aforementioned workflow; the most detail went into defining the process of sharing a given piece of news.

 

D. Walkthrough report

The purpose of the Cognitive Walkthrough is to figure out how easy it is for new users to use the system, and to determine any issues early on in the design process before starting work on the medium-fidelity prototype. Throughout the cognitive walkthrough, here is the list of questions we ask ourselves as designers:

  • Will the user try to achieve the effect that the subtask has? E.g. Does the user understand that this subtask is needed to reach the user’s goal?
  • Will the user notice that the correct action is available? E.g. is the button visible?
  • Will the user understand that the wanted subtask can be achieved by the action? E.g. the right button is visible but the user does not understand the text and will therefore not click on it.
  • Does the user get appropriate feedback? Will the user know that they have done the right thing after performing the action?

Here are the findings from the walkthrough:

  • On the ”Landing page”, user could be confused about the news feed with the “Sign in” tab. Specifically, user might directly click the news feed instead of the “Sign in”, and there is no feedback to indicate what user needs to do – Sign in as a new member of the App.
    • Potential solutions:
      • On the landing page, the interface only includes a “Sign in” tab. This way user shall understand that they need to sign in order to use this application.
      • Interface could have both “Sign in” and news feeds, but we as designers need to make sure that there is enough feedback. If user clicks on news feeds on the landing page, there will be an indication, saying that user needs to sign in first.
  • On the “Suggestions for you”, user could potentially be confused since there is a filtering system to select user’s preferences.
    • Potential solutions:
      • Designers could take out this page completely as it conflicts with the existing filtering system.
      • Designers could keep this tab, suggesting users what political figures they might be interested in outside their preferences as a supplementary page.
  • On “Repost page”, users could think that they need to write a summary in order to repost and there is no feedback to indicate otherwise.
    • Potential solution:
      • Designers could input a sentence in “Summary” that it is not necessary to write it in order to repost.

Beyond these issues, the user had no problem understanding the primary news feed, as well as the design conceit of “following” specific political figures, which was our main concern.

 

E. Proposed goal(s) of experiment for part B

From the design of the low-fidelity prototype, we decided to proceed with the following experiment goals, reflecting each of the core guiding principles that went into the development of the prototype. They remain relatively unchanged from our brainstormed experiment goals from previous milestones, but are listed below.

  • Sharing: is the process of sharing a piece of news intuitive? Can users share pieces of news without making many mistakes?
  • Filtering: is following/not following specific political figures a sufficient level of control/filtering? Should users have more control beyond that?
  • Moderation: how much consideration do people put into moderating news in their queue? What sorts of news do people tend to rate negatively? Positively? Is this convenient?

 

Update #2D: Design Alternatives

DESIGN PROPOSAL 1

Pros: concise, affords searching.
Cons: doesn’t afford browsing, no voting/flagging mechanism.

This design alternative takes inspiration from mobile apps that feature a news feed as part of their core functionality, e.g., Twitter. News items are displayed in a sort of ‘capsule’ type window, featuring the picture of the political figure in question, along with a brief summary of the news item itself. Adding to the Twitter analogy was the design requirement that users must be able to easily follow and track political figures of interest, and so a ‘profile’-type screen for each political figure was added from which users can easily check the most recent news items featuring that figure, as well as ‘follow’ them, adding them to their personal news feed.

Proposal 1, Sketch 1

 

DESIGN PROPOSAL 2

Pros: focuses on browsing the list of politicians to add them, allows exploring different subject topics, allows commenting.
Cons: doesn’t afford searching for a politician, doesn’t make clear how news is shared, commenting might become a problem because of abusive language.

Notes about pictures

A: You can select ‘major politicians’ by country or you can select ‘local politicians’ based on your gps location. The dropdown for ‘local politicians’ just specifies the distance in order to fit your definition of ‘local’.

B: Once you select either the ‘major politicians’ or ‘local politicians’ category (Note: It’s possible for politicians to be in both categories) you can sort politicians by popularity, ‘recent news’ (a politician that has recent news released about him/her), province, etc.

C: Once you select a politician you can sort the news about them by issues such as the environment, the economy, etc. Also, each particular issue like the ‘Kinder Morgan Pipeline Approval’ will have multiple news sources that are considered liberal, moderate, and conservative to get a more clearer and neutral understanding of the issues. Finally, there will be a comment section and all users will be anonymous to ensure privacy and there will be a simple up voting/ down voting system for each comment. Each user will be able to make one up vote or down vote per comment and the comments will be sorted by highest rated, lowest rated, etc.

D: Finally the ‘More News’ button in Picture C will lead you to this menu where you can choose more news about that particular politician with respect to the chosen issue from picture C (I.e. Environment).

 

DESIGN PROPOSAL 3

Pros: affords searching and browsing, supports sharing and flagging of news.
Cons: doesn’t support subject topics for news, news feed is empty by default.

In this smartphone app, the first time user is greeted with a screen that invites them to search for a political figure and offers some suggestions. If the user wants, they can browse the list of politicians by level, area, field of engagement, etc. On the politician profile page, the user can follow the figure, get more information, and see their recent news, activities, and current location.

Once the user is subscribed for news, some news is delivered to the lock screen of their phone. From there, the user can go to the page of the news piece, where they will find a link to the source, as well as the controls for flagging the piece as inappropriate and approving or disapproving of the politician’s activity.

If the user wants to share the news, they can go to a dedicated screen where they will have to paste a link to the source, or choose the politician the news applies to, and specify the place where the news happened. They can then submit the news for community review. Each particular piece is sent for review to several users at one, which they get notified about in real time. Once the piece passes the review, it becomes available for the audience of the app.

 

DESIGN PROPOSAL 4

Pros: good focus on a particular politician with respect to what events relate to them, easy to find all the different news sources for a single event.
Cons: Screen on the third sketch may be confusing for the user (are Breaking news / Top stories related to all politicians or just to a single one?)

On the landing page (sketch 1), there is the list of political figures that the user cares the most. In the sketch, they are labeled as “poli fig 1/2/3”. These are clickable buttons, and will lead users to each political figure’s own news feed page. Also on the landing page, there are “area 1/2” that are either the area the users are in or care the most about. After that, the list of top stories and breaking news is presented.

In the following sketch (sketch 2), I focused on political figures: for each political figure, there is a page that summarizes all the news updates for him or her. All news updates are grouped by each distinct event, therefore no report on the same event will be presented twice. If the user wishes to browse different sources reporting on one particular event, he or she must click on the event itself, which will bring the user to the page solely dedicated to one news feed (sketch 3). This allows user to choose which feed he or she wants to read first. The sources are ordered alphabetically, which helps avoid bias that might be introduced by the popularity of a particular source, or user’s personal preferences.

 

DESIGN PROPOSAL 5

Pros: allows a fair bit of flexibility and discovery when browsing the news, rich profile pages for political figures, encourages users to read articles before expressing opinions.
Cons: assumes the need for administrators, will require more editorial effort.

This design alternative takes inspiration newsfeed style applications like Reddit.

Consumption is done via push notifications or browsing the newsfeed. Users are only able to vote on articles once they have opened them, and spent at least 2 minutes reading the article. The “story page” also allows users to switch between different perspectives on the same headline. The newsfeed can be sorted by controversial, hot, or new (the main interests of our study pool).

Sharing using this app is done anonymously. There is a grace-period that an article must go through before it is published on the site. During this period, admins will approve the site.

Users are also able to follow popular nearby politicians. The politician’s basic profile consists of details that are relevant to users: recent news, party, political leanings, etc.

The option to remove sources is also available, this can be done to test one’s own biases.

Update #2C: Prioritized List of Requirements

REQUIREMENTS

Absolutely must include
All of our target personas are interested in receiving news about political figures. Some of our personas are also interested in sharing that news.

    1. User is able to search for a particular political figure
    2. User is able to follow a particular political figure
    3. User is able to receive updates about the activities of a particular figure
    4. User is able to read a feed containing all recent news they’re following
    5. User is able to share anonymously a piece of news about a particular figure


Should include
All of our users would like to receive unbiased and credible news.

    1. News that have just been shared are pre-moderated
    2. User is able to flag a piece of news as inappropriate


Could include
Some of our users (media professionals, community organizers) are interested in following political figures based on their location or occupation, and be more in control of their stream of news.

    1. User is able to browse a catalog of political figures
    2. User is able to choose how much news they want to see about a particular figure


Could exclude
None of our users explicitly need those features, but we thought they could be helpful for some.

    1. User is able to search for a tag
    2. User is able to follow all news matching a certain tag
    3. User is able to receive updates about all news matching a certain tag
    4. User is able to tag a piece of news when it’s being shared


USERS

Absolutely must include
Our system has to cater to both passive consumers of information, and those who actively seek out information.

    1. Casual consumers of political news
    2. Concerned citizens (activists, community organizers, etc)
    3. Users that wish to stay highly informed about politics


Should include
We should cater to people who are looking to increase their political knowledge.

    1. Media professionals
    2. Users that would like to get more informed about politics
    3. People who feel overwhelmed by the current ways of engaging with news


Could include
We should try to cater to the users who are uninformed about local politics.

    1. People who lack interest in local politics
    2. People who aren’t accessing information about local politics


Could exclude
We shouldn’t cater to users who wouldn’t instantly benefit from using the system.

    1. People who have no interest in politics.
    2. People who have no interest in real time news.

Update #2B: Updated Task Examples

#1
Summary of changes:

  1. Added aspect of fact checking/ verifying news sources to make sure if they’re trustworthy or not
  2. Added the aspect of minimizing the element of bias from news sources
  3. Tried to narrow focus more on political figures and news about them
  4. Expanded on the fact that major political news is important to Sarah (Because of how shared it is and how many people are talking about it)
  5. Added aspect of how news that personally affects the persona is news that she really cares about
  6. Removed the part where the persona talks about feminist causes around the world because it doesn’t relate to our study/ project

Sarah is a U.S. citizen who currently studies at UBC. Sarah has not been very interested in politics before the 2016 U.S. presidential election. A political figure that spiked her interest in particular was Donald Trump because he was shared among her friends, family, co-workers and articles about Donald Trump was in all her media sources. She was appalled by the subtle/ bold statements that the new U.S. president made during his campaign, and deeply shocked by the effect they imposed on women. She was particularly shocked by these statements because Sarah identifies as a female and she feels Donald Trump’s policies (I.e. His views on abortion) will negatively impact her. Sarah initially started reading multiple articles about Donald Trump only to find out after doing further fact checking/verifying that lots of them are composed with fake information or trivia. She is looking for a news platform that can minimize the effects of bias from reporters and authors that would keep her up to date with any policy changes made by the new U.S President.

 

#2
Summary of changes:

  1. Added details about the channels where information is obtained
  2. Added details about sharing habits
  3. Added details about the specific needs of the persona in terms of following certain political figures
  4. Removed the assertion that the persona attends plenty of events: interview suggests that actual journalists do not attend a lot of events
  5. Removed the assertion that the persona views work in media as an extension of sharing news on a personal level: interview suggests that actual journalists view these two activities as fairly separated from each other

Tom is a local political reporter who is actively researching information about political figures. He likes to spread the word about their current activities by posting updates on his social media accounts, mostly focusing on the positive news, novel opinions, and well-researched articles. He also writes short articles for the media company he works for. He doesn’t want to overload his social media presence, and the publication process in his media company is somewhat slow and complicated. He gets most of his news on social media, and he is subscribed to several government newsletters. He also checks a number of websites from time to time, but finds that time-consuming and inconvenient. He also finds it difficult to aggregate that information on his own, and often engages in collaborative research work with his peers. In particular, he needs more unbiased, credible information about the particular MPs, MLAs, and members of cabinet, and receiving real-time updates about their activity would be ideal for him.

 

#3
Summary of changes:

  1. Added information about trusting news that he receives… maybe he doesn’t know which source to trust?
  2. Remove email news digest/replace with twitter (follows specific people as an attempt to filter news)
  3. Mike considers himself more engaged with political news than an average person, and he puts a certain amount of work into accessing those news.

Mike is a father of two who is very busy with his day-to-day life (I.e work, family commitments, etc.) and has very little spare time, however he is interested in following the political news that affect him, and he is ready to spend some time finding those news. He is subscribed to several news outlets on social media, and he occasionally watches political commentary shows on television and online. In his community, a major pipeline project has recently been approved, and he wants to closely follow the news about that project. For that specific purpose, he follows several relevant channels on Twitter, so he can see updates on his smartphone as they arrive. Mike would like to spend less time filtering through different news pieces to find the information that is relevant to him. He wants to be more in control of the updates that he gets, and he is also interested in receiving those faster.

Update #2A: Recommendations

Conducting the interviews gave us plenty of insight into the kinds of information the users of our system would most likely be interested in receiving. Our interview participants expressed a need in real-time, credible, and factual information, free from biases and personal opinions as much as possible. During the design stage, we hope to elaborate on the mechanisms that would allow fact-checking, make sure the shared news are neutral, and that the news meets certain relevancy criteria. The relevancy criteria should exclude such news as celebrity gossip, or news about the activities of business people who are not employed by the government.

To encourage the users to share news using our system, we are going to focus on making sure that the users can share them with pride, and with as little discomfort as possible. Many interview participants stated that they would normally share political news only with people in their very close circles. To remove that barrier, we think that news sharing in our system should be anonymous, and the anonymity of the source should be protected. However, the system should track users who routinely share unacceptable content, in order to prevent them from spamming the user community.