Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Shared Components: Ad Hoc Design Testing Template

Ahead of each session, fill out the following info:

  1. Describe the design needs to be addressed:

  2. Describe the available options (no more than three):

  3. Give an example of how the design would be used:

  4. Describe how each design option empowers users:

Kick off the Session: Thank testers for joining. Introduce folks if they haven’t met before.

  • Explain what the tool is (or what tools are).

VEGSPEC: “Thanks for joining! We brought you here to help us test a tool called Vegspec. It’s for helping NRCS agents reach their conservation goals. Using this tool, agents can search a database of plants based on the needs of their specific site, their selected practice, and the planting purpose. In addition, it lets agents generate seed mixes and estimated costs for their project.”

COVER CROP SELECTOR: “Thanks for joining! We brought you here to help us test a tool called the Cover Crop Species Selector Tool. It’s for helping people figure out what cover crop would work best for their location and goals.”

SEEDING RATE CALC: “Thanks for joining! We brought you here to help us test a tool called the Seeding Rate Calculator. It’s for helping people figure out the best seeding rate based on their location and needs.”

  • If helpful, give an example.

SPECIES SELECTOR: “For example, a farmer looking to plant something in August to prevent erosion and break compaction might find Winter Barley or Winter Cereal Rye could work for them given their particular needs.”

Explain the purpose of testing. “We’re developing a number of decision support tools, and we’re looking for input on our design to make sure that the tools feel as clear and as easy to use as possible. We’re looking for honest feedback to help us improve the tools.“

Check that the tester(s) are comfortable moving forward by getting their consent to join the discussion and take the survey. Explain the following areas (as relevant) and ask whether or not they agree to participate.

  • How data gathered from the session can and will be used

  • What sensitive information will be collected

  • That participation is voluntary -- a chance to opt out or consent

Design Demo: Sit down with the participant and demo the design from start to finish. Explain the purpose and the function it serves with an example. Allow participants to interject and ask questions throughout the demo. Pause frequently to prompt for questions and make sure to allow time for this interaction.

When you’ve presented users with a key decision or aspect for feedback, ask the tester to answer the following questions and write down their responses.

  • "What was your initial impression of [design]? What stood out to you the most?" OR “What did you like? What did you dislike?”

  • *IF MULTIPLE OPTIONS: Of the options presented, which do you prefer? Why?

  • How easy do you think it would be to use this design for [insert task]? Are there any elements that you think might be difficult to navigate or interact with?”

  • Is there anything about this design that might be confusing for some folks? In what ways?

  • How do you feel about the visuals? Do the look and feel work for you? Why or why not?

  • Is there anything else you would like us to know?

Keep choices clear and simple. Users should only be weighing in on one choice at a time. Once users have weighed in on their choice, move on to demoing the next design choice until all key choices have been made.

Complete a survey as testers respond with their feedback.

Thank the testers for their time and help!


Ad Hoc Feature Testing

Ahead of each session, fill out the following info:

  1. Describe the feature to be tested:

  2. Describe the purpose of the feature:

  3. Give an example of how the feature would be used:

  4. Describe what the feature empowers users to complete:

Kick off the Session: Thank testers for joining. Introduce folks if they haven’t met before.

  • Explain what the tool is. “Thanks for joining! We brought you here to help us test a tool called Vegspec. It’s for helping NRCS agents reach their conservation goals. Using this tool, agents can search a database of plants based on the needs of their specific site, their selected practice, and planting purpose. In addition, it lets agents generate seed mixes and estimated costs for their project”

  • If helpful, give an example. [Add in example here]

  • Explain the purpose of testing. “We’ll test with a wider group in the coming weeks. Your feedback now can help us identify key issues to address before we share it with the wider group. The goal is to get your honest impression and input on the tool. “

Check that the tester(s) are comfortable moving forward by getting their consent to join the discussion and take the survey. Explain the following areas (as relevant) and ask whether or not they agree to participate.

  • How data gathered from the session can and will be used

  • What sensitive information will be collected

  • That participation is voluntary -- a chance to opt out or consent

Feature Demo: Sit down with the participant and demo the feature from start to finish. Explain the purpose and the function it serves with an example. Allow participants to interject and ask questions throughout the app. Pause frequently to prompt for questions and make sure to allow time for this interaction.

Ask the tester to answer the following questions and write down their responses.

  • Can you walk me through your initial impression of [feature]? What stood out to you the most?

  • Imagine you're trying to [Complete task]. Can you walk me through how you'd use this feature to accomplish that?

  • Is there anything about this feature that you find confusing or unclear? What could be better communicated about the feature?

  • What, if anything, is missing from this feature to make sure it’s useful when you (Complete task)?

  • How easy or hard does it seem to use this feature? What could improve it?

  • Is there anything else you would like use to know?

Complete a survey as testers respond to log their feedback.

Thank the testers for their time and help!

  • No labels