Design Card Sorting exercise for the redesign of the Organization Edit Form

[gigicobos]

Dependencies

#1142 #1141

Overview

As part of our effort to redesign our Organization Edit Form, we would like to design a Card Sorting exercise to create a better UX for data entry volunteers.

Action Items

• [x] UX researchers meet to discuss plan
• [x] Action items / timeline for this issue:

1. [x] Writing the Research Plan (NEED TO UNDERSTAND METRICS CAPABILITIES)
2. [x] Writing the Invitation Message (AWAITING EMAIL ADDRESS)
3. [x] Writing the Card Sort Scripts (Invitation, Follow-up, Instructions, Interview)
4. [ ] Participants Recruitment (Calendly)
5. [x] FigJam Planning
6. [x] Meet with PM / Design to review Figma board for card sorting exercise
7. [x] Pilot Test/Analysis

• [x] 1) Screenshot Ning's results on Figma
• [x] 2) Revise Figma board
• [x] 3) Show team revised Figma board (and share summarized findings from Pilot)
• [x] 4) Script for Figma link and Zoom link and confirmed appointment
• [x] 5) Revise instructions script

9. [x] Data Collection (appx. 10 hours)
10. [ ] Data analysis (3 days)
11. [ ] Share findings (slides)

if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.

Resources/Instructions

Heutistic Evaulation to Features

Related Issues

#320

FOLA: Research Plan: Volunteer interface: Card Sort FOLA: Volunteer interface: Script FOLA: Volunteer interface: Card Sort: Invitation Message [FOLA: Volunteer interface: Card Sort: Lessons from the Card Sorting Pilot Study] https://docs.google.com/document/d/1qqyBGwteLHK4Vvt60G_DV29q7utdUlDD5TKkKZmZlp0/edit [FOLA: Volunteer interface: Card Sort: Observation note https://docs.google.com/spreadsheets/d/1UJVTscFEULlmtvIXj8L791CzjHO36atiH_bqmhupbPA/edit#gid=0

[Benbaillou]

Notes of 2022-01-12 meeting - Score card meeting preparation

Attendees: Gigi C and Gigi P, Jieun, Bryan and Ben

How the exercice will be prepared

1. Research Plan: Gigi P and Jieun to create a research plan by end of January
2. Dogfooding: G and J to test their scorecard exercice with Fola team
3. Recruitment: FOLA team to recruit 5 to 8 volunteers (experience and "rookie" volunteers)
4. D-Day: Set up a time to organise the exercice with the recruited volunteers

Tools suggested: Figjam (from Figma suites)

Note: before recruiting the volunteers, make sure we are allowed to record the test if needed

[GigiUxR]

Ben and Gigi, please check out the issue I have updated with action items/time line that Jieun and I drafted up during our meeting Friday. She and I met briefly to hammer out some items for the card sorting activity.

[Benbaillou]

@LIlinit and @ryu-jieun. It looks perfect to me. Let us know where we can help you on writing the "Script" (action #1)

[GigiUxR]

Hello all,

Please review the Invitation Message template at the below link. If all is ok with the message, Gigi C and Ben, you can begin recruiting as soon as you would like - I recall one of you had offered to take care of that (remind me if I misremembered).

https://docs.google.com/document/d/1myRrhdK_z2OOSUeUbu0cu0Jop-N2dmuPGBFenkE6YT8/edit

Action items for Invitation Message:

• Review / provide feedback
• Email address to be inserted in the invitation message
• Give access to Jieun and Gigi P for the inserted email address

[gigicobos]

@ryu-jieun @LIlinit noted I'll work on recruiting this Saturday and next week. I'll get advice from Jordan.

[Benbaillou]

@LIlinit @ryu-jieun. Well done for the script. I just suggested some modifications to turn it a little more "punchy". Feel free to keep them.

[fancyham]

Updates:

We haven't heard back from Jordan so we realized we can use our volunteer log-in database to find volunteers and their email addresses and get in touch with them directly.

@entrotech did a query on the database showing recently active and who likely called and updated org info: "To obtain an indication of the active volunteers, I ran a query to get all the application users that have modified a listing, along with their email, the last time they edited a record and the total number of edits they have made. The query itself and results as a CSV file are in the G Drive folder https://drive.google.com/drive/u/0/folders/1cycU4m60_K2fsGtdAuKtfzR9SKThUXbD Not sure if there was an issue for this specific activity to, so I just created the files for now. Looks like there are lots of good candidates for the Volunteer user testing. "

So next @LIlinit and @ryu-jieun are working on a recruiting email to send to volunteers: https://docs.google.com/document/d/1myRrhdK_z2OOSUeUbu0cu0Jop-N2dmuPGBFenkE6YT8/edit

And now we're discussing some possible recruiting and screener questions:

Me: Some possible questions: ‘how many times have you volunteered in the past year’ or ‘approximately how many orgs have you updated in the past year (1-5, 5-10, 10+)’ And perhaps ’how did you do your research (phone only, web only, facebook only, combination of the above)? (edited)

Some of those questions could be in a followup screener. Oftentimes, I’ve seen respondent signups via a Google Form — which might be useful here:

Recruiting email > They fill out Google Form with their email and answer some screening questions > You do your screening to pick out the ones you want > Send a follow up email to those people asking them to schedule a time slot > Do the interview (and ask some more demographic questions during the call if you have them)

[staceyrebekahscott]

@rylantalerico @GigiUxR A reminder to add notes to this issue explaining the Research Project you launched in the fola Slack channel.

Is it possible to explain this issue and the work being done in the context of the other issues listed as related or as dependencies:

• Original issue is #320
• Dependencies are #1142 , #1141 , #1148

I moved all of the issues listed above to Prioritized Backlog as I assume the dependency issues would be addressed next or in tandem with this one, but they had been moved to Waiting, which suggests a less urgent priority, but no explanation of this prioritization logic was given.

• Is there anything pending with these issues that the Dev team needs to work on or be aware of?
• What is the proper prioritization the related/dependent issues should be given?
• How do these issues fit in to the Research Project?
  • Is there an intention to post the Research Project on to other channels to get more participation?
  • How many participants are you aiming for in order to get the data you need?

[itserindean]

@GigiUxR I closed the related issue #1141 and #1142 as not planned. Can I close this too?

[fancyham]

Hey folks, I know this is old, but before it’s completely left your brain, are there any insights or behaviors you can summarize and share from this study (and then we can close it out)?