Sihemgourou commented 3 years ago

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 commented 3 years ago

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 #1619
@Sihemgourou has now access to the google analytics account #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:

[x] 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.
[x] Ask the other pms if they want to join on the 1v1 with @Sihemgourou & @ExperimentsInHonesty => Done : see slack
[x] Review the design to development hand-of (Creating a file in gdrive to stock the figma images?)
[x] Finish cleaning the board by adding features on the Icebox
[x] Prioritized the issues on the prioritized backlog
[x] Create a roll call spreadshit ? (https://github.com/hackforla/website/issues/1734)

Sihemgourou commented 3 years ago

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 #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:

[x] Ask Bonnie why the Member Feature page has the same objectives as the wins page.
[x] Ask Bonnie about the things discussed with Akib about the wins page
[x] Adding descriptions to the newly created labels => gdoc with list of all the labels + add caracters limits and run it through the pm team
[x] Talk with Bonnie about this issue #1789
[x] 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 #1732) => we wanted to ask which image they prefer

Sihemgourou commented 3 years ago

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:

[x] @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
[x] @ExperimentsInHonesty has to check the wiki for tomorrow's meeting
[x] Ask @ExperimentsInHonesty about the zoom faq in the getting started page
[x] 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 commented 3 years ago

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:

[x] @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.
[x] @Sihemgourou will present another alternative which will be more compatible with the design
[x] Review the home page research strategy with @DanielekPark
[x] 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 #1789
[x] Ask Bonnie why the Member Feature page has the same objectives as the wins page
[x] 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 commented 3 years ago

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 commented 3 years ago

Meeting 21/06/24

Participants : @Sihemgourou & @ExperimentsInHonesty @sayalikotkar

Things discussed:

Actions to take:

[x] Talk with the devs about the amount of front end good second issues
[x] Make 3 bugs issues about the project cards bugs
[x] 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 commented 3 years ago

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:

[x] Make an audit about everything that is in figma and be ready to be developped
[x] All team : talk about people taking two issues at the same time
[ ] Onboarding/contributing md is too big ?
[x] @Sihemgourou will put [this issue ](Updating the HfLA Website Team Meeting Roster #1343) on the ice box and put a date on it.
[x] All team : how to create a note to cite an issue for the dev team meeting
[ ] issue 1445 : the issue should be self explanatory
[x] @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 commented 3 years ago

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:
[x] Figure out how to keep the flow of informaitons going between design and pm when @daniellex0 will leave
[x] Talk to Bonnie about the @hackforla/website-design and website merge team
[x] Create a UR role in labels
[x] 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 commented 3 years ago

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

Capture d’écran 2021-06-30 à 20 46 26

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

[x] Talk with the dev team about how the column dev meeting is working
[x] ALL TEAM : ask if everyone has the calendar invite
[x] 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 commented 3 years ago

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 commented 3 years ago

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:

[x] 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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 : https://github.com/hackforla/marketing/issues/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:

[x] 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 ?
[x] @Sihemgourou will do a draft to answer this issue => to review to next meeting https://github.com/hackforla/website/issues/1942
[x] 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 commented 3 years ago

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

[x] Review the mobile responsivness issue

Sihemgourou commented 3 years ago

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 https://github.com/hackforla/website/issues/1989

Actions to take:

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

Sihemgourou commented 3 years ago

Meeting 21/07/21

Participants : @ExperimentsInHonesty @Sihemgourou @Aveline-art

Things discussed:

The dev team will update the wiki page to create a new issue #1983

Sihemgourou commented 3 years ago

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:

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

Sihemgourou commented 3 years ago

Meeting 21/08/03

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

Things to discuss:

[x] Priotize design issues

Things discussed:

long version Research plan for home page redesign , shorter version for donors and partners

Sihemgourou commented 3 years ago

Meeting 21/08/03

Things discussed:

Github analytics: if the data are not

Actions to take:

[x] @Sihemgourou to create an issue to remove the looking for section and create a dependency with this issue (https://github.com/hackforla/website/pull/1837)

Sihemgourou commented 3 years ago

1-1 Meeting 21/08/05

Participants: @Sihemgourou @ExperimentsInHonesty

Things discussed :

Impact page : We have 2 types of funders: The city of LA and the non profits, and they want different things : the city is more into local impact whereas the non profits want more scalable projects. Note for the UX research team: Alesha and Josey (from youth justice nav project) they are the stakeholders to talk to about making grants.
Difference between advisors and senior people: sometimes its the same people (especially the ones that are not available at all time), we still don't have advisors to the management team (because we don't have leadership team), senior people who want to work as any other volunteers (number 1 priority +++ => having more senior people on dev teams)
Toolkit pages: quick win on putting the guides as pdfs, long term solution will be to put the guides as markedowns
Google analytics: for now put the trackers on the existing pages

Actions to take:

[ ] Talk about the impact page (impact at scale ?)

Sihemgourou commented 3 years ago

PM-Design Meeting 21/08/09

Participants: @kristine-eudey @ExperimentsInHonesty @kevngaleu @Sihemgourou @Basu3040 @Jhay95

Things to discuss:

we need to write down the design to dev handoff process

Things discussed:

New issue approval: Once the issue is reviewed and validated by the leadership team, the issue should have a ready for milestone label for the product team to put the right milestone and then move the issue to the prioritized backlog.
design to dev handoff =>
- Once a designer finishes their issue they should put it in the UAT column.
- Lead design @kristine-eudey will look at design issue that are open in UAT and close it once it is reviewed and approved.
- When reviewing issues in the UAT column there is no need to change labels.
- User Researchers will look at UR issues that are open in UAT and close it once it is reviewed and approved.
- Product team will look at design issues that are closed in UAT (and dev issues to be sure that there is no follow up issues.)

Actions to take:

[ ] @kristine-eudey will create a design meeting agenda so that we can put all the issues that should be reviewed by design
[ ] Product team (@Jhay95, @kevngaleu and @Sihemgourou) to review research plan for the homepage and put any comment before next pm meeting

Sihemgourou commented 3 years ago

PM-DEV Meeting 21/08/11

Things to discuss :

[ ] We need to make a new issue for development out of #1879 using #1739
[x] Ask @Aveline-art about the empty columns created on the board.
[ ] Product team to review research plan for the homepage

Things discussed :

HomePage v1 redesign:
- create subpages for sdgs
- build a randomizer for the wins
- waiting for the component from the toolkit page to be ready
- for now we can use the program areas cards from the program areas homepage
Citizen engagement:
- It is going to be a large issue and it will require javascript skills.
- it is a high priority because we cannot release the homepage without the program areas subpages

Actions to take:

[ ] make new issue for #1343

ExperimentsInHonesty commented 3 years ago

Agenda for next meeting

Review this and decide when we will use https://github.com/hackforla/website/issues/1734 Update this issue with the links at the top.

kristine-eudey commented 3 years ago

PM-Design Meeting 21/08/17

Participants: @ExperimentsInHonesty @kristine-eudey @Basu3040 @kevngaleu @sheltoG @sobe-an

Things to discuss: Basu agenda items:

Add research team to 1Password for siteresearch@hackforla.org
Clarification on Homepage redesign Business Plans and KPIs
How to reach out to more people to conduct donor interviews and conduct a short survey?
Can we have a schedule before the dev team meets on Sundays (for 30-40 mins) or any other suitable day?

Kristine agenda items:

Following from last week: "We need to write down the design to dev handoff process" <-- Has this been documented somewhere?
Potential for redesign of top nav to reflect main content areas as we expand our pages. Ideation here
Prioritization of issues in Prioritized Backlog
Kristine question: Do all design issues that involve something new being designed (rather than just small tweaks to existing design and copy) need to be brought to Sunday or Tuesday meeting for approval? Are there instances in which design issues go through the above design-to-dev handoff process without prior approval from Bonnie/PMs? Want to be sure I understand the appropriate process and what needs to be discussed with larger team vs. what doesn't.

Things discussed:

Clarified objectives & KPIs on homepage redesign research plan
- Need data scientist to scrape meetup data to help us understand the baseline of year-to-year growth as it currently stands
Sunday meeting scheduling: Going forward the first 30 mins will be Design/PM portion (beginning at at 10am PT / 1pm ET) and the second 30 mins will be all together (design, dev, pm)

Actions to take:

[ ] Bonnie will post call-out for research participants on general channel once team is ready
[ ] Basu will set up calendly to schedule with participants
[ ] Work with Mina to create documentation on interview scheduling so other teams can refer to it in the future

ExperimentsInHonesty commented 3 years ago

@Basu3040 will decide what message needs to be sent to the general channel... something like this

@channel The Hack for LA #hfla-site UX team is looking to interview people who have donated money in the past for social cause.  We want to understand their motivations.  If you know someone who has given a donation and would be willing to be interviewed.  [insert CTA here]

Basu3040 commented 3 years ago

@channel The Hack for LA #hfla-site
 UX team is looking to interview people who have donated money and/or service in the past for social causes.  We want to understand their motivations.  If you know someone who has given a donation and would be willing to be interviewed and be part of a short survey (expected duration 45-50 mins), please contact @Basu3040 @kristine-eudey. Thank you for your support.

kristine-eudey commented 3 years ago

Meeting: 8/24/2021

Participants: @ExperimentsInHonesty @kristine-eudey @Basu3040 @kevngaleu @sheltoG @sobe-an Things to discuss:

Review new header copy for Projects page
- 1051
- Figma - Projects Page
Functionality of Wins card on homepage redesign
Basu requests final review/sign-off on interview questions. Questions begin on page 5 of research plan document

Things discussed:

Review of all the design issues in the column "New issue to approval", milestones assigned, and moved to the prioritized backlog
Research team to give final feedback to the product team about their comments made on the research plan (interview). With the aim of allowing them to know what changes have been finally made and why.
@Basu3040 to finally review the following issues #1968 and #1789 Actions to take:

sheltoG commented 3 years ago

Meeting: 8/31/2021

Participants @ExperimentsInHonesty @kristine-eudey @Basu3040 @kevngaleu @sheltoG @sobe-an

Things to discuss

Shelton agenda items:

Alignment on Hfla business objectives

UX agenda items:

Running Usability testing with donor/partner interviews
Review new copy for projects page #1051

Things discussed:

Usability testing to be done by research and design - for donors and people in incorporate responsibility - Usability to be done first on desktop. Mobile will follow. - A mix of designers and researchers will participate to make it more efficient
Convention on Figma page: top to bottom for iteration and final versions. From left to right for a change.
Annotation on-page into Figma when handing over from design to development (Ready for development, In development)
Review of the latest Home page design

Actions to take:

A list of what we want people to think about of our projects
Product management to think about KPIs for the home page and others for the entire website (and organization) to share them with UX, and development teams.
Do an MVP of the "Explore over projects" by program area: No carousel,...Since we need enough information from other projects to implement, and it will take much time to develop.

ExperimentsInHonesty commented 3 years ago

review this at next meeting https://github.com/hackforla/website/issues/2021 https://github.com/hackforla/website/issues/19 https://github.com/hackforla/website/issues/918 & https://github.com/hackforla/website/issues/916

kristine-eudey commented 3 years ago

Meeting 21/09/07

Participants : Basu, Bonnie, Kayode, Kevin, Kristine, Shelton

Things to discuss: https://github.com/hackforla/website/issues/2021 - bonnie will talk to sophia then get back to ui https://github.com/hackforla/website/issues/19 - carry this over till next meeting but clarify that is ux research https://github.com/hackforla/website/issues/918 product will define labels and then meet with ui next meeting https://github.com/hackforla/website/issues/916 - move it into prioritized backlog - done

UX - Design Agenda Items

Follow up with Product regarding this from last week:
- As related to issue #1051 PM team will identify and give UX team clarity on what the most important elements we want to mention on the header of our Projects page.
  - Questions to answer: what do we want people to think about when they think about our projects? How do we want to frame our projects for them?”
  - carried over to next weeks agenda, product will look at this tomorrow.

Things discussed:

Actions to take:

ExperimentsInHonesty commented 3 years ago

21/9/14

Participants: Things to Discuss: Research hackforla/product-management#19

Design Homepage

918 product will define labels and then meet with Design

review of hompage design

1051 PM team will identify and give UX team clarity on what the most important elements we want to mention on the header of our Projects page.

   - Questions to answer: what do we want people to think about when they think about our projects? How do we want to frame our projects for them?”

2021 review the figma after Sophia indicates where her design work is

sheltoG commented 3 years ago

9/21

Product Management

Discuss removing the project team section on Hfla projects

UX Research

Please suggest on the script to recruit corporate donors https://docs.google.com/document/d/1Vxn0QV8bfk6yk3J91-aQ3PqANMHF7_0XCkwuaCtdjs4/edit

Design Homepage Projects page header

kristine-eudey commented 3 years ago

Meeting 9/28/21

Participants :

Things to discuss: Design: 2 new issues for approval: #2311 & #2312

Things discussed:

Actions to take:

ExperimentsInHonesty commented 3 years ago

Meeting: 10/5/21

Things to Discuss:

Discuss if there are any changes we need to make to the wins page to make it more accessible. For instance, does it matter that we do not have the word sort or filter next to the drop downs?
Discuss if we are going to make accessibility changes to Credits page. Guidance calls for external links to be marked
(Kristine) #1051 & #2069 - both are complete, what should my workflow for them be on the board?

Decisions made

To create a template issue for Auditing use Accessibility tools for each page. Divide the pages up 5 to design 2 to research and 3 development - milestone accessibility feature Accessibility audit
Kristine will make an issue to mockup change to credits page
Still waiting for Front End and Product to work out the approval process. Should have an answer by Tuesday of next week.

ExperimentsInHonesty commented 3 years ago

Design & Research to make an issue for new team member prework Design to make an issue to review making typograph changes to allow for Bold, Medium, Regular

kristine-eudey commented 3 years ago

Meeting: 10/12/21

Things to Discuss:

Kristine to update team (for Basu, who can't make it to the meeting) on research progress.
Review progress on homepage mobile version.

Decisions made

More top and bottom padding will be added to sections of mobile design for homepage (diverting from design system guidance, design system will be modified to account for this change)
Design to produce mockup of homepage with boxes having rounded corners for consideration (Join Us at bottom of page, and CoP gradient box have square corners in current design).
Weekly UX meetings will run the standup from the In Progress column on the board in order to guide team to keeping their issues more consistently updated.

kristine-eudey commented 3 years ago

Meeting: 10/19/21

Things to Discuss:

[x] Projects missing on Wins submission form - which role should this issue be for? #2374
[x] Design seeking review/approval for updated mobile Donate page #1841
[x] Please amplify the call-out for Civic Tech Infrastructure image submissions. Call-out Kristine posted:

Hi website team! The UX team is currently searching for a photo which best represents the Civic Tech Infrastructure program area for the new homepage and we would love your input! :camera_with_flash: Can you think of an image, or type of image, which represents Civic Tech Infrastructure to you? If so we'd love your input in order to best represent this on the new homepage! Please post the image (and link) to the comments in this issue. Ideally the photo would be open source and available for our use on the site, but if not that's okay too in that it can help us generate ideas for the type of images which best represent this. All input helps!
[x] Review of updated Homepage - mobile version #2213

Decisions made:

[ ] UX to write issue for creating a survey that is sent to people when they make a donation to help us better understand the demographics of our donors.
[ ] #2734 should be an issue for back-end. Is currently in new issue approval and is ready for milestone
[x] #1841 approved. Kristine to comment and add to note in new issue approval column for front-end to make issue.
[ ] Bonnie posted call-out for Civic Tech Infrastructure images on general channel. Kristine will create some mockups of the iPad screen in the current image showing some image elements relating to our current projects in this area (book, magnifying glass, people of every color, spreadsheet, gear, guide)
[x] Mobile homepage is approved and ready for development! Team agrees that all boxes (CoP, Join us at bottom) should have 20px radius for consistency. Kristine will get in touch with Sarah about this change since it will apply to both desktop and mobile versions)

ExperimentsInHonesty commented 3 years ago

11/2/21 Items for our agenda https://github.com/hackforla/website/projects/7#card-71939341

kristine-eudey commented 3 years ago

Meeting: 11/2/21

Things to Discuss:

From Bonnie:

the Current Pages tab on the figma needs to be updated
- Kristine question: (Working on issue for this now and need clarification) Is "Current Pages" section intended to show the versions of pages that are currently live on the site, or the most up-to-date versions in Figma (in the red box) including those that have been designed and are slated for development, but which are not yet live?
Are we keeping the uses column up to date on the design system in our figma
Let's talk about the spacing card.
The drop down on the design system does not seem to be updated see issue #2286
Is there a plan to use the component feature of figma on our figma? Similar to this Civic Tech Index so that when we update the footer it updates everywhere in figma or are we already doing that?
design to check out https://www.hackforla.org/citizen-engagement for the extra space that seems to be inside at the bottom of the sdg box
- Kristine: I took a look and you're right, the live version does not match the Figma in terms of spacing below the SDG box. There is also a mismatch in the font size and color (though Figma color is wrong/does not match Design System) of the headings in the project card, see below: Current live version:

Current Figma:

From UX:

Simone and Kristine need access to the Zoom account if possible for team meetings.
Kristine to transition out of the team at end of November. Currently working on documentation (here and here) that outlines the roles and responsibilities along with how-to's to prepare either a new team lead to take over, or to support whatever approach to leadership (more collective or small-group led, etc.) the team wants to take going forward.
In the past week 2 new designers have been onboarded to the team with another 2 to onboard this week!
Kristine: Can I assign issues that are still in new issue approval? For example, I am about to create a round of good first issues for the 4 new designers on the team and would like for them to be able to get started contributing as soon as possible. Within the current workflow, if I wait for these to be given milestones and released into the prioritized backlog this could take some time.
Review #2154
Simone: as new research lead, I'd like to talk about the site's UX research priorities and next steps moving forward, since the donor research project is just about wrapped up (I will be presenting results at next Sunday's meeting). We have created a donor persona, and I believe we have enough data from the volunteer interviews to create a volunteer persona. We do not currently have data for partners or advisors.
Simone: Can we adjust our meeting time? I usually have a weekly meeting that ends at 12:30 PST and I can not normally make this meeting time work.

Decisions made:
[ ] Design will update Current Pages section in Figma. Bonnie shared Civic Tech Index's Master Design File for inspiration. This Figma could provide a lot of practices our team/Figma would benefit from adopting.
[ ] Design to update the uses column in the Design System. Will also come up with a new framework and expectation around adding this to all issues: making sure that when new pages are created, or old designs are replaced that updating the Design System to reflect this is made a standard end step of the issue.
[ ] Kristine to create front-end issue for spacing on Citizen Engagement page cards (and to figure out what's going on with font mismatch) and Bonnie will clean up the issue for dev.

kristine-eudey commented 2 years ago

Meeting: 11/10/21

Things to Discuss:

[ ] Need new designers added to GitHub
[ ] 4 issues for new designers in New Issue Approval
- [ ] #2446,
- [ ] #2447
- [ ] #2448
- [ ] #2449
[ ] Discuss HfLA Figma account

Decisions Made:

Isaac, Simone, and Kristine have been added as maintainers on GitHub. New members can be added to our repo here: https://github.com/orgs/hackforla/teams/website-write/members
We decided on using a new process for onboarding new team members going forward: Decentralize this so that everyone on the team has a chance to practice leadership by onboarding new people, rather than lead.
Kristine to have 4 new designers assign themselves the pre-work issue.

ExperimentsInHonesty commented 2 years ago

Next meeting we must sort out the Figma!

kristine-eudey commented 2 years ago

Meeting: 11/17/21

Things to Discuss:

[x] Discuss Figma
[x] Clarification about research New issue approval and prioritized backlog
[x] https://github.com/hackforla/website/issues/2354 ]
[x] Design Issues Kristine/Isaac will create in the coming week:
- Create mobile version of new nav bar
- Rethink how we use hero images on Guides
- Create Design Issue template

Decisions Made:

Bonnie will reach out to Yuiko and ask her to move it to the new figma team
Bonnie will report on when the new homepage will launch at next weeks meeting https://github.com/hackforla/website/issues/2481
All hero images (regardless of size) will have alt=""
Isaac will make an issue that is more general about recording the decision record https://github.com/hackforla/website/issues/2354#issuecomment-971988754 using this page for the wiki https://github.com/hackforla/website/wiki/Decision-Records-on-Solutions-Adopted
Isaac will make an issue to
- review the figma to determine if there are pages or components without a mobile view.
- confirm no issues already exist for those pages for making mobile in figma
- make new issues if required
- make a issue to update the sitemap

kristine-eudey commented 2 years ago

Meeting: 12/1/21

Things to Discuss:

Decisions Made:

Kristine to make Isaac organizer of weekly UX team meeting, Isaac & Bonnie to then transfer the ownership of that meeting to the website@hackforla.org
Kristine to update "Onboarding new members to the team" Google doc (currently out of date since recent updates to process)
Issac and Bonnie will review all the pages on the current pages to check to see if status needs to be updated.

sacamp commented 2 years ago

Meeting: 12/8/21

Things to Discuss:

Research:

[x] send researcher an invitation to preferred github handle "summerharveyux" and delete the "summerharvey" account
[x] researchers are interested in quantitative work - can we access data for website analytics?
[x] new issue approval review

Decisions Made:

sacamp commented 2 years ago

Meeting: 12/15/21

Things to Discuss:

Research

[ ] address issue #2401
- updated the issue to reflect design and development will make seperate issues. Developments should be put on the icebox until design is done.
[x] review issue #2589

Decisions Made:

ExperimentsInHonesty commented 2 years ago

2021-1-22 Meeting Agenda

Prework to prep for meeting

[ ] Review the QA
- [ ] Prework issues: Add notes to this meeting agenda as a discussion or FYI item (if no action needs to be taken).
  - [ ] Check to see how new team members are doing
  - [x] Design
  - [ ] Research
  - [ ] Can we improve the prework template based on something we see as a pattern?

FYIs (nothing needs to be just, just keeping each other informed)

Recurring items:

[ ] review any issues that are in the new issue approval column for
- [ ] Design
- [ ] Research
[ ] Accountability and Support Check.
- [ ] Review assignments for each PM
  - [ ] Bonnie
  - [x] Isaac
  - [ ] Simone
- [ ] finish adding labels to the issue that are still missing them (see audit links above)

Research (add issue numbers to be discussed)

[ ] Discuss what next steps are for this note that was on the new issue approval column for Bonnie to make an issue
- [ ] write up an issue for a full life cycle of people RSVPing for meetings (zoom api, meetupapi, website, and ga tracking).

Design (add issue numbers to be discussed)

[x] Discuss #2361
[x] This is a new PR(#2417), but when I look at the headers for these two pages they are different getting started page <p class="header-p"> vs the communities of practice <p>
[x] Discuss options for #2606
[ ] Discuss what next steps are for this note that was on the new issue approval column for Bonnie to make an issue
- [ ] make a new issue with dependency to make issues for building the design system.
- [ ] Make an issue to show that mobile on wins page does not show the names for the icons if the text is not long enough to warrant a see more. Also the see more should start a space after the last full word.

Task items

[ ] Bonnie to fill in all the dates missing in the above agendas
[ ] Bonnie will make a Pre-work item to clear the new issue approval column
[ ] If haven't heard from Kristine on issue #2190 review with Bonnie
[ ] Talk to Tomas about recoding it so that any are two lines make it so all are two lines
[ ] Discuss with Simone about testing the different variations of See More.. within Wins page or have design redesign different variations of it.
[ ] Bonnie will make an issue to list out all the tools/ accounts a lead uses.
[x] Isaac will update developers on the correct size of text because getting started page and the communities of practice are inconsistent with each other.
[ ] Isaac will make an issue to ensure that Figma’s latest design's text (in the Current Pages) are components that are tied to the design system. After this we can revise the design system's titles and headers so that we don’t have to use only size and boldness styling as the only text variations. @ExperimentsInHonesty I need more clarification on what we discussed with this design system and what I should ask the design team to advice us on. -Isaac *Update: No need, I remembered to ask them during Thursdays UX Design meeting.

Hold for future meeting

[ ] Make an issue for Toolkit page #1708
Non-checked off items in today's agenda

IsaacDesigns commented 2 years ago

Meeting: 12/22/21

Things to Discuss:

Design

[x] Tomas needs Bonnie's opinion on making an issue to reorganize the page headers the card section
[x] Permission to make an issue to improve how the gradient looks over each pages hero image that will work for all pages hero images. Reference gradient issue.
[x] How does Bonnie want to make to list out all of the tools and accounts being used by leads so that we can onboard and transfer to future leads.
[x] Should I make an issue to add the audited navigation component menu (created from this issue) to the Design System.

Decisions Made:

I sent Tomas a mockup of how close the individual projects header should be to the cards.

Screenshot

No need to fix the gradient of individual projects because the problem of the gradient covering the logo and other important parts of images are the people who didn't follow the directions of providing us with a specific hero image.

See Task Items in above Meeting Agenda

ExperimentsInHonesty commented 2 years ago

items for next meeting agenda

This is the item I was refering to

IsaacDesigns commented 2 years ago

2021-12-29 Agenda and Notes

Prework to prep for meeting

Recurring items:

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

New Items

Design

[x] Chat with Design Lead of this project ‣ to learn how they implement their points system to give people working on issues more of a sense of urgency
[x] Allowing team members to write their own issues based on the prioritized tasks in the new Hack for LA Short Term Goals and Strategy.
- [x] Meant to help focus and prioritize the steps we need to take in order to reach our short term goals.
- [x] It will help onboard new designers and keep other teams (Devs, PM's etc..) informed of UX teams progress.
- [x] Will help the design team focus on the big picture and effectively deliver work that reaches these goals efficiently
- [x] Team members will be able to work on issues they are more interested in. more effectively write issues, and take ownership of them.
[x] Feedback on this issue https://github.com/hackforla/website/issues/2190#issuecomment-1000522831

FYIs (nothing needs to be done, just keeping each other informed)

Notes from meeting

We decided we would close this issue https://github.com/hackforla/website/issues/2361#issuecomment-1002763549 and make a new issue see note

Tasks

Isaac will add new points to issues

hackforla / website

HfLA: PM/ORG/UX Meeting Agenda of 2022 #1797

Dependency

Overview

Weekly Agenda

1051

918 product will define labels and then meet with Design

1051 PM team will identify and give UX team clarity on what the most important elements we want to mention on the header of our Projects page.

2021 review the figma after Sophia indicates where her design work is

Meeting: 11/2/21

Things to Discuss:

Decisions made:

Meeting: 11/10/21

Things to Discuss:

Decisions Made:

Meeting: 11/17/21

Things to Discuss:

Decisions Made:

Meeting: 12/1/21

Things to Discuss:

Decisions Made:

Meeting: 12/8/21

Things to Discuss:

Decisions Made:

Meeting: 12/15/21

Things to Discuss:

Decisions Made:

2021-1-22 Meeting Agenda

Prework to prep for meeting

FYIs (nothing needs to be just, just keeping each other informed)

Recurring items:

Research (add issue numbers to be discussed)

Design (add issue numbers to be discussed)

Task items

Hold for future meeting

Meeting: 12/22/21

Things to Discuss:

Design

Decisions Made:

See Task Items in above Meeting Agenda

2021-12-29 Agenda and Notes

Prework to prep for meeting

Recurring items:

New Items

FYIs (nothing needs to be done, just keeping each other informed)

Notes from meeting

Tasks