| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

User stories

This version was saved 15 years, 8 months ago View current version     Page history
Saved by Matt Cooperrider
on October 27, 2008 at 1:23:04 pm
 

Overview

Writing up "user stories" ensures that we are looking at this project from a user perspective and not only from a developer perspective.  What are some ways that our target audiences will engage with our data and applications from now through election day?  Add your user story to one of the categories below.  This is the perfect way for a non-technical volunteer to contribute to the project using only their imagination.

 

 

Naming Conventions

In order to keep the stories consistent, please hold to the following naming conventions

  • voter: a voter the polls who wants to report a success/failure
  • member: somebody who's actively volunteering, including a "more trusted user", Sweeper or SuperTweeter

 

Stories

You can either expand an existing story, or provide an entirely new story.  Don't worry if you think one of the stories below already did what you are trying to do.  If you are not sure, err on the side of being repetitive.

 

*Story Type: Voter reports*

 

Reporting on conditions - formatted report

Comment from Jon: can we go into a little more deail here -- for example, define "sends a tweet" (which presumably involves interacting with a phone in some way, but that's not currently obvious)

 

Voter sends a tweet to #votereport giving their location and a comment on one of the attributes they know from the votereport site:

  • location - either L: XXXX -or- zipcode XXXXX -or- some variant that can be distinguished
  • wait - either wait:(minutes) -or- waittime:(minutes)
  •  

Use Cases

Voter wants to report on the number of machines at their polling location and how many are working

Voter wants to report a broken machine

Voter wants to report on people being harrassed at the polling location by police, by lawyers, by activists, etc

Voter wants to report on length of the line at their location (e.g. how many people, how long the line is)

Voter wants to report how long it took for them to vote (e.g. tovote:(minutes))

Voter wants to know what are the commands available via #votereport

Voter wants to report an electronic voting machine that took the wrong vote when entered

 

Via Twitter

Via SMS

Via iPhone

Via phone

Via web (presumably VoteStory '08)

 

*Story Type: Amplify someone else's voter report*

 

Member wants to report on issue but low quantity of datapoints do not provide enough visibility of what is happening at the polling location.  Need to ask votereport for amplification/manification of their report (for example - manification of their tweets by some factor for visibility sake)

  • Suggestion - play the font size game as done in tag clouds?

SuperTweeter sends in reports for several voters

(particularly important in areas where Twitter usage is low -- which are likely to be the ones most at risk)

 

Member signs up

Via Web

  • Member goes to twittervotereport.com and registers
  • If a twitter member:
    • Member becomes a follower of @votereport
    • votereport then auto-follows the member
  • If not a twitter member, offer option to sign up at twitter (?)
  • Request cell phone number and carrier (to also have direct connection)
    • Have a confirmation sequence (is this important?)
  • Location request (is this important?)
  • Poll location request (is this important?)

Via twitter

  • Member follows @votereport (f votereport)

  • votereport autofollows member twitter account
  • votereport requests polling location with formatted message

 

Tracking and Acting

Monitoring at Max Magnitude

Sweeper sends out an alert

- identifies potential pattern

- identifies precinct (may not be unique in urban areas)

- validates data

- gets feedback and confirms

- sends notification

 

 

Sweeper detects bad data

- identifies pattern

- gets feedback

- purges data

- alerts somebody to look for broader pattern

 

*Story Type: Outside Groups Using Our Information*

 

Community activists looking out for local problems

 

what information and visualizations are important, how to convey confidence levels and minimize false alarms, how can they confirm itand to evaluate the severity?  how to determine specific precinct if it's not known?  what should they do next?  who do they contact if they have proble and know what to do/who to contact next?

 

Election protection group gets alert

what information is there to confirm it, allow the group to evaluate the severity, and know what to do/who to contact next?

 

Local reporter/blogger is following for a story

 

Reporter/blogger can go to Plodt.com to see what the wait times are in local areas, and how they compare nationally -- and see if there are other problems developing, also which local polling stations are reporting good experiences.

 

National reporter/blogger is following for a story

 

Reporter/blogger can go to Plodt.com to see what areas of the country have the longest wait times and how they've shifted throughout the day -- see which areas are trending as problem areas, and where people are having the best experiences.

 

Comments (0)

You don't have permission to comment on this page.