Skip to content
This repository has been archived by the owner on May 31, 2024. It is now read-only.

updated links to UX Guide equivalent pages, away from deprecated Method pages #682

Closed
wants to merge 1 commit into from
Closed

updated links to UX Guide equivalent pages, away from deprecated Method pages #682

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _methods/stakeholder-and-user-interviews.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ timeRequired: 1–2 hours per interviewee

## Additional resources

- <a href="{{site.baseurl}}/interview-checklist/" class="usa-link">Interview checklist template</a>
- <a href="https://ux-guide.18f.gov/interview-checklist/" class="usa-link">Interview checklist template</a>
- <a href="https://18f.gsa.gov/2016/02/09/tips-for-capturing-the-best-data-from-user-interviews/" class="usa-link">Tips for capturing the best data from user interviews — 18F Blog</a>
- <a href="https://18f.gsa.gov/2016/06/20/build-empathy-with-stakeholder-interviews-part-1-preparation/" class="usa-link">Build empathy with stakeholder interviews, part 1: Preparation — 18F Blog</a>
- <a href="https://18f.gsa.gov/2016/07/22/building-empathy-with-stakeholder-interviews-part-2-conversation/" class="usa-link">Build empathy with stakeholder interviews, part 2: Conversation — 18F Blog</a>
Expand Down
4 changes: 2 additions & 2 deletions _methods/usability-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ timeRequired: 30 minutes to 1 hour per test
## How to do it

1. Pick what you’ll test. Choose something, such as a sketch, <a href="{{site.baseurl}}/prototyping/" class="usa-link">prototype</a>, or even a "competitor's product" that might help users accomplish their goals.
1. Plan the test. Align your team on the scenarios the test will focus on, which users should participate (and how you'll <a href="{{site.baseurl}}/recruiting/" class="usa-link">recruit</a> them), and which team members will moderate and observe. Prepare a <a href="{{site.baseurl}}/usability-test-script/" class="usa-link">usability test script</a>.
1. Plan the test. Align your team on the scenarios the test will focus on, which users should participate (and how you'll <a href="{{site.baseurl}}/recruiting/" class="usa-link">recruit</a> them), and which team members will moderate and observe. Prepare a <a href="https://guides.18f.gov/ux-guide/usability-test-script/" class="usa-link">usability test script</a>.
1. Recruit users and inform their consent. Provide a way for potential participants to sign up for the test. Pass along to participants an <a href="{{site.baseurl}}/participant-agreement/" class="usa-link">agreement</a> explaining what participation will entail. Clarify any logistical expectations, such as screen sharing, and how you'll share links or files of whatever it is you're testing.
1. Run the tests. Moderators should verbally confirm with the participant that it’s okay to record the test, ask participants to think outloud, and guide the participant through the session. Observers should contribute to a <a href="{{site.baseurl}}/rolling-issues-log/" class="usa-link">rolling issues log</a> and relay any in-session questions to the moderator, refraining from interrupting the session from the participant's point of view. Engage your team in a <a href="{{site.baseurl}}/interview-debrief/" class="usa-link">post-interview debrief</a> after each test.
1. Run the tests. Moderators should verbally confirm with the participant that it’s okay to record the test, ask participants to think outloud, and guide the participant through the session. Observers should contribute to a <a href="{{site.baseurl}}/rolling-issues-log/" class="usa-link">rolling issues log</a> and relay any in-session questions to the moderator, refraining from interrupting the session from the participant's point of view. Engage your team in a <a href="https://guides.18f.gov/ux-guide/interview-debrief/-debrief/" class="usa-link">post-interview debrief</a> after each test.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the URL may be incorrect here -- there seems to be an extraneous /-debrief at the end of the URL you changed.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are correct. Thanks for catching that. The URL is wrong.

1. Discuss the results. Schedule a collaborative synthesis meeting to discuss issues you observed, and any questions these tests raise concerning user needs. Conclude the meeting by determining how the team will use what it learned in service of future design decisions.
main

Expand Down
2 changes: 1 addition & 1 deletion pages/archive/interview-script.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ permalink: /interview-script/

# Example User Interview Script

This document is designed as a useful starting point for leading a user interview. It includes example questions grouped along the key moments often found in an interview: introductions, warm-up, topic-specific questions, demos, etc. Edit these questions as you see fit. If your questions are specific or your user’s time scarce, consider sharing some questions ahead of time. See [this checklist]({{site.baseurl}}/interview-checklist/) for running an interview. GSA Staff, please see this [Google Doc Template](https://docs.google.com/document/d/1kju19eC5vjqAd6bZCprniLixr1_u1b4Qfs1zVwTn6UA/edit#)
This document is designed as a useful starting point for leading a user interview. It includes example questions grouped along the key moments often found in an interview: introductions, warm-up, topic-specific questions, demos, etc. Edit these questions as you see fit. If your questions are specific or your user’s time scarce, consider sharing some questions ahead of time. See [this checklist](https://guides.18f.gov/ux-guide/interview-checklist/) for running an interview. GSA Staff, please see this [Google Doc Template](https://docs.google.com/document/d/1kju19eC5vjqAd6bZCprniLixr1_u1b4Qfs1zVwTn6UA/edit#)

## Introduction

Expand Down
2 changes: 1 addition & 1 deletion pages/archive/usability-test-script.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ permalink: /usability-test-script/

# Example Usability Test Script

This document provides example questions grouped along the key moments found in a usability test: introductions, warm up, task completion, follow up, and wrap up. If your participant’s time is scarce, consider sharing a few of your questions ahead of time. See also this [checklist for running an interview]({{site.baseurl}}/interview-checklist/). GSA staff, please see this [Google Doc Template](https://docs.google.com/document/d/1VimyVSt7qK3iKc2uZkobLWM0zuJuvO03vFk_R_EjhOU/edit#).
This document provides example questions grouped along the key moments found in a usability test: introductions, warm up, task completion, follow up, and wrap up. If your participant’s time is scarce, consider sharing a few of your questions ahead of time. See also this [checklist for running an interview](https://guides.18f.gov/ux-guide/interview-checklist/). GSA staff, please see this [Google Doc Template](https://docs.google.com/document/d/1VimyVSt7qK3iKc2uZkobLWM0zuJuvO03vFk_R_EjhOU/edit#).

## Introduction

Expand Down
Loading