DS: UX/UI Team Meetings (2022)

[Hanastevenson]

Overview

This issue tracks the agenda for the Design team's weekly meetings:

Template

[DATE] Agenda and Notes

### Prework
- [ ] Add prework here

### Roll Call

#### Recurring items: Happens on the UX/UI meeting
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/design-systems/projects/1#column-15133576)

 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each PM
       - [ ] [Bernard](https://github.com/hackforla/UI-UX/issues/88)
       - [ ]  [Wataru Inoue](https://github.com/hackforla/UI-UX/issues/189)
       - [ ] [Ryan] (https://github.com/hackforla/UI-UX/issues/67)

#### New Items
- [ ] 
#### Task items from Team meeting to review
- [ ] 
  - [ ] Carry forward the "New Items" that we did not get to look at today

### FYI

### Notes from meeting
- 

### New Task Items

#### Items for next week's agenda

2021 Weekly Agendas:

Issues from 2021

[Hanastevenson]

Tuesday 18th January Agenda and Notes

Prework

• PM and Lead meeting

Recurring items: Happens on the UX/UI meeting

• House keeping - meeting times, slack, time commitment
• Brief history of the project and future plans
• review any issues that are in the In Progress Column
• Github, how it works, new issues
• Accountability and Support Check.
  • Review assignments for each PM
    • Bernard
    • Wataru Inoue
    • Ryan
    • Alena

Task items from Team meeting to review

• 01:A My first Issue - Design System Reading #260
• 01:B My first Issue - Design System Video #261
• 02: My Experience Profile #274

FYI

Notes from meeting

• Update Zoom link on invite and invite both new joiner.
• Open roles ticket check the timings of the meetings because it is missing the time for the monday evening.
• Ryan to create a ticket for the high fidelity foundation work
• Bernard will be copying this ticket and working on this for the next week
• Ryan to create slack dm group with all members
• PM to create Figma Foundation label and update labels in Roadmap file

New Task Items

Items for next week's agenda

Review: #62

[Hanastevenson]

Tuesday 25th Agenda and Notes

Prework

• PM and Lead to create the first[ UX/UI Issue] (03: My First UX/UI Issue #269)

Roll Call

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for each PM
    • Bernard
    • Wataru Inoue
    • Ryan

New Items

• New joiners to recreate this Issue during the meeting so they have feedback and support on how Issues work on the board.
• Ryan to present the Figma and the Wiki audit results
• Check with Anh regarding these outstanding tickets
• Discuss next steps for the foundation work

Task items from Team meeting to review

Notes from meeting

• New joiners created their first UX/UI Issue
• Ryan ran through the audit presentation - recording to be added to the Google Drive
• The research team will look through the insights report to view assumptions
• Anh will be taking a look at the Milestone 9 tickets that are in the Backlog. She will won't be joining the meetings as she has a full time role now but will be working on them in her own time. She will communicate with the team.
• The PM provided feedback on the Figma Foundations work, Ryan presented this back to the team.
• Alena asked where the Figma Foundation sits when completed. PM explained how the Figma Foundation will sit in the Design System Template file (in Figma) this is the template that any team can go and view, copy and add to their project. The file must be view only for members outside of the Design System team. There also could be another version that could sit in the Wiki.

New Task Items

• Ryan to update Zoom link on invite (to [email protected]) and changing the zoom link.
• Ryan to create Figma Foundation Issue for V4.
• PM to add Alena and Wataru to Figma project so they can edit.
• PM to upload presentation to the Google Drive.

Items for next week's agenda

• Discuss new joiner thoughts on the guide
• Go through Figma Foundation
• Go through the Universal design system

[Hanastevenson]

1st Feb Agenda and Notes

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column

• Accountability and Support Check.

  • Review assignments for each PM
    • Bernard
    • Wataru Inoue
    • Ryan

New Items

• Discuss new joiner thoughts on the guide
• Go through Figma Foundation

Task items from Team meeting to review

FYI

Notes from meeting

New Task Items

PM to upload presentation to the Google Drive.

Items for next week's agenda

• Go through the Universal design system

[Hanastevenson]

8th February Agenda and Notes

Prework

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for each PM
    • Bernard
    • Wataru Inoue
    • Ryan
    • Alena

New Items

• Design Exercise
• Setting goals for the next couple of weeks

Task items from Team meeting to review

FYI

Notes from meeting

• PM showed the UX/UI team how to create an agenda.

• The PM ran a time box exercise on the following questions:
  What problem are we solving with this piece of design work
  What were the objectives of the brief?
  What would make would make this design work successful

• Nas and Jeanette joined and worked through the exercise and added thoughts on the research work.

• Exercise notes can be found in the UX/UI Figjam

New Task Items

• Show list of elements/tasks we want to test on the Figma foundation.
• Revisit the designs and think about the questions asked in this meeting.
• Start to draft presentation for this piece of work.
• A ticket for the future - create an insights template - check with Anh later this week for her first draft.
• Meeting on Friday instead of the next tuesday so Ryan and Anh can join.

Items for next week's agenda

[allthatyazz]

3/1/2022 Agenda and Notes

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments
    • Wataru Inoue

New Items

• Go through Figma Foundation
• PM and Research team provide feedback for System Foundation Revision& Presentation #347
• Discuss recruiting new joiners

Task items from Team meeting to review

FYI

Notes from meeting

• Meeting attendees: Wataru (UX), Yas (PM), Jeanette (Research lead), Dongchen (Research), and Tammy ( a prospective UXer).
• This was the first UX team meeting after 3 weeks.
• Right now there is only one active team member (Wataru) on the UX team. Everyone else got a job recently and they needed to focus on their career.
• We had a new attendee (Tammy Trinh) at this meeting. Tammy is a member of another HfLA project but she is interested to join the DS team. Tammy and Anh (a previous DS team UX designer attended the same boot camp) and Anh recommend the DS team because she learned a lot from collaborating with researchers at the DS team.
• Wataru explained the UX team's efforts till the present day and the project history to the best of his knowledege (he joined the project just before other UX team members left the team).
• Wataru explained his current assignment and ask for PM and researcher's feedback. For his assignment, he was working on a presentation ( a tutorial for Figma Foundation). He made a Figma prototype out of presentation slides.
• The team discussed the possibility of defining usability studies for the tutorial itself.

New Task Items

• PM will discuss the tutorial idea with Bonnie.
• Wataru will make a template (on FigJam) to receive feedback from the team.
• Team members will review the work and give him feedback.

Items for next week's agenda

[allthatyazz]

3/8/2022 Agenda and Notes

Prework

• Read the notes from previous week for context

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments : Tammy and Nana Yaa explain their progress with their first tickets

New Items

• Hana (previous PM) helps the UX team understand the Figma Foundation initiative better
• Review Wataru's presentation with the new joiners
• Discuss Cherilyin (from the Internship project) who is sent by Bonnie to test our guide (opportunity for usability study)
• Discuss the steps needed for turning Wataru's tutorial into a test-ready MVP for the usability study

Task items from Team meeting to review

FYI

Notes from meeting

• Tonight's attendees: Yas (PM), Jeanette (Research lead), Tammy and Nana ( UX designers), and three new joiners who were observing our meeting.
• Everyone introduced themselves.
• Yas and Jeanette gave a general explanation about the project, the use of Wiki, the first tickets, and the history of our team.
• New joiners were guided to create their first issue.
• New joiners background: PhD in political science (interested in UXR ), a boot camp graduate (interested in UXD ), and an economics graduate student.

New Task Items

Items for next week's agenda

• Hana (previous PM) helps the UX team understand the Figma Foundation initiative better
• Review Wataru's presentation with the new joiners
• Discuss Cherilyin (from the Internship project) who is sent by Bonnie to test our guide (opportunity for usability study)
• Discuss the steps needed for turning Wataru's tutorial into a test-ready MVP for the usability study

[allthatyazz]

3/15/2022 Agenda and Notes

Prework

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments : Tammy and Nana Yaa explain their progress with their first tickets

New Items

• Hana (previous PM) helps the UX team understand the Figma Foundation initiative better
• Review Wataru's presentation with the new joiners
• Discuss Cherilyin (from the Internship project) who is sent by Bonnie to test our guide (opportunity for usability study)
• Discuss the steps needed for turning Wataru's tutorial into a test-ready MVP for the usability study

Task items from Team meeting to review

FYI

• This meeting has been recorded for those who could not come.

Notes from meeting

• Attendees: Wataru, Tammy, Hang - Yas - Nas
• Each team member will build their own Persona for Figma Foundations. Building Personas for the Figma Foundations Tutorial #375
• The team will continue to work on the tutorial to get it ready for the Stakeholder meeting.

New Task Items

Items for next week's agenda

[allthatyazz]

3/22/2022 Agenda and Notes

Prework

• Add items to the Agenda after stakeholder meeting and all-team meeting here

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments : Personas and Figma Foundations

New Items

• Adding Role label to the tasks.
• Cover page for Figma Foundations
• Discuss the grading idea
• Discuss usability

Task items from Team meeting to review

FYI

Notes from the meeting

• Attendees: Wataru, Tammy, Hang, Dongchen, Yas, new joiners Sandra and Deepa ( Observing only). Sandra is a UX writer and everyone became very excited to have her on the team.
• Discussed: The progress on Figma Foundations and the division of labor. The introduction page can include an instruction or "How To" section for the whole Figma Foundations.
• Decided: Yas would create issues for the following tasks:
  • Cover Page for Figma Foundations FF: Tutorial & Template: Cover page #383
  • Introduction Page Design introduction page/section #382
  • Completing the examples section for the cover page and start page FF: Example Page: Cover page #384 .

New Task Items

Items for next week's agenda

[allthatyazz]

3/29/2022 Agenda and Notes

Prework

• Inform the Design team so they can use the agenda and add their own items to it.

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments : Figma Foundations

New Items

• Discuss direction of Intro section and examples page,
• Go over any confusion/pain points.
• Discuss where we want to be by next week.

Task items from Team meeting to review

FYI

Notes from the meeting

• Attendees: Wataru, Tammy, Sandra
• Discussed: Current status of the Intro pages, examples page, and foundations cover. Critique and brainstorm on possible edits and improvements.
• Decided:
  • Simplify the wording in Intro to avoid the page from being too text heavy.
  • Try a checklist tier system for the examples page to keep it objective but still have a scale.
  • Keep the current MVP cover image for now

New Task Items

Items for next week's agenda

[allthatyazz]

4/5/2022 Agenda and Notes

Prework

• Prepare the agenda

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments : Figma Foundations

New Items

• Going through diffrent sections of Figma Foundations

Task items from Team meeting to review

FYI

Notes from the meeting

• Attendees: Wataru, Tammy, Sandra, Yas, Nana Ya
• Progress: The team went through the design and Yas updated the team about stakeholders' specific needs/requests.
• Discussed: We discussed how we can use the usability test to the UX team's advantage.
• Decided: Tammy and Sandra will polish the Start Page.
• Wataru will make a Figjam for a team so the team can add their input to the research team.

New Task Items

Items for next week's agenda

[allthatyazz]

4/11/2022 Agenda and Notes

Prework

• Prepare the agenda

Recurring items: Happens on the UX/UI meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress Column
• Accountability and Support Check.
  • Review assignments : Figma Foundations

New Items

• Going through diffrent sections of Figma Foundations

Task items from Team meeting to review

FYI

Notes from the meeting

• Attendees: Tammy, Wataru, Sandra, Yas
• Progress: Tammy and Sandra worked together to improve the Introduction page.
• Discussed: Team refined some last minutes details including cropping the Design system logos from the "How to" screenshots.
• Wataru brought up a very good point that what appears "common sense" to the designers is not necessarily that clear for the users.
• Decided to keep Sandra's latest copy as the backup for later iterations.

New Task Items

Items for next week's agenda

[allthatyazz]

Tuesday 4/19 Agenda and Notes

Prework

FYI

This is a joint session with the Research and Design teams in lieu of the All Team (All-hands) meeting.

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

• review any issues that are in the new issue approval column
• review any issues that are in the In Progress column
• Accountability and Support Check.
  • Review assignments for each team
    • Research
    • UX/UI

New Items

• Design Workshop Day: Research and design teams would go over the first usability study and present their observations Participant 1 analysis #394.
  • Provide the general overview of the first test.
  • Address how we can improve the design.
  • Discuss if we need another template for note-taking.
• Discuss the templates for usability Issue Templates for Figma Kit research #396
• Discuss the timeline for the 2nd round of usability studies
• (if we have time) Go over the GitHub's project board with the team to review the recent changes

Task items from Team meeting to review

Notes from meeting

• Progress:
  • The first usability test on Figma Foundations (FF)- Cover Page was conducted in the previous week and according to our Research lead, it was a success. In the first test Eric, Dongchen & Sandra were present. After the test, different team members rewatched the first usability video and documented their observations in a spreadsheet. In today's meeting, Dongchen, Sandra, Tammy, and Wataru presented their notes and observations to the team. Then the whole team discussed the observations and provided suggestions for improvment.
  • Kelene spent a great deal of time on the reorganization of the Github board/ Google Drive and she provided the team with a brief update at the end of the call.
• Discussion:
  • Team discussed the overall pain points for the user. Below are the highlights of what the team discussed.
    • The test environment is not "real enough" for the user to realize they can compare their own Figma file with the standards of FF or they can make some changes to their Figma.
    • The name "Figma Foundations" is confusing.
    • The size of the screenshots on the "how-to page" made the user zoom in.
    • The "additional resources" page seems not to add any value to the user experience at this stage.
    • On the tutorial page, the user tries to click on the GitHub link to open it but requires to hover over the GitHub link in order to see the link.
    • User has a positive attitude towards the examples page but it seems the user could not necessarily learn from it (We need further research).
    • There is confusion between "MVP" and "Ideal" templates and knowing the meaning and the differences.
    • When tasked with creating a cover page with the help of FF, the user tried to test in the FF but then started a new Figma file.
  • Team discussed the following strategies to help with the above pain points:
    • Creating a sandbox or a “safe space” for participants to test the templates within the Figma Foundations
    • Working with the PM of the specific projects to grant permission/authorization to the usability participants so the participants can make changes on their project Figma file without being worried.
    • Improving the language and the copy to clear some confusion points.
    • Creating a checklist for users when they follow the instructions or use the example pages.
• Team Decided:
  • For the sake of consistency between Participant A and B, the design team would only work on small fixes for now.

New Task Items

• Recruit participant B
• Work on the minor changes in the language and size of the images/texts of the current design
• Explore the idea of a sandbox or a “safe space” for participants to test the design elements
• Explore other naming options for "Figma Foundations"

Items for next week's agenda

[allthatyazz]

Tuesday 4/26 Meeting Notes

• Attendees: Wataru, John, Tammy, Yas
• Progress:
  • Team worked on minor/quick fixes after the usability test with Participant 1 or P1.
• Discussion:
  • We discussed the issues related to the next section in Figma Foundations which is going to be about "Creating a Start Page". We discussed the distinction between "MVP" and "Ideal" templates that are not going to work for every section like "Start Page" because "ideal" could mean different things for different projects. We discussed the possibility of merging the templates into one page.
  • We discussed some other solutions for the other pages.
• Team decided to keep the design consistent for the second participant or participant B.

[allthatyazz]

Tuesday 5/3 Meeting Notes

• Attendees: Wataru, John, Tammy, Yas
• Progress:
  • Team conducted the 2nd usability study in the past week and during Monday's all-hands meeting, the whole team collaborated on a FigJam file to consolidate the data after two usability tests. Each team member put down their sticky notes on the FigJam. Sandra's notes were turned into stickies by John, Yas, and Dongchen.
  • Research team lead @hdchangie provided a preliminary list of recommendations to the Design team to improve major and minor issues related to the design. The design team used this document during the meeting to discuss areas that needed improvement.
• Discussion:
  • We discussed the idea of the checklist and ways to make it "clear" for the users about "requirements/ mandatory changes" vs "optional changes".
  • We discussed ways to improve the "Start here" page such as
    • Have 1 frame on the Start page instead of multiple frames. In a way, the team is moving from "having a slide deck" to a sort of "building a landing page" mentality.
    • Include GIFs or animations to guide the user's attention to our intended section (John has more experience with this kind of interaction than the rest of the team).
    • Rework the "How to use" wording. Alternatives discussed "What to expect" or "How to Navigate FF".
    • Replace screenshots with illustrations.
    • Replace the list of steps (text) with graphics or columns of a more visually-appealing nature.
• Team decided that each designer would work on their version of the pages to present them during the next all-hands meeting. So, the researchers can vote on the design as well.

[allthatyazz]

Tuesday 5/17 and Wednesday 5/18 Meeting Notes
On Tuesday we met at the regular meeting time for an hour. The follow-up session happened on Wednesday and lasted two hours.

5/17 Tuesday Notes

• Attendees: Sandra, John, and Yas
• This session is recorded for the members who want to watch it later. View the recording here. Important time stamps are:
  • 0:00 - 1:52 The Agenda for the meeting
  • 2:21 The two Figma documents the team is working on
  • 3:11 What we tested on P3
  • 13:00 John provides feedback for the latest designs - he brought up an excellent point that how the requirements checklist lacks contextual information for the users
  • 17:00 Sandra provides feedback about the uniformity of the design seems repetitive to the user
  • 18:00 Yas' previous solution to make the design less monotone
  • 21:00 Yas and Sandra explain why the instruction/requirement page is not working
  • 24:40 Sandra presents her user flow
  • 33:00 Sandra's alternative solution for bringing the templates early on
  • 40:00 John recommends including the video tutorial

5/18 Wednesday Notes

• Attendees: Kelene, Sandra, John- Yas stopped by quickly.
• Please read the meeting notes here.

[sandraberjan]

6/1 Wednesday Design Team Meeting

Attendees: Wataru, Tammy, Sandra

Discussion

• Sandra’s slide deck on design decisions; Wataru “an ever-growing QA document for design”; placed it on back burner for now due to more pressing matters

• Most recent design(s) and research recommendations to make sure we're all up to speed and on the same page

• Issue of layout: vertical vs horizontal

• How we could solve the current problem of too much information/content if we use the “all one page” vertical layout as recommended by research
  -P3 is most like our target user
  -P3; too much instruction for a simple task
  -P2 not representative of our target user
  -Frontloading action-based content, adding more info/examples after

Action Steps:

• Create a mock-up of a new structure that could solve the above problem:
  Each page has three subpages

-Page 1.1 has a template and checklist (all you need to do the task)
-Page 1.2 has examples (more than two but not the big overwhelming chart)
-Page 1.3 has the “why”

Key point: Only Page 1.1 is actually needed for the task ONE-STOP SHOP
We think this will be most in line with how designers work in Figma

• We will present the mock-up at the next all-hands meeting

• Mock-up will be lo-fi

[allthatyazz]

Since June 2022, we have implemented a team sandbox (Whiteboard) and documented design decisions/ meeting highlights there.