DS: All-Hands Meetings (2022)

[Hanastevenson]

Overview

This issue tracks the agenda for the design systems meetings and weekly roll call for projects.

Please check in on the Roll Call Spreadsheet

Template

[DATE] Agenda and Notes

### Prework
- [ ] Invite new members to the team meeting

### Roll Call

#### Recurring items: Happens on the PM Monday meeting
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/design-systems/projects/1#column-15412961)
 - [ ]  review any issues that are in the [In Progress column](https://github.com/hackforla/design-systems/projects/1#column-15133576)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each team
       - [ ] [Research](https://github.com/hackforla/design-systems/projects/1?card_filter_query=label%3A%22role%3A+research%22)
       - [ ] [UX/UI Team](https://github.com/hackforla/design-systems/projects/1?card_filter_query=label%3A%22role%3A+ui%22+label%3A%22role%3A+ux%22)

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

Closing All team Meeting 2021 https://github.com/hackforla/design-systems/issues/7

[Hanastevenson]

Monday 17th January Agenda and Notes

Prework

• [x] Invite new members to the meeting
• [x] Confirm new first issue with research team
• [x] Interview Issues need to be on the board
• [x] UX/UI lead and PM meeting

Roll Call

Roll call

Items:

• [x] New joiners introduce themselves - Name, role, location, learnt/goals
• [x] PM to run through the agenda
• [x] PM to run through the Getting started page on the Wiki
• [x] PM to run through the board
  • [x] Accountability and Support Check.
  • [x] Review assignments for each team
  • [x] Product Manager
    • [x] Research
    • [x] UX/UI

New Items

Task items from Team meeting to review

• [x] Carry forward the "New Items" that we did not get to look at today

FYI

Notes from meeting

• New and returning team members introduce themselves
• Nasim announces that Jeanette will be joining her as Research Co-Lead
• New members present: UX/UI: Wataru, Alena; Research: Rosalie, Dongchen, and Kelene
• Hana addresses onboarding and setting goals, pairing new joiners with mentors and resources
• Hana turns to issues
• Updates on "Getting started" page on wiki
• Updates on Experience Profiles
• Provides overview of DS Project Management Board by column
• Describes importance of learning and working within Kanban / agile methodology, including pivoting and rethinking roadmaps
• Goes over first issue ticket templates
• Returning team members give updates
• Hana: working on Figma/wiki audit insight report
• Jeanette: provides research team update (research history and interview insights)
• Ryan: provides UX/UI updates (Figma foundations document)

New Task Items

Items for next week's agenda

Roadmap History

[Hanastevenson]

24th January Agenda and Notes

Prework

• [x] Invite new members to the team meeting

Roll Call

Recurring items: Happens on the PM Monday meeting

• [x] review any issues that are in the new issue approval column
• [x] review any issues that are in the In Progress column
• [x] Accountability and Support Check.
  • [ ] Review assignments for each team
    • [ ] Research
    • [ ] Hana
  • [ ] finish adding labels to the issue that are still missing them (see audit links above)
  • [ ] review issues with epic label and define how to break down further

New Items

• [ ] History
• [ ] RoadMap

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

For today’s meeting the PM went over the Github board to make sure that everybody feels comfortable while navigating Github and creating the tickets/issues. A few highlights:

• Tickets and issues are different names for the same thing. Github refers to tickets as issues.
• Please do not assign yourself when you create a ticket. Inform your lead instead if you have an interest in a ticket.
• Nobody should close a ticket. Instead place them in questions/review column and write a comment on the current state. If you have accidentally closed a ticket, no problem. But do inform your lead.
• Leads may write a comment for your ticket to ask for an update. Please, respond to this comment whenever you have the time, this update-comment is for planning purposes.
• If you have time to spare and want to practice your skills with new assignments. Ask your team lead if there is a ticket/issue that can be assigned to you instead of assigning and moving the ticket across the board yourself. This is not meant as an activity to hinder you, but to keep track of project development.
• The PM highlighted various issue labels, amongst which the milestones labels. These milestones are related to the project roadmap.

Ryan, Hana, and Nas walked the team through the history of the project. On a high level the following elements were covered:

1. Why and how the project came to be
2. Sharing of the current drafting of different HfLA Design System components and design pieces
3. The UX research roadmap including research steps performed (e.g. primary research), current research state (user interviews), and future research steps (e.g. usability testing)
4. UI-UX research elements such as the wiki and Figma audits.

The above will be discussed in more detail during the separate research and design meetings that are scheduled for tomorrow.

New Task Items

Items for next week's agenda

[Hanastevenson]

31st January Agenda and Notes

Prework

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

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

New Items

• [x] Review of the Roadmap

Task items from Team meeting to review

• [ ]

FYI

Notes from meeting

• PM went through the tickets that are in process, making sure the completed tickets are closed.
• Leads gave updates on their progress.
• The research team had no blockers. They discussed what they are going to cover at Tuesday's meeting.
• UX/UI lead went through open tickets. There were no blockers. They will be talking more about the tickets tomorrow in their meeting.
• The product manager talked about how she influenced the roadmap and also how the agile environment has affected it in the past.
• PM discussed the elements on the roadmap which are her responsibilities such as security. She also explained which roles are involved with different parts of the roadmap, and how it needs to be adaptable to the process of any project.
• PM gave a brief history of the resources that were available before starting the project.
• PM went through the second draft of the design guide.
• PM made sure everyone have access to the Figma files.
• PM will be uploading Ryans' presentation from last week.
• PM answered questions

New Task Items

Items for next week's agenda

[Hanastevenson]

Monday 7th February Agenda and Notes

Prework

N/A

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

• [x] review any issues that are in the new issue approval column
• [x] review any issues that are in the In Progress column
• [x] Accountability and Support Check.
  • [ ] Review assignments for each team
    • [x] Research
    • [x] Hana

New Items

Task items from Team meeting to review

• [x] Where are we with recruitment for interviews
• [x] How to add images to the wiki, or Issues
• [x] How to add articles to the wiki
• [x] Need to create a new zoom link for the

FYI

Notes from meeting

• Research team to Duplicate ticket #305
• Next week bring along Interview questions from recruiters/interviews
• Research will talk further about collecting insights
• Hana to add articles regarding Personas, how to act interviews.
• Nas to talk separately to Eric.
• Jeannette is working on the onboarding survey, with feedback from Hana and Ryan.
• Discussed using https://www.typeform.com/ for surveys since it has branching.
• Hana announced that she will leave the project. The team is going to miss her terribly.

New Task Items

Items for next week's agenda

Discuss interview questions. In two weeks time the UX/UI team will show their Figma Foundations work.

[allthatyazz]

Monday 2/28 Agenda and Notes

Prework

• [x] Create a new Calendar Invite for this meeting
• [x] The new PM reviews the related material on Google Drive, Figma files, and Github's board in preparation for the meeting.
• [x] Prospective joiners get referred to the Wiki page/ getting started.

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

• [x] review any issues that are in the new issue approval column
• [x] review any issues that are in the In Progress column
• [x] Accountability and Support Check.
  • [x] Review assignments for each team
    • [ ] Research
    • [ ] [UX/UI] (https://github.com/hackforla/design-systems/projects/1?card_filter_query=label%3A%22role%3A+ui%22+label%3A%22role%3A+ux%22) According to agenda for previous team meeting (2/7) the UX/UI team had two weeks to show their Figma Foundations work. #347

New Items

• [x] New PM introduces herself.
• [x] Old PM explains the team's progress.
• [x] New joiners introduce themselves.

Task items from Team meeting to review

• [x] Where are we with each person's individual goals, how can we address that?
• [ ] Do we need to bring in more designers? What about more researchers?

FYI

Notes from meeting

• Hana (old PM) introduced Yas (New PM).
• We had a new joiner Cherilyn from the "Internship project". Since Cherilyn is already a member of another HfLA project, she can not join the DS team as a designer but she expressed interest to shadow DS team to learn more about Design systems.
• It seems that the stakeholder's vision is to test DS team's guides on other projects and since DS research team already is looking for usability studies participants, DS team thinks Cherilyn would be a nice participant for upcoming usability studies.

New Task Items

Items for next week's agenda

[allthatyazz]

Monday 3/07Agenda and Notes

Prework

• [x] Onboard new joiners.

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] (https://github.com/hackforla/design-systems/projects/1?card_filter_query=label%3A%22role%3A+ui%22+label%3A%22role%3A+ux%22)

New Items

• [x] Welcome new joiners to the team.
• [x] Explain Bonnie's vision about the tutorial and usability studies to the team.
• [x] Ask for team's input about the new product roadmap.

Task items from Team meeting to review

FYI

Notes from meeting

• The new PM, Yas, introduces two new design team members to the Design Systems team.
• Yas first informs the team about the roll-call procedure (attendance sheet) to show how to keep attendance for every weekly general meeting.
• The previous PM, Hana, informs the team on previous work done, also with regards to Figma and Wiki audits done by the previous design team. On the basis of that work has been done to create a low and mid fidelity Figma tutorial files previously.
• Yas announced that the stakeholder is interested in a first usability testing of the currently formulated Figma tutorial (by Wataru). Research added that as a team we should be careful to keep in mind that the tutorial is still based on assumptions predominantly, since the user interview results are still rolling in as we speak.
• The overall stakeholder's vision is to test the Figma tutorial and test it on designers who are currently within a team that has NO design system in place. The initiation of this usability testing form stems partly from the Internship Project.
• The team discussed how the usability testing should look like in its current phase, to make sure that there is not a solution presented that needs to much retweaking while informing the stakeholder correctly concurrently.

New Task Items

Items for next week's agenda

[allthatyazz]

Monday 3/14 Agenda and Notes

Prework

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

• [x] review any issues that are in the new issue approval column
• [x] review any issues that are in the In Progress column
• [x] Accountability and Support Check.
  • [ ] Review assignments for each team
    • [ ] Research
    • [ ] [UX/UI] (https://github.com/hackforla/design-systems/projects/1?card_filter_query=label%3A%22role%3A+ui%22+label%3A%22role%3A+ux%22)

New Items

• [x] Welcome new joiners to the team.
• [x] Discuss the new deadline set by Bonnie.
• [x] Ask for team's input about the new product roadmap.

Task items from Team meeting to review

FYI

Notes from meeting

• We went through the new product vision for the tutorial (previously referred to as Figma Foundations) and discussed how design and usability studies could go hand in hand.
• Research team brought up their concerns about the new direction would become a distraction for the ongoing research.
• The concerns brought up were :
  • How the new direction would be aligned with previous research.
  • Is the stakeholder aware of the scope of the research (the "Onboarding" and "Governance" aspects of our project)?
  • Division of labor: Who should be assigned to what in a way that we can conclude the previous research.
  • Unless there is a clear objective for usability studies defined by the stakeholder, some researchers are afraid that they would waste their time.
  • Yas & Rosalie addressed the latter concern by stating that we can define the problem (for the usability test) based on what we think is valuable to learn more about in a way that meets our original project goals. We can also write a research plan with metrics that we want to measure and show it to Bonnie to see if she has anything to add.
  • Other suggestions were to (1) have stakeholders put her requirements list in a doc and share it with all so the team can reconcile her expectations ( To add to this point, the stakeholder already shared her clear expectations during an interview with the research team, please refer to the transcripts of that interview). (2) having sprints such as (gv. com-style) could be helpful with meeting stakeholders' needs.

New Task Items

Items for next week's agenda

[allthatyazz]

Sorry team for the mixed up with the assignees! I was removing the inactive members and accidentally unassigned everyone.

[allthatyazz]

Monday 3/21 Agenda and Notes

Prework

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

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

New Items

• [x] Take the zoom screenshot of the whole team for HfLA website team according to this CTA.
• [x] Rosalie and Nas offboarding.
• [x] Remind team about PM's upcoming vacation, discuss next week's schedule.
• [x] Discuss the updates after meeting with Bonnie.

Task items from Team meeting to review

FYI

Notes from meeting

• Team voted that there would be no team meeting on Monday 3/28.
• In the meantime, the research team and design team will continue to work on their assignments.

New Task Items

Items for next week's agenda

[allthatyazz]

Monday 4/4 Agenda and Notes

Prework

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

• [x] Discuss the updates after meeting with Bonnie.
• [x] Discuss team's progress in the last week
• [x] Asking for team leads' input about "planning week"
• [x] Discuss timeline for usability study

Task items from Team meeting to review

FYI

Notes from meeting

• Attendees: Yas, Wataru, Tammy, Sandra, Eric, Dongchen
• Progress: Wataru and the design team explained their progress on the Figma Foundations work. Tammy and Sandra had worked on the introduction/ start page. Wataru improved the grading system for other projects in a very objective way so that other teams don't feel offended. Everyone was impressed by the Design team's great job.
• Yas gave some updates requested/suggested by Bonnie.
• Discussion: team discussed the applicability of the current grading for other pages such as the start page where there are not that many examples.
• Eric was interested to explore the relation of the Figma Foundations to HflA's volunteers' overall user journey. The team discussed the potential of Figma Foundations to enhance onboarding of new joiners.
• Team discussed the timeline for starting the usability tests and the challenge of recruitment.
• Decided:
  • The first usability tests would be around one tutorial/ template at a time to keep the interview process short and sweet. For example, the first test would be around Cover Page only.
  • We need to recruit two participants at least for each test: 1 person from a HfLA project whose Figma file does not have a cover page yet. The 2nd participant would be from a project where they have a cover page but their cover page requires improvements.
  • By the end of this week, the design team would clean up the file to make it test-ready. The research team would finalize the research plan for the first usability test for the Cover page tutorial. Both teams (research and design) would present their work to each other next Monday (the next all-team meeting). So that we can finalize the last details.
  • The expected timeline for the first test would be the 2nd half of week 4/11-4/15.)
  • Yas will work with Bonnie to identify the participants so the research team can focus on the research rather than recruitment.

New Task Items

Items for next week's agenda

[allthatyazz]

Monday 4/11 Agenda and Notes

Prework

• [ ] Review previous meeting notes

Roll Call

Please check in on the Roll Call Spreadsheet

• [ ] Discuss if we will have a meeting on Easter Monday

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

• [x] Presentation Day: Research and design teams would present their work to each other.
• [x] Finalize the last-minute details on the usability test
• [ ] (if we have time) Go over the GitHub's project board with the team to review the backlog

Task items from Team meeting to review

FYI

Notes from meeting

• Progress: Eric and the research team had finalized the interview script. The design team still needed to make some changes to the design.
• Discussion: We discussed that prompts from the research plan are meant to act as a mental map for the usability moderator to ask follow-up questions.
• Decided: Team decided to leave the participant as free as possible to see how they would interact with the file.

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

• [x] Design Workshop Day: Research and design teams would go over the first usability study and present their observations #394.
  • [x] Provide the general overview of the first test.
  • [x] Address how we can improve the design.
  • [ ] Discuss if we need another template for note-taking.
• [x] Discuss the templates for usability #396
• [x] Discuss the timeline for the 2nd round of usability studies
• [x] (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]

Monday 4/25 Agenda and Notes

Prework

• [x] Read the previous meeting notes ( Everyone has to do it to refresh their memory and know where we left off last week.)

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

• [x] Recap the team's progress in the past week
• [x] Go over the GitHub's project board with the team to review the recent changes ( Kelene would present)
  • [x] Discuss the team's templates (where to find them and how to use them)
  • [x] Discuss the onboarding board
• [x] Discuss the following items that we touched upon in the last meeting
  • [x] Recruit participant B
  • [ ] Work on the minor changes in the language and size of the images/texts of the current design
  • [x] Explore the idea of a sandbox or a “safe space” for participants to test the design elements
  • [ ] Explore other naming options for "Figma Foundations"

Task items from Team meeting to review

Notes from meeting

• Progress:
  • Since the team was still waiting to conduct the 2nd usability on the following Thursday, we briefly discussed the minor changes to the design and the test protocol. We spend the remainder of the meeting discussing GitHub project management and onboarding. Each team member explained their own onboarding experience. So it is fair to say that we turned the meeting into a focus group study to learn more about the frustration of the team members.
  • Kelene presented the recent changes to the GitHub board, and the team expressed their appreciation and admiration for the work she has done. Kelene also revolutionized the team's onboarding process by doing the following:
    • Build a separate project board for the onboarding
    • Include a clear indication of where the new joiners must start on the Wiki, GitHub Read Me, Project Boards, and Slack channel description.
    • Combine the onboarding tickets (first issues) into 1 cohesive onboarding ticket.
• Discussion:
  • As a team, we discussed the usefulness of the content of the onboarding issues such as Jennie Yip (Atlassian Video).
• Decided: Team voted to remove the Atlassian Video from the onboarding issue because the scope of it is overwhelming and confusing for new joiners.

New Task Items

Items for next week's agenda

[allthatyazz]

Monday 5/2 Agenda and Notes

Roll Call

Please check in on the Roll Call Spreadsheet

Recurring items: Happens on the PM Monday meeting

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

New Items

• [x] Recap the team's progress in the past week
• [x] Go over the result of participant 2
• [x] Jam on the results from the two studies

Task items from Team meeting to review

Notes from meeting

• 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.
• Discussion:
  • We discussed the iterative nature of Figma Foundations.
• Team Decided:
  • Research team lead, Dongchen would provide a preliminary list of recommendations to the Design team to improve major and minor issues related to the design.
  • The design team would use this document during the UX/UI meeting to discuss areas that needed improvement.
  • There would be no research team meeting on the following Tuesday so everyone would focus on the analysis. The researchers would complete the recommendation document by Friday.

New Task Items

Items for next week's agenda

[allthatyazz]

Monday 5/9 Agenda and Notes

FYI

This is a design review session to decide which design solutions should be included in the 3rd usability test. The 3rd usability test is expected to happen on Friday 5/13.

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

• [x] Designer would present their work to the team following the decisions made at the previous UX/UI meeting https://github.com/hackforla/design-systems/issues/264#issuecomment-1116889044
• [x] Reserahcer would assess each design solution based on their findings from Usability tests
• [x] The team would vote/decide on the design solutions we would like to test on Participant 3.

Notes from meeting

• Progress:
  • Design team presented their latest designs one by one and other team members provided feedback on them .
• Discussion:
  • We discussed what parts of each design we should choose to include for the user testing.
• Team Decided:
  • Research would leave more comments for the designers and the design team would improve the designs based off of the recommendations.

Items for next week's agenda

[allthatyazz]

Monday 5/16 Agenda and Notes

FYI

This is going to be a recorded session because several members would be absent. The 3rd usability test was conducted on Friday 5/13 and the team would discuss the latest stages of the design prior to testing, the test session, and the analysis. Furthermore, The team would welcome new researchers to the team. Cherilyn from Internship Project (p1) might attend this session as well.

Roll Call

Please check in on the Roll Call Spreadsheet

The Agenda

First 15-20 mins

• [x] Welcome Hannah and Leslie to the team.
• [x] Brief introduction to the DS project and our current initiatives + brief intro of team members
• [x] The brief intro by Hannah and Leslie + their progress with our onboarding process

  15 - 25 mins

• [x] Discuss the latest stages of the design on the night before the test and on the morning leading to the test
  • [x] Discuss the change in the naming of Figma Foundations

    The second half of the meeting

• [x] Discuss the 3rd usability test and the insights can be driven from the test

Notes from meeting

• New members introduced themselves. Hannah has Ph.D. in Anthropology and Leslie's Ph.D. is in Sociology. They are both transitioning academicians.
• Progress: Last week, designers had a deadline to complete their designs by Thursday, at 6 PM PST. At 6 PM, Sandra, Kelene, and Yas met for a quality control/check (QC) session to ensure that the latest designs were reflective of the research team's recommendations. They had an extended conversation over multiple zooms calls for the following 3 hours till almost 9 PM PST. The result was a few changes to the structure and copy of the previous design :
  • The instruction section for the cover page has had the most drastic changes to the content and structure. We included a clear list of requirements. And there was an added requirement for "legibility." We combined the content of the former instruction page with Tammy's design for the examples page.
  • The copy of the Start Here page has been simplified.
  • The UI of the example and template pages have been updated.
  • Discussion: Kelene and Sandra explained their observations regarding the P3 test. It seems that P3 has more experience and skills with Figma and usability tests as was apparent from the recording.
  • There was a disagreement/confusion between team members on whether the user had been able to accomplish the task or not. The task for the participant was to create a Cover Page for their HfLA's project according to the requirements stated by Figma Kit. PM stated that just because the participant did not choose a full-bleed image for their cover art, it does not mean the task was unsuccessful. PM believed that the user has chosen a smart way to adjust their project cover page based on the existing content on their team's Figma and the requirements.
  • PM asked Sandra if the new instruction section (as stated above) is better compared to the previous design. Sandra mentioned that a task-based instruction (step 1: Do this as depicted in Picture A, step 2: Do that as depicted in picture B, ... ) with a checklist format might still work better for the users.
  • Kelene has presented her analysis according to a lesson by Debbie Levitt/Larry Marine of Delta CX.
  • Team discussed that working on the user flow might guide the team with better decision making and IA.
  • Team Decided:
  • Each member will bring their suggestions and recommendations regarding the ideal user flow to their team's meeting.

Items for next week's agenda

During the meeting, PM discovered that the zoom link had been in use for this meeting since the previous PM, WAS NOT in fact associated with any of HfLA's Zoom accounts ( according to HfLA's Zoom spreadsheet we were supposed to use Zoom 3 for Mondays meetings).

• [x] Set a new Zoom link for all-hands meetings
• [x] Update the Calendar invites
• [x] Update the GitHub board's zoom links
• [x] Delete the previous Slack reminder
• [ ] Set a new Remider

[allthatyazz]

Monday 5/23 Agenda and Notes

Prework

• [x] Read the last week's meetings notes to refresh your memory
  • [x] https://github.com/hackforla/design-systems/issues/263#issuecomment-1128123537
  • [x] https://github.com/hackforla/design-systems/issues/264#issuecomment-1130699310

Roll Call

Please check in on the Roll Call Spreadsheet

The Agenda

First 5-10 mins

• [x] Recap the team's progress in the previous week
• [x] Update the team about the stakeholder meeting and her feedback

  10 - 30 mins

• [x] Members would present their recent work
  • [x] Sandra
  • [x] Kelene
  • [x] John

    The second half of the meeting

• [x] Other members (non-presenting) would provide feedback on the newest design. The work would be evaluated based on
  • [ ] How well the new design considers the user feedback from P1, P2, and P3 tests
  • [ ] Aesthetics and visual appeal (if the low fidelity wireframes are presented the focus would be on IA, content, and coherency of the user flow)

    Final 5-10 minutes

  • [x] Discuss further actions that can be taken during the team's meetings on Tuesday

Notes from meeting

• Progress regarding the onboarding of recent joiners
  • Hannah completed her onboarding checklist. She described the GitHub issue as "very straightforward and clear".
  • Leslie has completed the majority of the tasks from the onboarding checklist. She is instructed to share her feedback with Kelene or Yas.
  • John completed his onboarding issue as well. Kelene updated the onboarding issue template after John started his. John's feedback can be collected to compare the efficiency of different versions of the onboarding template.
  • Discussion around the latest design iterations by each member
  • John's latest iteration considered the possibility of adding a 30 seconds YouTube video at the start here page so that we can save users' time and energy by visually showing them rather than requiring them to read. Other team members' feedback regarding this idea is presented in the following.
    • Yas: The idea of the video requires more discussions around what we should include in the video.
    • Dongchen: Opening an external link can distract the user. We earlier excluded other external links like the Design Systems' additional resources to reduce the noise and distraction for the users. The same logic shall apply to the YouTube link.
    • Hannah: Including a video can help create buy-in and make foundational knowledge of "why" users need to use Figma Kit. [Hannah's comment opened the doors for more discussions that would be addressed later in the notes.]
  • Sandra presented a hierarchy based on the ideal user flow we discussed last week. Her hierarchical model follows this sequence: 1. DO the task (action) 2. CHECK: result meets requirements (verification) 3. COMPARE: other possibilities (example chart) 4. UNDERSTAND: Read the “why” (reasoning). Other team members' feedback regarding this idea is presented in the following.
    • Tammy: This direction stood out to me and I am excited to see how it moves forward.
    • Leslie: Everything about the use of the templates goes back to who the users are. If their project has already had a very nice cover page, their first step is not copying/pasting the template.
    • Kelene has shown an example of the template that has the requirements written inside the template so the users would not go back and forth between Figma Kit and their own file.
    • Wataru: in real-life scenarios users may find many workarounds to eliminate the hassle of going back and forth. For example, they can copy the whole requirements checklist or the tutorials into their file and once they are done, delete the rest.
  • Kelene presented the task analysis one more time and showed her latest iterations for the pages. Her latest iterations include fewer examples. Kelene also showed the user workflow that a PM of a project would make assign a designer to adopt Figma Kit.
    • Yas : On one hand including the fewer examples makes sense because moving forward with other sections of Figma Kit, for the Start page we only have two examples to show. On the other hand, we cannot rule out the usefulness of the example pages for the users based on the P3 test (For context, P3 decided to skip the example page in its totality). The psychological burden for the user (P3) who had been given a task is different than P1&P2 who were prompted to navigate the Figma Kit as if the moderator was not there.
    • Dongchen: P3 pointed out an imbalance in the designs because they think their task was relatively very easy but at first they thought it should be more complex because they felt they had to read a lot.
  • Addressing Why:
    • Wataru: Our Why has evolved throughout time. At first, we needed buy-in from the projects. Then, the Stakeholder said she required all the teams to comply with our standard. So even if a PM of a project assigns a designer to adopt the Figma Kit, we need to provide the context for the user at least as a "courtesy".
    • Leslie: Also, the stakeholder might not be around to give the instruction to all the PMs or newer PMs so it makes sense if the "Whys" are provided for the users.
  • Team Decided:
  • Research direction for the week:
    • Dongchen we would prioritize "User Journey" over the "Persona" because that generates more useful data for our current workflow (the Figma Kit usability studies).
  • Design direction for the week:
    • Yas: At this point, we have many ideas for the design and we have questions that can be solved once we move into the next section of the Figma kit "Creating a Start page for your project".
    • Wataru: We have some designs that we are undecided about. We would first make some choices between different iterations so at least we would have 1A, 1B, 1C, then we can discuss which is more applicable to the next section.

Items that can be addressed before next week's meeting

There would be no All-hands meeting on Memorial Day. Tasks and assignments would be decided during Tuesday's meetings.

[allthatyazz]

Monday 6/6 Agenda and Notes

Roll Call

Please check in on the Roll Call Spreadsheet

The Agenda

First 10 mins

• [x] Greet new joiners + Housekeeping rules
• [x] Recap the team's progress in the previous week

  10 - 30 mins

• [x] Research team would go over their recent progress + Discussion
  • https://github.com/hackforla/design-systems/issues/431#issuecomment-1154438120

    30-50 mins

• [x] Design team would go over their recent progress + Discussion

  Final 5-10 minutes

  • [x] Each lead would give direction for their team meeting

Notes from meeting

• Research-related notes are reflected here
• Design-related notes: After the review of work from the design team, PM showed some other examples of how other projects create a file menu for the Figma pages on the left-hand navigation bar with the use of emojis, indent, spacing and etc.
  • Leslie brought up a good point that it seems other projects use the HfLA Website team's Figma file as a reference when they want to organize their files. This is an accurate observation as the Stakeholder is acting as the PM of the website team and PMs from other projects are referred to the website team Figma file by Bonnie. The research team has done an interview with the stakeholder in the past that confirms this observation.
  • The above phenomenon creates a competing force for the DS team and our initiatives.

Items that can be addressed before next week's meeting

[allthatyazz]

Monday 6/13 Agenda and Notes

Roll Call

Please check in on the Roll Call Spreadsheet

The Agenda

First 5 mins

• [x] Ctaching up with new joiners on their progerss

  5 - 30 mins

  • [x] Recap the team's progress in the previous week
  • [x] Research team would go over their recent progress + Discussion
  • [x] Design team would go over their recent progress + Discussion

    30-50 mins open floor for discussion

• [x] Discussion and brainstorming

  Final 5-10 minutes

  • [x] Each lead would give direction for their team meeting

Notes from meeting

• Leslie gave a summary of the progress she and Hannah have made on designer synthesis since last week. The current document has the following format: 1) Insights on the major categories ( Onboarding, documentation, mentorship expectation, design systems, design workflows, and .... 2) Individual participant synthesis 3)Takeaways from the major user pain points
  • Leslie asked if there is a recommended format for how to present the findings. PM suggested pain points related to each category can be organized into tables with columns specifying the prevalence of the pain, and seriousness ( how big that pain point is - for example if the pain points prevent the users from accomplishing their tasks or just add an extra headache ), the priority level for our team to address the issues, and the potential solutions/opportunities for improvement.
  • Regarding the specific audience for the report/reports, as of now we have not decided on a firm audience. The team has to contact the relevant projects/teams at HfLA to present the work. For example, insights related to Onboarding might be most useful to the VRMS team and the insights about documentation are most relevant to the Guides team. Materials that are to be presented to Stakeholder is better to be concise Slidedecks.
  • Sandra summarized the design team's progress in the previous week. The design team discussed strategies to improve the workflow and collaboration between designers.
  • Each design or Figma frame can be annotated with the date so others would know what is the latest design.
  • The annotation can enhance further if a couple of sentences are added for each design: What problems the design tries to solve / the relation to the user pain points.
  • In order to increase the consistency between the work of the designers, John has created a design system/style guide for the Figma Kit.
  • The team discussed the preliminary Personas or the low-fi personas, designers created before working on the design of the Figma Kit which used to be called Figma Foundations. Please refer to
    • The team addressed the need to improve the preliminary personas based on the interview data.
    • The team also discussed that concise user stories/ or use cases can help the team include features in the Figma Kit that are more relevant to the users.
    • Although there were earlier doubts and concerns about the usefulness of the personas, designers find Personas to be a very useful tool for guiding them in the design and coming up with solutions.
• Some valuable reminders from team members:
  • Dongchen " we cannot expect the Figma Kit would solve all the user pain points."
  • Sandra "Personas that are based on the real research data are the most valuable".
  • Yas " Figma Kit is only the MVP and we can make it better over time."
  • Wataru " we are doing agile."

Direction for the following team meetings

• Research team can discuss ways that they can improve the low-fi personas or expand them to include PM participants
• Design team must reach a consensus on the MVP of the format for at least the cover page.

FYI

• Dongchen would become less involved for the next two weeks as she has to relocate to a new city and wrap up her teaching assignments.
• Hannah would be in India for the following weeks and she might have less opportunity for attending the meetings due to time zone differences but she would be able to contribute to the research.

[allthatyazz]

Monday 6/27 Agenda and Notes

Roll Call

Please check in on the Roll Call Spreadsheet

The Agenda

First 5 mins

• [x] Catching up with the DSers

  5 - 20mins

  • [x] Recap the team's progress in the previous week
  • [x] Design team would go over their recent progress + Discussion
  • [ ] Discuss items from research team meeting : Team's Priorities and Big Picture vision

    20 - 35 mins

  • [x] Discussing User stories relevant to Figma Kits + Discussion

    35- 45 minutes

  • [ ] Each lead would give direction for their team meeting/ or their team work for the week

    Last 10- 15 mins

• [x] Critical thinking practice : What role can civic tech play in response to recent SCOTUS rulings?

Notes from meeting

Direction for the following team meetings

[allthatyazz]

Monday 7/11 Notes

• We had two designer observers from other HfLA projects who came to our team meeting with the hope to learn more about design systems and design operations.
• We put each designer in a Zoom breakout room so the research team can conduct introductory interviews with them separately. The details can be found here #437 .

[allthatyazz]

Monday 7/18 Agenda and Notes

Roll Call

Please check in on the Roll Call Spreadsheet

The Agenda

First 5 mins

• [x] Catching up with the DSers

  5 - 20mins

  • [ ] Research team's progress
  • [x] Dongchen presents the findings/insights from the designers interviews

    20 - 40 mins

  • [ ] Updating the team on Stakeholder feedback + design team progress
  • [x] Future steps for the Kit
    • [x] Housekeeping Rules from Start here example pages
    • [x] Building A Design System for your project
    • [x] Color systems
    • [x] Typography +Typeface

      40- 45 minutes

  • [x] Each lead would give direction for their team meeting/ or their teamwork for the week

    Last 10- 15 mins and beyond : Working with your team in a breakout room

Notes from meeting

Direction for the following team meetings

[kelenelee]

Aug 1

Attendees @kelenelee @hdchangie @LeslieCi @hannahcarlan @kangina-tech @winoue90

Yas is on vacation. I lead the all-hands tonight and presented the preliminary findings from the product manager interviews. Debbie asked for feedback on the new lighter blue banner, which I approved because it matched the cover art closely.

Hannah raised concerns that the research objectives for the next study don't feel clear. We decided that the next research meeting on the 4th should address this

[kelenelee]

Aug 8

Attendees @hannahcarlan @winoue90 @hdchangie @kelenelee

Short meeting today. We asked Wataru for feedback on the research plan and whether the research will fulfill the design team's needs. He approved of it. The research team was concerned that the research plan as it stands wouldn't be actionable for the design team, but Wataru finds that having designers walk through their file will be very helpful for designers to see what Figma file characteristics work vs don't work. Although the designers have seen other teams' Figma files, they want to hear from the designers themselves to truly understand their point of view, and figure out what organizational systems work, what doesn't, and what they wish could be better.

Wataru also suggested releasing the Kit, V1, once cover page, start here page, file menu page, and housekeeping page are done. V2 with more design system things like color, typography guidelines will be in V2. He will propose this to the design team this week 8/11 and at the next all-hands 8/15 once PM @allthatyazz is back

Dongchen suggested that the research could also investigate the collaborative aspect of understanding / finding out the latest iteration of a given design.

[allthatyazz]

Aug 15

Attendees @hannahcarlan @winoue90 @hdchangie @kelenelee @nasimbiglari

• PM gave the summary of the stakeholder meeting to the team. Then, we discussed the team's progress in the past two weeks.

• We discussed Wataru's suggested plan for releasing the Kit, V1, once the cover page, start here page, the file menu page, and the housekeeping page are done. V2 with more design system things like color, and typography guidelines will be in V2. And the team agreed on this plan.

• PM followed up on the stage of the 3 documents requested by PM during the research meeting on 7/28. https://github.com/hackforla/design-systems/issues/142#issuecomment-1199899264

  • 1 sheet is ready to share with the team.
  • New interviews based on the new research plan are happening.
  • The external report slide deck still needs time. The team expressed dissatisfaction after hearing this document had been shared.
    • We discussed creating housekeeping rules for our sharing practice.
    • PM could give the team a heads-up before sharing. (PM note: I personally prefer this strategy- it is simple and requires minimum effort.)

[allthatyazz]

Aug 29

Attendees @hannahcarlan @winoue90 @hdchangie @kelenelee @rachelita2 @sandraberjan

• We discussed the release plan for V1 of Figma Kit: once the designs are ready and reviewed, we would publish the V1 along with a release note to HfLA #General slack channel and the #UX/UI CoP. The team has the option to ask the stakeholders to push the implementation of V1 but this is not favorable at the moment because we like to see what will happen organically. Also, we can post on each project's slack channel and open the discussion with their PMs and designers. The next stage would be doing the post-launch research with the goal of enhancing the V1.

• We had a discussion about the possibility of changing the name of "Figma Kit". Sandra raised the initial concern that the naming came as a result of a meeting with only 3 people and the name might be confusing for users.

  • Yas " let's not forget that the complete name is HfLA Figma Kit .... and naming like UI Kit or Figma Kit are pretty common among designers and used for the same purposes."
  • Sandra " I think it's the word “Figma" that’s a bit problematic for me since it's a product name for another product so that's what worries me ... ."
  • Hannah "I think that's a really good point, Sandra! HfLA Design Kit would be clearer - happy to spitball names later."

(PM note: The original naming of the product was Figma Foundation. Originally, we were thinking the problematic part is the word Foundation and not Figma. I still think Figma Kit sets more straightforward expectations for users who are designers familiar with similar terms and have seen and used different UI kits. Imagine they would see a link somewhere on a HfLA toolkit page and they would have a much easier time recognizing what the Figma Kit would be about. Design Kit does not have a similar impact. )

• Dongchen gave a presentation on P15. Her presentation is recorded and can be found here.

[kelenelee]

@allthatyazz i'm going ahead and posting these notes I took. please feel free to edit this

Sep 26

Attendees @allthatyazz @kelenelee @rsschacht @sandraberjan @rachelita2 @hdchangie

@hdchangie will be stepping back as of this meeting. in case it has not been documented elsewhere in Github, @hannahcarlan @LeslieCi @tamalatrinh @winoue90 have been hired for other positions as of several weeks ago.

Moved product v1 release from end of Sep to end of October. Cover page min req to be researched more and revisited. @kelenelee to

• present research findings on user behavior and file menu patterns on Thursday
• at some point meet with @sandraberjan and @rsschacht to discuss copy direction
• at some point meet with @rachelita2 to discuss current research synthesis

Team to

• annotate the Kit with their thoughts. (Which page in the file?) Major points of kit to focus on: product name, excess copy
• reach out to senior UXers for advice and brainstorm improved ways of collaboration

[kelenelee]

Oct 3

Attendees @allthatyazz @kelenelee @sandraberjan @rachelita2 @winoue90

I presented a slide deck of insights and recommendations based on 3 1-on-1 interviews I had with designers from different teams, who talked about their Figma file and the way they use it and their self-reported needs.

Oct 17

Attendees @allthatyazz @kelenelee @sandraberjan @rachelita2 @winoue90

A potential new researcher Ayah came to observe this meeting. Yas went over Bonnie’s feedback of our team from their 1-on-1. I presented my recommendations based on two observation sessions I did with two design teams. Sandra presented the copy she worked on this week. We debated the pros and cons of releasing the product in two weeks.

[allthatyazz]

Oct 24

Attendees @allthatyazz @winoue90 @sandraberjan @rachelita2 @kelenelee

Sandra presented the latest design work to the team and Rachel, Wataru and Yas provided some recommendations. Kelene joined at the end of the meeting and worked with Sandra to coordinate meeting times for the following days.

This week, Sandra and Debbie met every day and Kelene participated in some of their sessions and provided consultation based on users' data.

Meeting highlights

• Research recommended that teams should avoid empty pages as a way to create breaks in their Figma pages menu (AKA file menu). Although discussed in early design meetings, Wataru reaffirmed that "the line/"wasted” pages are pretty common practice in the industry. Plus unless the team has 100+ pages and running out, the only other page issue would be having 3 pages. In that case, that's an issue beyond design systems." Also, Figma recommended the use of emojis and line/wasted pages as best practices.
• Content made the decision to relocate the yellow "caution" box from the footer to become a banner. The team had no objection to Sandra's justifications for this decision.
• The requirement for the size of the cover page has changed to "larger than 1200 x 800". The template we provided follows Figma's recommended size of 1600 x 960.

Direction for this week and the next one

Official HfLA operation will be closed for the month of December. That means no general onboarding and no stakeholder meetings. Monday 11/7 is the deadline to present work to Bonnie for her final approval before publishing the HfLA Figma Kit V1 to the CoP. This is the only way we can get something out of the door before the end of the year and save the DS project from getting dismantled.

• The ideal timeline to meet the stakeholder's 11/7 deadline is to finish all design work on Monday 10/31 so we could have spent the week on the fine details, release notes, and working with the research on the areas we want/need users' feedback.
• The more realistic timeline based on our internal workflow would be
  • Thursday 10/27 will be the deadline for the Cover page, Cover example, and Pages sidebar panel (File menu).
  • Monday 10/31 will be the deadline for the File menu example.
  • Monday to Thursday (11/3), we have to fix the Start here ( and the housekeeping section if we can)and do the final touchups on the previous pages.
  • If we cannot fix the housekeeping up to standards that satisfy Content and Research, those sections would be left out of the first release.

[allthatyazz]

Oct 31

Attendees @allthatyazz a new joiner Nirae.
This meeting happened on Halloween so the regular team members could not attend the meeting. PM met with the new joiner and explained the project and the different things we did for the full hour.

Nov 7

Attendees @allthatyazz @sandraberjan @rachelita2 @winoue90 @edela0015

• The team received the stakeholder's approval to release Figma Kit v1.0 .
• The following Wednesday (11/9) was the release day for the CoP. We talked about the tasks we needed to complete prior to the release of V1. https://github.com/hackforla/design-systems/issues/445
• HfLA has a winter break for the full month of December.
• The roadmap for 2023 will be
  • Post-launch user research and fixing the issues with v1.0
  • New content for the Figma kit (new sections for design systems: typography, color, etc. ..)
  • Working on an internal design system for the DS team. We don't have a system for spacing, components, and ...

[allthatyazz]

For the last three meetings of 2022, we experimented with a new agenda format in FigJam. The notes below are directly from FigJam agenda and for documentation purposes, PM added the status for the action items.

11/14

Attendees: Yas, Rachel, Sandra, Khanh (New joiner)

Meeting Summary
PM, research lead, and content lead put down stickies first and we prioritized them and discussed the next steps. Action Items for next steps

• [x] Onboarding new members for the start of next year (By the end of Jan 2023, the team grew to a decent size as a result of open role posts on the UX-UI CoP job board.)
• [x] Sorting the housekeeping section of the Kit (As of 2/2023 still WIP)
• [x] Yas to attend PM meetings and advertise the kit (PM attended 11/18 PM CoP's)
• [x] Yas to contact the Website team to update the DS page (The issue https://github.com/hackforla/website/issues/3731#issue-1455782888 submitted to the Website team on 11/18 and as of 2/2023 still a WIP)
• [x] Rachel to work on the post-launch research during the break (As of 2/2023 WIP #476)
• [ ] Sandra to work on the mission/vision statement for the team + the wiki rewrite during the break ( As of 2/2023, we still have to expand the content team to both support the UX designers and improve the Wiki.)

11/21

Attendees: Yas, Rachel, Khanh, Faezeh (New Joiner) Meeting Summary Rachel, Faezeh, Khanh, and Yas talked about the potential path for the research in 2023. We did a walkthrough of Google Drive and different studies.

• Yas attended the PM CoP meeting on Friday 11/18 to advertise the kit to other PMs and she & Bonnie discussed the possibility to plan a workshop for UX/UI CoP to introduce and then conduct interviews with designers in the breakout rooms. This plan entails training other UXRs across all HfLA to help us conduct interviews with attendees in the breakout rooms. The DS team researchers not only would work on the research plan and scripts for the user tests, but also they will have an opportunity to put together a training protocol for other UXRs who are not members of the DS team. The format can be similar to what the Internship project has done here.. (In January 2023, the team leads and the PM decided not to explore this option.) Action Items for next steps
• [x] Faezeh will start the onboarding process and review the previous research. (Completed)
• [x] Yas will upload the missing recordings. (Completed)
• [x] Khanh would like to help the researchers to come up with questions. (Completed #463)

11/28

Attendees: Yas, Wataru, Rachel, Sandra, Khanh, Faezeh Meeting Summary and notes This was the last meeting of the year. Khanh presented a re-imagined version of Figma Kit. The team praised the hard work and discussed the possible next steps for the year 2023.

• Based on Khanh's redesign, the team has to distinguish between the Fix and the Hypothesis.
  • The Kit Start page, the fixes in the texts (e.g better wording and typos), and changes in the font sizes and visual elements can be categorized as fixes.
  • Changes in the overall layout ( e.g Template first vs Standard first vs. Tutorials first) are hypotheses.
• A/B testing or other preference testing is not applicable when two designs have fundamental differences.
• What researchers should research the released version or the new designs that designers are working on? We test what we have released officially. We would treat the redesign efforts as our bank of ideas to pull from after we get the results back from user tests. Other notes from FigJam
• "Have a clear list of pages as suggested by research team as we currently are only ended at housekeeping and don’t really know what the next pages are." Response provided by PM : "Our roadmap for 2023 is to work on DS sections of the Kit. The previous team identified the following sections and I think we can stick to this for the roadmap: Color, Typography, Grids and Spacing, Radius and shading, Icons, Component libraries. We do have a starter template for these. Please refer to Design System file in the project."