HfLA: PM/ORG/UX Meeting Agenda of 2022

[Sihemgourou]

Dependency

When we have a new research lead

Overview

This issue tracks the agendas and notes for the meeting that PM has with UI/UX

Template:

## 2022-MM-DD Agenda and Notes 

### Prework to prep for meeting
Review and prepare items that have [ready for research lead](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22ready+for+research+lead%22#column-15235217) labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agenda.


### Recurring items: 
 - [ ] review any issues that are in the new issue approval column
   - [ ] [Research](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+user+research%22#column-15235217)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Lead and Org rep
       - [ ] [Isaac](https://github.com/hackforla/website/issues/assigned/IsaacDesigns)
       - [ ] [Bonnie](https://github.com/hackforla/website/issues/assigned/ExperimentsInHonesty)
       - [ ] [Simone](https://github.com/hackforla/website/issues/assigned/sacamp)


### New Items


### Notes from meeting
- 
### Tasks


### Items for next meeting agenda

Participants :

Things to discuss:

Things discussed:

Actions to take:

Weekly Agenda

21/06/20
21/06/21
21/06/22
21/06/23
21/06/24
21/06/28
21/06/29
21/06/30
21/07/06
21/07/07
21/07/09
21/07/13
21/07/14
21/07/15
21/07/20
21/07/21
21/08/02
21/08/03
21/08/05
21/08/09
21/08/11
21/08/17
21/08/24

fill in the rest

2021/12/08
2021/12/15
22/01/08

[Sihemgourou]

Meeting 21/06/20

Participants : @ExperimentsInHonesty & @Sihemgourou

Done:

• Assigned feature labels to issues with feature missing + created new labels
• Cleaned the project board
• Made some comments about the Getting started page Develop Updated Getting Started page #1619
• @Sihemgourou has now access to the google analytics account Google Analytics #1730
• @Sihemgourou has been made owner of the HFLA Github so that she can edit the website write team
• Talked about the program areas page (@Sihemgourou has to contact Ali for the SDG issue)
• Created ALL TEAM agendas for the Sundays meetings
• Talked about a new way of organizing the ALL TEAM (time keeping + how to talk the issues)
• @ExperimentsInHonesty showed @Sihemgourou how to clean an old issue (how to hide comments)
• Checked if people were assigned to multiple issues
• Checked if Danielle was still assigned on issues

Todo:

• Talk with @akibrhast about the winssubmissions issue template (it shoud appear as any other template so we can edit it) => Done: Its not possible to have the issue template because the issue is made from the google app script. He will made variables on the script so that we can update the labels. The process would be to create an issue for the devs in order to update it.
• Ask the other pms if they want to join on the 1v1 with @Sihemgourou & @ExperimentsInHonesty => Done : see slack
• Review the design to development hand-of (Creating a file in gdrive to stock the figma images?)
• Finish cleaning the board by adding features on the Icebox
• Prioritized the issues on the prioritized backlog
• Create a roll call spreadshit ? (HfLA: ALL TEAM Meeting Agenda☀️ #1734)

[Sihemgourou]

Meeting 21/06/21

Participants : @akibrhast & @Sihemgourou

Things discussed:

• Wins page :
  • The github pitcures are not showing on the page. There is a bug.
  • Should we remove the question about getting the github pitcure and take it directly ? Because we are already showing all the contributors pitcures on the project profile cards (see akib comment in PR toggle see more/see less on wins card #1732)
  • Should we have the linkedin & github icons in all the cards and just gray the buttons when we don"t have the info

Actions to take:

• Ask Bonnie why the Member Feature page has the same objectives as the wins page.
• Ask Bonnie about the things discussed with Akib about the wins page
• Adding descriptions to the newly created labels => gdoc with list of all the labels + add caracters limits and run it through the pm team
• Talk with Bonnie about this issue Research on the Wins submission process #1789
• Should we remove the question about getting the github pitcure and take it directly ? Because we are already showing all the contributors pitcures on the project profile cards (see akib comment in PR toggle see more/see less on wins card #1732) => we wanted to ask which image they prefer

[Sihemgourou]

Meeting 21/06/22

Participants : @Sihemgourou & @ExperimentsInHonesty & @daniellex0

Things discussed:

Home page :

• We want to test the design with people who do not know us (people with a donator profil would be ideal)
  Getting started page :
• Discussed about the suggestions in this comment. (All checked boxes are changes are validated changes)

Actions to take:

• @Sihemgourou will rewrite the description text on the top of the Getting started page so that it can be more adapted to volunteers. Something like "Volunteers..." / Done : see comment
• @ExperimentsInHonesty has to check the wiki for tomorrow's meeting
• Ask @ExperimentsInHonesty about the zoom faq in the getting started page
• Write a template message to ask potential donators if they want to do a user test, and publish it in HFLA slack so that volunteers can spread it through their networks.

[Sihemgourou]

Meeting 21/06/23

Participants : @Sihemgourou & @ExperimentsInHonesty @sayalikotkar

Things discussed:

• VRMS: David from the VRMS team, is working on something that will affect the jobs team, he's building a CMS for people to update their meeting time and any infos that the projects hold on the website.
• Wins page:
• Getting started page => "Start your Hack for LA volunteer journey"
• Wiki : Changes proposed to the side bar
• Home page : The UX research should be a more general analysis (user interview), ask questions as what are you looking for on project website in order to donate and then make a usability testing. The user interview should be made by all the UX CoP. We should test it with the fund raising team first.
• Onboarding automation

Actions to take:

• @Sihemgourou will connect with David to know more about the features his project would have => Done: The VRMS team is not actively working on what needs to be displayed on the website. Maybe they could internalise the updating process on their interface but this should come up with V.05.
• @Sihemgourou will present another alternative which will be more compatible with the design
• Review the home page research strategy with @DanielekPark
• Talk about the github picture permission on the sunday meeting
• Write a template message to ask potential donators if they want to do a user test, and publish it in HFLA slack so that volunteers can spread it through their networks.
• Talk with Bonnie about this issue Notify Win's submitter Research on the Wins submission process #1789
• Ask Bonnie why the Member Feature page has the same objectives as the wins page
• Review the design to development hand-of (Creating a file in gdrive to stock the figma images?) => Done: @sayalikotkar is going to ask devs about what needs to be checked before handing the issues from design to dev.
• Finish cleaning the board by adding features on the Icebox
• Prioritized the issues on the prioritized backlog

[Sihemgourou]

Meeting 21/06/23

Participants : @Sihemgourou & @daniellex0

Things discussed:
Getting started:

• @daniellex0 said: It's ok if the header is not standardized because this page is unique + the other pages are not standardized either
• Ashley will come back with more ideas about the headers
• We have to write hypothesis about the flows to analyze on GA

Home page research:

• Why do we want to involve the UX Cop? Who are the person involved in the fund raising team?

Actions to take:

• @Sihemgourou will connect with Rosalyn to documents the UR strategy (waiting @DanielekPark approval first)

[Sihemgourou]

Meeting 21/06/24

Participants : @Sihemgourou & @ExperimentsInHonesty @sayalikotkar

Things discussed:

Actions to take:

• Talk with the devs about the amount of front end good second issues
• Make 3 bugs issues about the project cards bugs
• Do a serie of test of the mobile version of the website (design). @Sihemgourou need to make an issue with a list of all the pages connected to the menu (use this all the other links are secondary. If things are not right, the design team should edit the issue with how it should look like. For that, @Sihemgourou needs to create a template issue so that designers could use it. Process: put the issue in the review column to see if the devs would need additional details on the issue. All the page which are not live are here

[Sihemgourou]

Meeting 21/06/28

Participants : @Sihemgourou & @ExperimentsInHonesty

Things discussed:

• https://github.com/hackforla/.github where to put issue template to spread to all other project repository
• hidden issues on the board https://github.com/hackforla/website/issues?q=is%3Aissue+is%3Aopen+no%3Aproject => we are going to try a manual process (asking people if they need help putting it in the repo) and maybe automate it ?

Actions to take:

• Make an audit about everything that is in figma and be ready to be developped

• All team : talk about people taking two issues at the same time

• Onboarding/contributing md is too big ?

• @Sihemgourou will put [this issue ](Updating the HfLA Website Team Meeting Roster Discussion: HfLA website/other projects Team Meeting Roster #1343) on the ice box and put a date on it.

• All team : how to create a note to cite an issue for the dev team meeting

• issue 1445 : the issue should be self explanatory

• @Sihemgourou will gather the status on every page of the website on the sitemap for tomorrow's meeting. and if there are issues assigned to it

• @Sihemgourou assign those issue to the right labels

[Sihemgourou]

Meeting 21/06/29

Participants : @Sihemgourou & @ExperimentsInHonesty & @daniellex0

Things discussed:

• We need a research plan for the home page:
  Recap of our personas : Donors, advisers/partners.
  Lets start with one user segment first => starting with questions for donors group. We can test the interviews on @ExperimentsInHonesty friends (2 people).
  Blocker : About page et donate page need to be public.

• Design will add credits in the footer of every page => Design team need to have a meeting before sunday meeting and decide what subject is important to bring with us.

• Who is going to do the quality control/design review on PR when @daniellex0 will leave ? is website/design an answer ? => It's up to the junior designers to do that

• Maybe the pms needs to find the right sdgs themselves ?

• should we replace the Feature label by an epic ? misunderstanding with the common use of the term feature

• How much are we ready to devlop the design system

Actions to take:

• Figure out how to keep the flow of informaitons going between design and pm when @daniellex0 will leave

• Talk to Bonnie about the @hackforla/website-design and website merge team

• Create a UR role in labels

• Credit page : make a bunch of good first issue to Link images with name link. Ask Daniel why there is more images on the live credit page vs on the figma file (we need them on the figma file). Add this to the remaining alt text issues. we need to change the title-link: https://thenounproject.com/. check this. This is a blocker before putting the page. Get dev to write the issue samples together.

[Sihemgourou]

Meeting 21/06/30

Participants : @Sihemgourou & @ExperimentsInHonesty @akibrhast

Things discussed:

• Next time : lets close the loop on why people are assigned to multiple issues.
• Find out why Erika is not taking large issue

Actions to take:

• Talk with @daniellex0 about the links that are not refering to the specific image link

The links Im talking about

- We're moving on with the prioritisation https://docs.google.com/spreadsheets/d/14aFsmDOp4Aqcwbbtj5Ngx_3J48v7_dNLFZrhal5lb2w/edit#gid=0

Akib :

• We should begin with the development on mobile view before the website view
• 3 dimensions per pages: for 3 different view ( check link)
• How to make devs ask more questions to devs so that we don't develop fishy designs.
  issue example : alignment problem with person and the text
• Akib will leave in on the (Ava and Alex will takeover), we should rely on Ava for discussion between PM and dev.

Actions to take

• Talk with the dev team about how the column dev meeting is working
• ALL TEAM : ask if everyone has the calendar invite
• ALL TEAM : Talk about a new process for design review => the devs need to provide detailed screenshots ?
• MAKE vscode text larger in contrib file

[Sihemgourou]

Meeting 21/07/6

Participants : @Sihemgourou & @ExperimentsInHonesty & @daniellex0 & @smithasindagi

Things discussed:

• Use the website/design team to @ design team for all the issues Danielle was involved in.
• What's the process to add people on the subteams?
• Danielle is creating good second issues for the credit page (to replace the title links)
• Who will create design issues ? It has to be prioritized by the product team

Actions to take:

[Sihemgourou]

Meeting 21/07/07

Participants : @Sihemgourou & @ExperimentsInHonesty & @smithasindagi

Things discussed:
Use-case impact prioritization:

• We checked the twitter historic: HFLA was a big event organizer, we cannot see our history on our website. Key messages to communicate : all the different contributors thoughout time, the community building started from hack nights.
• We need to focus our communication on milestones and how we are accelerating things.
• We don't have a social media presence : we need a marketing team but for now we have 1 guy.
• Fundraising team : come with template for project to fill out and raise money for specific projects.
• The data science team is working on their own project => we have to put it on the website
• We have unlimited person from the user research CoP => we should use it
• Somebody needs to do board maintenance: Bring a junior pm to check weekly for dependencies;
• The template for information that we are asking for the project card needs to be updated: with SDGs => check olivia slides deck

Actions to take:

• Let Sayali run the next board
• Check the velocity every week
• Make a spreadsheet for projects SDGs
• @Sihemgourou will make this issue :The template for information that we are asking for the project card needs to be updated: with SDGs.
• Clean all the issues with product label for next meeting
• Update the accomplishments in the about page, list of sdgs

[Sihemgourou]

Meeting 21/07/09

Participants : @Sihemgourou & @ExperimentsInHonesty
Things discussed:

• Qiqi is in charge of accessibility in CoP engineer.
• The pdf for the onesheets needs to move
• Try the spreadsheet system for 1 project and then think about the automation
  Actions to take:
• check with qiqi if there is a guide for alt text for the image in the project card. Find infos about how to write good alt text
• Fix the normal ratio for hero image to 720 by checking all the hero image
• put animated gif on how to get slack id here

[Sihemgourou]

Meeting 21/07/13

Participants : @Sihemgourou & @ExperimentsInHonesty & @daniellex0

Things discussed:

• Research report for the homepage : about the insights from volunteers interviews, benchmark insights, usability testing. ETA : 07/18
• Process for design handoff: when design is ready, double-check with UX team (everything is componentized, wording is ok) => Lead design will review it and put a time sensitive and product label and put it in the review column => Product team will create development action items and check it with senior devs => put issue in prioritized backlog

Actions to take:

[Sihemgourou]

Meeting 21/07/14

Participants : @ExperimentsInHonesty @smithasindagi

Things to discuss:

• Tracking plan for acquisition and revenue (and volunteers turnover)
• Product needs to define marketing objectives : Define Marketing Objectives for Hackforla.org Website project marketing#21
• Could we have stats about the project board ?
• Review all product issues
• Problem with google analytics : /website ?
• Google Data Studio Dashboard

Things discussed:

• onboarding schedule on meetups
• we don't have standards on the mobile view : someone need to do a mobile audit. Put all the page on the same figma page.

Actions to take:

• Make an issue for a redirection when someone click on hacforla.org/website
• @Sihemgourou : put website analytics on the preexistent dashboard
• check with the design team why we are desiging on desktop => should we start designing on mobile ?
• @Sihemgourou will do a draft to answer this issue => to review to next meeting Product needs to define marketing objectives #1942
• Create an Issue about what we need to learn from board analytics and discuss it with leadership team (brainstorm about what is interesting for them and what's the feasability)

[Sihemgourou]

Meeting 21/07/15

Participants :

Things to discuss:

• Put roadmap milestones on each isssue

Things discussed:

• All medium issues are administrative
• We need to recruit more designers. We need to create a card for HFLA website.

Actions to take:

• list all the roles on the onboarding link column
• ask the UR team if they want their own role label

Issues labeled UX Research
Issues labeled Design

• Review the mobile responsivness issue

[Sihemgourou]

Meeting 21/07/20

Participants : @ExperimentsInHonesty @daniellex0 @kristine-eudey @Sihemgourou @Basu3040

Things discussed:

Donate page:

• We have to test the writing of the donate page with user tests. Add a donate button to have a strong CTA.
• @smithasindagi proposed to talk more about the impact for donors

Sitemap:

• add an additional status for content refreshing

Program areas:

• We need to rewrite the description text for each program areas

Other subjects :

• We should have a collection of deck to use for external and internal communication
• Privacy policy: find where to put this issue Create privacy policy #1989

Actions to take:

• @kristine-eudey will create a template to edit for CoP lead update on the website
• @kristine-eudey will create an issue to edit the top of the donate page
• Create a size missing label

[Sihemgourou]

Meeting 21/07/21

Participants : @ExperimentsInHonesty @Sihemgourou @Aveline-art

Things discussed:

• The dev team will update the wiki page to create a new issue Audit Website Team Labels #1983

[Sihemgourou]

Meeting 21/08/02

Participants : @ExperimentsInHonesty @Sihemgourou

Things to discuss:

• Marketing objectives

Things discussed:

• We need to check the done column to congratulate people and to do QA testing
• Github repo =>
  • New issue approval : Product will check labels on all issues, and validate design issues. Ava will review dev issues.
  • Process to take a new issue : A volunteer should be able to filter by milestones and then by roles
  • The goal is to create links for github board management: ex: "weekly label check"
• Marketing objectives => Potential spokesperson : peter thiel through his organization once we have enough infos around workforce development.
• Citizen engagement => We should add problem, solution impact to markedown files for each project (from olivia's slideck) then create the issue (@ExperimentsInHonesty will make it)

Actions to take:

• @Sihemgourou to create milestones plan with shortnames check this
• Create issues to update each project profile card with impact-solution-problem
• Create issue for program areas check this

[sacamp]

2022-05-11 Agenda and Notes

Prework to prep for meeting

Recurring items:

• review any issues that are in the new issue approval column
  • Design
  • Research
• Accountability and Support Check.
  • Review assignments for each Lead and Org rep
    • Bonnie
    • Simone

New Items

• Taking off May 29th-Jun 4th (1 week)
• Still need to add templates to the wiki page and assess completeness of audits
• ArcGIS access update for Roadmap: Research: True Intent Survey #2663

Notes from meeting

Tasks

Items for next meeting agenda

[Providence-o]

Add to next agenda

• People assigned to more than 1 issue
• https://github.com/hackforla/website/issues/assigned/dionw412
• Members not active (update pre-work in QA after discussion)
• https://github.com/hackforla/website/issues/assigned/ivicoded

[sacamp]

Recurring items:

• review any issues that are in the new issue approval column
  • Design
  • Research
• Accountability and Support Check.
  • Review assignments for each Lead and Org rep
    • Bonnie
    • Simone

New Items

• Issues Ready for milestone:
  • Research What Volunteers Want to See in Onboarding Videos #3011
  • Quiz for New Volunteers to Help w/ Team Selection #3005
• In progress: adding templates to the wiki page and assess completeness of audits
• ArcGIS access update for Roadmap: Research: True Intent Survey #2663

Notes from meeting

Tasks

Items for next meeting agenda

[7kram]

@vaisali89

2022-09-21 Agenda and Notes

Prepwork to prep for meeting

• Review and prepare items that have ready for research lead labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agenda.

Recurring items:

• Accountability and Support Check.
  • Review assignments for each Lead and Org rep
    • Bonnie
    • Vaisali

New Items

• Discuss Next Steps after Pre work Issues Cleanup Project Board: Pre-work #3530

Notes from meeting

Tasks

Items for next meeting agenda

[ExperimentsInHonesty]

2022-11-09 Agenda and Notes

Prework to prep for meeting

• Review and prepare items that have ready for research lead labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agen

Recurring items:

• Accountability and Support Check.
  • Review assignments for each Lead and Org rep
    • Isaac
    • Bonnie
    • Simone

New Items

• Roadmap research template for website (https://github.com/hackforla/website/wiki/Research-Output-Overview). Member feature page.
• Next steps for resource organization.
• New Issues to be created.

Notes from meeting

• Review this issue to understand more about the member feature page Member Feature Page #656

Tasks

Items for next meeting agenda

[vaisali89]

2022-11-30 Agenda and Notes

Prework to prep for meeting

• Review and prepare items that have ready for research lead labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agen

Recurring items:

• Accountability and Support Check.
  • Review assignments for each Lead and Org rep
    • Isaac
    • Bonnie
    • Simone

New Items

• Roadmap research template for website (https://github.com/hackforla/website/wiki/Research-Output-Overview).
• Next steps for resource organization.
• New Issues to be created.

Notes from meeting

Tasks

Items for next meeting agenda

[vaisali89]

2023-1-10 Agenda and Notes

Prework to prep for meeting

• [] Review and prepare items that have ready for research lead labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agen

New Items

• Roadmap research template for website (https://github.com/hackforla/website/wiki/Research-Output-Overview).
• Next steps for resource organization.
• New Issues to be created.

Notes from meeting

• Add RP labels to existing issues for organization

Tasks

Items for next meeting agenda

[ExperimentsInHonesty]

2022-02-05 Agenda and Notes

Items

• Review assignments Vaisali assigned issues
• Review and prepare items that have ready for research lead labels in the new issue approval column, so that they if you have any questions for product that you can add them to this agenda.
• review any issues that are in the new issue approval column
  • Research

Notes from meeting

Tasks

Items for next meeting agenda

[ExperimentsInHonesty]

Currently, not having meetings