EA: Open Sync Meeting Agenda

[SamHyler]

Overview

This issue tracks the running agenda for the Content x Design x UXR team weekly meetings (Fridays 9:30AM PST)

Reply in the comment using this format to create weekly agenda.

Format

# [YEAR-MO-DAY] Agenda and Notes
### Attendees
- [ ]

### Facilitator 
- [ ] Sylvia

### Notetaker
- [ ] 

### FYI:
- [ ] 

### Recurring items: 
- [ ] Content updates
- [ ] Design updates
- [ ] UXR updates
- [ ] PM updates 

### New meeting items:
- [ ]


### Notes from meeting:
- [ ] 

### Task items:
- [ ] 

### Items for next week's agenda:
- [ ]

[anitadesigns]

Overview

This issue tracks the running agenda for the Content and Design team weekly sync meetings (Fridays 9:30 AM PST)

Reply in the comment using this format to create weekly agenda.

###Format

[July 22, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Anita
• [ ] Serena

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Irene
  • [ ] Serena
  • [ ] Anita

Recurring items:

• [ ] Sitemap updates
• [ ] Content Guidelines updates
• [ ] Figma Re-organization

New Meeting Items

• [ ] Review changes for Landing Page and receive feedback from Content Design
• [ ] Review changes for Letter Generator pages and receive feedback from Content Design

FYI

• [ ] n/a

Notes from Meeting

• [ ] Content Guidelines: Serena and Anita have ideas to include visuals and include different designs to make the information easier to scan and read - [ ] Google doc for Guidelines
• [ ] Go over Sitemap - [ ] Agreed that a content inventory would not be needed and having a derailed sitemap fits our needs and goals - [ ] Using one frame/board to include the content for all pages - [ ] Anita will update the content portion for the landing page - [ ] Sam is working on the letter generator portions and fitting a new page - [ ] New page: an overview of the questions on the form - [ ] Aiming to have it completed for review next week
• [ ] Review changes and receive feedback from Content - [ ] Landing Page - [ ] Serena and Anita built the flow of the landing page based on user needs/pain points from Pilot Usability testing -[ ] Needs/pain points: - [ ]Privacy - [ ] Understanding of expungement process and tool/how to use tool - [ ] Re-organizing sections - [ ] Anita and Serena will re-organize sections for next week’s review - [ ] Discussed having a section on the Figma page next to the wireframes that would have the copy approved by Content so that Design can use - [ ] Working on improving copy with each iteration + usability testing - [ ] Discussion on making information more visual and giving users a visual overview of what the tool consists of - [ ] Using a gif or including a video on how to use - [ ] Using a step-by-step overview of how the letter generator fits within the expungement process but would need to verify information with Research - [ ] Code for America’s Clear My Record is a great reference that we could hyperlink some pages that would point users to the next steps after they write their letter - [ ] Last pages of Letter Generator - [ ] Between the final preview page and download page, there was not a lot of content to have on two different pages, so we decided to combine those pages in one. - [ ] Wireframes for this merge can be found under the Desktop page on Figma. - [ ] Anita will place a note on the wireframe that Irene and Sam can make content edits on - [ ] Internal Usability testing shared that some users wanted to edit their letter on the final preview, but Dev shared that changes on the final preview page would not sync to previous pages if users were to go back to those pages - [ ] Solution: include a section (either before letter preview or after) that shares that if they would like to make edits, they would have to copy text or download the letter into a word doc and make those changes. OR go back to the page that would allow edits - [ ] Need copy for this from Content - [ ] Revisiting this next week to discuss where to place copy based on content flow
• [ ] Figma Re-organization - [ ] Anita worked on some ideas which can be referenced here - [ ] If anyone has any ideas, feel free to bring them too!
• [ ] Discussion on meetings - [ ] Aim to meet every Friday at 9:30 am PST - [ ] Anita will ask Irene is this is feasible. If so, will ask Jaime to set up zoom links for us

Task Items

• [ ] Design - [ ] Re-arrange content on Landing page - [ ] Update About Us page wireframe - [ ] Anita will ask Irene about meeting time and ask Jamie if they could set up a zoom link for us - [ ] update Dev about new changes to the about page and create a new page in the Letter generator - [ ] Create a new wireframe for the new Letter Generator page that gives overview of questions - [ ] Anita will readjust landing page content to make more room for content on other pages - [ ] Improve design on Content Guidelines on Figma - [ ] continue working on sitemap
• [ ] Content - [ ] Continue working on the sitemap and add the content components for other pages onto the frame - [ ] Review and improve the copy on landing page - [ ] Add copy for the section on keeping information safe - [ ] Choose 3 questions from FAQ to include in the FAQ section on the landing page - [ ] Create copy for the section that shares either a disclaimer that users cannot edit on the final preview page or how they can further edit their letter ( going back to edit pages or downloading letter into word doc or copying text)

Items for next week's agenda

• [ ] Review sitemap
• [ ] Go over the copy on the landing page and letter generator
• [ ] Figma re-organzation
• [ ] content guidelines update

[anitadesigns]

[July 29 2022] Agenda and Notes

Attendees

• [ ] Serena
• [ ] Sam
• [ ] Anita

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Irene
  • [ ] Serena
  • [ ] Anita

Recurring items:

• [ ]

New Meeting Items

• [ ] Review Sitemap
• [ ] Review Landing Page
• [ ] Present About Us page
• [ ] Review Letter Generator pages
• [ ] Figma re-organization
• [ ] Content Guidelines update

FYI

• [ ] We will meet weekly or bi-weekly on Fridays based on tasks
• [ ] Content shared they are shifting their tasks to focus on copy Design needs for the next iteration and then going to re-focus on tasks they need to complete that require collaboration with Design and Dev

Notes from Meeting

• [ ] Sitemap - [ ] almost complete. just need to finish legend, add comment, and review - [ ] About Us portion will change as we continue to work on it - [ ] Placement of Overview of questions on the form---where should it be placed? Currently, it will be placed between the "before you begin page" and the "advice" page. Could change based on content flow and dev recommendations
• [ ] Overview of questions - [ ] Serena presented wireframes she has for page - [ ] Sam pointed out that some of the design for LG pages would need to be updated since the current website, desktop wireframes, and mobile wireframes differ from each other
• [ ] Landing Page - [ ] Landing page needs copy to be updated - [ ] Content will be working on it next week---FAQ portion - [ ] there is a wireframe on Landing Page (June 1 2022) for content to work on
• [ ] About Us Page - [ ] There are content/copy overlaps on page - [ ] Content can work on the content of the page after working on the landing page and Letter Generator - [ ] About Us page is on Desktop page on Figma -- there are two wireframes with different content but the content will be adjusted. The design structure could remain the same
• [ ] Letter Generator Page - [ ] Anita will make a new wireframe and space under the Desktop page for content to work on copy for this page - [ ] Content will try to work on it next week
• [ ] Figma Re-organization - [ ] Anita has been brainstorming different approaches to our re-organization and researching how others organize their team's Figma workspace - [ ] Want to have a space that indicates the source of truth, a space for Content and Design to work on, a space to indicate to Dev (and research) what final designs are with comments - [ ] Sam shared that Design Systems are working on a guide for how all teams in HFLA should organize their Figma spaces and it would be best to reach out to implement those changes - [ ] We have been leaning toward to Idea 3a and Idea 3b on figma page Anita has been working on - [ ] May take out "Wireframes" section since it overlaps with "Working" section - [ ] We agreed to separate the pages and we would update the master pages with current designs

Task Items

• [x] Anita will add a legend and comment section on Sitemap
• [ ] Content + Design to review sitemap
• [ ] Content- work on copy for landing page and last page on letter generator
• [ ] Content- work on content on About Us page
• [x] Design will talk to Dev and ask about past handoffs and what designs they based the web dev on (including grid size )
• [x] Anita will make a new wireframe and space under the Desktop page for content to work on copy for LG page
• [x] Anita will reach out to Design Systems team re: Figma organization

Items for next week's agenda

• Figma re-organization
• [ ] Updates on copy for pages
• [ ] Updates from Design

[anitadesigns]

[August 5, 2022] Agenda and Notes

Attendees

• [ ] Serena
• [ ] Irene
• [ ] Anita
• [ ] Sam

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Irene
  • [ ] Serena
  • [ ] Anita

Recurring items:

• [ ] Sitemap update- done
• [ ] Landing page update
• [ ] Letter Generator pages - [ ] Question Overview - [ ] Final letter preview + Download - [ ] Updating buttons on pop-up pages (desktop and mobile)
• [ ] About Us page update
• [ ] Figma re-organization
• [ ] Advice page visual collab
• [ ] Quick Q: add pop-up buttons in Design system?

New Meeting Items

• [ ] LG: Advice page

FYI

• [ ] No meeting next week?

Notes from Meeting

• [ ] Sitemap - Reviewed the Sitemap but noticed that we need to update the LG pages to reflect the merge of the last two pages - Keeping the sitemap issue on GitHub open for changes
• [ ] Letter Generator Pages - Will the LG progress bar have the steps presented? All progress bars will have the name of the step and are in the design system (desktop + mobile) - There will be another wireframe reflecting when download buttons are activated - Sam made a Github issue to update buttons on LG pop up buttons. Also to update the pop up card on design system to say "let's continue" - Flow of last page --- perhaps have a pop-up that shares that exiting the page would delete letter. --- discussion on page vs pop- up. We would need to make pop up bold and different than the others.
• [ ] Advice page visual collab - Sam updated content to target pain points from UT. Design to add icons and include visual elements to make it easier to consume--- x or circle with slash between. Design on mobile will differ in terms of layout- stack "do" and "don't" information with visuals instead of having it in one line (mobile)
• [ ] Landing page - Content assessed their tasks and will probably finish before schedule and work on copy on LP before next UT - Demo ideas: PPT of screenshots of LG , use figma prototype to show how it works, video, screen record prototype or website. We would need to create something that is feasible within our skill set and time. - Illustrations: where were they pulled from? Perhaps HfLA has a repository since many have the same artistic style.
• [ ] Figma re-organization
  • Anita created a mock up of Figma organization --- spaces for dev,content, and WIP. Could move pages around as we hand off
  • Better to keep WIP and keep pages there instead of moving to save design progress and assist folks new to team what is current
  • Pages will have a section in each page sharing the most up to date frame---include date
  • Archive: have pages names with the name of page and date of launch/push --- that page would have all works/iterations that were worked on during that launch/push
  • Next meeting we will re-organize figma together

Task Items

• [x] Anita will update sitemap with LG page merge
• [ ] Anita- create wireframe with activated buttons (LG pages)
• [ ] Design to work on mock ups of pop up and page that alarms users of losing their letter that was generated.
• [ ] Design- work on advice page
• [x] Serena is moving the wireframes + comments to Desktop page on Figma
• [ ] Content will be writing copy for users instead of Partners
• [x] Ask Jamie whether Hack for LA has a database or repository of illustrations for us to use/update on the website

Items for next weeks agenda

• [ ] Figma re-organization

[anitadesigns]

[August 19, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Serena
• [ ] Jamie
• [ ] David

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Irene
  • [ ] Serena
  • [ ] Anita
  • [ ] David

Recurring items:

• [ ] Update EA Team's Figma page to reflect mockup
• [ ] Content Updates
• [ ] Design Updates

New Meeting Items

• [ ] Unemployment sequence in LG
• [ ] Onboarding flow
• [ ] Discussion about Landing page and About page content and how to present it between the two

FYI

• [ ] Made updates to the main Figma page organization.

Notes from Meeting

• [ ] Overlapping content for "Partner with us" on the LP and about page
• [ ] Where to place content about timeline and information supporting legitimacy (connection with Code for America etc)
• [ ] Focus on the immediate users, what would be important information for them to have
• [ ] Involvement categories on the LG need to be updated to allow more flexibility and new category for unemployment
• [ ] Questions on the LG for Parenting questions should have the option to have more than one child, and a child younger than 1 years old

Task Items

• [ ] Content to finalize LP and About Us content
• [ ] Content confirm with Design what the new / updated involvement categories for the LG
• [ ] Content to update copy for Before You Begin page

Items for next weeks agenda

• [ ] Onboarding flow
• [ ] Review About Us page
• [ ] Unemployment / Children LG questions

[anitadesigns]

[August 26, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Serena
• [ ] David
• [ ] Jamie
• [ ] Anita

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Irene
  • [ ] Serena
  • [ ] Anita
  • [ ] David

Recurring items:

• [ ] Updates from Content
  • [ ] Landing page
  • [ ] About Us page
  • [ ] Before you begin page ( no updates )
• [ ] Updates from Design
  • [ ] Planning to gather and select illustrations by next week

New Meeting Items

• [ ] User journey map
  • [ ] https://github.com/hackforla/expunge-assist/issues/616#issue-1315308193
• [ ] overview of Desktop wireframe process/update for "Master" page
• [ ] Review About Us page
• [ ] onboarding flow
• [ ] LG in entirety (Content) https://github.com/hackforla/expunge-assist/issues/597 which parts can we tackle now and not? Includes point below (Sam can present)
• [ ] Unemployment/ Children LG questions

FYI

• [ ]

Notes from Meeting

• Last page of letter generator's copy is complete. Anita will update icon and review spacing-- sending copy and design changes in one issue
• With so many Content and Design changes happening, how should Design and Content send changes to Dev? should we send changes together or separately?
  • Dev shared they like issues broken up but also easier to bundle changes.
  • Could create umbrella issue that is placed in ice box and break up the issue into separate issues and link to umbrella issue with dependency --- umbrella issue may be forgotten if put in Ice Box
  • Will ask Dev on preference --- Make issue for LG with copy and content changes and ask Dev for Feedback
• About Us page
  • About Us at the top to tie in content
  • About us page having similar content to LP but go more in depth
  • Timeline: shares the history of hack for la, EA and CFA to show legitimacy
    • is there a pain point that this may help solve from UT?
    • Have a visual layout with statistics/ number that could tie this together and show legitimacy --- CFA has data on website
  • What is a declaration letter generator? section
    • moving this to LP and creating a visual that may break up the text of this section
    • Best to keep content on About Us page focused more on hack for la, efforts, and success
• Landing page
  • Content will look at 3rd question next week --- the answer to that question just has filler
  • rest of the copy is final
  • Design will make updates and is looking at illustrations to add
• UX worked on Figjam flow and google doc on the expungement process
  • more research may need to be done. Pushback visual on LP for next launch --- MVP: Add a question on FAQ that would address how the letter fits in process or why it matters
• Parenting flow on LG
  • is it feasible to add something to give users flexibility in adding number of children and information to add to letter
  • Design can make a lo-fi wireframe to present to Dev to get feedback
• Updating Desktop wireframes on Figma
  • Anita worked on a few flows.
  • overview of emoji documentation
  • Skip parenting flow for now since we will be working on a new design/ flow for questions. will add those wireframes when done
  • Content will review desktop wireframes when design is done updating

Task Items

• [ ] Update icon on LG page and review spacing. Send copy and design changes to Dev (Anita)
• [ ] Make issue for LG with copy and content changes (Anita) and ask Dev for Feedback (Design)
• [ ] Design
  • [ ] Update About Us page
    • [ ] choose illustrations
    • [ ] Add FAQ button to LP
    • [ ] Move section (what is declaration letter) from About us to lp
• [ ] Content
  • [ ] updating 3rd ? on LP FAQ section
  • [ ] Creating bullet points for About Us section on statistics (reference CFA website)
  • [ ] add a question on FAQ ( "Why does the deceleration letter matter to me/ expungement process/ in getting my record cleared?")

Items for next weeks agenda

• [ ] unemployment/children LG Questions
• [ ] About Us page updates (Design and Content)
• [ ] Parenting flow --- Design present wireframes
• [ ] onboarding flow

[anitadesigns]

[September 2, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Serena
• [ ] David
• [ ] Anita

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Serena
  • [ ] Anita
  • [ ] David

Recurring items:

• [ ] Updates
  • [ ] Content
  • [ ] Design

New Meeting Items

• [ ] unemployment/children LG Questions
• [ ] About Us page updates (Design and Content)
• [ ] Parenting flow --- Design present wireframes
• [ ] onboarding flow
• [ ] List privacy policy in FAQ https://github.com/hackforla/expunge-assist/issues/658 (discussion)

FYI

• [ ] Jamie is returning after Labor day weekend
• [ ] New page on Figma for Design/Content hand-offs
• [ ] No meeting next week due to planning meeting
• [ ] Sam is the solo content writer on the team from this week

Notes from Meeting

• [ ] Design shared MOsCoW bucket and re-alignment of task priorities
• [ ] Parenting flow--- Serena shared different mock ups ---we agreed with 3rd option
• [ ] Separating last question in the parenting flow to have its own page/card
• [ ] Design will present to Dev for feasibility
• [ ] David shared design showing relationship of EA/HfLA/CFA
• [ ] Reviewed previous About Us page design and agreed to carry over designs and copy that align with goals
• [ ] LP--- agreed to have an MVP for Demo. Content can adjust text once Design has a layout
• [ ] Asking Jaime about Privacy Policy in FAQ page since link to Privacy Policy is in footer
• [ ] New Figma page for Dev hand-off ---- include wireframe for copy and design changes so that Dev can reference

Task Items

• [ ] Ask Jamie about Privacy Policy
• [ ] Design--- show Dev Parenting flow

Items for next weeks agenda

• [ ]

[anitadesigns]

[September 16, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Serena
• [ ] Anita
• [ ] David
• [ ] Kyle
• [ ] Jamie

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Kyle

Recurring items:

• [ ] Updates
  • [ ] Content
  • [ ] Design

New Meeting Items

• [ ] Finishing up Parenting Flow - update
• [ ] Finishing up About Us page - any new/remaining content needs
• [ ] Finishing up Landing page - any new/remaining content needs with new iterations?
• [ ] LG - new proposed flows from Content - what’s needed and what’s feasible?
• [ ] LG - Auto-generated text fixes, Design input needed on variable sentences, possibility to create multiple options depending on what’s clicked (also have asked Dev). Problems: 1. repetitive letters/judge gets same exact letter 1000 times: how to fix - variable sentences? 2. Transitions to make paragraphs flow together. 3. etc. (unfinished iteration)
• [ ] Naming categories: Need some input from everyone about what to call “Recovery” (I’m stuck)
• [ ] Advice page update
• [ ] Milestone updates and alignment for remaining work for IUT2 release

FYI

• [ ]

Notes from Meeting

• [ ] Introductions
• [ ] Jamie presented milestone updates: We can now filter our issues based on milestones. We are on W2 working on IUT2 milestones. For issues we would like to push for the next release, we can label them under W3. There is also an option for a time way later in the future. This helps us visualize and plan ideas and solutions.
• [ ] Parenting flow: Serena worked on Dev feedback and will later show Content to review copy for grammar
• [ ] About Us page--- working on next week
• [ ] Landing page --- Sam will take a look at it next week and Design will continue synthesizing ideas. We can borrow designs from the iterations to convey the information we may need. Having the animation would be great. Need to ask dev if feasible
• [ ] Recovery--- Sam is having trouble on what to call this category. Figma has her notes on different options she has already come up with but would like more feedback and help from Design. We can talk more about it through Slack
• [ ] Adding categories: How many categories should we add? Which ones should we prioritize? Is it feasible for Dev? We will ask dev if we can add more flows and categories. We would continue with the parenting flow and hold off on caretaking. We would rather much like to have an other option to fulfill other experiences users may have (i.e. loans, starting a business, buying a home etc). If possible, we can add one more besides others about small business, buying a home, or loans.

Task Items

• [ ] Begin assigning Milestones to future issues created on Github
• [ ] Discuss "recovery" options on Slack
• [ ] Talk to Dev about adding category/flow and if it is feasible

Items for next weeks agenda

• [ ]

[anitadesigns]

[September 23, 2022] Agenda and Notes

Attendees

• [ ] Jamie
• [ ] Serena
• [ ] Anita
• [ ] David
• [ ] Kyle
• [ ] Phuong

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phuong

Recurring items:

• [ ] Content Updates
• [ ] Design Updates

New Meeting Items

• [ ] Questions from Content
  • [ ] Clarification on Issue 657 (new FAQ question)
  • [ ] Brainstorm on Before you begin copy
  • [ ] Question about onboarding section (Before you begin + Advice)
  • [ ] Spell check
• [ ] Q&A

FYI

• [ ] Sam will be out this weekend and will return on Monday
• [ ] Phu joined our team as a UX Designer! 🎉

Notes from Meeting

• [ ] FAQ Question: @kyle-whitaker shared that the question that we drafted to include in the FAQ page was already included in the current FAQ. He then changed the question to make it more specific to how the declaration letter fits within the whole expungement process. He did some research and created a general answer and one that is more detailed. He wanted our feedback on whether he is in the right direction and if we want to add this in W2.
  • [ ] We decided to have this issue be pushed for the next iteration to give more time to research the answer. Anita will also take a look more in-depth at the responses created and give feedback
  • [ ] Design also decided that this page will not have an accordion design until the next push.
  • [ ] Before you begin: Kyle asked what Design was planning for this page and if there was a conversation on having a new onboarding process. Anita shared that it was briefly mentioned but we had decided to revisit this idea for the next push.
  • [ ] Spell check: Kyle asked if we have explored the idea of having a spell check feature on the letter generator. A great idea that we would have to ask Dev about in W3
  • [ ] No updates from Design -- communicating through Figma with Sam
  • [ ] Phu asked for clarification on the short input field for mobile. Anita clarified what we needed help with but the Design team decided to keep the width of the mobile text input field the same for usability.

Task Items

• [ ] Anita - look at answers to the FAQ question Kyle created and provide feedback
• [ ] Design will ask Dev on Monday if an accordion is possible for LP
• [ ] David will prepare a prototype of how the accordion will respond

Items for next weeks agenda

• [ ]

[anitadesigns]

[September 30, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Kyle
• [ ] Serena
• [ ] Anita
• [ ] David
• [ ] Jamie

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu

Recurring items:

• [ ] Content Updates
• [ ] Design Updates

New Meeting Items

• [x] Parenting Flow
• [x] Something else flows- 2nd question also requires a flexible response option (months/years) how to proceed?
• [x] Landing Page: update and copy needed
• [x] Advice Page -- updates and ready for handoff?
• [x] Update on About Us page
• [x] Improving collaboration and workspace on Figma so that copy and designs do not get lost
• [ ] Prioritizing issues for Dev to communicate which issues are critical to have for IUT2
• [x] Removing the word "involvement"
• [x] Naming "Jenny" - ideas on diverse/gender neutral name

FYI

• [ ] Serena and Anita are the Design team's new Co-leads!
• [ ] No Design + Content Sync meeting next week

Notes from Meeting

• [ ] Parenting Flow: Serena showed Content the different options she came up with for this flow based on the previous discussion. She had one that incorporated radio buttons for the age question (but would be optional) and then another option that changed the questions to be more general. If we choose to have the age question to be optional, we have to consider how the text would be generated. We also have to ask Dev how this would look like with an "optional" question.
• [ ] Adding more detail to "Add" feature..."Add child" instead of "Add" so the instructions are clear. Content and Design agreed to this
• [ ] Something else flow: Anita created the wireframes for the Something else flow but noticed that we run into the same problem as the parenting flow regarding time. Content decided to delete the second question. Kyle is working on smoothing out the copy
• [ ] Question/Discussion regarding the Progress bar title. Each categories page has "Involvement: [category name] for the progress bar. Sam asked if having "Involvement" was for internal use or if was it also for users. We noticed that the progress does not move at all for these categories page and having the word "Involvement" in front of the category indicates that the user is still under the "Involvement" section and that is the reason the progress bar has not changed. If we remove the word "Involvement", it is feasible for Design to increase the length of the solid progress bar slightly to show progress for each section. We then wondered if this would be dependent on what choices they make. David shared that it would still be possible and it does not matter what and how many categories they select. We can still design a progress bar that reflects progress. We would have to collaborate with Dev on this for W3. We can also flag this for UXR to research for the next testing
• [ ] Advice page: The design is done. Anita tried to fix the font size based on Dev's feedback. They shared that the font sizes between mobile and desktop were drastically different. Will keep it for now. Asked if Content is updated for handoff? Not yet, Content is working on "Miss Jenny"...having "Miss Jenny" infantilizes the users...Content asked for feedback from design. They are seeking gender neutral and racial-inclusive name...We decided to remove "Miss" and are going to seek another name
• [ ] Improving collaboration and workflow on Figma so that copy and design do not get lost. we brainstormed different ideas. Sam will archive the Sandbox page. We want to incorporate icons that would move around wireframes to signify which wireframe has the most updated copy or design. A different icon for Content and Design to communicate this. Both content and design will work in the same space but use headers. For the next push, we can have a Figma page for each WIP and then archive it into one page at the end of the phase. We will need to remember to update designs and copy in both mobile and desktop Master copies
• [ ] Prioritizing issues for dEV: Can Content and Design work on this with Dev during the planning meeting? It would be best for us to prioritize issues before the meeting so that Dev could assess and plan for Friday's meeting ...Since we are not meeting next week, we can work on this asynchronously. Anita can create a Figjam board and we work from there and handoff to Dev. If needed, we can schedule a meeting where Design and Content leads meet to do this before Friday

Task Items

• [ ] Serena is going to ask Dev about "optional" question about age in the parenting flow
• [ ] Serena will change add feature copy to "Add child"
• [ ] Anita will make an issue so that the team revisits the discussion and improvement on the progress bar.
• [ ] Design and Content will add whether the progress bar is clear once users are directed to the category flows
• [x] Content is going to research and find gender natural and racial inclusive name for the Advice page
• [x] Sam will archive sandbox and bring over copy from mobile to the letter generator page
• [ ] Anita will create Figjam board with issues we have

Items for next week's agenda

[anitadesigns]

[October 14, 2022] Agenda and Notes

Attendees

• [ ] Serena
• [ ] Jamie
• [ ] Anita
• [ ] David
• [ ] Kyle
• [ ] Sam

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu

Recurring items:

• [ ] Content Updates
• [ ] Design Updates
  • [ ] Parenting flow

New Meeting Items

• [x] Re-visiting the Figjam Prioritization board we did for Dev (trying to complete the Must do tasks first)
• [x] Finalizing any collab items (parenting flow and others) to finish and close issues. What's left?
• [x] Finalizing the hand over Github issues for dev (those still labeled "Draft")
• [x] Improving workflow/process when collaborating on Figma and Github issues
  • [ ] Would including details in the issues help?
• [x] Cleaning up/organizing the "Design Handoff" Figma page
  • [ ] Discussion with Daniel on this
• [x] moving over designs into Master pages on Figma

FYI

• [ ]

Notes from Meeting

• [ ] Going through Figma Prioritization board to focus on completing issues for this week based on the prioritization
• [ ] LP: Anita and David are working on this. We just need illustrations for this and to adjust the spacing. Then we can hand over to Dev
• [ ] Want to focus on updating the Unemployment, Employment, and Self-Improvement flow for this weekend
• [ ] Parenting flow: Serena showed two different options. The conversation about grammar for the generated text that gets inputted. Perhaps we can ask Dev about this? Continuing to go with the "add child" option with drop-down
• [ ] Content is waiting for the parenting page to officially finalize the automated generated text appearing in the "preview and edit" pages for each flow.
• [ ] Phu is working on the FAQ page. Will tag Content once completed to give it one more look for approval and then will work together to
• [ ] Improving collaboration/ communication on Figma: For future issues that include collaboration we will begin to include points on the GitHub issue regarding receiving approval from Design/Content, Coordinating moving wireframes to the Design handoff page on Figma, and updating the "Draft" Github issue . We will also include a point to ensure that wireframes are updated in the Master Figma pages
• [ ] Anita went ahead and deleted the wireframes that Dev completed on the Design hand off page on Figma. We should keep an eye out on when issues are closed as done so that we deleted the wireframes from there and move them over to the master page.
• [ ] We are still in the process of cleaning up and moving over wireframes to the master page. Content would like to review the copy to make sure the copy is updated. For now, continue on the WIP Desktop pages. The design will leave a checkmark emoji for the ones that are updated so that Content can begin to look over the copy. Content will then leave a star for the ones that are ready to move on over to the Master pages

Task Items

• [ ] Anita: create a separate issue to do a sweeping copy change for the preview page on each flow---" Preview and edit"
• [ ] For future issues that include collaboration we will begin to include points on the GitHub issue regarding receiving approval from Design/Content, Coordinating moving wireframes to the Design handoff page on Figma, and updating the "Draft" Github issue . We will also include a point to ensure that wireframes are updated in the Master Figma pages

Items for next weeks agenda

• [ ]

[anitadesigns]

[October 21, 2022] Agenda and Notes

Attendees

• [ ] Serena
• [ ] Jamie
• [ ] Anita
• [ ] Sam
• [ ] Kyle

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu

Recurring items:

• [ ] Content Updates
• [ ] Design Updates

New Meeting Items

• [ ] Updates/Finalizing any hand-offs to Dev
• [ ] About Us page
• [ ] Planning/working on the slide deck to hand over to UXR https://github.com/hackforla/expunge-assist/issues/719

FYI

• [ ]

Notes from Meeting

• [ ] Employment, Unemployment, Something else, Self-improvement flow are ready to be taken off draft and handed over to Dev
• [ ] LP- copy is done and Anita and David are working on finalizing
• [ ] Parenting flow: going with the general wireframe that will protect privacy. Dev shared that they could work with the grammar when users share having more than 1 child. Serena is going to create a GitHub issue for Dev and prepare wireframes for Handoff
• [ ] Autogenerated text: The LG page on Figma has all the preview pages with the autogenerated text. We need to create a hand-off section on the Design hand off the page and update the Draft GitHub issue. The line with the star is the final copy for this issue that Content has worked on
• [ ] We want to prioritize the LG pages to test them for IUT2. We will let Dev know they are the highest priority. We would want to have these completed because it may not be fully possible or flexible if these are not implemented and we conduct the interviews using a prototype
• [ ] Prototype: There was a discussion on Design working on a prototype in case Dev cannot finish implementing the new updates. It would be possible, but we would need to know what questions would be asked from UXR because users would not be able to type on the prototype. Everything would be pre-filled and they can only interact with the buttons and pages. We want to prioritize the LG pages so that we would not be limited to a prototype.
• [ ] How did UXR conduct the interviews for IUT1 and has there been any discussion for IUT2? UXR is building off on the Research script and plan from IUT1. Things will change based on the feedback we will ask for, but there is a possibility not everything will be covered. They are planning to have two groups to interview and each group would have different questions asked
• [ ] Google slide deck we are handing over to UXR: will organize it by themes instead of by page. We will also share priority of each theme

Task Items

• [ ] Kyle will be assigning and removing drafts from Employment, Unemployment, and Self-improvement GitHub issue
• [ ] Serena preparing wireframes for handoff and creating a GitHub issue for Dev
• [ ] Design will flag Dev to work on the LG pages first before the other pages on Monday

Items for next week's agenda

• [ ]

[anitadesigns]

[October 28, 2022] Agenda and Notes

Attendees

• [ ] Anita
• [ ] Serena
• [ ] Sam
• [ ] Kyle

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu

Recurring items:

• [ ] Content updates
• [ ] Design Updates
  • [ ] Land page

New Meeting Items

• [ ] Landing page Complete letter copy
• [ ] Affinity map exercise to assess themes for UXR hand off
• [ ] Sections feature on Figma and using it in our workspace
• [ ] Mobile page and updating figma master pages
• [ ] Category order

FYI

• [ ] Jaime is not available today
• [ ] No meeting next week due to planning a meeting

Notes from Meeting

• [ ] Anita presented LP to Content and shared ideas re: letter. Pulled copy from auto-generated issue to create 3 different letters. Just changed the name and dates. Doing the letter screenshot because it is more tangible and shows users what to expect after they download their letter.
• [ ] Category order: we thought that some wireframes on Figma had different category orders that would impact Dev. Concluded that it looked okay and the order we handed off to Dev would be okay
• [ ] Mobile page and updating Figma: Going to work on this a bit more once we hand over everything to Dev
• [ ] Anita showed Content the new sections feature to Content. We found that you cannot link sections and only can copy the link to frames
• [ ] Affinity map: decided to do this exercise so everyone can participate and we can gain more feedback from the team. We are starting off with "brain dumping" areas we would like feedback on and then organizing them by theme. This is helping us to organize the slide deck

Task Items

• [ ] Anita will update the other two letters in LP

Items for next weeks agenda

• [ ]

[anitadesigns]

[Friday, November 11, 2022] Agenda and Notes

Attendees

• [ ] Serena
• [ ] Anita
• [ ] Kyle
• [ ] Kelsey (UXR lead)
• [ ] Sam

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu

Recurring items:

• [ ] Design updates
  • [ ] FAQ hand off
• [ ] Content updates

New Meeting Items

• [ ] Complete affinity mapping
• [ ] #739
• [ ] figma re-organization: where does everything stand/anything that needs to be done/are we waiting on handovers to finish it?

FYI

• [ ] New updates to the website have been published 🎉
• [ ] Jaime will be back on Monday

Notes from Meeting

• [ ] Discussed the bugs to hand over to Dev that we are collecting in the issue listed above. Discussed briefly how other teams do troubleshooting, and how much work it is for both teams and Content to double check everywhere. Design will ask Dev on Monday if they want this kind of feedback now or when they are done implementing (i.e. maybe they are in the middle of work and that's why things don't work right now).
• [ ] Finished exercise on the Figjam board (affinity mapping) by grouping and thematizing. Next step we will transfer to the IUT2 feedback slide deck. Kyle start lead this process and hand back to us for feedback. Goal to finish by Friday.
• [ ] Fielded some questions about the figma re-organization. We will continue discussing next meeting. For now, can close old comments that don't need to be saved for future teams to see how we came to a decision.

Task Items

• [ ] Finish IUT 2 slide deck for UXR
• [ ] Compile bugs to Dev
• [ ] Ask Dev when/how they want troubleshooting feedback

Items for next weeks agenda

• [ ]

[anitadesigns]

[November 18, 2022] Agenda and Notes

Attendees

• [ ] Anita
• [ ] Serena
• [ ] Sam
• [ ] Kyle
• [ ] Jamie
• [ ] Minqi

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu

Recurring items:

• [ ] UXR Slide deck https://github.com/hackforla/expunge-assist/issues/719

New Meeting Items

• [ ] Discussion on future meetings
  • [ ] Next week is Thanksgiving
• [ ] Figma re-organization
• [ ] Updates on discussion with Dev

FYI

• [ ] UXR will start working on IUT2 next year
• [ ] No meeting next week
• [ ] Planning meeting on Dec 2

Notes from Meeting

• [ ] Slide deck is organized alphabetically order. It would be helpful for researchers to know the priority of the themes they should address. Minqi mentioned that some of the feedback we have may fit better with other research methods, but that would be discussed in January. UXR will not be able to proceed with surveys and IUT2 due to an org-wide break in December and limited availability. There is no rush to complete the slide deck, but Anita will order the themes from highest priority to lowest and post them on slack for us to discuss. Once we have an order, we will work on adding links to the screenshots and adding arrows to the screenshots we address in the feedback. UXR would find it helpful for Design to present the website flow to research and add how UXR can improve. Perhaps next year when everyone is back.
• [ ] No meeting next week and perhaps no meeting on Dec 2nd due to planning meeting. It would be good for us to create a doc of our availability. Anita can create that doc
• [ ] Update from Dev: Dev found value in our feedback and would try to work on them. They are prioritizing fixing the user flow for the categories.
• [ ] Figma re-organization: we will work on this in steps. It is important for us to have the master pages completed before archiving. Our plan for tackling Figma re-organization is as follows:
  • Design will create mobile wireframes for the pages that do not have a wireframe
  • Content will go through the pages to ensure they are correct.
  • Once master pages are complete, we will compile all IUT2 workspaces on Figma into one page and archive it. Will be labeled IUT2.
  • Then we will work on the Design system together and Start here page.

Task Items

• [ ] Anita will create a priority list before Thanksgiving and create an availability doc for the next two months

Items for next week's agenda

• [ ]

[anitadesigns]

[December 2, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Serena
• [ ] Anita
• [ ] Jamie

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin

Recurring items:

• [ ] Content Updates
• [ ] Design Updates

New Meeting Items

• [ ] 2022 reflection

FYI

• [ ] December 16th will be our last meeting for the year!
• [ ] Phu and David will return 2023
• [ ] Justin is our new UX Designer 🎉

Notes from Meeting

• [ ] Worked on 2022 reflection

Task Items

• [ ]

Items for next weeks agenda

• [ ]

[anitadesigns]

[December 9, 2022] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Serena
• [ ] Jamie
• [ ] Anita

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin

Recurring items:

• [ ] Content Updates
• [ ] Design Updates

New Meeting Items

• [ ] 2022 reflection

FYI

• [ ] December 16th will be our last meeting for the year!
• [ ] Phu and David will return 2023

Notes from Meeting

• [ ] Expanded on finding underlying barriers to "I wish" and "I Wonder" thoughts we had during our 2022 reflection exercise
• [ ] We worked on a 5 Whys exercise to determine the root cause/barrier of creating a Content Source of Truth. Discovered that our major roadblock is that Figma has limitations for UX Writers and we need more resources to use tools created for UX Writers
• [ ] We then worked on creating action items to take to address these limitations. Sam shared she is exploring tools to use and whether we can use the main ea/hack for the LA account to use Writer.com
• [ ] We also want to explore and use a Content Source of truth page on Figma. We will need to speak further on whether this page would also be used as a space for Content to work in
• [ ] We then proceeded with exploring barriers to documentation in Figma. What are we using now that is working? What can we adjust? or expand? add? The problem we are facing is documenting our work process and the decisions and actions needed to take. We want to stray away from using comments for these factors.
• [ ] We explored different templates on Figma's community page and thought it would be good to use post-its/card on the design we work on and color-code them
  • [ ] https://www.figma.com/community/file/1168610243698621594
  • [ ] https://www.figma.com/community/file/944644388375583520
  • [ ] https://www.figma.com/community/file/852552326144345707
• [ ] Concern: Would be difficult for Content Designers to build new cards each time. Is there something that Content can copy and drag? Anita mentioned the component library and shared we can show Content how to use it. We would make these annotation cards components so we wouldn't have to rebuild them each time

Task Items

• [ ] Figma re-design: Add content source of truth page
• [ ] Further look for templates to use for annotations and create a component on Figma

Items for next week's agenda

• [ ] Further exploring the other questions posed in the reflection board and creating a general list specific to content and design for our 2023 goals

[jamiesiu]

[December 16, 2022] Agenda and Notes

Attendees

• [ ]

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin

Recurring items:

• [ ]

New Meeting Items

• [ ] Workshop on Prioritized Points from EOY Reflection
• [ ] 2023 Goals

FYI

• [ ]

Notes from Meeting

• [ ]

Task Items

• [ ]

Items for next weeks agenda

• [ ]

[anitadesigns]

[January 13, 2023] Agenda and Notes

Attendees

• [ ] Anita
• [ ] Phu
• [ ] Sam
• [ ] Serena
• [ ] Kyle
• [ ] Jamie
• [ ] James

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin

Recurring items:

• [ ]

New Meeting Items

• [ ] Introductions
• [ ] Overview of monthly goals/Figjam
• [ ] Update on mobile wireframes
  • [ ] Had to pause to confer with Dev about dimensions. Will resume soon
• [ ] Figma re-organization:
  • [ ] Can we begin archiving pages under "WIP"?
  • [ ] Start here page
    • [ ] Jamie and Serena volunteered to help and will lead this task.
    • [ ] Anita created a format which can be seen under the start here page- okay with changing
    • [ ] Would anyone from Content like to join to help?
    • [ ] Anything missing that should be included?
  • [ ] Adding Overview boxes on each page
• [ ] UXR slide deck: schedule with UXR via slack
• [ ] Design system:
  • [ ] Go over the general approach proposal
  • [ ] Share background knowledge we all have regarding design systems

FYI

• [ ]

Notes from the Meeting

• [ ] We all went around introducing each other to the team
• [ ] Design shared our Figjam board with Content to go through the tasks we are collaborating on
• [ ] Figma re-organization: We decided to move "The landing page" , "Letter Generator", "Faq", "About us", and "Terms of Service/Privacy policy" pages on Figma under a new page labeled "IUT1(2022)" under the archive page. We will create sections on this page for each page listed above. As for comments, Anita will go through the comments and create notations for comments we should document. Will ask Sam and Serena for advice and help
• [ ] We also decided to implement a section on each page that shares the overview or about that page. For master pages, we would also share the last time they were updated and the "start here" arrow.
• [ ] Anita shared where she left off with the Start here page
• [ ] We are scheduling with UXR a date to present the slide deck
• [ ] Since the Design system is an overwhelming task to tackle, we decided to break it down by creating a plan of action. We want to begin by sharing what we know about Design Systems as a team and conducting background research as needed.
• [ ] We created a word doc to track our research.
• [ ] Where did the previous team leave off? Sam shared that at the time Design and Content were separated and was not aware of the process. Serena shared that the Design system was a wip as they worked on IUT1 but really had not been updated. Serena and Jamie were conducting background research by talking to other teams in HackforLA to get guidance. Jamie shared the website team's and CivicTechIndex team's design system and a guide for us to follow. There are two checklists on out own design system page on Figma that are themes we could use to include/work on in our own design system.
• [ ] Since we need time to go over a few of these resources before creating a plan of action, we are going to take the week to go over the resources listed in the google doc. For those who take a look at the resources, we decided it would be a good idea to write a TL;DR of concepts that are good for the rest of the team to know. We will share more about our findings next week

Task Items

• [ ] Anita will reach out to Dev about dimensions for Desktop and Mobile
• [ ] Anita will format the Design System doc for us to use
• [ ] Anita will archive pages and reach out to Sam and Serena for comment help
• [ ] Team will review resources on Design system and share a tl;dr on google doc to share with the team next week

Items for next weeks agenda

• [ ] Go over design system learnings

[anitadesigns]

[January 20, 2023] Agenda and Notes

Attendees

• [ ] Jamie
• [ ] Anita
• [ ] Serena
• [ ] Sam
• [ ] Kyle
• [ ] James

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] Phu
  • [ ] Justin
  • [ ] Jamie
  • [ ] James

Recurring items:

• [ ] Design System

New Meeting Items

• [ ] Overview of tasks
• [ ] UXR slide deck presentation
• [ ] Sharing what we learned on DS (Figjam)
  • [ ] Sharing tips Danielle Vedivi shared
  • [ ] Working off doc
• [ ] Planning and assigning tasks for the Design system/content system
  • [ ] Perhaps start with auditing one component
    • [ ] Anita created a page on Figma called "Design system audit" as a space for us to work on the audit

FYI

• [ ] Anita has to leave early today
• [ ] Kyle may be able to make it today and maybe for a short time
• [ ] Jamie will be unavailable 1/27-2/5
• [ ] Sam will be away 1/31-2/6 (can chat via slack but will be limited)
• [ ] No meeting on 2/3
• [ ] Content will only meet with Design on this sync for three weeks until Feb 17th.

Notes from Meeting

• [ ] Anita presented the Figjam board, there are two parts. 1. There is a board now to the right for developing and brainstorming our ideas about the Design system. 2. Current project. Content can add Github issues/tasks under the tasks now as well, so all tasks will be present.
• [ ] Content/Design will present next week to UXR (IUT 2 transfer) on the 27th and will meet the Thurs before during the regular Content mtg to go over the UXR presentation.
• [ ] Design will met with Dev to go over some Figma changes (dimensions). Discussion about how long it will take to make changes to develop the mobile wireframe.
• [ ] Anita is still updating the Figma pages (removing comments and archiving).
• [ ] Start Here and Wiki are lower priority than the Design system. Jamie will take point on the Wiki updates. We decide to reorder tasks, Wiki is a higher priority because it's a barrier to UXR moving forward, but the Start Here page could be moved down.
• [ ] Overlap between Content and Design systems - Sam will add a separate task for the Content system to the board and we will see where the overlap is (like in creating components) as we go along.
• [ ] Moved on to the Design systems exercise in Figjam board - we use sticky notes to say what we've learned about Design systems. Anita presents the idea of UX Design like atoms (from the book "Atomic Design"). Serena shares that working on the Design system by category can be a useful approach (from meeting with Danielle). Jamie notes that storybook approach is helpful in working with Dev. The Design System can be a helpful tool for collaboration between Dev and Design.
• [ ] We need some more time to learn about Design systems, and tangible next steps as we are learning. We will reconvene next week.

Task Items

• [ ] Learn more about Design systems (everyone)
• [ ] Wiki - Jamie will look into it and UXR is helping with the inventory
• [ ] Content will update the board, Sam and Kyle will work on team planning/creating dates for the next time period
• [ ] Mobile wireframes with Dev
• [ ] UXR presentation next Friday, we will meet the Thursday before to discuss how to present

Items for next weeks agenda

• [ ]

[anitadesigns]

[January 27, 2023] Agenda and Notes

Attendees

• [ ]

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin
  • [ ] Jamie
  • [ ] James

Recurring items:

• [ ]

New Meeting Items

• [ ] Presentation prep for UXR slide deck
• [ ] Design system - Audit
  • [ ] Discussion on overlap of content and design system

FYI

• [ ]

Notes from Meeting

• [ ]

Task Items

• [ ]

Items for next weeks agenda

• [ ]

[anitadesigns]

[February 10, 2023] Agenda and Notes

Attendees

• [ ]

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin
  • [ ] Alexis

Recurring items:

• [ ]

New Meeting Items

• [ ] Introductions
• [ ] Overview of Monthly goals
• [ ] Mobile wireframes update: Ready to hand off to Content
• [ ] About Page
• [ ] Design System update

FYI

• [ ] Alexis Ramos joining our meeting to learn more about team
• [ ] Kyle will be out until March

Notes from Meeting

• [ ] Introduced ourselves to Alexus and welcomed her to the team
• [ ] Showed Alexis how Design and Content collab and spaces to note that our progress
• [ ] Design handed over the mobile wireframes to Content to go over
• [ ] Discussed potential changes to the About page. We do not have to make any changes and continue to proceed with Dev updating it
• [ ] Design system update: Design is moving onto auditing colors first

Task Items

• [ ]

Items for next weeks agenda

• [ ]

[anitadesigns]

[February 17, 2023] Agenda and Notes

Attendees

• [ ]

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin
  • [ ] Alexis

Recurring items:

• [ ]

New Meeting Items

• [ ] Dev update / discussion on issues
• [ ] Design System update
• [ ] Update on Archived pages
  • [ ] All have been updated and are under "IUT 2" under the Archive section
  • [ ] Good news from the Design System team regarding our Figma
• [ ] Mobile wireframes hand-off to Content
  • [ ] #844
• [ ] Open Q & A

FYI

• [ ] No meeting on Monday 2/20 President’s Day

Notes from Meeting

• Brainstorming on how to improve workflow between dev + design + research. Now with more devs how can we have smaller projects to work on
• Hard to push out issues with dependencies between dev + design
• What is considered the MVP? Team should agree on what that looks like for Expunge Assist
• Look at starting QA process. Catch and fix bugs when new changes are pushed.
• IUT2 work have been moved to archive. Only mobile + design audit is under WIP
• Reviewed new process on documentation on Figma

Task Items

• [ ] Re-evaluate issues labeled "Draft" to either push to dev or cancel
• [ ] Audit colors on mobile/desktop wireframes and live website

Items for next weeks agenda

• [ ]

[anitadesigns]

[February 24, 2023] Agenda and Notes

Attendees

• [ ] Serena
• [ ] Sam
• [ ] Jamie
• [ ] Julia
• [ ] Alexis
• [ ] Anita

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle (Out until March)
  • [ ] Serena
  • [ ] Anita
  • [ ] Phu
  • [ ] Justin

Recurring items:

• [ ]

New Meeting Items

• [ ] Mobile wireframes update
• [ ] CMS

FYI

• [ ] Team Planning week next week - Leads & PM are meeting on Friday 3/3. All regular syncs cancelled. We are considering still having Monday Dev Design sync
• [ ]

Notes from Meeting

• [ ] Introductions
• [ ] Updating mobile wireframes: Content has a slow start but started working on them. Will be placing a gold star on top of the ones they complete.
• [ ] Anita went over the new workflow Design is implementing. Using a pull system to encourage designers to use the board
• [ ] CMS: Summarized the discussion on Slack and are excited to see a demo of it. Jamie shared that Tom G already set it up but is working on how it would look for Content. We are concerned about having to manage two sources of truth and would love to have it integrated with Figma. This may not be feasible as it is a CMS but would create efficiency in updating copy.
• [ ] Ditto: Sam mentioned she would focus on creating an account. Shared that all Content Designers would need access to 1Pass so that they can use Ditto. Ditto is a plugin for Figma that would update all the copy and would become the source of truth.
• [ ] Design system: Anita shared zerheight as an option for us to house our design system. There is also storybook but we need to research more the differences
• [ ] Julia asked about the tools Dev uses and how Design and Dev sync. We shared that Dev uses Github and the languages they use. Anita shared our design handoff space. Sam was interested in how we can improve the hand-off space. What information do they need that is missing?
• [ ] conversation on cleaning up the Issue board and prioritizing tasks. Would be good to do since there are issues that were worked on by previous volunteers that may no longer be relevant. Would help with assessing the direction of the project and issues to work on.
• [ ] Bridging the gap between research and design. It would be nice to join interview or analysis for designers to learn more about process and get iterations out quicker

Task Items

• [ ] @SamHyler prioritizing creating Ditto account and setting it up
• [x] Design team to continue auditing colors
• [ ] Content team continue reviewing copy
• [x] @lexramos01 to relay question to Dev about improving our hand off
• [ ] @SamHyler @RenaNicole @anitadesigns to look over design issues and content issues on board and assess which ones can be closed and/or re-prioritized
• [ ] @anitadesigns will talk to the rest of Design team on interest in joining research on interview/analysis

Items for next weeks agenda

• [ ] Reviewing board

[anitadesigns]

[March 10, 2023] Agenda and Notes

Attendees

• [ ]

Facilitator

• [ ] Anita
• [x] Serena
• [ ] Alexis

Notetaker

• [ ] Sam
• [x] Serena
• [ ] Jamie
• [ ] Anita
• [ ] Phu
• [ ] Kyle
• [ ] Justin
• [ ] Alexis

Accountability and Support Check

• [ ] Review assignments for each team member
  • [x] Sam
  • [ ] Kyle
  • [x] Serena
  • [ ] Anita
  • [ ] David
  • [ ] Phu
  • [ ] Justin
  • [x] Alexis

Recurring items:

• [x] Content updates
• [x] Design updates

New Meeting Items

• [x] Summary of all team meeting - Revisiting Design and Content's goals
• [x] Discussion on live website updates
• [x] Renaming Github issues for Dev- Anita making new ones for Dev to update the URL slug for updated flow names
• [x] Contentful demo created by Dev Tom G. Open for testing with account signup (limit 4 total accounts)

FYI

• [x] Anita will be out from Friday, 3/10- Sunday 3/19, and will tune into meetings on the last week of March
• [x] Dev pushed some more updates onto the live website 🎉
• [x] Potential PM Christian shadowing/observing team

Notes from Meeting

• [ ] Alexis finished mobile wireframe review -> found differences with the number of screens in the mobile flow vs. desktop and the copy for the final preview flow for desktop
• [ ] Discussed the limitations of Ditto's free serves.
• [ ] Reviewed the possibilities of using Contentful
• [ ] Noticed the outdated page names in the URL code (ex. 'job' in url should now be 'employment')
• [ ] Discussed ways to collaborate on updating Github board issues. Figjam table to consolidate backlog issues, similar to MOSCOW prioritization to visually determine what is still necessary or not.

Task Items

• [ ]Alexis to work on the content guidelines
• [ ] Create Contentful accounts for Sam, Alexis, and someone from design. (Max 4 accounts)

Items for next weeks agenda

• [ ] Create Figjam table for backlog issues for desgin and content from IUT1 & IUT2

[anitadesigns]

[March 31, 2023] Agenda and Notes

Attendees

• [ ]

Facilitator

• [x] Anita
• [ ] Alexis

Notetaker

• [ ] Sam
• [ ] Jamie
• [ ] Anita
• [x] Kyle
• [ ] Alexis
• [ ] Julia

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Anita
  • [ ] Alexis

Recurring items:

• [ ]

New Meeting Items

• [ ] Updates from Design and Content team
• [ ] Facilitators?
• [ ] MOSCOW for Issues on Project Board
• [ ] UXR Timeline
• [ ] Packaged issues
• [ ] Review Issue https://github.com/hackforla/expunge-assist/issues/885 (Download frame discrepancy) together
• [ ] Tracking changes - how does Design input copy? And Dev?
• [ ] Meeting for next week?

FYI

• [ ]

Notes from Meeting

• [ ] Discussed rotating meeting facilitators and note-takers (will do this)
• [ ] Content updates
• Alexis finished a draft of Content Guidelines, will update yearly
• Kyle is working on Source of Truth issue
• Discussed 885 mobile wireframe issue, including the discrepancies between the mobile and desktop and live site, how the discrepancies are occurring, and what we can do to avoid them in the future (more careful checking when transferring content, hopefully resolving the source of truth issue & updating the design QA process will help). o Sam will find previous final text (written by Irene) and content will decide from there what to keep o Kyle will update button & letter copy in mobile and desktop; Anita will adjust design on both to accommodate full letter preview
• Anita suggested speaking with Dev about having an option for Dev where they put a check on the Figma handoff page so we know when an issue is completed, or perhaps publish updates weekly; will discuss with Sydney.
• [ ] MOSCOW task
• Prioritized outstanding issues for both teams in Figjam board and discussed issues that were unclear how they should be prioritized; will continue this at next meeting o Thumbs up means can be closed; question mark means needs further investigation to decide
• [ ] Didn’t get to; will discuss at next meeting:
• UXR timeline discussion
• Packaged issues
• Tracking changes

Task Items

• [ ]

Items for next weeks agenda

• [ ]

[lexramos01]

[April 21, 2023] Agenda and Notes

Attendees

• [ ] Audrey
• [ ] Sam
• [ ] Alexis
• [ ] Sam

Facilitator

• [ ] Anita
• [x] Alexis
• [ ] Julia

Notetaker

• [ ] Sam
• [x] Anita
• [ ] Kyle
• [ ] Alexis
• [ ] Julia

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Anita
  • [ ] Alexis

Recurring items:

• [ ]

New Meeting Items

• Introductions
• Finalize discussion on MOSCOW for Issues on Project Board
• UXR Timeline
• Packaged issues
• Review Issue https://github.com/hackforla/expunge-assist/issues/885 (Download frame discrepancy) together
• Tracking changes - how does Design input copy? And Dev?
• Info: Content is updating the Content Guidelines ex: https://github.com/hackforla/expunge-assist/issues/906 - Will seek input (close test)
• Who attends which meetings & PM support?

FYI

• [ ] Design added two new volunteers: Liz and Michelle!

Notes from Meeting

• [ ] Audrey has officially joined the team and Design has two new UX Designers!
• [ ] Hoping others from the Design can join to meet the content team. Anita is hoping to integrate "Packaged" issues to help UX Designers develop strong case studies where they led a design solution, but this would require designers to be able to attend Content and Dev meetings.
• [ ] Clarify Icebox. There is an understanding that Icebox is used for issues that have a hold due to dependencies. Talk to PMs about defining the Icebox (what issues can go there)
• [ ] Using MOSCOW board to reflect the structure of the Project Board on Github
• [ ] Deciding to move issue in the prioritized backlog for Bonnie to review before we close. We can add comments to the issue for Bonnie to consider
• [ ] UXR timeline- recruiting is taking a bit longer but is expected. The results of the survey may not have design-related improvements so the Design team may be able to continue working on the Design system with Dev
• [ ] Tracking: Shared with Content summary of our meeting with Dev and discussion on issues. Agreed to collab and communicate with Dev more to create Github issues that are more efficient for development and merging issues
• [ ] Review Issue: will revisit this another time when Kyle is available
• [ ] Meeting attendance: discussed the idea of opening our Friday meetings to Dev and Research folks. Thought we can do it once a month - twice a month. Also, an opportunity for a representative from UX Design to attend research meetings

Task Items

• [ ] Anita will copy the MOSCOW board with new labels that reflect the Github Job board so that the team can prioritize issues based on what is reflected on the Project board
• [ ] @SamHyler and @anitadesigns will reach out to PMs to better define "Icebox"

Items for next weeks agenda

• [ ] Review Issue https://github.com/hackforla/expunge-assist/issues/885 (Download frame discrepancy) together
• [ ] MOSCOW board update
• [ ] Error prevention pop-up

[jccchurch]

[April 28, 2023] Agenda and Notes

Attendees

• [ ] Audrey
• [ ] Sam
• [ ] Alexis
• [ ] Sam

Facilitator

• [ ] Anita
• [ ] Alexis
• [x] Julia

Notetaker

• [ ] Sam
• [ ] Anita
• [ ] Kyle
• [ ] Alexis
• [ ] Julia
• [x] Audrey

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Kyle
  • [ ] Anita
  • [ ] Alexis

Recurring items:

• [ ]

New Meeting Items

• [ ] Introductions
• [ ] Finalize discussion on MOSCOW for Issues on Project Board](https://www.figma.com/file/SRsM0BvWhtmFwpg23bKTLB/EA-IUT2-Collaboration-(Design%2FContent)?node-id=0-1&t=PXGJ06PxR33NfldN-0)
• [ ] UXR Timeline](https://docs.google.com/spreadsheets/d/1xfqBZG_LICowdpmJX2h_mEpqMU9KgGhdP0SDIHj5E-I/edit#gid=477646646)
• [ ] Packaged issues
• [ ] Review Issue https://github.com/hackforla/expunge-assist/issues/885 (Download frame discrepancy) together
• [ ] Tracking changes - how does Design input copy? And Dev?
• [ ] Info: Content is updating the Content Guidelines ex: https://github.com/hackforla/expunge-assist/issues/906 - Will seek input (close test)
• [ ] Who attends which meetings & PM support?
• [ ] Issue #884

FYI

• [ ] Design added two new volunteers: Liz and Michelle!

Task Items

• [ ] Anita will copy the MOSCOW board with new labels that reflect the Github Job board so that the team can prioritize issues based on what is reflected on the Project board
• [ ] @SamHyler and @anitadesigns will reach out to PMs to better define "Icebox"

Today's agenda

• [ ] Review Issue https://github.com/hackforla/expunge-assist/issues/885 (Download frame discrepancy) together
• [ ] MOSCOW board update
• [ ] Error prevention pop-up

[SamHyler]

[May 12, 2023] Agenda and Notes

Attendees

• [ ] Analicia
• [ ] Sam
• [ ] Anita
• [ ] Audrey
• [ ] Alexis

Facilitator

• [ ] Anita
• [ ] Alexis
• [ ] Julia
• [x] Sam

Notetaker

• [ ] Sam
• [x] Anita
• [ ] Alexis
• [ ] Julia
• [ ] Audrey

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Anita
  • [ ] Alexis
  • [ ] Audrey
  • [ ] Michelle
  • [ ] Liz

Recurring items:

• [ ]

New Meeting Items

• [x] Team member shifts. What are our availabilities and needs? Changing meeting times/days/Adding UXR
• [ ] Finalize discussion on MOSCOW for Issues on Project Board.
  • [ ] What's needed?
• [ ] Issue #690 status
• [ ] Issue #924
• [ ] Product Principle development & cross-functional tie ins

FYI

• [x] Sam reached out to PM's regarding Icebox definition and guidance on issues that are on hold
• [x] Kyle will be stepping away from the team due to work conflict

Meeting Notes

• [ ] Thoughts on opening the meetings to UXR: Decided to begin opening the meetings to UXR. Analicia shared that she could come to every meeting to shadow and observe what we are working on. We could use the first ten minutes of the meeting to go over updates from UXR and answer/ask any questions. We would also like more folks from research/design join.
• [ ] MOSCOW: we are still waiting for an update on defining Icebox and how to label issues for Bonnie to review before closing. Analicia shared that next week PMs will have a meeting with Bonnie on Friday.
• [ ] Summary of Planning meeting regarding principles: Each team to create their own and we can come together and synthesize them.
• [ ] Issue #690: Noticed there is inconsistency in the text. Some have file formats while others do not. Agreed we should group options that say "download" together. We would like to later test which options are preferred by our audience/partners. Content will talk this over on Slack and have an answer by the end of May or sooner.
• [ ] Issue #924 : Overview of issue. Discussed update from Dev on that letter progress is not lost unless the browser or tab is closed. Content would need to review this behavior more to write correct information. Alexis brought up a good point for us to explore on whether the "return home" button is necessary and whether there are other solutions we can provide. We agreed someone from Content and Design would team up to work on this and this would be prioritized.

Task Items

• [x] Analicia sending Audrey a calendar invite for research meetings
• [x] Add research updates on board as a re-occurring task
• [ ] Each team to workshop their own individual team goals/values to share with the overall team
• [ ] Sam will create slack message for content to talk about #690 . Github to keep track of this task https://github.com/hackforla/expunge-assist/issues/930 . Anita will follow up with Sydney regarding update on this
• [ ] Sam will fix the bugs: https://github.com/hackforla/expunge-assist/issues/929 and https://github.com/hackforla/expunge-assist/issues/928

Items for Next Agenda

• [ ] Status of #690
• [ ] Update on #924

[lexramos01]

[May 19, 2023] Agenda and Notes

Attendees

• [x] Analicia
• [ ] Anita
• [x] Sam
• [x] Audrey
• [x] Alexis
• [x] Julia

Facilitator

• [ ] Anita
• [ ] Julia
• [x] Alexis
• [ ] Sam

Notetaker

• [x] Sam
• [ ] Anita
• [ ] Alexis
• [ ] Julia
• [ ] Audrey

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Anita
  • [ ] Alexis
  • [ ] Audrey

Recurring items:

• [ ] UXR updates

New Meeting Items

• [x] Status of https://github.com/hackforla/expunge-assist/issues/690
• [x] Update on https://github.com/hackforla/expunge-assist/issues/924

FYI

• [ ]

Notes from Meeting

• [ ] The first issue Content finished in the meeting the hour before on this same day. It is done and will be handed over to Design.
• [ ] Liz and Alexis will work on iterations in a way suitable for them. Sam advised them to use a blank page on Figma as a joint workspace. Anita may have ideas about how to best organize this work on Figma.
• [ ] Julia and Analicia shared a slide deck for the next Bonnie meeting happening today, went through the high level points and asked for feedback. The document is here: https://docs.google.com/presentation/d/1NggwSMseidohkPsBzByLzQaXEmbt9Xs0IR4HZBsWdQI/edit#slide=id.g245106dc73c_0_44 Sam will also join the meeting, everyone was invited to join. Sam also added points for Content's high level goals.

Task Items

• [ ]

Items for next weeks agenda

• [ ]

[anitadesigns]

[May 26, 2023] Agenda and Notes

Attendees

• [ ] Sam
• [ ] Julia
• [ ] Analicia
• [ ] Alexis
• [ ] Audrey
• [ ] Danielle
• [ ] Anita

Facilitator

• [x] Anita
• [ ] Julia
• [ ] Alexis
• [ ] Sam

Notetaker

• [ ] Sam
• [ ] Anita
• [ ] Alexis
• [x] Julia
• [ ] Audrey
• [ ] Liz
• [ ] Michelle

Accountability and Support Check

• [ ] Review assignments for each team member
  • [ ] Sam
  • [ ] Anita
  • [ ] Alexis
  • [ ] Audrey

Recurring items:

• [x] UXR updates

New Meeting Items

• [x] Issue #924 check-in: Updates and how's it going?

• [x] Updates from Bonnie meeting?

FYI

• [ ] Anita wont be available next week. Will return on Monday!

Notes from Meeting

UXR updates

Research is planning IUT2 of the landing page Will take place mid June Opportunities to do other types of testing – A/B, HeuristicAnalysis Additional Usability testing beyond just the landing page What specifically to teams want to test? Start new UT 1st week of July Planning steps in motion 

Is Dev done with all the updates? Check in with Dev what is complete Check with Content – there will be some changes Dev hasn’t gotten to yet Other teams can observe testing – finalizing moderator guide for IUT2 of landing page UXR will do a quick 1-pager with idea of what focus is, what we’re doing, etc Training session invites will go out for that as well

Design – working on color auditing Why the purple? Research can assist with A/B Testing with current colors in wireframes Color system – continue that conversation Finishing up with auditing of the live website Developing our own design principles within specific teams and then broadening that out with the rest of the team – to do after the planning meeting Color theory considerations

Issue #924 Design – error prevention pop up for letter generator Completed journey didn’t feel complete – working on new pop up ideas “You’re one step closer to record clearance” – finalizing tone of voice Will have more iterations to show next week

Design is working on improving headers & typography Did we finish the mobile wireframe audits? Need to finalize and create an issue for Dev Change the headings before moving to master

Notes from Bonnie Meeting

• [ ] Establishing our own user journey for EA Collaborate on colors – look at other brands https://principles.design/

• [ ] When do we want to demo to Bonnie? Putting together our brand guide Example: https://drive.google.com/file/d/1v257uSAW8CdJamC32VBuN4QpZCJTI2Pb/view Let’s look at other brand books- Julia will pull some examples to share

Task Items

• [ ] What do we want to prioritize for our Bonnie demo?
• [ ] Review at Team Planning meeting

Items for next weeks agenda

• [ ] Planning meeting summary
• [ ] Brainstorming Product/design principles
• [ ] Moving over mobile wireframes to master section on Figma?
• [ ] Issue #924