Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EA: Research Team Meeting Agenda #423

Open
thomasdemoner opened this issue Jan 13, 2022 · 94 comments
Open

EA: Research Team Meeting Agenda #423

thomasdemoner opened this issue Jan 13, 2022 · 94 comments
Labels
documentation Improvements or additions to documentation feature: agenda issue level: missing This issue is missing an issue level label priority: low role: product management role: research UX and other research size: 1pt can be done in 6 hours or less
Milestone

Comments

@thomasdemoner
Copy link
Member

thomasdemoner commented Jan 13, 2022

This issue tracks the running agenda for the Research Weekly Meetings

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

### Notetaker

### Recurring items: 
- [ ]
### New Meeting Items
- [ ]
### FYI
- [ ] 
### Notes from Meeting
- [ ] 
### Task Items
- [ ] 
### Items for next week's agenda
- [ ] 

@thomasdemoner
Copy link
Member Author

@yumengluo please add other assignees that would be appropriate for this issue, you'd know much better than I. And let me know if there's anything missing from it :)

@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Jan 18, 2022

14 January 2022 Agenda and Notes

Attendees

  • Jessica, Larisa, Yumeng, Val, Sam

Accountability and Support Check

Recurring items:

  • Research Plan

New Meeting Items

  • Database (Create a Legand)
  • Write Recruitment document (Word doc)
  • Create History of Partnership (Excel)

FYI

  • We need to recruit writer and 1-2 researcher for the team

Notes from Meeting

  • Marketing versus UX Research questions

Task Items

  • Jess/Val will assign issues discussed in the meeting to team
  • Val/Jess work on organising Github/Google Drive
  • Val/Jess touch base with Bonnie about recruiting researchers

Items for next weeks agenda

  • Recruitment to the team (writer, researchers), what is the procedure
  • GitHub task assignment (issues/check-in)
  • Confirming All Team meeting time

@jessicaherling
Copy link
Member

jessicaherling commented Jan 21, 2022

[1/21/22] Agenda and Notes

Attendees

  • Jessica, Larisa, Yumeng, Val, Sam

Accountability and Support Check

Recurring items:

  • Research Plan

New Meeting Items

  • Recruitment Updates
  • GitHub task assignment (issues/check-in)
  • Confirming All Team meeting time
  • Deadlines for research plan and recruitment

FYI

  • Jess creating task about expungement in other states in the U.S.

Notes from Meeting

  • Discussion about discovery research plan versus usability plan and timeline for this (see notes in link)

Task Items

  • Val incorporate comments from Yumeng and Larisa into Research Plan and will assign to Jess and Sam
  • Jess/Val check with Bonnie - need to have research plan for usability
  • Jess/Val confirm MVP launch timeline with PMs
  • Jess/Val confirm new team members and get them added to team
  • All team members review and update Github tasks
  • Sam send Content Writer information to Val
  • Jess/Val ask Bonnie about Content writing at Hack for LA
  • Sam send description to Jess/Val of what kind of support is needed to content writing
  • All team members review participant database to add any context

Items for next weeks agenda

  • Finalize team members
  • Github task assignment (cleaning up tasks)
  • Deadlines for research plan and recruitment

@jessicaherling
Copy link
Member

jessicaherling commented Jan 28, 2022

[1/28/22] Agenda and Notes

Attendees

  • Jess, Sam, Larisa

Accountability and Support Check

Recurring items:

  • [ ]

New Meeting Items

  • Val and Jess interview 4 researchers this week; want feedback from group about bringing on board 2
  • Val and Jess setting up 2-3 more chats next week with researchers
  • Sam/Jess discuss meeting with content writers next week
  • Research plan updates
  • Check in about team members review participant database to add any context
  • Github task assignment (cleaning up tasks)

FYI

  • Val/Jess still need to talk with Bonnie about Content writing

Notes from Meeting

  • Timeline for usability testing; dependent on timelines of creation of MVP; concerns about being able to change content and adapting to users' needs
  • Larisa brought up being able to prepare ourselves for usability testing - walk through prototypes (talk to designers)

Task Items

  • Jess/Val MVP deadline and what stage the product is
  • Jess ask at R&D meeting to have design show prototype at meeting
  • Jess/Val meet with more research recruits
  • Jess/Val/Sam meet with UX content writers

Items for next weeks agenda

  • [ ]

@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Feb 4, 2022

[2/4/22] Agenda and Notes

Attendees

  • Jess, Val, Sam, Larisa, Yumeng, Rhiana, Thomas

Accountability and Support Check

Recurring items:

  • Github task assignment (cleaning up tasks)
  • Research plan updates, set separate tasks, create issues for each team member on Github (someone works on screener, other tasks could be working on MVP part
  • See if someone is interested to work on state research or creating guidelines on how to reach out to stakeholders

New Meeting Items

  • Update for Sam, a community of practice for UX writers, need writers; Zoya and Sam working together on creating open board role, already has an open line of communication with Zoya; Bonnie can assist with reaching out to HfLA teams
  • UX writers volunteer discussion, interview feedback; Joanna's role

FYI

  • MVP deadline is 1-1.5 months away, like March
  • Jess ask at R&D meeting to have design show prototype at meeting

Notes from Meeting

  • Sam to work with Zoe on Ux content writing; place to redirect some folks who are content writers interesting in the team
  • Creating separate issues for people to complete tasks
  • Repository building - Rhianna - what do we do with the data? Interested in making the research accessible for future
  • Sam: re: confidentiality for this project - esp. since there are many people who could potentially access the drive; /and anonymizing if it’s important
  • Bringing in more writers - Sam is doing a lot of work on content writing
  • Link for application: https://expungeassist.org/#/./form/intro; Rhianna says you can test through Figma

Task Items

  • Tom and Rhianna read over Expunge Assist Google Drive Documents and Github

  • - Team tell Jess/Val about any task preference

  • - Jess/Val assign tasks on Monday to team

  • - Sam reach out to writers

  • - Sam create Github content writing tasks

  • - Jess/Val ask PMs about usability testing for https://expungeassist.org/#/./form/intro (moderate through Figma)

  • - Jess/Val assign Tom to state research

Items for next weeks agenda

@SamHyler
Copy link
Member

SamHyler commented Feb 5, 2022

Just checking in: @ValeriyaMetla @jessicaherling I know of a Zoe who is a writer, but not a Zoya. Is this maybe the same person, or Val did you mean someone who isn't a writer?

@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Feb 5, 2022 via email

@jessicaherling
Copy link
Member

jessicaherling commented Feb 18, 2022

[2/18/22] Agenda and Notes

Attendees

  • [ Jessica, Val, Larisa, Yumeng, Sam, Rhianna, Ana, Nicolas]

Accountability and Support Check

Recurring items:

  • [ ]

New Meeting Items

  • Github discussion
  • Research lead request

FYI

  • [ ]

Notes from Meeting

  • Val reviewing Github tasks for usability testing (Usability Testing Research Plan #443)
  • Larisa has draft of research plan (goals and priorities; pre-test questions and questions more specific to legal clinics and sample tasks (5-6 - can modify); post-questions split into general audience versus people who work in legal clinics) - suggest broad overview feedback - need to talk to design and development
  • Rhianna - I will be leaving Sunday for a work project again. would love to continue to do desk research and assist in prep or analysis.
  • Research plan for interviews - Yumeng working on questions - Yumeng wrote questions for usability testing

Task Items

  • Assign Rhianna to do desk research and assist in prep or analysis.
  • Val/Jess write to PMs/Daisy/Daniel and ask if we can spend some time during All teams meeting with design and development and go over the MVP and chat about usability study and get more information

Items for next weeks agenda

  • Jess/Val assign Github tasks for usability and desk research

@ValeriyaMetla
Copy link
Member

ValeriyaMetla commented Mar 11, 2022

[03/11/2022] Agenda and Notes

Attendees

Accountability and Support Check

Recurring items:

  • Documenting research in Wiki
    • Organizing Google Drive
  • Usability Testing Study
    • Finalizing usability testing research plan for users (legal clinics and people going through record expungement process)
    • starting research plan for internal user testing

New Meeting Items

FYI

  • MVP is planned to be ready by the end of March/Early April

Notes from Meeting

  • By Monday - Ana will create the internal usability testing document.

Task Items

  • Val
    • create sidebar for UX Content Writing
    • move the rest of the copies of research-relevant docs to the Wiki folder
    • remove the reminder for the old team meeting link in Slack
    • send relevant documents on expungement in CA to Tom
    • ask Bonnie if there is any guide for editing Wiki
    • reach out to Myranda - invite her to the meeting, get the link for the Slack channel about record expungement
  • Ana
    • create a document for internal testing and trim it down (remove what is not needed as we are testing internally, keep assigned people so we don't have to assign sections again)
    • create copies of all ongoing documents for research and move them to Wiki folder - checking GitHub issues to have clear folders for ongoing projects
    • create a timeline of the project (e.g., main milestones, deadlines, etc.)
  • Val and Ana
    • work on creating GitHHub issues for internal testing
    • work on outreach procedure document so we can start reaching out to legal clinics
      • assign another person to this task
  • Joanna
    • last edit of the usability testing plan (legal clinics and people going through expungement)
    • created a document to make sense of past research, please attach it to the Wiki issue on GitHub
  • Tom
    • working on research across the states, checking the notes, organizing
    • Val will send relevant documents
  • Yumeng and Larisa
    • start working on an internal testing document (Ana will create it on Monday)
  • Rhianna and Nick
    • help Tom with research across states OR
    • help Joanna with last edits of the usability testing (legal clinics and users) to finalize for review with Bonnie OR
    • help Yumeng and Larisa with working on internal testing research plan
  • Everyone
  • the team will comment on possible terms for glossary under this issue

Items for next weeks agenda

  • Accountability and check-in

[11/18/21](https://github.com/hackforla/expunge-assist/issues/

@sylvia-nam
Copy link
Member

sylvia-nam commented Feb 7, 2024

[2/9/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia

Agenda Items

Recurring Items

  • Updates from Design and Content
  • Notetaker?

New Items

  • Introductions - skills (current and future)
  • All team meeting recap (Roadmapping)
  • Follow-up conversation with R&R attorney: Sara
  • Content research: updates and discussion: Sam and Ann
  • User journey and generative research
  • Next steps: what needs to be done

Notes from Meeting

Updates from Design and Content: They are working on privacy initiative and tone of voices, Amanda(the marketing representative) will meet with Analicia today to discuss the branding(the color, content about the branding book)and might also help with partnership.

All Team recap last week: launch prep (bonnie’s requirement/ credit page, accessibility(developer), content research, post launch (branding). We now have 1 milestone for all teams instead of one for each team for consistency.Sylvia and Analicia will work on this and let the team know more!

Content research :
We will need to reorganize the issues for content research and will have a meeting with Sylvia next week (before the research meeting) to discuss the scope and next steps.

Next week, Sara will share the interview( note with a legal professional) with us. And we will focus more on content research discussion and actions.

@sylvia-nam
Copy link
Member

sylvia-nam commented Feb 15, 2024

[2/16/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia
  • Melissa

Agenda Items

Recurring Items

  • Updates from Design and Content
  • Notetaker?

New Items

  • New member intros
  • Invite UXR to collab with Content and Design
  • PM updates for Launch Prep
  • Reset, retool, reground
  • Root & Rebound Zoom workshop
  • Follow-up conversation with R&R attorney: Sara
  • Survey discussion: Sam and Ann
  • Next steps: what needs to be done

Notes from Meeting

Updates from Design and Content: How can UXR collaborate better with content and design? Should make the sync a required meeting for UXR? I

PM updates:1) See the figma board )for current and upcoming milestones.
2) PM met with Amanda (branding) to help for make issues for following development
3) EA is a California project, following meeting of PMs last week. So scope of research is the state.

Reset, retool, reground: Our team needs to be the experts in expungement in California, and communicate up-to-date information, data to other teams. If we know how the structure of how expungement and the criminal justice system in California works, we can make recommendations accordingly. Sylvia will post information on a webinar on record clearance and encourages people who want to learn up-to-date information to attend. Future possibility: a regular check in every meeting on what each member is working on now or what new idea we’d like to work on.

Follow-up conversation with R&R attorney: Sara shared the conversations with the attorney and Sylvia commented that we can think about how to communicate the process on our website, which is missing some key parts of the process

Survey discussion: If putting a stop on the survey and what are next steps? Sam is working on issue organization and sees if Ann could help in any way.

@sylvia-nam
Copy link
Member

sylvia-nam commented Feb 22, 2024

[2/23/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia
  • Melissa

Agenda Items

Recurring Items

  • Updates from Design and Content
  • Notetaker?

New Items

  • Announcements: 1) no UXR meeting next Friday, 3/1, 2) All Teams meeting next Friday, 3/1
  • Launch Prep priorities for UXR: 1) Understand expungement in CA, 2) Content Terminology
  • For Launch Prep priorities, identify: 1) Tasks, 2) Benchmarks, 3) Deliverables, 4) Division of labor

Notes from Meeting

Updates from Design and Content:How are content, design and research communicating better? PMs of both content and design will need to discuss the purpose of Friday Syn meeting.

-Analicia and Sylvia discussed a proposal for how the research team communicates between teams: a certain team submitted the request ▶ ️ Research build the issue ▶ ️ get back to the request team at a certain point. Melissa shared that thinking Figma is an efficient way.

-Launch Prep priorities for UXR: 1) Understand expungement in CA: We talked about contributing to internal guide to show the EA process, maybe the wiki page or others? We talked about what is the benchmark of being an expert for the EA project?

Next action item:

  • Each of us at the research team tries to find what laws could be applied to the expungement process in California? And what does that mean? We will share our ideas as a group in next research meeting.

@sylvia-nam
Copy link
Member

sylvia-nam commented Mar 7, 2024

[3/8/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia
  • Melissa

Note taker

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia
  • Melissa

Announcements

Recurring Items

  • Team alignment and check-in
  • Updates from Design and Content:
  • Launch Prep priorities for UXR: 1) Understand expungement in CA, 2) Content Terminology
  • For Launch Prep priorities, identify: 1) Tasks, 2) Benchmarks, 3) Deliverables, 4) Division of labor

New Items

  • Voice and tone: Supportive, straightforward and trustworthy (Content)
    Color system: to change from bright purple to something else
    For UXR: color theory request for another round of IUT, and identify additional methods for color theory analysis
  • Questions about proposals or Creating GitHub issues?
  • Root & Rebound webinar (2/29)
  • Discussion on team members' findings on recent expungement-related laws

Notes from Meeting

  • Sylvia announced that Github issues were restructured and there are templates for writing issues. We can think about how to organize the issues on Github as a research operation. Melissa showed interest in helping this.
    -Team alignment: Sylvia brought up an idea of “workshop”, that welcome team members can bring up methods that they want to learn and people can brainstorm about them and give feedback.
    -Sylvia brought up the issue from content and design about the A/B testing of color systems. Sara showed interest in helping the initiative.
    -Sylvia shared insight about root and rebound webinar.
    -We had little discussion on the assignment: CA laws related to expungemen

@sylvia-nam
Copy link
Member

sylvia-nam commented Mar 15, 2024

[3/15/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia
  • Melissa

Note taker

  • Analicia
  • Sam
  • Ann
  • Britney
  • Sara
  • Sylvia
  • Melissa

Announcements

Recurring Items

  • Team alignment and check-in
  • Updates from Design and Content:
  • Launch Prep priorities for UXR: 1) Understand expungement in CA, 2) Content Terminology
  • For Launch Prep priorities, identify: 1) Tasks, 2) Benchmarks, 3) Deliverables, 4) Division of labor

New Items

Notes from Meeting

  • Analicia's work schedule is heavy: one suggestion is to add a co-PM, and/or to add processes to onboarding to ensure that her institutional knowledge isn't lost.
  • Updates from collab meeting (Design + Content + UXR): the color system needs to be changed based on IUT testing, Sara on our team will be providing research to support the issue, including research on best practices, research on color that brings together academic literature (anthropology, disability studies to get at accessibility if applicable). Design also had a discussion on typography (currently Roboto), so the issue has expanded to include color and, also, typography
  • The other discussion during the collab meeting was about the LG overall, spec how to reduce the cognitive load of a user writing a letter requesting expungement. Some possibilities to get at the question of revamping the LG post-Launch Prep and during Launch Prep 2.0: through a gap analysis and a heuristic evaluation. Analicia and Sam point out how the LG's functionality and usability have been ongoing discussions at least since last year (maybe longer).

Resources shared during the meeting:

  • UXR specific FigJam board is here
  • Sylvia is working on a graphic on the expungement process DOC Issue Create expungement process graphic #1173
  • Sylvia created a FigJam so that we can work together on reaching a shared understanding of the expungement laws in CA.
  • Melissa will make a proposal for next week for Research Ops repository

Action Follow-up

  • Check out FigJam board on expungement laws
  • Continue researching laws individually for next meeting

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented Mar 22, 2024

[3/22/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia
  • Melissa

Note taker

  • Sylvia

Announcements

Recurring Items

  • Team alignment and check-in
  • Updates from Design and Content:
  • Launch Prep priorities for UXR: 1) Understand expungement in CA, 2) Content Terminology
  • For Launch Prep priorities, identify: 1) Tasks, 2) Benchmarks, 3) Deliverables, 4) Division of labor
  • Updating UXR understanding of current expungement laws and polices #1214
  • Discussion on team members' findings on recent expungement-related laws

New Items

  • New team members?
  • Updated UXR Glossary tied to Content Terminology Research #999. For discussion: revised research plan, how to collab with Content team, future research direction
  • Sara will present research plan on Design request for UXR support for color system and typography

Notes from Meeting

Team member updates

  • Two departures: Britney has new job and finished her Ph.D. (yay!), and Ann is returning to Taiwan
  • Sam is reducing time on UXR team

TYPOGRAPHY AND COLOR

  • Sara's research on typography and color: secondary research on website trust, color theory, and accessibility based on dif lit
  • Findings: blue (towards darker) most trustworthy, sans senif most trustworthy
  • Things to consider: users made judgments in > 3 seconds, visual appeal vary by demographics and culturally-informed
  • Color theory: framework for how people perceive and react to dif color and combinations
  • How a user feels (aesthetic qual) impacts how a user feels about a website
  • Classical aesthetics (cooler colors - blue, green, purple) v expressive aesthetics (warmer colors - orange, red, yellow)
  • Alignment between visual design and product brand
  • How will Design balances legal and modern, and how prioritize moving forward?
  • Currently the design of the website is purple closer to pink
  • Recommendation: context matters to context so blue, and meanings of color are culturally informed and lit focuses on western contexts
  • Blue: reliability and trust and safety (most govt sites like NSF, Facebook)
  • Purple: wealth, romance
  • Color saturation: low levels of images and color saturation increases trust, lighter blue -- friendliness, darker blue -- somberness
  • Alt to blue in high-risk websites: green and greys
  • Also the need to understand interaction between color, typography, and graphics

Typography

  • Line spacing affects users' trust -- 1.5 enhances comprehension and readability
  • Tight spacing and mixed images and high density of color -- appeals to younger audience
  • Moderate spacing -- formal and white space
  • High spacing -- calm
  • Serif - can be classical
  • Sans Serif - can be classical
  • Both serif and sans serif are considered trustworthy
  • Too rounded and decorative are not trustworthy
  • Roboto: considered more informal but hits balance between professionalism and modern

Accessibility

  • Now a lot of online tools that integrate accessibility issues with color scheme
  • Tools: ACE (developed by researchers in Scotland in 2017), Adobe Color
  • Before ACE, color was considered from pov of aesthetics and not accessibility
  • San serif typeface is accessible to people with dyslexia

Recommendations

  • Decide web design priorities (clarity v originality)
  • Consider what elements of design to balance out based on design priorities
  • Consider color options in relation to: saturation, font, spacing, graphic styles (if sticking with existing color palette, then consider serif font, if not blue with existing Roboto)
  • A/B testing

Comments

  • Goes well with V&T (supportive, straightforward, and trustworthy), and branding initiative
  • Will present to collab
  • Branding contact Amanda should also attend
  • Can Sara look more into illustrations based on her background on communications and linguistic anthropology, rounded lines communicate femininity and neutrality

Action Follow-up

  • Sara will present at next collab meeting

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented Mar 29, 2024

[3/29/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia
  • Melissa

Note taker

  • [ ]

Announcements

Recurring Items

  • Team alignment and check-in
  • Updates from Design and Content:
  • Launch Prep priorities for UXR: 1) Understand expungement in CA, 2) Content Terminology
  • For Launch Prep priorities, identify: 1) Tasks, 2) Benchmarks, 3) Deliverables, 4) Division of labor
  • Updating UXR understanding of current expungement laws and polices #1214
  • Discussion on team members' findings on recent expungement-related laws

New Items

  • New team members?
  • Updated UXR Glossary tied to Content Terminology Research #999. For discussion: revised research plan, how to collab with Content team, future research direction. Sylvia will present Glossary and findings from Root & Rebound webinar at All Teams
  • Sara will present research plan on Design request for UXR support for color system and typography at All Teams next week
  • [ ]

Notes from Meeting

Action Follow-up

  • [ ]

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented Apr 12, 2024

[4/12/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia
  • Melissa

Note taker

  • Sara

Announcements

Recurring Items

New Items

Notes from Meeting

First we did an overview about April’s all teams meeting last Friday. In that meeting, Sara presented her findings on color and typography and it was established that Launch Prep will now be called Stakeholder Review, to describe that we’re waiting to meet the approval from Bonnie. Content and design team are all meeting their issues and internal milestones. For our team, our priority is to gain competency and expertise in expungement and content terminology.

We talked about several issues within and across our teams, namely the iterative nature of research related to expungement in CA and the need for it to be ongoing. (Especially because policies change throughout time). One of the issues discussed was how to communicate findings (and all our rich information gathered on expungement) to other teams. Analicia suggested we have a rotating issue where the research team shares quick general information on expungement in CA, at an all teams meeting every 6 months. This can serve both as a refresher and as an opportunity to talk about any changes in the process.

A potential priority for Launch Prep 2.0 - The team is at a good place of understanding the process of expungement, so a priority would be to figure out how to communicate that across teams.

Another new issue for the UXR team is to identify our target user. Analicia said she could create that issue. Currently work is being done based on assumptions of the target user, so it would be good to work on identifying our target users’ characteristics.

There are questions about how to communicate or implement changes within content based on the UX glossary.

To improve our internal team’s goals and process, Analicia will create an issue template that serves as a guide/action items for what to do after research is done.

Analicia explained how Bonnie had visualized this process: create an excel sheet with one column with findings, and next column with an action item. And the item becomes an issue for another team.

We’ll keep using Github issues for now. After findings are shared, UXR creates an issue with action items for another team to work on. Sara for example will create issues for design team to reconsider new visual style.

For content, UXR can create action items for collaboration and an issue with action items on what to do with the glossary.

Another priority for milestone 2 is to revise how information is presented on the site.

Action Follow-up

  • [ ]

Items for next week's agenda

  • [ ]

@hackforla hackforla deleted a comment from saraisabelcf Apr 13, 2024
@sylvia-nam
Copy link
Member

sylvia-nam commented Apr 18, 2024

[4/19/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia
  • Melissa
  • Maria

Note taker

  • Sylvia

Announcements

Recurring Items

New Items

Notes from Meeting

  • What is the definition of Information Architecture? How to collab with Content it?
  • At next collab meeting, talk about IA with Content and Design, and what do you do with IA
  • But without target user, can we determine the next steps?
  • First metric -- is the information on the website correct? No
  • What matters less (for now) is the user, but rather subject matter
  • Step 1 is presenting information accurately > create issues called expungement basics
  • Since now it is CA specific, we need to update the site
  • Then we can make decision about target user and later determine how we structure and organize information according to user
  • GitHub is supposed to be the tool we should use before we use another tool, we need to give GitHub a fair shot, cleaning up some of the ways we use GH
  • Let's do an audit of our own pages on Wiki
  • What are pain points when it comes to process (for comms and collab) -- not using GH as much as we should, onboarding, Wiki
  • Is there a process for Content x UXR x Design? We could create a process for Content: before you rewrite X, you must do YZ
  • Larger question for PMs and Leads - how do we build a mechanism to ensure that information on website is correct. UXR team needs to create processes to ensure that we remain experts in expungement as a min pre-requisite so that if anyone leaves, the site can have checks and balances. No one in Content knows enough about expungement right now, and so UXR needs to maintain a channel to inform them.
  • Create a set of documents that you can constantly refer to: UXR glossary, Wiki, expungement laws doc that UXR can regularly update, and that Content Lead will know to refer to.

Action Follow-up

  • Audit our own Wiki

Items for next week's agenda

  • Mechanisms for ensuring that information on website is correct

@sylvia-nam
Copy link
Member

sylvia-nam commented Apr 24, 2024

[4/26/2024] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia
  • Melissa

Note taker

  • [ ]

Announcements

  • Use GitHub for project management: work is only authorized if it is on the board. Write up issue > will be in column for approval > discussed by PM and Lead > moved to the prioritized backlog column > assigned > active > etc.
  • Other HfLA best practices: make comments on GitHub board, Slack can be used for communication to notify someone to take a look at GitHub but for documentation, transparency GitHub is primary, Slack / Figma / Google Drive secondary
  • On creating issues on GitHub

Recurring Items

New Items

Notes from Meeting

Action Follow-up

  • [ ]

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented May 9, 2024

[2024/5/10] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia
  • Melissa

Note taker

  • [ ]

Announcements

  • Melissa will off board soon

Recurring Items

  • Team alignment and check-in
  • New UXR team members?

New Items

Notes from Meeting

Action Follow-up

  • [ ]

Items for next week's agenda

  • [ ]

@github-actions github-actions bot added the issue level: missing This issue is missing an issue level label label May 12, 2024
@sylvia-nam
Copy link
Member

sylvia-nam commented May 16, 2024

[2024-5-17] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia

Note taker

  • [ ]

Announcements

Recurring Items

  • Team alignment and check-in
  • Auditing our Wiki page

New Items

Notes from Meeting

Action Follow-up

  • [ ]

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented May 22, 2024

[2024-5-24] Agenda and Notes

CANCELED: move agenda to next week

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia

Note taker

  • [ ]

Announcements

Recurring Items

New Items

Notes from Meeting

Action Follow-up

  • [ ]

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented May 31, 2024

[2024-5-31] Agenda and Notes

Attendees

  • Analicia
  • Sam
  • Sara
  • Sylvia

Note taker

  • Sylvia

Announcements

  • No meeting next week
  • All Teams meeting next week

Recurring Items

New Items

Notes from Meeting

Color testing

  • What are KPIs for testing new color system: can be indicator X will be a measure of trust
  • How will Sara measure outcome?
  • In the past, KPIs are set somewhat arbitrarily but we never refer back to them
  • What is goal? What is the indicator that we've reached the goal. AND how to get back to it
  • Qual data should be measured qualitatively, quant data should be measured quantitatively

Brainstorm for Wiki and Slack's Canvas

  • What do we have on the Canvas? What do we have on Wiki?
  • What are the headers of what we'd like to see?
  1. General rules and expectations: how to use Slack, how to use GitHub
  2. Research repo: before you take up an issue, make sure you review expungement presentation, linked to Wiki
  • Before you start on issue, do these 1-2 things. What are they?
  • Rules and expectations
  1. Current and past research: problem is that research is relative. How do we categorize. Do we create a legend that outlines past work.
  • What would be user friendly
  1. Not on the Wiki -- issue templates
  • Research team: 1st issue > processes > ready for lead. Have you read through expectations and rule: check this box and answer this question. Expungement background: check this box, answer this question. Current and past research: check this box, answer this question.

Research templates

  • for Sara -- was the template she used helpful? For Sara prompts were useful, already there. Less intimating
  • Incorporate research templates into UXR practices #1395
  • If we use research templates, they are tweaks because they're HfLA templates. If they're revamped templates, we need to get okay from Bonnie

Action Follow-up

Items for next week's agenda

  • [ ]

@sylvia-nam
Copy link
Member

sylvia-nam commented Jun 14, 2024

[2024-06-13] Agenda and Notes

Attendees

  • Analicia
  • Sara
  • Sylvia

Note taker

  • Sylvia

Recurring Items

  • [ ]

New Meeting Items

  • Define roles and responsibilities of research team
  • Sara on illustrations research

FYI

  • PM transition
  • GitHub board migration
  • Sylvia out 6/28

Notes from Meeting

ILLUSTRATIONS

  • Sara will start illustrations research
  • Question for Design: what do they want to accomplish with illustrations? How does the Design team convey what that is? Is it seriousness or friendliness?
  • Draft a set of questions for Design as a background issue? Or as an Agenda item
  • Can you do a stakeholder interview with Design?
  1. What questions do you want to be answered with this research project?
  2. What types of answers are you expecting or assuming? (Great for uncovering biases!)
  3. What is the ideal outcome for you?
  4. What decisions are you trying to make with the insights from this research project?
  • Worth thinking about how to integrate into research templates
  • @saraisabelcf will write up the issue on research on illustrations
  • Incorporate illustrations to existing color research? Or to proceed as discrete issues?
  • Wait to do research on illustrations?
  • Clarify with Design on where they are in illustrations?
  • How to collab on the order of operations: to collab on illustration revisions before and not after
  • Sara will post on Slack who the point person is? @sylvia-nam @amejiamesinas -- can ask for update at next PM and Leads meeting to follow-up

DRAFTING ROLES AND RESPONSIBILITIES OF OUR TEAM

  • Draft: provide support dev, content, design teams in 3 ways: 1) building expertise and repository in expungement laws in CA (foundational knowledge), 2) collaborate with design, content, dev to use best practices in user research, 3) evaluation of product 
  • Analicia on number 3: is too vague to say so in spec ways -- add "ongoing" evaluation of product
  • What's the goal here: to provide feedback, it's not explicit in this draft. It's not obvious that we are trying to do so that supports decision-making in product development, and to ensure good user experience
  • Build in context for the overall product development
  • Sara's comments via Slack: 2) maintaining collaborative process with design, content, dev to support product decisions and ensure best practices in user research, 3) evaluation of product through ongoing research to provide feedback and ensure quality of product quality

Task Items

  • [ ]

Items for next week's agenda

  • Revisit draft of roles and responsibilities of our team and to revise again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation feature: agenda issue level: missing This issue is missing an issue level label priority: low role: product management role: research UX and other research size: 1pt can be done in 6 hours or less
Projects
Status: Start Here
Development

No branches or pull requests