Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provisional Storyboard for Website User #74

Closed
20 of 22 tasks
melissamurphy opened this issue Sep 22, 2021 · 8 comments
Closed
20 of 22 tasks

Provisional Storyboard for Website User #74

melissamurphy opened this issue Sep 22, 2021 · 8 comments

Comments

@melissamurphy
Copy link

melissamurphy commented Sep 22, 2021

Dependency

Will be updated based on user research #62

Overview

A storyboard provides a visual of user experience and supplies a common reference for the entire team.

Action Items

Define provisional User Persona types based on latest discussion across Access the Data site & workshop teams and stakeholders:

  • The person who knows nothing about data + has community causes they are passionate about (Persona 1)
  • The person who has used data before, in their work with community activism (Persona 2)
  • The prospective data user who is curious to know more about how data could apply to community causes (Persona 3)

All users share a minimum level of community involvement and interest in data, but we assume no minimum level of data literacy or even familiarity in our design.

For each provisional User Persona type, cover these points in the storyboard:

  • Set the user's environment
  • Note the user persona
  • Identify the goal - what is the user looking to get done and how?
  • Depict the user's pain points in the process
  • Narrative - Follow their story through from beginning to middle to end

After storyboard authors have shared theirs amongst themselves,

  • Have the team look at the storyboard together and discuss.

As new user needs come to light from research and the team iterates through new solutions, update the storyboard to keep the team vision aligned.

  • Define personas
    • The person who knows nothing about data + has community causes they are passionate about
      • Set the user's environment
      • Note the user persona
      • Identify the goal - what is the user looking to get done and how?
      • Depict the user's [pain points]
      • Narrative - Follow their story through from beginning to middle to end
    • The person who has used data before, in their work with community activism
      • Set the user's environment
      • Note the user persona
      • Identify the goal - what is the user looking to get done and how?
      • Depict the user's [pain points]
      • Narrative - Follow their story through from beginning to middle to end
    • The prospective data user who is curious to know more about how data could apply to community causes
      • Set the user's environment
      • Note the user persona
      • Identify the goal - what is the user looking to get done and how?
      • Depict the user's [pain points]
      • Narrative - Follow their story through from beginning to middle to end
  • Have the team look at the storyboard together and discuss.
  • user research Research plan for website #62
  • update based on user research

Resources/Instructions

For more definition of a person's tendency towards activism, see the Activism Orientation Scale from Corning's Social Cognition Lab for examples of the kind of statements that tally an individual's orientation towards social action.

Storyboarding process and purposes served by storyboarding:
Adobe's "The What, Why, & When of Storyboarding in UX Design"
Smashing Magazine's "The Role of Storyboarding in UX Design"

Workshop Survey Feedback
311 data notes
User Personas issue with links to EmpowerLA workshop survey results
User Stories issue with links to workshop survey responses to Introduction to Community Data

FigJam of User Stories based on above survey feedback:
https://www.figma.com/file/nqls7mJsNB4w03wSfiVGLQ/Goals-and-Motivations-for-User-Map?node-id=0%3A1

Data Literacy Persona Theory
Who Needs Literacy? Three Key Personas
Data Literacy Personas in an Organization

@melissamurphy melissamurphy added role: UX/UI size: 2 pts 2 points = 7-12 hours labels Sep 22, 2021
@melissamurphy melissamurphy added this to New Issue Approval in ATD Product Management via automation Sep 22, 2021
@lrchang2 lrchang2 added this to the 4 - Website Requirements Gathering milestone Sep 25, 2021
@lrchang2 lrchang2 moved this from New Issue Approval to Prioritized Backlog in ATD Product Management Sep 25, 2021
@ElizabethWarninger
Copy link

ElizabethWarninger commented Sep 29, 2021

@lrchang2 lrchang2 moved this from Prioritized Backlog to In progress (actively working) in ATD Product Management Sep 30, 2021
@ElizabethWarninger
Copy link

@lrchang2 & @abryant35, what do you think about adding both the Stakeholder and Potential Funders as new personas? Per the updated MVP V1 & V2. . We can discuss if they should be added to our personas to understand their motivations/needs/goals/pain points and if a storyboard would be helpful as well. @melissamurphy & @miguel-hugo!

@lrchang2
Copy link
Contributor

lrchang2 commented Oct 4, 2021

@ElizabethWarninger the needs for the stakeholder is to show "tangible progress on our project" and for potential funders, we can replace that with Bonnie, cause she may potentially use the website to present to funders. But the needs for the funders are the same as users who would want to know the purpose and potential of the project.

since there is overlap, i don't think their needs warrant a persona for themselves.

@ElizabethWarninger
Copy link

@lrchang2, thanks for your response and clarifying and stating the needs of the stakeholder.

@abryant35 abryant35 moved this from In progress (actively working) to Questions/Review in ATD Product Management Oct 6, 2021
@melissamurphy
Copy link
Author

Background research updated with outside theories of data literacy personas.

@lrchang2 lrchang2 moved this from Questions/Review to In progress (actively working) in ATD Product Management Oct 8, 2021
@ExperimentsInHonesty
Copy link
Member

please rewrite this issue so that we will know when its completed (add checkboxes)

@ExperimentsInHonesty ExperimentsInHonesty moved this from In progress (actively working) to Questions/Review in ATD Product Management Oct 12, 2021
@melissamurphy melissamurphy changed the title Storyboard for Website User Provisional Storyboard for Website User Oct 13, 2021
@melissamurphy
Copy link
Author

@ExperimentsInHonesty There is no one checklist for this issue as we produced 3 distinct storyboards--each of which had to run through the steps (which was originally bulleted for this reason) by a distinct person.
How might we note a set of requirements/steps that apply to 3 different team members and results?

@lrchang2 lrchang2 moved this from Questions/Review to Ice Box in ATD Product Management Oct 18, 2021
@lrchang2 lrchang2 modified the milestones: 4 - Website Requirements Gathering, 04 - User Development Nov 2, 2021
@melissamurphy
Copy link
Author

@kimberly-tellez @hannahsgr @ashleyxz The Activism Orientation scale (from the Social Cognition lab at Cornell) I mentioned as a validated measure of activism is here https://www.midss.org/activism-orientation-scale-aos/ May provide some inspiration in defining our potential community activist users or some segment thereof.

@mxajPrice mxajPrice closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2022
ATD Product Management automation moved this from Ice Box to Done Jun 21, 2022
@mxajPrice mxajPrice removed this from Done in ATD Product Management Jul 7, 2022
@mxajPrice mxajPrice added this to New Issue Approval in [ON HOLD] AtD Personas via automation Jul 7, 2022
@mxajPrice mxajPrice moved this from New Issue Approval to Done in [ON HOLD] AtD Personas Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

6 participants