Figma Foundation Design and Research

[allthatyazz]

trafficstars

Overview

We need to build tutorials and templates so that HfLA's projects have a way to guide themselves in the building of consistent and effective Figma files for their team.

Details

HfLA’s Design Systems (DS) team has conducted a series of audits on 22 HfLA projects’ main Figma files since November 2021. The audits revealed a lack of consistency in the way each team creates and maintains their Figma files. In response to the needs of HfLA’s Executive Director (Stakeholder) and with the aim of creating consistency across the organization, the DS team proposed a guide called Figma Foundations. Figma Foundations includes a set of instructions and templates for current and future teams at HfLA to adopt.

Note from ED: When all the templates and tutorials are completed, it can collectively be known as Hack for LA's Figma Foundations and will all use the same Design System, so the experience is consistent. But each resource that we produce (i.e. cover page, tutorial, template) must stand alone as a usable resource, being both self-explanatory and useful without the other resources.

Action Items

• [ ] Create a new issue with the following template of Action Items and Resources. Repeat for each section of Figma Foundations:
  • Cover page
  • Start page
  • File menu
  • Plugin library
• [ ] Add the created issues to the list of issues at the bottom of this comment

### Action Items
- [ ] Each issue gets the label "**feature: [section]**"
- [ ] Each issue gets the milestone "**Figma File Foundations**"
- [ ] Copy issue templates from https://github.com/hackforla/design-systems/issues/396
- [ ] Tutorial & Template: [section]
  - role: design
  - size: 1pt
- [ ] Example [section]
  - role: design
  - size: 1pt
- [ ] Plan the [section] usability test
  - role: research
  - size: 5pts
- [ ] Give feedback on [section] usability test plan
  - role: design
  - size: 1pt
- [ ] Usability test the [section]
  - role: research
  - size: 1pt

### Order to conduct work
- Create Tutorial & Template
- Create Example Page
- Create a Usability Test plan
- [ ] Design team informs the research team they are ready for the pilot to be conducted
- Usability research plan review feedback from Design Team
- Design Team provides researchers feedback on the Usability Test Plan using the FigJam file (e.g., if a designer has a specific question that hopes to find an answer through user's feedback.) 
- [ ] Research Team incorporates the designers' feedback into Test's script (see Usability Test Plan)
- [ ] Design performs the last review to ensure their goals are met.
- Conduct user research
- Analyze the usability findings

 
### Resources/Instructions
- [Figma Foundations]( https://www.figma.com/file/5NacfOm45QlrWgr6wWEg4k/Design-System-Template-for-HfLA?node-id=2%3A7) 
- [FigJam to exchange feedback between research and design](https://www.figma.com/file/mmvbxZ6lctjQneEeqTjC8O/UX%2FUI-Discovery-FigJam?node-id=0%3A1)
- [Google drive contains Usability Test plans](https://drive.google.com/drive/folders/1U7f9yH0VZgZPxtpAru5RL1LmIJo9ghfz?usp=sharing)

Resources/Instructions

Figma Foundations FigJam to exchange feedback between research and design Google drive contains Usability Test plans

List of issues

• [ ] https://github.com/hackforla/design-systems/issues/392
• [ ] FF: Section Work Overview: Start page

[ExperimentsInHonesty]

@allthatyazz Which of the issues above cannot be done because another issue will have to be created first?

For instance, can the research plan be made before the following?

• [ ] Tutorial & Template: [name of section]
• [ ] Example Page: [name of section]

I ask because it will help with the answer to your original question about what to do with the issues. If one issue is dependent on another, we can put a dependency label on it, put it in the backlog. But it would be good to know that now, so we can sort out the template, to reduce the time you spend making issues from scratch.

Also, you will notice that I specify above a label for p-feature: [name of section] (e.g., p-feature: cover page) If we make a label for each section, then you will be able to see where they are in flight and how close to finished (time wise)

[allthatyazz]

@ExperimentsInHonesty First thank you for reworking the issue. The breakdown and organization of content look amazing.

About the dependency label, I suppose because we are using a similar format for all different sections, the research team can start working on the general format of the research plan.

So we can include a dependency label on the following issues.

• Usability research plan review feedback for [name of section]
• Conduct user research

[ExperimentsInHonesty]

@allthatyazz Generally what we are looking for are issues to be closed which releases the dependency on another issue. But we don't quite have that here. See what I mean: https://github.com/hackforla/design-systems/issues/392 Did I put the dependency on the wrong issue? Or was it the wrong dependency? Also what issue would be the dependency that gets released in order to work on Conduct user research?

[allthatyazz]

@ExperimentsInHonesty I see what you mean. The dependency you added is correct. I added the other dependency for Conducting user research. I just realized that the other issues should be reworked so they correctly reflect the dependency.