Create personas: volunteers

[ExperimentsInHonesty]

trafficstars

Dependency

• #2561
• #2589

Overview

We need to have personas so that we can evaluate if the features we are developing service the audience

Action Items

• [x] Collate data from previous interviews on google drive of volunteers and product managers.
• [x] Create Miro board for Volunteer Persona data analysis and synthesis.
• [x] Transfer data from volunteer interviews, product manager interviews, and internal stakeholder interview on Miro Board.
• [x] Code sticky notes and create tags on Miro.
• [x] Discuss with the UX research team: how many personas should be there for volunteers?
• [x] Transfer coded sticky notes to the emerging themes section.
• [x] Create Persona and review with team
• [x] Write interview script for second volunteer persona - long term volunteers
• [x] Get list of contacts from Bonnie and outreach
• [ ] Conduct user interviews
• [ ] Synthesize interviews and perform analysis on Figma
• [ ] Create second user persona
• [ ] Review with team and Bonnie for final approval

Resources/Instructions

• This issue is part of an epic issue https://github.com/hackforla/website/issues/2015
• Interview Guide
• Interview Script (Longterm Volunteers)
• Long Term Volunteer User Survey
• Long Term Volunteer Interviewee List - Potential Volunteers

[github-actions[bot]]

Hi @ExperimentsInHonesty.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: Size, Role, Feature

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[ghost]

1. Progress: Analyzing and synthesizing data from previous interviews and internal stakeholder interviews on Miro.

2. Blockers: Need to discuss with the UX research lead how to approach the user persona because there are multiple kinds of 3. people who volunteer at HackforLA with different skill sets. Need more nuance in the persona or multiple volunteer personas.

3. Availability: 6-7 hours

4. ETA: Analysis should finish by this weekend. 5 Pictures: N/A

5. Resources:

Miro Board Link https://miro.com/app/board/uXjVO8mpdzI=/

Internal Stakeholder Interview https://docs.google.com/document/d/1kj8wWrykXJiE5RJk4S-iJNgJXrXm9kocV84QJ0ZcdlI/edit

Product Manager Interview https://docs.google.com/document/d/1fYS8QiFQKLK3wux32N_KmJS1kghS4zAb0_i9a_f2R5A/edit

General Volunteer Onboarding Interview https://docs.google.com/document/d/1JhmssH6ecN4Nu8ImyRywJL4AYH-qDgfW9rt1cl-hypU/edit

Homepage Redesign Interview https://docs.google.com/document/d/11MhdWy-Mco-a7txy9x4cY5O_LRoSdp1AuWdRqaLhReQ/edit

[ghost]

1. Progress: Creating User Personas for Volunteers

2. Blockers: Need to understand who is going to use the personas. That will determine what kind of volunteer persona to create. What is the end goal? People who volunteer at HackforLA with different skill sets. Need more nuance in the persona or multiple volunteer personas.

3. Availability: 6-7 hours

4. ETA: Depending on the response from upcoming Sunday meeting, will work on this issue.

5 Pictures: N/A

[github-actions[bot]]

@ShrutiMukherjee

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, May 31, 2022 at 12:19 AM PST.}

[ghost]

1. Progress: Creating User Personas for Volunteers

2. Blockers: Need to understand who is going to use the personas. That will determine what kind of volunteer persona to create. What is the end goal? People who volunteer at HackforLA with different skill sets. Need more nuance in the persona or multiple volunteer personas.

3. Availability: 6-7 hours

4. ETA: Depending on the response from the Sunday meeting, will work on this issue.

5 Pictures: N/A

[github-actions[bot]]

@ShrutiMukherjee

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, June 14, 2022 at 12:19 AM PST.}

[github-actions[bot]]

Hi @sandarshp, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[github-actions[bot]]

@sandarshp

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, July 19, 2022 at 12:21 AM PST.}

[sandarshp]

Progress - Stuck at Action Item 6

Blockers - Need Miro login credentials to access the personas

Availability - 6 hours/week

ETA - 29th July

[sandarshp]

Progress - Discussed with Bonnie the need to interview volunteers on 7-24-22. Preparing the interview guide.

Blockers - None

ETA - 8-5-22

[github-actions[bot]]

@sandarshp

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 9, 2022 at 12:20 AM PST.}

[sandarshp]

Progress - Working on the interview guide. Should have it ready for peer review by the next research Team Meeting.

Blockers - None

Availability - 6 hours

ETA - 8-17-22

[sandarshp]

Progress - Created the interview guide. Next step is getting it peer reviewed and approved.

Blockers - None

Availability - 6 hours

ETA - Next meeting

[github-actions[bot]]

@sandarshp

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 23, 2022 at 12:25 AM PST.}

[github-actions[bot]]

@sandarshp

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, August 30, 2022 at 12:27 AM PST.}

[github-actions[bot]]

@sandarshp

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, September 6, 2022 at 12:28 AM PST.}

[github-actions[bot]]

@sandarshp

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Tuesday, September 13, 2022 at 12:32 AM PST.}

[ExperimentsInHonesty]

Hi @sandarshp 😃! I noticed that you joined the Hack for LA website team on June 15th but have not finished the Pre-work process or closed any issues.

Will you be coming back? Please let us know so that we can unassign you from this issue if you are not going to work on it.

Do you have feedback for us?

[sandarshp]

Hi @ExperimentsInHonesty My apologies for not being regular with the updates. I think I will unassign myself from this issue. Things have been getting busy work wise and I don't think I'll be able to put the required hours at HfLA in the near future. I would love to get involved again early next year if that's alright. My workload will be more manageable then.

Thanks!

[github-actions[bot]]

Hi @vzpeopledesign, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[vzpeopledesign]

I am assigning myself this issue and will check in with Vaisali on next steps by Wednesday 10/19.

[vzpeopledesign]

1. Created a persona and ran it by UXR team. Will run it by Bonnie to assess and evaluate further need of research: user interviews, survey > to create a second persona.
2. Need to finish migrating sticky notes in Miro to bring all insights to light and complete the Miro board.
3. Sticky note migration ETA: 4 hrs max to be completed by Oct 30.

[vzpeopledesign]

Need another user persona for long term volunteers. Current volunteer addresses our short term volunteers: 0 - 6 month average. We need a persona for the long term volunteer.

Next steps:

1. Write interview script by reviewing the script previously used and making any necessary additions/changes.
2. Get contact list from Bonnie and outreach
3. User interview
4. Post analysis on Figma
5. Create persona

[bishrfaisal]

Hello @vzpeopledesign, since you are actively working on this issue it needs to be in the in-progress column. We have moved it for you 😄 In the future please move it to that column when you self-assign.

[vzpeopledesign]

Today: Potential list of long term volunteers gathered and outreach email ready for clearance from Vaisali Next: Send outreach emails > Interview > Analyze > Persona Goal is to send outreach emails between 11/17/22 - 11/22/22

[vzpeopledesign]

Today: Finished sending out all interview invites via email, slack, and LinkedIn. All names contacted are colored grey in the Longterm Volunteer Interview List Google Sheet doc to mark those I have reached out to vs those I have not.

I have made a Calendly link so they can book time with me and I extended it out 2 months in case no wants to interview during the holiday season

Next steps: wait for responses / follow up in a few days / find more people to interview

[github-actions[bot]]

@vzpeopledesign

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, December 5, 2022 at 11:16 PM PST.}

[github-actions[bot]]

@vzpeopledesign

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, December 12, 2022 at 11:15 PM PST.}

[github-actions[bot]]

@vzpeopledesign

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, December 19, 2022 at 11:16 PM PST.}

[github-actions[bot]]

@vzpeopledesign

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

_{You are receiving this comment because your last comment was before Monday, December 26, 2022 at 11:15 PM PST.}