Potential Questions for Research Team to include in post launch user testing

These are the questions on the current "Figma Kit" that we would like addressed during usability testing.

No response

Design Questions

[ ] For the “Start Here” page, do we need to switch the look of it to be more cohesive with the remainder of the page and look more like a step by step process than a cover page?
[ ] Standards - Will putting an additional screenshot visual be helpful to users for better understanding or just be too much to look at and overwhelm the user?
[ ] What would be the best layout for these screens?
[ ] Displaying “Standards” first or instructions on how to make the cover first?
[ ] Do all of the example screenshots make sense or is there confusion? How can we make them better?
[ ] For the illustrations on the Figma kit, do they feel unnecessary to the page? Can we make the illustrations more impactful for the page by adding illustrations with more related meaning to them?
[ ] Would it be helpful to make an “Icon Guidelines” for users? Or give more examples?
[ ] Do the “Descriptive Names” make sense or should there be a more extensive example for them?
[ ] How does the overall layout feel to users? Is there something off about it that makes it distracting to read?
[ ] With the “templates”, is it obvious enough that they will be able to copy the templates?
[ ] Dark mode vs. light mode?

Content Questions

[ ] Do “standards” make sense? Or should we say “requirements”?
[ ] Do the instructions make sense on the “Start Here” page?
[ ] Do we need a table of contents?
[ ] Do we need a clearer definition of the product?
[ ] Is it clear what this product is, does, and what it will help the user accomplish?
[ ] Are the pages scannable?
[ ] Do people navigate easily or are they unsure where they are in the product?

There are some additional questions that our team wanted to focus on after getting some feedback from the new designers.

[ ] "Start Here" page - See if the action steps on the first page make sense.
- Are they too small?
- Are the steps confusing to users?
[ ] Are both action steps and standards needed?
- Is there a better way of combining the two items or a way to make them both less redundant?
- Or do we need to add more additional steps to the action steps?
- Are the steps clear? Are there any other additional questions with the steps?
[ ] How impactful are the icons for designers when labeling the different pages?
- Should they be used sparingly for main pages?
- Are they needed at all?
- What are icons that make sense relating to pages? And can we combine these icons onto a guide, would that help users? (ex. What icon can be used for mockups? Components? Colors? etc.)
[ ] How does the typography size options affect the page?
- Is the main header text too big?
- Is the body text too small in comparison to other things?
- Would it be okay to make the pages bigger to accommodate for bigger text or should we add more additional pages?

hackforla / design-systems