CoP Onboarding Prep: UI/UX

[rfambro2]

Overview

We need to prepare the UI/UX CoP project board so that new members of our community can have something work on immediately.

Action Items

• [x] Create README for UI/UX CoP
• [ ] Create a template and related labels for new guides
• [ ] Turn Icebox items into Guide issues
• [ ] Edit Readme with steps for getting involved and current major initiatives

Resources/Instructions

UI/UX Community of Practice UI/UX Community of Practice management board UXR pilot findings

[tan-zhou]

Work with Bonnie and Danielle to turn Ice Box cards into issues in Prioritized Backlog

[tan-zhou]

We created issue templates for

1. creating a guide
2. designing/conducting a pilot

We are going to get the first batch of new volunteers without projects coming to UI/UX CoP next Monday (3/1). So we are expecting them to go through the claiming "the first issue" process at the meeting. I will be there to introduce and observe the process, then gather feedbacks afterward.

[tan-zhou]

Create a UI/UX experience profile model after the product management one This should have a list of UX/UI tasks that volunteers can do at Hack for LA (setting up a Figma page, cleaning up a Figma page...), so it serves as a roadmap guiding their next step, as well as a checklist of their accomplishment at CoP.

We need to come up with a list of UI/UX tasks. Maybe we can run a Brainstorm session to generate more ideas.

[tan-zhou]

Items for Sunday discussion:

• [x] Audit the getting started page
• [x] Discuss the entry point - after the onboarding ends and before the CoP meeting starts
• [x] Review the introduction slidesDanielle's Research
• [x] GitHub Training and assigning
  • [ ] For now, we'll ask (slack message) Olivia or Bonnie to add new volunteers to CoP board, if neither of them joins the meeting
• [ ] Walkthrough of the "claiming first issue" process
• [x] UI/UX list of tasks for Experience Profile
  • [ ] use to track tasks completed at CoP

[tan-zhou]

Issue: UX Experience Profile

Overview

Fill in the following fields as you work on these items at Hack for LA. Add the link of the items you worked on in the list as examples.

Action Items

• [ ] [Managing the project board]()
  • [ ] [Making good issues (Reference - https://www.hackforla.org/guide-pages/github-issues)]()
  • [ ] [Prioritizing the backlog]()
• [ ] [ HfLA/COPM Onboarding process Feebback]()
• [ ] [Guide Create]()
• [ ] [Template Creation]()
• [ ] [Review Wiki Guides]()
• [ ] [Competitive Analysis]()
• [ ] [User Persona Creation]()
• [ ] [Journey Map Creation]()
• [ ] [Project Roadmap]()
• [ ] [Desk Research]()
• [ ] [Figma Training]()
• [ ] [Design System Contribution]()
• [ ] [Agile Learning]()
• [ ] [HTML/CSS]()
• [ ] [Cross-funcitnoal communication]()
• [ ] [User Testing]()
• [ ] [User Interview]()

Resources/Instructions

[tan-zhou]

Outline for the COPM:

• New volunteers Setup (10 mins)
• In-process topics and discussions (20)
• Issues they have with their team (10)
• Assigning new issues (10)
• Project Role Openings(10 mins)

[tan-zhou]

Outline for March 8th meeting: All returning members are in the main room Main Room Agenda led by Danielle

• Featured/spotlight in-progress issue: effective communication between developers and designers
• Other in-progress issue updates

Breakout Room Agenda led by Tan (45 mins)

• Confirm they are added to Google Drive, roster, and GitHub
• CoP Kanban walk-through
• Explain what's expected from the first tasks and assign issues
• Going around stating the next step

Observation notes:

1. 2 volunteers followed the getting started steps, 2 didn't.
2. 3 volunteers claimed their first issue at CoP
3. Concerns about tracking progress - if people don't show up to COP meeting, haven't updated the issue in weeks, do we just gave the issue to another person? How should we standardize the check-in practice guide?

[tan-zhou]

1. 2 volunteers followed the getting started steps, 2 didn't.

After meeting with Danielle, we agree that on CoP lead will join the onboarding meeting at 7 pm to take all the volunteers to a breakout room for the first step - add to Google Drive, roster, and GitHub.

Tan will create a flowchart explaining how he structures the meeting currently.

3. Concerns about tracking progress - if people don't show up to COP meeting, haven't updated the issue in weeks, do we just gave the issue to another person? How should we standardize the check-in practice guide?

@ExperimentsInHonesty will discuss the current check-in process at product CoP with Olivia before UI/UX copies it.

[tan-zhou]

New practices to discuss with Danielle on Friday:

• the implementation of the UI/UX CoP Experience profile

  • Mandatory for everyone. One member can use it to self-evaluate their experience.

• Returning HfLA/Code for America alumni joining CoP meeting sharing their experience

  • Discuss how to frame our volunteer experience to get a job
  • Attract the old-timers who haven’t been attending as much lately

[tan-zhou]

Concerns about tracking progress - if people don't show up to COP meeting, haven't updated the issue in weeks, do we just gave the issue to another person? How should we standardize the check-in practice guide?

Refer to this issue about establishing check-in process https://github.com/hackforla/communities-of-practice/issues/2

[tan-zhou]

Last week, we introduced the new practice:

• roll call spreadsheet
• Experience profile usability tests
• I joined the onboarding at 7 pm to set up new members
• assigned new guides to new members

Before we roll out the Experience Profile, I want to verify the current Experience profile with usability tests. So far three members signed up - Bret and Sim( both Researcher), Dhwani (Designer).

Notes from Bret's session

1. Need help with navigating GitHub layers - A Help Documentation with step-by-step guides and screenshots.
2. Each Method can link to a page explaining what it is, in case someone isn't familiar with the method
3. Ability to tailor the profile to ones own experience

In the coming week, we will have

• a HfLA alumni sharing her thoughts on framing her HfLA experience in job searching

New practice needs to establish

• quality control on guides
  • we plan to assign reviews to in-progress guide

[tan-zhou]

Olivia created a guide to how to write a Guide and a document template.

In terms of peer reviewing, the author will tag reviewers.

And in the guide, if you give comment, you will be credited as well. https://github.com/hackforla/knowledgebase-content/issues/106

Assigning owners to each practice at CoP

[tan-zhou]

Tasks to Complete:

• [x] UX Experience Profile
  • [x] Document the learnings from usability testing sessions
  • [x] Create a guide for using Experience Profile
  • [ ] Cord sorting to decide the order of the list

[ExperimentsInHonesty]

to meet with UI/UX community of practice over the colors and content of the template guide. Which should be here https://docs.google.com/document/d/1-8gmeC-wnfM8C8fVvmTP1BLA2WfNjKH_XJrHB1OAV6Q/edit but is in the middle of getting fixed. You will know it is fixed when it doesn't say anything about the code of conduct.

[tan-zhou]

We need to have the pink and orange highlights on the same screenshot to control the variables.

[ExperimentsInHonesty]

guide that we put online that started this whole conversation Hack for LA guide template-WIP Demo of markdown to html

[Arjayellis]

New template for screenshots. Will be added to a guide. https://docs.google.com/presentation/d/1xu_lYuucKkBKD9jWfLDZkEv3PkmIjcFEf0MnjEJdV5c/edit#slide=id.gcd1d3ada7a_0_0

Issue about annotating the guide https://github.com/hackforla/knowledgebase-content/issues/93

[Arjayellis]

CoP's will confirm if people need role assignments and share the open roles board. We want to ensure people focus on one project at a time.

[tan-zhou]

Danielle is working with Michael Morgan in creating an annotation style for our guides.

[tan-zhou]

UI/UX Document outline

• onboarding to CoP   
• structuring meeting agenda 
• assigning guides 
• assigning reviewers 
• creating Experience Profile