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

Review and update personas #885

Closed
1 of 4 tasks
ktjnyc opened this issue Mar 3, 2021 · 16 comments
Closed
1 of 4 tasks

Review and update personas #885

ktjnyc opened this issue Mar 3, 2021 · 16 comments
Assignees
Labels
Role: Design UI/UX User interface / user experience design Role: User Research Tasks related to understanding users, needs, context

Comments

@ktjnyc
Copy link
Member

ktjnyc commented Mar 3, 2021

Dependencies

#955

Overview

We need to update our personas so that we are building the tools/pages that match our users.

Action Items

  • Review personas (none one record)
  • Create new personas
  • Provide comments on personas
  • Select & prioritize personas

Resources/Instructions

Hack for LA Guide for personas/user stories
FOLA user stories/personas
USC Food Insecurity Report
Current User Persona Research
Draft Personas

@ktjnyc ktjnyc added the Role: Design UI/UX User interface / user experience design label Mar 3, 2021
@ktjnyc

This comment has been minimized.

@ktjnyc
Copy link
Member Author

ktjnyc commented Mar 9, 2021

Looks like what was linked previously was the guide on creating the user personas.

Current personas exist here - https://github.com/hackforla/food-oasis/wiki/User-Stories

@ktjnyc
Copy link
Member Author

ktjnyc commented Mar 17, 2021

Bryan asked Thy to provide some additional guidance from her experience.

@fancyham
Copy link
Collaborator

fancyham commented Apr 2, 2021

@wanderingspoon

@wanderingspoon
Copy link

wanderingspoon commented Apr 2, 2021

I’m currently reading and aggregating research addressing food insecurity and mobile tech use among vulnerable communities in CA.

@wanderingspoon
Copy link

wanderingspoon commented Apr 10, 2021

Here's a document that brings together demographic information about food insecure households in California and US, along with some studies on visitors to food pantries and mobile tech use in low-income communities.

I think we can use the data to create solid personas for now. These will ideally be validated later for FOLA's specific objectives, of course, but I think they can still be helpful in the meantime for design and development teams.

For those not working on the personas proper, I recommend reading Key Points, pp. 1-2. The rest is information that we'll use to flesh out personas.

Food Insecurity & Mobile Tech Use Among Low-Income Households: Distillation of Published Research

@nkiwan

@wanderingspoon
Copy link

wanderingspoon commented Apr 10, 2021

How will personas fit into larger workflow?

Provisional action items, depending on discussion with larger team:

  • Create template for personas based on design and development objectives
  • Select and prioritize archetypes
  • Flesh out archetypes with details (e.g. circumstances, problems, and desires)
  • Present user group profiles to team
  • Select 3-5 primary working personas, with 2-3 secondary for contingency or long-term
  • Finalize personas
  • Share out, discuss and document

Upon completion, potential next steps, depending on team needs

  • Create user stories
  • Sketch out user journeys
  • Validate with user research

@nkiwan @ktjnyc @fancyham

@wanderingspoon
Copy link

Could we add a parallel issue? @ktjnyc

It would be ideal if, while Natalie and I work on the personas, that another team is coming up with the criteria which will be used for selecting and prioritizing them later, after we present them to all stakeholders. I would prefer strongly that those criteria are established and communicated out before we present. Or at least, very close together in time. @fancyham

Natalie and I will confer soon to clarify our soonest delivery date for the personas. We can also delay the presentation as needed to sync with creating the criteria. @nkiwan

@wanderingspoon
Copy link

wanderingspoon commented Apr 16, 2021

Current persona team: Natalie Kwan, Thy Tran

Working Task List

PHASE 1

  • Kick off meeting for persona team
  • Schedule stand-up or milestone meetings for persona team
  • Establish scope of work and deliverables
  • Create template for persona sheets
  • Divvy up work
  • Commit to deadline and sketch timeline; share out with larger team

@nkiwan

@wanderingspoon
Copy link

wanderingspoon commented Apr 16, 2021

Not sure how to create dependencies? In order to ensure that we can later select and prioritize personas successfully.

  • Coordinate with design and development teams: prioritization of resources and objectives.
  • How will personas be used by design and development team?
  • Coordinate with management and product teams: clarification of overall goals and criteria for selecting personas.
  • How will we decide which personas to target and research further?

Natalie and I will not need these to deliver the personas. But they're critical for progress afterward.

@fancyham @ktjnyc

@ktjnyc
Copy link
Member Author

ktjnyc commented Apr 16, 2021

@wanderingspoon I'll create the parallel issue and link it here under dependencies at the top.

@nkiwan
Copy link
Member

nkiwan commented Apr 20, 2021

Persona Task List Update

  • Create template for persona sheets
  • Commit to deadline and sketch timeline; share out with larger team

Personas have been assigned
Expected timeline for deliverables: 4-6 weeks

Next steps are to build out assigned personas (with qualitative data from interviews if possible) and check in at weekly stand-ups.

@wanderingspoon

@wanderingspoon
Copy link

wanderingspoon commented May 21, 2021

Created script for 20-30 informational interview for professionals working with food insecure populations.
Interviewed national director of food insecurity at federal gov't agency.

@wanderingspoon
Copy link

Natalie and I are leaning toward group profiles (e.g. single parents, seniors, case managers) instead of individual personas (e.g. named, fictionalized). To us, the latter feel fragile, forced and less useful as we have not conducted user research for the details. Group profiles, while not conventional user personas, seem more robust as they'll be data-driven or supported by secondary sources.

We presented examples of both and asked the group about their preferences. After short discussion, consensus settled on group profiles. Later, once we have enough research on actual users, we can create specific, named personas.

Examples of group profiles vs. individual personas

@nkiwan

@wanderingspoon
Copy link

Some delay in presenting, as we lost files during the May 31 bug with Google Drive and still have not retrieved more recent notes during May.

Have decided to move forward with documents from April.

@fancyham fancyham added the Role: User Research Tasks related to understanding users, needs, context label Aug 6, 2021
@fancyham
Copy link
Collaborator

fancyham commented Aug 6, 2021

The current thinking on this (with feedback from @wanderingspoon) is that since we haven't done new research, that the document mentioned above (linked again below) should give us the best understanding of our users without the risk of making things up from whole cloth, or taking from news or publicity pieces (where stories are used to illustrate a larger narrative).

Please refer to this document to better understand food seekers in the Los Angeles area:
Food Insecurity & Mobile Tech Use Among Low-Income Households: Distillation of Published Research

A future project would be to interview actual food seekers, people helping food seekers, which can optionally be used to create accurate, more detailed personas, if that's useful to the team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Role: Design UI/UX User interface / user experience design Role: User Research Tasks related to understanding users, needs, context
Projects
Archived in project
Development

No branches or pull requests

6 participants