Merge pull request #557 from 18F/356-interview-checklist-debrief-and-…

…scripts-update-links

issue #356 interview checklist debrief and scripts update links

content/methods/discover/stakeholder-and-user-interviews.md

@@ -29,7 +29,7 @@ method:
 
 ## Additional resources
 
-- [Interview checklist]({{ "/methods/interview-checklist/" | url }})
+- [Interview checklist]({{ "/ux-guide/interview-checklist/" | url }})
 - [Tips for capturing the best data from user interviews — 18F Blog](https://18f.gsa.gov/2016/02/09/tips-for-capturing-the-best-data-from-user-interviews/){.usa-link .usa-link--external}
 - [Build empathy with stakeholder interviews, part 1: Preparation — 18F Blog](https://18f.gsa.gov/2016/06/20/build-empathy-with-stakeholder-interviews-part-1-preparation/){.usa-link .usa-link--external}
 - [Build empathy with stakeholder interviews, part 2: Conversation — 18F Blog](https://18f.gsa.gov/2016/07/22/building-empathy-with-stakeholder-interviews-part-2-conversation/){.usa-link .usa-link--external}

content/methods/interview-checklist.md

@@ -98,7 +98,7 @@ Once the interview is complete, **spend 15 minutes** completing a post-interview
 
 ### Make sure to
 - If you’ve recorded the interview: Move any recordings from your Google Drive to the project folder
-- Engage the team in a post-interview debrief ([example]({{ "/methods/interview-debrief/" | url }})) to discuss surprises and reflect on what you heard
+- Engage the team in a post-interview debrief ([example]({{ "/ux-guide/interview-debrief/" | url }})) to discuss surprises and reflect on what you heard
 - Consider updating the interview guide based on this interview
 - If you promised the participant any follow-up communications, identify who will send them and when
 - Optional: Update your study contact list

content/methods/interview-script.md

@@ -15,7 +15,7 @@ eleventyExcludeFromCollections: true
 
 <div class="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]({{ "/methods/interview-checklist/" | url }}) 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]({{ "/ux-guide/interview-checklist/" | url }}) for running an interview. GSA Staff, please see this [Google Doc Template](https://docs.google.com/document/d/1kju19eC5vjqAd6bZCprniLixr1_u1b4Qfs1zVwTn6UA/edit#)
 
 ## Introduction
 
@@ -62,7 +62,7 @@ What’s one thing you wish were more straightforward about `[topic]`?
 
 ## Demo
 
-_Note: If you’re running a usability test, consider this [example usability test script]({{ "/methods/usability-test-script/" | url }}) instead._
+_Note: If you’re running a usability test, consider this [example usability test script]({{ "/ux-guide/usability-test-script/" | url }}) instead._
 
 Thanks. Now I’m going to ask you to consider how you might respond to the following scenarios using this website. I’m going to read each scenario out loud, and I’ll also share the text of the scenario via chat.
 

content/methods/usability-test-script.md

@@ -8,7 +8,7 @@ layout_class: layout--example-usability-test-script
 eleventyExcludeFromCollections: true
 ---
 
-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]({{ "/methods/interview-checklist/" | url }}). 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]({{ "/ux-guide/interview-checklist/" | url }}). GSA staff, please see this [Google Doc Template](https://docs.google.com/document/d/1VimyVSt7qK3iKc2uZkobLWM0zuJuvO03vFk_R_EjhOU/edit#).
 
 ## Introduction
 

content/methods/validate/usability-testing.md

@@ -22,9 +22,9 @@ method:
 ## How to do it{#how-usability}
 
 1. Pick what you’ll test. Choose something, such as a sketch, [prototype]({{ "/methods/make/prototyping/" | url }}), 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 [recruit]({{ "/methods/fundamentals/recruiting/" | url }}) them), and which team members will moderate and observe. Prepare a [usability test script]({{ "/methods/usability-test-script/" | url }}).
+1. Plan the test. Align your team on the scenarios the test will focus on, which users should participate (and how you’ll [recruit]({{ "/methods/fundamentals/recruiting/" | url }}) them), and which team members will moderate and observe. Prepare a [usability test script]({{ "/ux-guide/usability-test-script/" | url }}).
 1. Recruit users and inform their consent. Provide a way for potential participants to sign up for the test. Pass along to participants an [agreement]({{ "/ux-guide/participant-agreement/" | url }}) 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 rolling issues log 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 [post-interview debrief]({{ "/methods/interview-debrief/" | url }}) 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 rolling issues log 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 [post-interview debrief]({{ "/ux-guide/interview-debrief/" | url }}) after each test.
 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
 

content/ux-guide/research/do.md

@@ -137,7 +137,7 @@ Most 18F interview guides include these sections:
 - Concluding thanks, questions, and opportunities to follow up
 - Ask who else you should meet with (if appropriate)
 
-For starting points, see this [example interview guide [18F design methods]](https://guides.18f.gov/methods/interview-script/) ([Google Docs example interview guide](https://docs.google.com/document/d/1kju19eC5vjqAd6bZCprniLixr1_u1b4Qfs1zVwTn6UA/edit#)).
+For starting points, see this [example interview guide [18F design methods]](https://guides.18f.gov/ux-guide/interview-script/) ([Google Docs example interview guide](https://docs.google.com/document/d/1kju19eC5vjqAd6bZCprniLixr1_u1b4Qfs1zVwTn6UA/edit#)).
 
 When interviewing stakeholders, ask about their work as it relates to your research area of focus. Ask about business processes in which they play a role, the information and tools they use, the things they produce or make, and the decisions they’re responsible for. Ask about the people they work with on a regular basis and any challenges they face.
 

content/ux-guide/resources/research-lead.md

@@ -15,7 +15,7 @@ While being mindful that [18F practices research as a team sport]({{ '/ux-guide/
 - **Educate others on the role, types, and methods of research.** Help the team understand the different types of research (foundational, generative, evaluative), and why specific research [18f design methods](https://guides.18f.gov/methods) apply. Explain how to employ specific methods. Facilitate [research retrospectives](https://18f.gsa.gov/2018/10/23/two-exercises-for-improving-design-research-through-reflective-practice/) to encourage reflective practice.
 - **Identify and recruit a diverse and representative group of people to participate in design research.** Set up repeatable participant recruiting processes. Help the team understand the importance of diversity in recruiting.
 - **Keep the team's research on track and on time.** Plan for and execute studies around shared goals with predictable scope. Incorporate asynchronous tasks like “homework”, diary studies, etc. to make the best use of everyone’s time. Encourage [collaborative research analysis (see 18f blog)](https://18f.gsa.gov/2018/02/06/getting-partners-on-board-with-research-findings/) and synthesis, and help the team manage transitions between learning and building.
-- **Maintain quality.** Identify and mitigate risks to quality design research, such as ethics, bias, and privacy and legal risk (for example, help the team understand how to conduct research that is Paperwork Reduction Act-compliant by design). Ensure rigor with [checklists [18F design methods]](https://guides.18f.gov/methods/interview-checklist/).
+- **Maintain quality.** Identify and mitigate risks to quality design research, such as ethics, bias, and privacy and legal risk (for example, help the team understand how to conduct research that is Paperwork Reduction Act-compliant by design). Ensure rigor with [checklists [18F design methods]](https://guides.18f.gov/ux-guide/interview-checklist/).
 
 - **Make research visible.** Inspire others to adopt a richer and more nuanced perspective of the people for whom they’re solving problems. Help people take findings back to the organization in a way that can be acted upon. Update project-level onboarding, knowledge management, etc. to reflect the research done to date.