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

• [x] Define places to look for glossary words
• [x] Create spreadsheet within Google Drive (using template)
• [x] Look in resources below for terms that might need to be defined and fill into spreadsheet
• [x] Complete peer review (steps will be added in comment below)
• [x] UX Research Lead signs off on peer review
• [x] 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

[Nat-nn]

Great. Thank you. I will look into it.

[epierotti3]

Update:

1. Progress: Issue created by @epierotti3 - left role as missing because this could be worked by any new team member regardless of role. @Nat-nn is working on this as of now after we reviewed the issue and addressed the blocker of what kind of terms should be put into the glossary. Answer: any term that is unclear to a TWE team member!
2. Blockers: N/A (Natalia - you can add blockers if they arise to your next update).
3. Availability: N/A (Natalia - you can fill this in on your next update)
4. ETA: N/A (Natalia - you can fill this in on your next update)

[ExperimentsInHonesty]

I updated the spreadsheet to have the branding.

[bradyse]

@Nat-nn Please provide update

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

[Nat-nn]

1. Progress: Added 20+ additional terms, discussed existing terms with the team during a meeting 09/06/22.
2. Blockers: Need to confirm how many terms we want to include, need to verify the scope.
3. Availability: 2-3 hours / week
4. ETA: 2 weeks (by 09/22/22)
5. Pictures or Links: (if necessary): Link: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit?usp=drive_web&ouid=115085926732799078164

[ExperimentsInHonesty]

Notes from meeting 2022-09-08

• add where term appeared
• add who benefits categorization

[Nat-nn]

My update 09/15/22 :

1. Progress: Updated who benefits and added links; Added several new terms.
2. Blockers: Who benefits - need some clarification; Where located: Are we trying to find only 1 location or want to add all locations where we have it coming up?
3. Availability: 2-3 hours
4. ETA: 2 weeks (by 09/22/22)
5. Pictures (if necessary): N/A

[Nat-nn]

Discussed during the meeting: Scope of the project, terms needed. Next Steps: To update sources/ links

[Nat-nn]

Progress: Updated Glossary (added additional terms, Updated links and added term reference pages) Blockers: Need Team Lead to review, to confirm Ok to add to WIKI Availability: 1-3 hours per week ETA: After next UX team meeting Pictures or links: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit#gid=0

[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]

@Nat-nn

• Difference between "Official Link" and "Review Link" is that the official link includes the most reputable, credible source that defines that term. Review is simply where we are referencing it for the time being.

Please provide update

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

[Nat-nn]

Progress: Added additional terms, ready to review. Blockers: Need to get Team lead approval for general links. Availability: 1-3 hours per week ETA: After next UX team meeting Pictures or links: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit#gid=0

[bradyse]

Setup for a Peer Review

• [x] Confirm with UX Lead that this document needs a peer review.
• [x] 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.
• [x] In the Resources, clearly identify the link to the document being created or updated that requires a peer review (use subheadings if needed).
• [x] Copy and paste the Action Items for Peer Review into a comment of the issue.
• [x] Customize the Action Items according (adding items that are more relevant to this issue and removing items that are less relevant).
  • [x] 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).
  • [x] 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.
• [x] For a spreadsheet review, add a column and label it "Peer Reviewer Questions and Feedback." If this step is not needed, remove this step.
• [x] 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

• [x] Review this issue
  • [x] Read the issue overview to learn about why this document was created.
  • [x] Locate draft of the document or spreadsheet in the Resources.
• [x] Review draft
  • [x] Preview the draft quickly to get a sense of how the draft is structured and the type of content.
  • [x] Review the structure of the draft to ensure that the headings (in a Google Doc) or columns (Google Sheet) are clearly identified.
  • [x] Determine if the information is communicated in a way that is concise, precise, and free from jargon.
  • [x] Identify whether the draft adheres to the basic branding guidelines for the project (see Branding or Design wiki link in Resources).
• [x] Provide feedback
  • [x] 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.
  • [x] 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.
  • [x] For each suggested improvement, provide a link or reference within your comment to justify your suggestion.
• [x] Specific to this issue:
  • [x] 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".
• [x] 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.

[bradyse]

@Nat-nn

I have added the actions items for a peer review. Now we need to assign a peer reviewer to your issue. Perhaps @adarosh or @lkawentel would be interested in conducting this peer review (assuming that they don't currently have an issue to work on). If one of them cannot do it, then I would reach out to some of the other team members.

[Nat-nn]

Progress: Updated terms and links, moved project to 'peer review needed' status Blockers: Wailing for "Peer Review" Availability: 1-3 hours per week ETA: After next UX team meeting Pictures or links: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit#gid=0

[sophie-delsaux]

Progress: Reviewed the issue and draft and started to give feedback Blockers: I have overall feedback but the format only allows me to provide detailed feedback. Not sure if the "who benefits" column is really for who would benefit from the glossary or based on where the terms appear. Availability: 2h ETA: this week Pictures or link: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit#gid=0

[bradyse]

@sophie-delsaux

Thanks for your work on this. The "who benefits" column is who would benefit from knowing the term. For example, the "TWE" acronym would benefit our team but "content analysis" would benefit anyone within the organization of HfLA.

If you have any general comments, you can add them in the first row of the next column over.

[Nat-nn]

• Progress: Added Term the definition (per suggestions from the team meetings). After All team review it was decided to remove ' column blocking', this way we can see the term right away (and there is no need to add the term itself into the definition) Going to leave this issue now and work on a different issue.
• Blockers: Was Waiting for the 2nd "Peer Review"
• Availability: 1-3 hours per week
• ETA: Leaving this issue, going to work on some other issue
• Pictures or links: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit#gid=0

[bradyse]

@Nat-nn

Please go through each description and revise the formatting such that the description starts with the term in bold and is followed by a verb (not a hyphen).

✅ TWE Intern is in the correct format. ❌ Mentor uses the incorrect format.

[Nat-nn]

Progress: Updated term formatting (per review comments).
Blockers: Waiting for Team lead approval Availability: 1-3 hours per week ETA: after Holidays (January 2023) Pictures or links: https://docs.google.com/spreadsheets/d/10omnFb1L8lM4n4Rz610UzI1E51ZMRG6tuVnphrYnay0/edit#gid=0

[dialectic51]

I am currently conducting a peer review of the Glossary Draft spreadsheet. Is there any reason why the terms aren't in alphabetical order? Should they be?

[dialectic51]

@pandanista @bradyse @Nat-nn

I have completed my peer review of the draft of the glossary for the wiki page. All of my feedback is limited to the Peer Review Questions and Feedback column, with the exception of eliminating extra spaces or adding periods to the end of sentences (or, in rare instances, some very light editing). In the Peer Review column I indicate which component of the wiki glossary requires revision. When necessary, I provide links to sources to justify suggested revisions.

I believe that the next step is for the UX Research Lead to sign off on the peer review. According to the Sara's comment, I'm also supposed to reach out to the original owner of the issue to see if they can complete the issue. However, I don't think that Natalia will have time to do this. If necessary, I could make the revisions, but since I currently have a number of other items on my plate (issue 338 and some guides), I think it would make the most sense to assign it to someone else--the process should be pretty straightforward.

[dialectic51]

Provide Update

1. Progress: Completed.
2. Blockers: Requires sign off by UX Research Lead; original owner (or new UXR) will then complete the issue.
3. Availability: As needed.
4. ETA: Completed

[pandanista]

UX lead reviewed the glossary as of 1/19, and discussed the first 11 terms during the team meeting on 1/20. Waiting on product and team to finish the review.

[priyatalwar]

1/31 Update: I was under the weather, but I've reviewed the comments. I need more time to review rest of the doc. I should have it ready for sign-off at our 2/6 meeting.

[ExperimentsInHonesty]

@priyatalwar, I have added a new column for proposed description. Please use that to take the Peer Reviewer Questions and Feedback and provide a revised description (if applicable).

[priyatalwar]

2/6 Added proposed description where applicable. We will review on 2/8.

[cbutcher318]

Provide Update

1. Progress: Just starting
2. Blockers: None yet
3. Availability: 2 hours
4. ETA: Middle of next week (~2/14)

[cbutcher318]

Progress: added a column with new proposed descriptions, ready for review

[ExperimentsInHonesty]

@cbutcher318 Please bring this up at our very next meeting (where I attend)

[pandanista]

We will add t-test and paired t-test to the glossary per #375 since it will be used as one of the data analysis technique.

[pandanista]

Assigning @adarosh to this issue so she could add some statistic concepts such as t-test into the glossary.

[pandanista]

T-test, paired sample t-test, independent sample t-test, significance test, N0, descriptive, inferential, Chi-square, mean, median, SD

[pandanista]

Please provide update:

1. Progress: "What is the current status of your project? What have you completed and what is left to do?" - we know you just came back from break, please just summarize the progress from before then
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.

[pandanista]

@adarosh The review link is for product to reference where the term was used or discussed to provide more context. For paired t-test, we can refer to issue #375 and RP019 research roadmap. Hope it helps.

[adarosh]

Progress Update:

Progress: Added the following terms with their definitions to the glossary: t-test, paired samples t-test, independent samples t-test, statistical significance, hypothesis testing, null hypothesis, descriptive statistics, inferential statistics, chi-square test, mean, median, standard deviation. Blockers: None Availability: N/A ETA: N/A Pictures (if necessary): N/A

[pandanista]

@priyatalwar I've reviewed the definitions of a handful statistical concepts we have decided to include for the glossary.

Please see the newly added rows filled in blue color in column A of the Glossary Draft spreadsheet. Let me know if you have any questions.

If Product approves the updates, then we can move on to the next step to include the glossary to the wiki page.

Thank you.

[sunannie27]

Next step: copy content to new columns

[sunannie27]

1. Finished reorganizing proposed descriptions and feedback in alphabetical order to match the terms. Reviewed the who benefits column and made edits/comments.
2. N/A
3. The issue should be completed.
4. Should be done

[ExperimentsInHonesty]

Next step, review each set of previous reviews and identify your proposed description from what is already there or write your own.

[sunannie27]

1. Progress: Have to go through most of the descriptions and/or write my own
2. Blockers: None
3. Availability: 1 hour
4. ETA: Within 2 weeks

[ExperimentsInHonesty]

KC will do another review

[KC-skc]

Review completed. Ready for final product review.

[ExperimentsInHonesty]

@KC-skc Do you think we need the word ultimately in this definition?

End User is the person who ultimately uses the product or service.

[sunannie27]

@KC-skc Before

Card Sorting is a UX research method where study participants group "words" or "phrases" written on notecards (physically or virtually) according to categories that make sense to them. Card sorting could be open (participants make up the categories), closed (researchers provide the categories), and hybrid (a mix of the two).

Your proposed description

Card Sorting is a research method commonly used in UX where participants categorize "words" or "phrases" presented on notecards (physically or virtually) according to categories that make sense to them. Card sorting could be open (participants make up the categories), closed (researchers provide the categories), or hybrid (combining both).

Why did you change UX research method to a research method commonly used in UX?

[ExperimentsInHonesty]

@KC-skc For this definition

Evaluative Research is a research method used for assessing whether a product or proposed solutions addresses users' wants and needs.

I found the following other links that say it's not a method https://www.questionpro.com/blog/evaluation-research-definition-methods-and-examples/ Evaluation research, also known as program evaluation, refers to research purpose instead of a specific method. Evaluation research is the systematic assessment of the worth or merit of time, money, effort and resources spent in order to achieve a goal.

Google search for Evaluative Research, where the previews seem to indicate same

[sunannie27]

@KC-skc

Foundational research (also referred to as generative research, exploratory research, pathfinding research, or discovery research) attempts to identify and solve a real human problem. The problem centers on a topic or area that has not been clearly defined or explored in the past.

Do you agree that generative research is the same as foundational research? If so, I think we can just put "see foundational research" in the definition for generative research instead of its own definition

[ExperimentsInHonesty]

@KC-skc

Exit Interview is a meeting between management representatives and a person who is leaving an organization or project. The purpose of an exit interview is generally to incorporate the findings to improve the program or product.

Do we need to specify (can be researchers)? Exit Interview is a meeting between management representatives (can be researchers), and a person who is leaving an organization or project. The purpose of an exit interview is generally to incorporate the findings to improve the program or product.

[ExperimentsInHonesty]

Bonnie left off on her review at Exit Interview. Will continue later.

[KC-skc]

End User

Do you think we need the word ultimately in this definition?

End User is the person who ultimately uses the product or service.

@ExperimentsInHonesty I think it could go either way. Since the original word is "End" User, it's okay to emphasize with ultimately, but it can go either way.