Populate Glossary Wiki Page

[epierotti3]

Dependencies

This glossary needs a peer reviewer to review the "Who Would Benefit" column.

Overview

We need to find terms to fill into the TWE Glossary Wiki Page so that this page is no longer empty. The TWE Glossary will educate new team members on the common terms used by the TWE team and HfLA in general.

Action Items

• Define places to look for glossary words
• Create spreadsheet within Google Drive (using template)
• Look in resources below for terms that might need to be defined and fill into spreadsheet
• Complete peer review (steps will be added in comment below)
• UX Research Lead signs off on peer review
• Bring to team meeting for review
• Once approved, can copy words into wiki page

Resources

Draft of Glossary

• Glossary Draft spreadsheet (located in Internships > wiki)

Relevant Wiki Pages

• Glossary Wiki Page
• Templates & Product Branding

Places to look for glossary words

• Wiki
  • Research Plans listed for Parents/Guardians
  • Research Output Overview
  • Every page on the wiki should be checked for unclear terms
• Figma
• Google Drive

[ExperimentsInHonesty]

Notes from meeting

• We can link the where found, to the location it was found in
• official link, refers to either the domain holder or a wiki article, etc.
• line returns can be made in sheets by using alt-enter
• moved links for the team to work on this glossary, to the new column Review links
• rules for when to include link to where you found it
  • when the place it came from helps understand the context
  • where we might want to update the reference in the future
• Who Benefits
  • HfLA items should be applicable to all projects
  • TWE items should be specific to our project (they can also be subsets of more general terms)

Next Steps

Natalia will

• Revisit the who benefits
• move links to where term appears

[bradyse]

Setup for a Peer Review

• Confirm with UX Lead that this document needs a peer review.
• Check if the Issue Overview clearly defines why this document needs to be created or updated. If it is not clear, add that information to the overview in 1-2 sentences.
• In the Resources, clearly identify the link to the document being created or updated that requires a peer review (use subheadings if needed).
• Copy and paste the Action Items for Peer Review into a comment of the issue.
• Customize the Action Items according (adding items that are more relevant to this issue and removing items that are less relevant).
  • Replace the text in square brackets with the name of the document that requires a peer review (use the same name as it is called in the Resources).
  • If you have a specific task that you want the Peer Reviewer to accomplish for their peer review that is nuanced to your issue, add that as a final action item to the list.
• For a spreadsheet review, add a column and label it "Peer Reviewer Questions and Feedback." If this step is not needed, remove this step.
• Determine who will do the peer review and unassign yourself to this issue and assign the peer reviewer to this issue.

Action Items for Peer Review

• Review this issue
  • Read the issue overview to learn about why this document was created.
  • Locate draft of the document or spreadsheet in the Resources.
• Review draft
  • Preview the draft quickly to get a sense of how the draft is structured and the type of content.
  • Review the structure of the draft to ensure that the headings (in a Google Doc) or columns (Google Sheet) are clearly identified.
  • Determine if the information is communicated in a way that is concise, precise, and free from jargon.
  • Identify whether the draft adheres to the basic branding guidelines for the project (see Branding or Design wiki link in Resources).
• Provide feedback
  • Add feedback in the form of (1) questions and/or (2) explicit instructions for how the content should be improved. Feedback in a Google Doc should be given in the form of document comments. Feedback in a Google Sheet should be given in the column labeled for Peer Review.
  • Determine the accuracy of the content for each section (doc) or row (sheet). If you find an inaccuracy, error, or mis-categorization, explain how the information presented could be improved.
  • For each suggested improvement, provide a link or reference within your comment to justify your suggestion.
• Specific to this issue:
  • Make sure that the "Who Benefits" column is accurate. If a term is used exclusively for TWE, then it should be identified as "TWE Team Members," but if it is a term used outside of the TWE Team, it should be identified as "HFLA General".
• Once all the steps have been completed, reach out to the original owner of this issue to determine if they can complete the next steps in the issue.

[ExperimentsInHonesty]

• archetype and personas glossary entries

Current Glossary entry:
Persona is a user archetype, often with description, that helps designers and developers empathize with their users' business and personal contexts.

Please review this article https://www.nngroup.com/articles/personas-archetypes/ and revisit this definition and make sure we have both

Personas and archetypes in UX are two slightly different ways of visualizing the same kinds of insights. Both summarize user research data: they are representations of audience clusters, capturing major areas of overlap in user behaviors, attitudes, motivations, pain points, and goals. (Note that these clusters are not based on either demographic characteristics such as age, country, income or personality traits such as extraversion and openness.) By finding these clusters of users, we end up with a small set of composites that showcase key characteristics and major differences across a few types of users. In that respect, personas and archetypes are identical.

The difference between them is in whether each one of those user types is presented as a specific human character. With personas, we invent a (plausible) name, bio, photo, and other personal characteristics, whereas with archetypes, we omit those details and refer to the user type merely by an abstract label that represents the defining behavioral or attitudinal characteristics of that user type.

[ExperimentsInHonesty]

I left off on Qualitative Analysis

[ExperimentsInHonesty]

What is missing from this definition of Qualitative Analysis is that it's the analysis of free form word answers shared by the research participant

Qualitative Analysis is a research methodology used to anwer questions and often used to understand the motivations, thoughts, and attitudes of a target audience. Qualitative analysis can involve coding, content analysis, and thematic analysis of oral or written data to reach conclusions.

[ExperimentsInHonesty]

left of on Qualitative Research

[KC-skc]

@bonniewolfe

Edited Persona to add archetype. Please let me know if this is acceptable, or whether you'd prefer a separate entry for 'archetype'.

Persona is a detailed fictitious profile. These descriptions helps managers, designers and developers empathize with their product users' business and personal goals, needs and behaviors. While personas are specific, in comparison, archetypes label abstract characteristics.

[KC-skc]

Qualitative Analysis definition updated per above comment to add examples of qualitative data.