diff --git a/.DS_Store b/.DS_Store
new file mode 100644
index 0000000..24e8f29
Binary files /dev/null and b/.DS_Store differ
diff --git a/_pages/about.md b/_pages/about.md
index c4793be..10e916c 100644
--- a/_pages/about.md
+++ b/_pages/about.md
@@ -8,20 +8,20 @@ description: "How 18F user experience (UX) designers improve interactions betwee
 [//]: make it possible to put a class on a ul tag
 {::options parse_block_html="true" /}
 
-18F user experience (UX) designers join cross-functional teams to improve interactions between government agencies and the people they serve. The 18F UX Guide helps us get this job done. It’s a starting point for UX design at 18F: doing it, discussing it, and ensuring it’s done to a consistent level of quality.
+18F designers join cross-functional teams to improve interactions between government agencies and the people they serve. The 18F UX Guide, or User Experience Guide, helps us get this job done. It’s a starting point for design research at 18F: doing it, discussing it, and ensuring it’s done to a consistent level of quality. Throughout this guide we use “design research” as a substitute and broader  term for “user research” to show the focus of our research work is making designs better for people.
 
 
 ## What this guide is
 
-Like [our 18F Content Guide](https://content-guide.18f.gov/how-to-use-this-guide/), the 18F UX guide is written for our internal designers, but we hope it’s a useful reference for anyone. Our working assumptions for this guide include that 18F UX designers are expected to possess, among other things:
+Like [our 18F Content Guide](https://content-guide.18f.gov/how-to-use-this-guide/), the 18F User Experience guide is written for our internal designers, but we hope it’s a useful reference for anyone. Our working assumptions for this guide include that 18F designers are expected to possess, among other things:
 
 * design research skills
 * the ability to skillfully navigate organizational relationships
 * the communication and facilitation skills to explain research clearly and run co-design and workshop sessions
 * consulting and coaching skills, especially supporting those new to research, design, and/or modern development practices
-* the ability to deliver artifacts that guide development, like wireframes and prototypes
+* the ability to deliver artifacts that guide development and service improvements, like wireframes, service blueprints, and prototypes
 
-This guide includes information that may be new to the designers we hire (who may be new to government), and useful starting points for conversations with the people we work with (who may be new to design). For details of specific UX activities and how to conduct them, see [18F's methods](https://methods.18f.gov/).
+This guide includes information that may be new to the designers we hire (who may be new to government), and useful starting points for conversations with the people we work with (who may be new to design). For details of specific UX and service activities and how to conduct them, see [18F's methods](https://methods.18f.gov/).
 
 18F staff should consult the following additional guidance:
 
@@ -33,7 +33,7 @@ This guide includes information that may be new to the designers we hire (who ma
 
 ## How to use this guide
 
-We created this guide for our reference. It’s here for a refresher on [ways to protect research participant privacy]({{site.baseurl}}/research/privacy/), or for quick access to [UX-related templates, presentations, etc.]({{site.baseurl}}/resources/) You’re also welcome to read it from start to finish if you like.
+We created this guide for our reference. It’s here for a refresher on [ways to protect research participant privacy]({{site.baseurl}}/research/privacy/), or for quick access to [design-related templates, presentations, etc.]({{site.baseurl}}/resources/) You’re also welcome to read it from start to finish if you like.
 
 This guide is divided into three sections:
 
@@ -45,16 +45,16 @@ This guide is divided into three sections:
 
 
 
-If you have any suggestions or want to get involved, read [our contributing page on GitHub](https://github.com/18F/ux-guide/blob/main/CONTRIBUTING.md#non-18F-contributors); find us on our TTS Slack in either #ux, #ux-guide, or #g-research; or [create an issue in GitHub](https://github.com/18F/ux-guide/issues).
+If you have any suggestions or want to get involved, read [our contributing page on GitHub](https://github.com/18F/ux-guide/blob/main/CONTRIBUTING.md#non-18F-contributors); find us on our TTS Slack in either #ux, #ux-guide, #service-design, or #g-research; or [create an issue in GitHub](https://github.com/18F/ux-guide/issues).
 
 
 ## Reusing this guide in other organizations
 
 As a work of the federal government, this project is in the public domain within the United States. Additionally, we waive copyright and related rights in the work worldwide through the [Creative Commons CC0 1.0 Universal public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/legalcode).
 
-This guide is written for internal use and is shared in the spirit of open source.  This guide is a product of what we’ve learned from doing UX research and design in government over the past few years, in collaboration with GSA’s Office of General Counsel, Privacy Office, PRA (Paperwork Reduction Act) Desk Officer, and our partners within GSA and throughout other agencies.
+This guide is written for internal use and is shared in the spirit of open source.  This guide is a product of what we’ve learned from doing UX and service research and design in government over the past few years, in collaboration with GSA’s Office of General Counsel, Privacy Office, PRA (Paperwork Reduction Act) Desk Officer, and our partners within GSA and throughout other agencies.
 
-Feel free to [fork this guide  via GitHub](https://help.github.com/articles/fork-a-repo/) on GitHub and personalize it for your organization; we trust you’ll change it in whatever ways are best for you. If you have a suggestion, spot an error, or otherwise want to make constructive contribution to this guide, head over to [our contributing page hosted on GitHub](https://github.com/18F/ux-guide/blob/main/CONTRIBUTING.md#non-18F-contributors).
+Feel free to [fork this guide  via GitHub](https://help.github.com/articles/fork-a-repo/) on GitHub and personalize it for your organization; we trust you’ll change it in whatever ways are best for you. If you have a suggestion, spot an error, or otherwise want to make constructive contributions to this guide, head over to [our contributing page hosted on GitHub](https://github.com/18F/ux-guide/blob/main/CONTRIBUTING.md#non-18F-contributors).
 
 ## References
 
diff --git a/_pages/design/build-a-prototype.md b/_pages/design/build-a-prototype.md
index ce765c4..7b4caff 100644
--- a/_pages/design/build-a-prototype.md
+++ b/_pages/design/build-a-prototype.md
@@ -25,15 +25,18 @@ Use prototypes to:
 - Demonstrate that your ideas are technically possible
 - Explore/set up the deployment process
 - Demonstrate a collaborative design process
-- Reduce risk
+- Reduce risk (“What are the riskiest assumptions and how can we test them?”)
 - Validate a [design hypothesis [18F design methods]](https://methods.18f.gov/decide/design-hypothesis/)
 
-Prototypes can range in fidelity from basic paper prototypes to fully functional software. The idea is to build something that will help you answer your questions with the least investment. Prototyping can take many different forms depending on what you are trying to do. For example:
+Prototypes can range in fidelity from basic paper prototypes to fully functional software.  Prototypes can be digital products as well as services. The idea is to build something that will help you answer your questions with the least investment. Prototyping can take many different forms depending on what you are trying to do. For example:
 
 - Paper sketches are fast to make and to change, and easy for the whole team to participate in designing
 - [Wireframes [18F design methods]](https://methods.18f.gov/make/wireframing/) are preliminary blueprints that can help teams align on structure, placement, and hierarchy for a product or service
 - Static visual mock-ups can help communicate and test things like brand identity and tone
 - Clickable prototypes can help test usability by finding out if users can complete the needed tasks
+- A service prototype or simulation that mimics, as much as possible, what users might experience which can include space, online and offline touchpoints, people, and time
+- Service storyboards that visualize scenarios of a future service and can illustrate parts of a service
+
 
 
 ## Communicating with prototypes
@@ -70,7 +73,7 @@ Once they’ve added your account, you can [sign in](https://pages.cloud.gov/) b
 
 ## Authorized prototyping tools
 
-Depending where you worked prior to joining 18F, you are probably accustomed to having some flexibility around your design toolset. Working for the government means only using tools that have been granted an Authority to Operate, an approval granted after a thorough review of the secuirty and privacy of a tool. Due to the sensitive nature much of the data we encounter of government work, we are only allowed to use GSA IT-approved tools.
+Depending where you worked prior to joining 18F, you are probably accustomed to having some flexibility around your design toolset. Working for the government means only using tools that have been granted an Authority to Operate, an approval granted after a thorough review of the security and privacy of a tool. Due to the sensitive nature of much of the data we encounter in government work, we are only allowed to use GSA IT-approved tools.
 
 Don’t fret! 18F has done a great job of getting us licenses to standard prototyping [tools as listed on the TTS handbook](https://handbook.tts.gsa.gov/design/#tools). To request licenses, [review the TTS Handbook](https://handbook.tts.gsa.gov/design/#tools). Ensure you review the usage parameters for each tool.  
 
diff --git a/_pages/design/index.md b/_pages/design/index.md
index 4c5ec3f..a3d989b 100644
--- a/_pages/design/index.md
+++ b/_pages/design/index.md
@@ -8,5 +8,5 @@ sidenav: design
 sticky_sidenav: true
 ---
 
-This section covers prototypes, how they inform our work and what prototypes help us convey. It contains resources to get started prototyping with our website publishing platform, [Cloud.gov Pages](https://cloud.gov/pages/), as well as information and resources related to the U.S. Web Design System, —the set of website standards agencies should use per the 21st Century IDEA.
+This section covers prototypes, how they inform our work and what prototypes help us convey. It contains resources to get started prototyping with our website publishing platform, [Cloud.gov Pages](https://cloud.gov/pages/), as well as information and resources related to the [U.S. Web Design System](https://designsystem.digital.gov/)— the set of website standards agencies should use per the 21st Century IDEA.
 
diff --git a/_pages/our-approach/defining-design.md b/_pages/our-approach/defining-design.md
index 125bcce..350dac2 100644
--- a/_pages/our-approach/defining-design.md
+++ b/_pages/our-approach/defining-design.md
@@ -7,26 +7,33 @@ sidenav: our-approach
 sticky_sidenav: true
 ---
 
-We see design as a process of intentionally deciding, over and over, how interactions should work for users, based on research.
+We see design as a process of intentionally deciding, over and over, how interactions and systems should work for people, based on research.
 
 
 ### Design is a series of intentional decisions
 
-Every project is shaped by a series of decisions, whether those decisions are about meeting agendas, research plans, or what constitutes a minimum-viable product. Taking a design approach means identifying opportunities for decision-making, and being intentional about making decisions.
+Every project is shaped by a series of decisions, whether those decisions are about meeting agendas, research plans, how people are engaged in the process, what constitutes a minimum-viable product, or how a technical solution is supported within the wider organization. Taking a design approach means both identifying opportunities for decision-making, and also being intentional about decision-making.
+
+
+### Design impacts equity and inclusion 
+
+Most research focuses on the mindsets, behaviors and experiences of people and groups. There are times when you need to look broadly at the system and structures that fail to serve communities equitably, rather than focusing solely on the community or individual. To create equitable and inclusive products, it is important to move beyond understanding an individual participants’ experience to the broader system they interact with and the barriers they face.
 
 
 ### Design depends on context
 
-What’s the right approach? It depends. We use [design research]({{site.baseurl}}/research/clarify-the-basics#what-it-is) to better understand the problems we might solve, and the systems those problems connect to. We actively validate the success of our solutions through design research.
+What’s the right approach? It depends. We use [design research]({{site.baseurl}}/research/clarify-the-basics#what-it-is) to better understand the problems we might solve, the systems those problems connect to, and what the opportunities for technical and service changes are. We actively validate the success of our solutions with people through ongoing and iterative design research.
+
 
+### Design supports people's needs
 
-### User-centered design is for people
+We proactively engage with people to understand their needs and determine how well our decisions have met those needs. Since some of our work involves creating solutions that are used, managed, delivered, or informed by government employees or partner organizations, who we engage in the work may not always be just members of the public.
 
-We proactively engage with users to understand their needs and determine how well our decisions have met those needs. Since some of our work involves creating solutions that are used by government employees, our users are not always members of the public.
+Stakeholders are anyone with a legitimate interest in what we’re designing. Stakeholders include our agency partners and the people they serve—that is, their constituents. We regularly collaborate with our agency partners, and while all design processes must take their needs into consideration, our process ultimately puts those most impacted by our work at the center of our decision-making as our primary concern.
 
-Stakeholders are anyone with a legitimate interest in what we’re designing. Stakeholders include our agency partners and the people they serve—that is, their users. We regularly talk with our agency partners, and while all design processes must take stakeholder needs into consideration, our process ultimately puts users, rather than stakeholders, at the center—that is, as our primary concern.
+### Design should be cross-functional
 
-When design is practiced together, it creates shared understanding. We bring together cross-functional teams to arrive at more well-informed, less [biased]({{site.baseurl}}/research/bias/) decisions. Moreover, we rely on two kinds of thinking:
+When design is practiced together, it creates shared understanding. We bring together cross-functional teams, including a range of different types of designers, to arrive at more well-informed, less [biased]({{site.baseurl}}/research/bias/) decisions. Outside of the range of methodologies that come from different design approaches, cross-functional teams allow for two kinds of thinking:
 - **Divergent thinking** helps us to identify opportunities for decision making, and to explore possible choices
 - **Convergent thinking** helps us narrow our choices, and follow through on our decisions
 
@@ -35,12 +42,12 @@ Intentionally transitioning between divergence and convergence helps make the de
 
 ### Design shapes organizations, and vice-versa
 
-Products and services impose requirements on the organizations that support them, and vice-versa. We shouldn't design an agency’s homepage to include images on every news post, for example,  if we haven’t yet made certain that agency can reasonably source images for each of its news posts. To best support the endeavor as a whole, we want to proactively acknowledge when our design recommendations will require organizational shifts or new resources.
+Products and services impose requirements on the organizations that support them, and vice-versa. We shouldn't design an agency’s homepage to include images on every news post, for example,  if we haven’t yet made certain that the agency can reasonably source images for each of its news posts. To best support the endeavor as a whole, we want to proactively acknowledge when our work may require nw investments, organizational shifts or new resources.
 
 
 ### Design is never done
 
-We don’t have all the answers. And that’s okay. We take an iterative, cyclical, [lean]({{site.baseurl}}/our-approach/stay-lean) approach. We try things out. We commit to continuous improvement using critiques, [wireframes](https://methods.18f.gov/make/wireframing/), [prototypes](https://methods.18f.gov/make/prototyping/), [usability tests](https://methods.18f.gov/usability-testing), etc.
+We don’t have all the answers. And that’s okay. We take an iterative, cyclical, participatory, [lean]({{site.baseurl}}/our-approach/stay-lean) approach. We try things out and learn from them. We commit to continuous improvement using critiques, [wireframes](https://methods.18f.gov/make/wireframing/), [prototypes](https://methods.18f.gov/make/prototyping/), [usability tests](https://methods.18f.gov/usability-testing), service blueprints, etc. and we strive to build the capacity of our partners to do the same. 
 
 ![A conceptual image that describes iterative design. The phrase 'iterative design' is surrounded by four labels connected by a circle of clockwise-pointing arrows. Starting at the top, the labels read 'concept', 'try it out', 'gather feedback', 'incorporate feedback']({{site.baseurl}}/images/iterative-design.png)
 
diff --git a/_pages/our-approach/meet-people-where-they-are.md b/_pages/our-approach/meet-people-where-they-are.md
index 30360de..53e8e39 100644
--- a/_pages/our-approach/meet-people-where-they-are.md
+++ b/_pages/our-approach/meet-people-where-they-are.md
@@ -36,7 +36,7 @@ We view our partners as co-creators of our design process. We are especially min
 
 ## Ability to participate
 
-Partner participation is essential to our [UX team's principle]({{site.baseurl}}/our-approach/values-and-principles) of training design advocates. But just because an agency enters into an agreement with 18F doesn’t mean we take their ongoing participation as a given—we actively work to engage our partners at every step of the way.
+Partner participation is essential to our [team's principle]({{site.baseurl}}/our-approach/values-and-principles) of training design advocates. But just because an agency enters into an agreement with 18F doesn’t mean we take their ongoing participation as a given—we actively work to engage our partners at every step of the way.
 
 At a high level, to encourage participation we:
 
@@ -73,8 +73,10 @@ These engagements will begin by contemplating questions related to design maturi
 
 - What is our partner agency’s design awareness and ability?
 - Who in their agency already does design? Does that person have a full-time design role or is design the side job of an engineer, program manager, etc.
+- How does the partner learn from those most impacted by design decisions?
 - How often does our partner team prototype new ideas?
 - How often does our partner team engage in critique?
+- How do product changes ladder up to service design or organizational considerations?
 
 By initially assessing design maturity, we're able to help our partners increase their skills over time, and better measure how far they’ve come.
 
@@ -91,7 +93,7 @@ Engaging partners in conversations about how they might level-up in their practi
 - How might we better incorporate our partner’s perspective into the creative process (via stakeholder interviews, design studios, etc.), so that they see design’s ability to facilitate constructive dialog?
 - How could we more directly communicate design’s ability to meet their goals (such as demonstrating how proactive usability testing helps them reduce risk)?
 
-People who are new to design will need to appreciate its direct benefits (like improved usability and customer adoption) before its indirect benefits (such as helping the team identify the most important problems for them to solve). We aim to give our partners something tangible, and let them experience the show before pulling back the curtain.
+Partners who are new to design will need to appreciate its direct benefits (like improved usability and customer adoption) before its indirect benefits (such as helping the team identify the most important problems for them to solve). We aim to give our partners something tangible, and let them experience the show before pulling back the curtain.
 
 
 ## Remote friendliness
@@ -124,22 +126,22 @@ Our collaborations are frequently anchored by at least one or two in-person sess
 
 ## Security and privacy norms
 
-Risk management is a big part of developing government digital services. 18F relies on a number of platforms to create secure, compliant-by-default websites and web applications, including the use of [Cloud.gov Pages](https://cloud.gov/pages/),[Cloud.gov](https://cloud.gov/), [Login.gov](https://www.login.gov/), and [Seach.gov](https://search.gov/).
+Risk management is a big part of developing government digital services. 18F relies on a number of platforms to create secure, compliant-by-default websites and web applications, including the use of [Cloud.gov Pages](https://cloud.gov/pages/), [Cloud.gov](https://cloud.gov/), [Login.gov](https://www.login.gov/), and [Search.gov](https://search.gov/).
 
 As our work moves closer to production, our partners may ask us to help them obtain an Authority to Operate (ATO) for the products or services we’ve helped create. We often begin this conversation by identifying who at our partner agency will play key roles in the authorization process (such as the authorizing official and system owner). It can also be helpful to ask about:
 
 {:.list-item--margin-bottom-extra}
 - Authentication (it’s okay to have short-term and long-term solutions)
 - Our partner agency’s existing policies around account management
-- Our partner’s use of tools authorized governement-wide via the [FedRAMP](https://marketplace.fedramp.gov/) authorization program.
+- Our partner’s use of tools authorized government-wide via the [FedRAMP](https://marketplace.fedramp.gov/) authorization program.
 
-We discuss privacy norms and relevant information practices to ensure mutual understanding of essential concepts and identify differences in each agency's approaches. For example, 18F’s design research is defined by information practices outlined in [GSA’s Privacy Impact Assessment for Design Research](https://www.gsa.gov/reference/gsa-privacy-program/privacy-impact-assessments-pia). However, our norms are not our partner’s norms; and just because GSA’s Privacy Office sanctions our design research program doesn’t mean that our partner agency’s privacy office will do the same (see [legal]({{site.baseurl}}/research/legal/) and [privacy]({{site.baseurl}}/research/privacy/)). As we conduct design research on behalf of our agency partners, we may need to prompt conversation between the following GSA offices and their counterparts at our partner agencies:
+We discuss privacy norms and relevant information practices to ensure mutual understanding of essential concepts and identify differences in each agency's approaches. However, our norms are not our partner’s norms; and just because GSA’s Privacy Office sanctions our design research program doesn’t mean that our partner agency’s privacy office will do the same (see [legal]({{site.baseurl}}/research/legal/) and [privacy]({{site.baseurl}}/research/privacy/)). As we conduct design research on behalf of our agency partners, we may need to prompt conversation between the following GSA offices and their counterparts at our partner agencies:
 
 - Privacy office
 - Office of General Counsel
 - [Paperwork Reduction Act](https://pra.digital.gov/) (PRA) Desk Officer
 
-Beyond research, we engage with our partner's privacy office when the systems we design will collect or use information specific to an individual. For systems that will interact with personal information, called personally identifable information (PII) in the government, we work with our partners and their organization's privacy office to assess the privacy impacts of that use, and document that impact in a Privacy Impact Assessment. If the system will routinely allow the government to retrieve PII by an identifier such as a social security number, then our partners will ensure there is a public notice and a legal purpose to process that PII. These notices are called System of Record Notices or SORNs.
+Beyond research, we engage with our partner's privacy office when the systems we design will collect or use information specific to an individual. For systems that will interact with personal information, called personally identifiable information (PII) in the government, we work with our partners and their organization's privacy office to assess the privacy impacts of that use, and document that impact in a Privacy Impact Assessment. If the system will routinely allow the government to retrieve PII by an identifier such as a social security number, then our partners will ensure there is a public notice and a legal purpose to process that PII. These notices are called System of Record Notices or SORNs.
 
 ## Policy
 
@@ -152,4 +154,4 @@ As we collaboratively design with partners, we should ask:
 - Which policies will shape our design process? (are we considering a research design that will require approval from our partner’s Paperwork Reduction Act Desk Officer?)
 - Whose permission will be required if we need a policy exception?
 
-We recognize our partners are working to deliver their missions in a complex ecosystem of regulatory, organizational, and technological policies and constraints. Taking the time up front to agree on tools and practices helps set the foundation for a strong collaboration.
+We recognize our partners are working to deliver their missions in a complex ecosystem of regulatory, organizational, and technological policies and constraints. Taking the time upfront to agree on tools and practices helps set the foundation for a strong collaboration.
diff --git a/_pages/our-approach/stay-lean.md b/_pages/our-approach/stay-lean.md
index 676f134..e4e267b 100644
--- a/_pages/our-approach/stay-lean.md
+++ b/_pages/our-approach/stay-lean.md
@@ -6,25 +6,24 @@ permalink: /our-approach/stay-lean/
 sidenav: our-approach
 sticky_sidenav: true
 subnav:
-  - text: Lean UX at 18F
-    href: '#lean-ux-at-18f'
-  - text: Lean UX Principles
-    href: '#lean-ux-principles'
+  - text: Lean Design at 18F
+    href: '#lean-design-at-18f'
+  - text: Lean Design Principles
+    href: '#lean-design-principles'
   - text: Acknowledgements
     href: '#acknowledgements'
 ---
 
-18F UX designers take a collaborative, outcome-focused approach to our work. We manage risk through continuous learning. Each new iteration builds on the user-validated research of the previous iteration.
-Incrementally identifying and challenging assumptions helps keep the cost of change low. The Lean UX process, which is described below, incorporates ongoing research into each phase of work and fits nicely into the rhythms of agile product management and development processes (scrum, kanban, extreme programming, etc.).
+18F designers take a collaborative, outcome-focused approach to our work. We manage risk through continuous learning. Each new iteration builds on the people-validated research of the previous iteration. Incrementally identifying and challenging assumptions helps keep the cost of change low. The Lean UX process, which is described below, incorporates ongoing research into each phase of work and fits nicely into the rhythms of agile product management and development processes (scrum, kanban, extreme programming, etc.) and helps to inform larger investments and areas of opportunity within the service delivery itself. 
 
 
-## Lean UX at 18F
+## Lean Design at 18F
 
 18F engagements generally transition between two phases: [Path Analysis](https://18f.gsa.gov/how-we-work/#path-analysis) (PA), during which the problem is framed, and Experiment & Iterate, when solutions are explored. The first stage of any effort is to do research and identify the highest-impact opportunity areas.
 
-Lean UX becomes particularly relevant during the [Experiment & Iterate](https://18f.gsa.gov/how-we-work/#experiment--iterate) (E&I) phase of 18F engagements when we iteratively test hypotheses and assumptions. The result of this series of experiments is a product designed to take into account user needs.  
+Lean Design becomes particularly relevant during the [Experiment & Iterate](https://18f.gsa.gov/how-we-work/#experiment--iterate) (E&I) phase of 18F engagements when we iteratively test hypotheses and assumptions. The result of this series of experiments is a product designed to take into account user needs.  
 
-The Lean UX process iterates through these steps:
+The Lean Design process iterates through these steps:
 
 ### Research
 
@@ -38,10 +37,12 @@ Problem statements can be expressed in this format:
 
 > We have observed that [product/service/organization] isn’t meeting [these goals/needs], which is causing [this adverse effect]. How might we improve so that our product/service/team/organization is more successful based on [these measurable criteria]?
 
+You can read more about defining problems in the [18F Product Guide](https://product-guide.18f.gov/define/problem/#define-the-problem).
+
 
 ### Identifying Assumptions
 
-An iterative approach requires that we make assumptions based on the information available to us in any given moment.
+An iterative approach requires that we make assumptions based on the information available to us at any given moment.
 
 Those assumptions may include:
 - Who our users are
@@ -59,7 +60,7 @@ Those assumptions may include:
 - What features we think will be most important
 - Our mission, vision, business model, etc.
 
-Assumptions are a necessary part of the process; bias is unavoidable. But it is important to identify and validate (or invalidate) our assumptions through ongoing experimentation and research.
+Assumptions are a necessary part of the process; [bias](https://ux-guide.18f.gov/research/bias/) is unavoidable. But it is important to identify and validate (or invalidate) our assumptions through ongoing experimentation and research.
 Any proposed solution is an assumption until it’s validated through research with users. Before deciding what to test (building hypotheses), it’s important to consider all of our team’s potential assumptions — especially about our users.
 
 Once assumptions have been identified, we have to prioritize which are most important to test first. When prioritizing we should consider which of our assumptions create the biggest risks.
@@ -72,16 +73,16 @@ Hypotheses make our assumptions explicit, and experiments help us test our hypot
 
 ### Designing experiments
 
-We validate or invalidate our hypotheses through experimentation. These experiments check our assumptions with feedback from our users, and can take the form of prototypes, wireframes, drafts of messaging, or other research probes.
+We validate or invalidate our hypotheses through experimentation. These experiments check our assumptions with feedback from our users, and can take the form of service blueprints, diagrams, prototypes, wireframes, drafts of messaging, or other research probes.
 
 ### Iterate
 
 The application of these experiments brings us back to the research phase and feeds into another iteration of testing and learning. Lean UX can be used to identify and test the riskiest assumptions in each iteration. This process of ongoing learning allows our teams to be truly agile and responsive to our emerging understanding of the problems we are solving for our users. The ability to continually test and learn and adjust our approach increases our teams’ efficiency and effectiveness while managing risk for our partners.
 
 
-## Lean UX Principles
+## Lean Design Principles
 
-In addition to our team principles, the following principles from Lean UX are especially important in our work:
+In addition to our team principles, the following principles from Lean Design are especially important in our work:
 
 **Problem first.** Prudent experimentation requires that we first identify the problem(s) we’re solving. We work with stakeholders to define and prioritize specific problem(s) that the project will attempt to resolve.
 
@@ -91,7 +92,7 @@ In addition to our team principles, the following principles from Lean UX are es
 
 **Learn and respond.** Our Experiment & Iterate (E&I) engagements are essentially a series of small experiments conducted in close collaboration with users. Each experiment informs the next, so that we’re always building on the things that bring us closer to desired outcomes and removing or adjusting things that are not helping us reach our goals.
 
-**Build shared understanding.** Jeff Gothelf, author of Lean UX, says: “Strive toward shared understanding at all times. Shared understanding is the collective knowledge of the team that builds up over time as they work together. It is a rich understanding of our partners, their products, and users.” Shared understanding supports informed discussions and decisions at every level. It reflects diverse perspectives and inputs, helps reveal potential problems earlier, and ensures everyone on the team is working toward the same goals.
+**Build shared understanding.** Shared understanding supports informed discussions and decisions at every level. It reflects diverse perspectives and inputs, helps reveal potential problems earlier, and ensures everyone on the team is working toward the same goals.
 
 **Make assumptions explicit.** We write down and discuss the assumptions we have about users and the problems they face as part of our research planning process, and test the riskiest or most critical assumptions as early as possible.
 
@@ -100,4 +101,4 @@ In addition to our team principles, the following principles from Lean UX are es
 
 ## Acknowledgements
 
-This article is primarily based on our experiences practicing Lean UX at 18F, For more information, see [references](https://docs.google.com/document/d/1ZH6TrVBOQvmlUFRKZlFFk182fiOhyaqyZqiTrVcEW4w/edit).
+This article is primarily based on our experiences practicing Lean Design at 18F, For more information, see [references](https://docs.google.com/document/d/1ZH6TrVBOQvmlUFRKZlFFk182fiOhyaqyZqiTrVcEW4w/edit).
diff --git a/_pages/our-approach/values-and-principles.md b/_pages/our-approach/values-and-principles.md
index e5efc2b..8bd4e84 100644
--- a/_pages/our-approach/values-and-principles.md
+++ b/_pages/our-approach/values-and-principles.md
@@ -12,7 +12,7 @@ subnav:
   href: '#our-principles'
 ---
 
-We believe good design helps government better serve the public. 18F UX designers join cross-functional teams to improve interactions between government agencies and the people they serve. Together, we’re helping build a 21st century government that works for all.
+We believe good design helps government better serve the public. 18F designers join cross-functional teams to improve interactions between government agencies and the people they serve. Together, we’re helping build a 21st century government that works for all.
 
 Our approach is fundamentally collaborative. This document exists to help our cross-functional and often cross-agency teams collaborate better through a shared understanding of the values and principles that guide us.
 
@@ -54,7 +54,7 @@ Having a team with varied life experience — particularly around issues of acce
 
 ### We use an iterative process of learning and discovery informed by data
 
-A flexible vision is critical. We use data and direct conversations with and involvement of relevant members of the public to inform our decisions. We prototype ideas and do frequent rounds of research to give our teams the context to make better decisions. We deliver early and often, using an iterative cycle of build, test, and learn to refine our ideas over time. Quick feedback loops keep the cost of change low and mean that little mistakes don’t become big failures.
+A flexible vision is critical. We use data and direct conversations with relevant members of the public to inform our decisions. We prototype ideas and do frequent rounds of research to give our teams the context to make better decisions about products and services. We deliver early and often, using an iterative cycle of build, test, and learn to refine our ideas over time. Quick feedback loops keep the cost of change low and mean that little mistakes don’t become big failures.
 
 ### We coach advocates
 
diff --git a/_pages/research/clarify-the-basics.md b/_pages/research/clarify-the-basics.md
index ed4348c..8fa0620 100644
--- a/_pages/research/clarify-the-basics.md
+++ b/_pages/research/clarify-the-basics.md
@@ -26,13 +26,13 @@ Design research can feel overwhelming, even to people who’ve done it before! C
 
 
 ## What it is
-Design research explores possibilities, tests assumptions, and reduces risk by actively and systematically engaging with the world. It includes qualitative and quantitative methods, investigating tools and systems, and interacting with members of the public.
+Essentially, when we say design research, we mean the process of thoughtful exploration and learning with people to inform decisions. Design research explores possibilities, tests assumptions, and reduces risk by actively and systematically engaging with the world. It includes qualitative and quantitative methods, investigating tools and systems, and interacting with members of the public.
 
-All 18F teams do design research. [Design involves continuous decision making]({{site.baseurl}}/our-approach/defining-design), and those decisions are made better when they’re informed by end-user perspectives. As a result, we’re committed to continuous research. Rather than seeing designed products or services themselves as the goal, we view the products or services we’re designing as the result of our continued effort to identify, understand, and address user needs.
+All 18F teams do design research. [Design involves continuous decision-making]({{site.baseurl}}/our-approach/defining-design), and those decisions are made better when they’re informed by people's perspectives. As a result, we’re committed to continuous research. Rather than seeing designed products or services themselves as the goal, we view the products or services we’re designing as the result of our continued effort to identify, understand, and address people's needs.
 
 
 ## A team activity
-Because a collaborative approach increases the team’s overall empathy and efficiency, research is best done as a team activity. See our [18F blog on the impact of whole team collaboration on user research](https://18f.gsa.gov/2016/08/16/what-happens-when-the-whole-team-joins-user-interviews/). This means the entire team, including your agency partners, shares responsibility for:
+Because a collaborative approach increases the team’s overall empathy and efficiency, research is best done as a team activity. See our [18F blog on the impact of whole team collaboration on design research](https://18f.gsa.gov/2016/08/16/what-happens-when-the-whole-team-joins-user-interviews/). This means the entire team, including your agency partners, shares responsibility for:
 
 {:.list-item--margin-bottom-extra}
 - **Research design** — Formulating a research plan, including research questions and interview guides
@@ -49,34 +49,45 @@ Because a collaborative approach increases the team’s overall empathy and effi
 ## Research types
 On any given project you should only include the research activities that will inform the decisions you plan to make. Broadly speaking, 18F research falls into several categories. You can do research from any category on its own or in a sequence as you focus from problem definition to solution exploration:
 
+### Always start with background research
+Background or secondary research should be done on every project. This involves reviewing what is already known about the context you are working in or the people you want to learn about. Background research can save you and others time by reviewing findings from previous research studies or similar projects so you can build on what is already known, develop unique questions, and eliminate asking unnecessary, redundant, or triggering questions to people that could be harmful and reduce trust. 
+
+Background research helps you ask: what do we already know? 
+
 ### Foundational research
 
-Foundational research is the research you do to identify and clarify the team’s objectives, assumptions, and constraints. This includes stakeholder interviews, secondary research, and workshops. Foundational research is primarily (though not exclusively) the domain of [18F Path Analysis](https://18f.gsa.gov/how-we-work/#path-analysis) engagements and results in, among other things, a [problem statement as outlined on our GitHub repository](https://github.com/18F/path-analysis/blob/master/approach.md#2-draft-a-problem-statement).
+Foundational research is the research you do to identify and clarify the team’s objectives, assumptions, and constraints. On the 18F Methods site, [Discover methods](https://methods.18f.gov/discover/) help to build context for the problem you’re investigating. This includes; [Stakeholder and user interviews](https://methods.18f.gov/discover/stakeholder-and-user-interviews), [heuristic evaluation](https://methods.18f.gov/discover/heuristic-evaluation), and (Hopes and fears workshops)[https://methods.18f.gov/discover/hopes-and-fears]. Foundational research is primarily (though not exclusively) the domain of [18F Path Analysis](https://18f.gsa.gov/how-we-work/#path-analysis) engagements and results in, among other things, a [problem statement as outlined on our GitHub repository](https://github.com/18F/path-analysis/blob/master/approach.md#2-draft-a-problem-statement).
 
 Foundational research helps you ask: what problem are we trying to solve?
 
 ### Descriptive research
 
-Descriptive research focuses on understanding and documenting the context of a known problem. It could look like describing the needs and characteristics of a particular audience. 
+Descriptive research focuses on understanding, validating, and documenting the context of an assumed problem. On the 18F Methods site, [Decide methods](https://methods.18f.gov/#decide) help develop a deeper understanding of workflows and processes. It could look like describing the needs and characteristics of a particular audience like [Journey mapping or Mental modeling](https://methods.18f.gov/decide/journey-mapping).
 
 Descriptive research helps you ask: who or what are we solving this problem for? 
 
 ### Generative research
 
+Generative research helps you better frame the problem(s) you’re solving, spark new ideas, and reveal opportunities. On the 18F Methods site, [Make methods](https://methods.18f.gov/#make) help create testable designs like [Prototyping and Wireframing](https://methods.18f.gov/make/wireframing) to ensure your product reflects your users’ needs. 
+
 Generative research helps you better frame the problem(s) you’re solving, spark new ideas, and reveal opportunities. 
 
 Generative research helps you ask:
 
-- What are our users’ goals, behaviors, and pain points?
+- What are our people's goals, behaviors, and pain points?
 - What is their context?
 - How might we address the problems we’ve identified?
 - What does success look like?
+- How do design opportunities impact the overall service and organizational context?
 
 ### Evaluative research
 
-Evaluative research is the research you do to test assumptions, hypotheses, and the ease of use of design solutions, such as prototypes. 
+Evaluative research is the research you do to test assumptions, hypotheses, and the ease of use of design solutions. On the 18F Methods site, [Validate methods](https://methods.18f.gov/#validate) like [Multivariate testing](https://methods.18f.gov/validate/multivariate-testing), and [Usability testing ](https://methods.18f.gov/validate/usability-testing) help to understand how to determine if the product or service delivers as you designed.
+
+Evaluative research helps you ask: 
 
-Evaluative research helps you ask: Are we building the right thing — or if this research is done regularly, are we building the thing _right_? Does it meet user needs?
+- Are we building the right thing — or if this research is done regularly, are we building the thing _right_? 
+- Does our product or service meet the needs of people who use it?
 
 ## The process
 
@@ -101,7 +112,7 @@ As a distributed team, 18F defaults to remote-friendly ways of working. This giv
 
 ### In person
 
-With most projects you’ll conduct an in-person kickoff, during which you may have the chance to meet, interview, and conduct activities with stakeholders. If feasible, consider adding [contextual inquiry as described in the 18F methods]( https://methods.18f.gov/discover/contextual-inquiry/) into your kick-off activities. Direct user observation will provide firsthand understanding of your stakeholders’ and users’ processes and contexts.
+With most projects you’ll conduct an in-person kickoff, during which you may have the chance to meet, interview, and conduct activities with stakeholders. If feasible, consider adding [contextual inquiry as described in the 18F methods]( https://methods.18f.gov/discover/contextual-inquiry/) into your kick-off activities. Direct observation will provide firsthand understanding of your stakeholders’ and users’ processes and contexts.
 
 We prefer in-person research when we want to better understand the environment in which users normally interact with a government service. We also prefer in-person research when our participants aren’t especially proficient with, or don’t have access to, video conferencing software.
 
@@ -110,12 +121,12 @@ We prefer in-person research when we want to better understand the environment i
 
 {:.list-item--margin-bottom-extra}
 - **[Choose a research lead.]({{ site.baseurl }}/research/lead)** A research lead is the team member ultimately responsible for setting the research agenda, explaining the team’s methods, tracking the team’s progress, and ensuring research quality. (While the research lead is normally 18F staff at the start, we work with our partners to identify someone on their side before the engagement ends.)
-- **Discuss.** Discuss your research plan and interview guides. Debrief after each session. Make sure to include partners in these discussions, which will go a long way in, getting them on board with research findings [as we discuss in our blog](https://18f.gsa.gov/2018/02/06/getting-partners-on-board-with-research-findings/).
+- **Discuss.** Discuss your research plan and interview guides. Debrief after each session. Make sure to include partners in these discussions, which will go a long way in getting them on board with research findings [as we discuss in our blog](https://18f.gsa.gov/2018/02/06/getting-partners-on-board-with-research-findings/).
 - **Determine research questions as well as interview questions.** (They’re different.)
     - Example research question: _How do medical librarians find and make use of academic journal literature in answering questions for their patrons?_
     - Example interview question: _Tell me about the last time you helped a patron answer a question that required you to review academic journal literature._
 - **Be clear about who your research participants are.** How we approach our research will depend on whether we are interacting with:
-    - Stakeholders (generally our agency partners)
+    - [Stakeholders](https://product-guide.18f.gov/discover/stakeholders/#understand-your-key-stakeholders) (generally our agency partners)
     - Users (those interacting with the system or product we’re investigating)
     - The public at large
 
diff --git a/_pages/research/index.md b/_pages/research/index.md
index dd22bc5..eb415e3 100644
--- a/_pages/research/index.md
+++ b/_pages/research/index.md
@@ -7,4 +7,4 @@ sidenav: research
 sticky_sidenav: true
 ---
 
-The Research section is the foundation of the UX Guide and is core to our work at 18F. This section covers everything you need to know about conducting ethical, inclusive, and unbiased user research from start to finish and includes information about privacy and storing PII as well as legal considerations such as PRA and compensation.
+The Research section is the foundation of the 18F User Experience Guide and is core to our work at 18F. This section covers everything you need to know about conducting ethical, inclusive, and unbiased research with people from start to finish and includes information about privacy and storing PII as well as legal considerations such as PRA and compensation.
diff --git a/_pages/research/make-research-actionable.md b/_pages/research/make-research-actionable.md
index 0dab15b..cdb366e 100644
--- a/_pages/research/make-research-actionable.md
+++ b/_pages/research/make-research-actionable.md
@@ -22,7 +22,7 @@ subnav:
 [//]: make it possible to put a class on a ul tag
 {::options parse_block_html="true" /}
 
-Design research is most valuable when it leads to shared understanding.  Analysis, synthesis, and sharing help us reflect on the data we’ve collected and determine a course of action that involves the broader team.
+Research with people is most valuable when it leads to shared understanding.  Analysis, synthesis, and sharing help us reflect on the data we’ve collected and determine a course of action that involves the broader team.
 
 
 ## From data to insights
@@ -39,12 +39,13 @@ At 18F this generally involves:
 Making meaning always happens in relation to the research questions and/or problem statements identified during [research planning]({{site.baseurl}}/research/plan). Some questions you might ask:
 
 {:.list-item--margin-bottom-extra}
-- What notable experiences did participants share? What were outliers?
+- What notable experiences did people share? What were outliers?
 - What is the root cause of those experiences?
 - What is the context of their use of the product or service?
 - What is their mindset and/or emotional state while using the product or service?
 - What is their mental model of using the product or service?
-- Were there any differences between what users said and what they actually did?
+- Were there any differences between what people said and what they actually did?
+- What are the needs, motivations, and workflows of not only people using the service, but also those of staff supporting the service?
 
 ### Involving the team
 Finding patterns in research is a great time to involve partners and team members, especially people who were not involved in conducting the research. A collaborative approach helps to:
@@ -53,6 +54,7 @@ Finding patterns in research is a great time to involve partners and team member
 - Make research visible
 - Build consensus within the team
 - Harness the perspectives of different listeners (which can help correct for [bias]({{site.baseurl}}/research/bias)
+- Create artifacts that can generate buy-in for overall service design and organizational investments
 
 When inviting partners, think about how exposed they were to the research process and set clear expectations on how you would like them to engage. Be mindful of your [ethical obligation]({{site.baseurl}}/research/ethics) to respect the people who participated in your research. For example, you might want to be careful when involving a CIO in analyzing data you collected while interviewing their employees.
 
@@ -70,7 +72,8 @@ Outside of writing a summary, you should choose your methods based on the desire
 - To build empathy for users and inform future design strategy, you might create a [mental model [18F design methods]](https://methods.18f.gov/decide/mental-modeling/) diagram, by combing through transcripts looking for reasonings, reactions, and guiding principles
 - To create reusable archetypes for grounding user stories and scenarios, you might create a [persona [18F design methods]](https://methods.18f.gov/decide/personas/), by reviewing transcripts for goals, behaviors, and pain points
 - To find themes in your data via a bottom-up process, try [affinity diagramming [18F design methods]](https://methods.18f.gov/decide/affinity-mapping/). Record ideas, quotes, or observations from your research on sticky notes (one idea per sticky note), place them on a wall or whiteboard, and then move the sticky notes into related groups. If working virtually, you can use digital whiteboarding tools such as Mural. Once you have the groupings, you can label them according to a theme or pattern.
-- To make the complexities of a work process or service visible, you might use [task flow analysis [18F design methods]](https://methods.18f.gov/decide/task-flow-analysis/) and [journey mapping [18F design methods]](https://methods.18f.gov/decide/journey-mapping/): these show connections between stakeholders or across organizational silos. Once you’ve visualized the process or journey, you can analyze for key interactions, pain points, and dependencies.
+- To make the complexities of a work process or service visible, you might use [task flow analysis [18F design methods]](https://methods.18f.gov/decide/task-flow-analysis/), service blueprints, or [journey mapping [18F design methods]](https://methods.18f.gov/decide/journey-mapping/): these show connections between stakeholders or across organizational silos. Once you’ve visualized the process or journey, you can analyze for key interactions, pain points, and dependencies.
+- To get buy-in from agency stakeholders or to validate insights and opportunities further with groups most impacted by the work, consider storytelling approaches within reporting, blog posts or press releases, presentations, or sharing sessions. 
 
 Whichever method you use, introduce it to your partner as well so they can build their research skills.
 
@@ -97,6 +100,7 @@ Artifacts that we use to do this include:
 - User stories
 - [Storyboards [18F design methods]](https://methods.18f.gov/decide/storyboarding/)
 - [Journey maps [18F design methods]](https://methods.18f.gov/decide/journey-mapping/)
+- Service blueprints 
 - [Prototypes [18F design methods]](https://methods.18f.gov/make/prototyping/)
 - Other creative outputs
 
@@ -104,7 +108,13 @@ These artifacts are tools for communicating the answers to your research questio
 
 ### Making decisions based on the research
 
-After each round of research, the whole team should identify how the research findings change the work planned for the next sprint. After discovery research, this could include prioritized areas for further exploration or prototyping. For a new or existing product, this could include new bugs identified, new features to explore, or a different design focus.
+After each round of research, the whole team should identify how the research findings change the work planned for the next sprint or for future service design efforts. After discovery research, this could include prioritized areas for further exploration or prototyping. For a new or existing product, this could include new bugs identified, new features to explore, or a different design focus.
+
+Artifacts are most useful when you act on them. For example, a current-state service blueprint could highlight the lengthy amount of time it takes for the public to receive certain benefits, while also highlighting the constraints that staff experience processing applications. What do you do next with these learnings? Here are some activities your team could do to act on these opportunity areas: 
+
+- __Develop user stories:__ A user story is one or more sentences in the language of the user that captures what a user needs to accomplish. You can write it like this: “As a [X], I need [Y] so that I (can) [benefit].” Based on the learnings from the service blueprint, you can create user stories for the public and staff that can inspire recommendations. These user stories can be incorporated into sprint planning at the ticket level, where you can also link back to the service blueprint that inspired these user stories. 
+- __Conduct a prioritization exercise:__ Your team may have a variety of ideas to reduce the time it takes to deliver benefits for both the public and staff. You can set up a two-by-two matrix on a virtual or physical whiteboard, with “level of effort” on the x-axis and “level of impact” on the y-axis. With input from your team’s product owner and any teams impacted by these ideas, like a representative from the staff processing benefit applications, you can plot the ideas from your service blueprint on this matrix. During this exercise, it is important to consider how proposed changes to the product or service could impact the staff delivering the service, which is why it is important to have a representative from the staff participate. Ideas with high impact and low effort could make sense to prioritize first, while ideas with high impact and high effort could be revisited later.
+- __Incorporate recommendations into the product roadmap:__ Based on the results of your prioritization exercise, you can slot recommendations into your [roadmap](https://product-guide.18f.gov/define/roadmap/), using a “Soon/next/later” framework.
 
 
 ## Sharing
@@ -125,7 +135,8 @@ Our research often gets shared far beyond the project team. Depending on the pro
 - The broader 18F organization (chapters, guilds, business development, etc.)
 - Managers and employees above and across our partner’s organization (managers, engineers, press offices, steering committees, legislative bodies, etc.)
 - Other government agencies
-- Members of the public (vendors, press, curious citizens)
+- Policymakers
+- Members of the public (community-based organizations, advocacy groups, vendors, press, others impacted or interested)
 
 Sharing research is all about storytelling. When packaging research, think about what role the audience plays in that story and what the outcomes will be for them. Being clear about who the audience is, what they need to understand, and how they might best understand it, helps us communicate our findings more effectively.
 
@@ -158,7 +169,7 @@ Research handoffs occur when wrapping up a round of research or an engagement, w
 
 {:.list-item--margin-bottom-extra}
 - Who will lead the research moving forward?
-- What will the next research team who picks this up this need to know?
+- What will the next research team who picks this up need to know?
 - Are the notes, recordings, and findings properly organized? ([List of things to catalog](https://docs.google.com/document/d/1m4Q98Ah8XdUs4kfJk7n9vwAEhNApoXMWib_jptMF63Y/edit).
 - Where and how do files containing PII need to be stored in order to maintain privacy? Was all identifying information removed from data that hasn’t been stored securely?
 - Who should have access to what data? How will we get it to them?
diff --git a/_pages/research/plan.md b/_pages/research/plan.md
index 4e716da..0298470 100644
--- a/_pages/research/plan.md
+++ b/_pages/research/plan.md
@@ -76,19 +76,7 @@ Consider holding a research alignment workshop to help stakeholders share and di
 
 ### Methods
 
-Choose one or more methods appropriate for meeting your goals and answering your research questions. Multiple methods can help you challenge or verify information collected and create a more complete understanding.
-[18F’s Methods](https://methods.18f.gov/) provide an overview of our preferred research and design methods. Use these as a starting point, not as a list of constraints.
-
-
-- [Stakeholder and user interviews](https://methods.18f.gov/discover/stakeholder-and-user-interviews/)
-- [Contextual inquiry](https://methods.18f.gov/discover/contextual-inquiry/)
-- [Content audit](https://methods.18f.gov/decide/content-audit/)
-- [User interviews](https://methods.18f.gov/discover/stakeholder-and-user-interviews/)
-- [Design studio](https://methods.18f.gov/discover/design-studio/)
-- [KJ Method](https://methods.18f.gov/discover/kj-method/)
-- [Usability testing](https://methods.18f.gov/validate/usability-testing/)
-- [Cognitive walkthrough](https://methods.18f.gov/discover/cognitive-walkthrough/)
-- [Card sorting](https://methods.18f.gov/validate/card-sorting/)
+Choose one or more methods appropriate for meeting your goals and answering your research questions. Multiple methods can help you challenge or verify information collected and create a more complete understanding. [18F’s Methods](https://methods.18f.gov/) provide an overview of our preferred research and design methods. Use these as a starting point, not as a list of constraints. See the [Research types](https://ux-guide.18f.gov/research/clarify-the-basics/#research-types) section of UX Guide for more on which methods might be the best fit for the type of research you are doing.
 
 ### Team participation
 
@@ -140,7 +128,7 @@ Most of 18F’s design research depends on you directly interacting with people.
 
 ### Identifying participant groups
 
-Because of the time-limited nature of 18F engagements, participant groups can depend on the [type of research]({{site.baseurl}}/research/clarify-the-basics/#research-types) you're doing and where you’re at in the overall design process. For example, if you’re doing stakeholder interviews as part of a Path Analysis project, you’re likely to learn more about who you need to talk to with each interview you do. We recommend asking “Who else should we speak with?” in these discovery issues. This can help you learn of user groups whose needs should be considered. You might focus future rounds of research on learning from people within these user groups.
+Because of the time-limited nature of 18F engagements, participant groups can depend on the [type of research]({{site.baseurl}}/research/clarify-the-basics/#research-types) you're doing and where you’re at in the overall design process. For example, if you’re doing stakeholder interviews as part of a Path Analysis project, you’re likely to learn more about who you need to talk to with each interview you do. We recommend asking “Who else should we speak with?” in these discovery issues. This can help you learn of groups whose needs should be considered. You might focus future rounds of research on learning from people within these groups.
 
 Once you've [framed a problem](https://github.com/18F/path-analysis/blob/master/approach.md#2-draft-a-problem-statement) or research hypothesis, it’s important that your participant groups include people who represent the make-up of the public who may experience the problem or need to use the related service. User profiles and personas are a good place to start, if they are based on existing data. Revise them as you learn more about the users of your service.
 
@@ -153,7 +141,7 @@ Consider especially:
 - People who may need help using the service in question
 - People who have limited internet access
 
-[The Access Board's Section 508 standards](https://www.section508.gov/) require that our designs are accessible to people with disabilities. The best way to make sure our products and services are accessible is to design for these users from the start. Include people with disabilities in your user research and usability testing. To learn more about inclusive design, visit [Digital.gov's Accessibility for Teams](https://accessibility.digital.gov/), [18F's Accessibility Guide](https://accessibility.18f.gov/), or the TTS Accessibility guild [#g-accessibility](https://gsa-tts.slack.com/archives/C02BT4H5Q).
+[The Access Board's Section 508 standards](https://www.section508.gov/) require that our designs are accessible to people with disabilities. The best way to make sure our products and services are accessible is to design for these users from the start. Include people with disabilities in your research and usability testing. To learn more about inclusive design, visit [Digital.gov's Accessibility for Teams](https://accessibility.digital.gov/), [18F's Accessibility Guide](https://accessibility.18f.gov/), or the TTS Accessibility guild [#g-accessibility](https://gsa-tts.slack.com/archives/C02BT4H5Q).
 
 ### Defining recruitment criteria
 
@@ -182,7 +170,7 @@ It’s important to ensure the audiences you’re designing products and service
 
 #### Recruitment with non-native English speakers
 
-You could consider many scenarios to include non-native English speakers in user research activities, including:
+You could consider many scenarios to include non-native English speakers in research activities, including:
 - **Developing multilingual website content:** When your public-facing website is offered in multiple languages, you need to ensure the content in each language is written in plain language, accessible, and culturally appropriate. Set up usability sessions to test the content with people who speak these languages.
 
 - **Understanding barriers:** When you’re conducting discovery research to understand barriers that people face accessing your service, decide on multiple populations to conduct interviews with, including non-native English speakers.
@@ -191,9 +179,9 @@ We recommend recruiting people who speak the language you are focusing on as the
 
 Cultural and historical context matters when we decide how to screen for participants who speak certain languages and not others, especially when considering those who live in not just states but tribes and territories, too. If possible, consult on wording for screening questions with colleagues from the communities you want to conduct research with.  
 
-There are two distinct modes of engaging with language that you might encounter in the user research process: interpreting and translating.
+There are two distinct modes of engaging with language that you might encounter in the research process: interpreting and translating.
 
-**Interpreting:** Applies to spoken language in real time or with a delay. For example, including an interpreter in a user research interview with someone who only speaks Portuguese, or collaborating with an interviewer who will conduct interviews for you in the language you are focusing on. 
+**Interpreting:** Applies to spoken language in real time or with a delay. For example, including an interpreter in a research interview with someone who only speaks Portuguese, or collaborating with an interviewer who will conduct interviews for you in the language you are focusing on. 
 
 **Translating:** Applies to written content. This can include recruitment materials, your interview script, interview notes, and video clips.
 When translating materials, it’s essential to consider the cultural context of the demographic you’re recruiting. Some groups will need a little more context, some less. For instance, a newcomer to the U.S. may need a little more information about how to register and vote than a person who grew up in the U.S. and had voting woven into the fabric of their lives.
@@ -210,7 +198,7 @@ See if your partner agency has an Interagency Agreement (IAA) set up with either
 
 #### Resources for recruiting non-native English speakers
 
-The [Multilingual Community of Practice](https://digital.gov/communities/multilingual/?promo) is a valuable resource for practitioners across government to expand and improve digital content in languages other than English. It includes a mailing list where people can share user research opportunities seeking participants who speak particular languages, among other ideas, challenges and best practices for managing multilingual content and websites. 
+The [Multilingual Community of Practice](https://digital.gov/communities/multilingual/?promo) is a valuable resource for practitioners across government to expand and improve digital content in languages other than English. It includes a mailing list where people can share design research opportunities seeking participants who speak particular languages, among other ideas, challenges and best practices for managing multilingual content and websites. 
 
 #### Recruitment within underserved communities
 
@@ -226,7 +214,7 @@ Examples of underserved communities:
 - People otherwise adversely affected by persistent poverty or inequality
 
 #### Partnering with community organizations 
-When conducting user research with people who have been historically underserved, we must make sure we are not contributing to the power imbalances, extractive practices, and harm that led to these communities becoming underserved and marginalized in the first place. 
+When conducting research with people who have been historically underserved, we must make sure we are not contributing to the power imbalances, extractive practices, and harm that led to these communities becoming underserved and marginalized in the first place. 
 
 In this research, it is important to partner with community organizations, who work closely to support and advocate for the needs of their communities.
 
@@ -244,7 +232,7 @@ Just as you consider diversity in your recruitment criteria for participants, yo
 
 If your partner agency does not have established relationships with communities or the organizations that support them, carefully consider whether to move forward with this research. 
 
-We encourage you and your partner organization to weigh the tradeoffs of trying to introduce yourselves and the research opportunity. Recruiting is often the most time-consuming part of user research, and without established relationships with communities, you are more likely to encounter delays. It takes a long time to earn trust. 
+We encourage you and your partner organization to weigh the tradeoffs of trying to introduce yourselves and the research opportunity. Recruiting is often the most time-consuming part of design research, and without established relationships with communities, you are more likely to encounter delays. It takes a long time to earn trust. 
 
 #### Guiding questions to help you and your partner agency decide to conduct research with communities
 
@@ -271,9 +259,9 @@ To learn about various strategies for creating recruitment materials and screeni
 
 ### Compensating research participants
 
-GSA can compensate members of the public for participating in user research. We can not compensate government employees. <strong>We must do research with people who will actually use our services</strong>. See the TTS Handbook for specifics on the process we use to [compensate user research participants](https://handbook.tts.gsa.gov/18f/how-18f-works/research-guidelines/#compensating-user-research-participants).
+GSA can compensate members of the public for participating in design research. We can not compensate government employees. <strong>We must do research with people who will actually use our services</strong>. See the TTS Handbook for specifics on the process we use to [compensate research participants](https://handbook.tts.gsa.gov/18f/how-18f-works/research-guidelines/#compensating-user-research-participants).
 
-[Section 508 standards](https://www.access-board.gov/ict/) require that our designs are accessible to people with disabilities. The best way to make sure our products and services are accessible is to design for these users from the start. Include people with disabilities in your user research and usability testing. To learn more about inclusive design, visit [Accessibility for Teams](https://accessibility.digital.gov/), [18F's Accessibility Guide](https://accessibility.18f.gov/), or the TTS Accessibility guild [#g-accessibility](https://gsa-tts.slack.com/archives/C02BT4H5Q).
+[Section 508 standards](https://www.access-board.gov/ict/) require that our designs are accessible to people with disabilities. The best way to make sure our products and services are accessible is to design for these users from the start. Include people with disabilities in your design research and usability testing. To learn more about inclusive design, visit [Accessibility for Teams](https://accessibility.digital.gov/), [18F's Accessibility Guide](https://accessibility.18f.gov/), or the TTS Accessibility guild [#g-accessibility](https://gsa-tts.slack.com/archives/C02BT4H5Q).
 
 #### Why do we offer compensation?
 
diff --git a/_pages/resources.md b/_pages/resources.md
index ff56a80..2582edf 100644
--- a/_pages/resources.md
+++ b/_pages/resources.md
@@ -80,7 +80,7 @@ An email asking participants to review and sign a participant agreement before t
 
 ### Collaboration
 
-Doing UX at 18F can involve working with Content and Visual Designers, or people in our [Acquisition](https://handbook.tts.gsa.gov/acqstack/), [Product Management](https://handbook.tts.gsa.gov/product/) and [Engineering](https://handbook.tts.gsa.gov/engineering/) Chapters. Read their pages in the [TTS/18F Handbook](https://handbook.tts.gsa.gov/) for more information.
+Designers at 18F should work together with other designers or people in our [Acquisition](https://handbook.tts.gsa.gov/acqstack/), [Product Management](https://handbook.tts.gsa.gov/product/) and [Engineering](https://handbook.tts.gsa.gov/engineering/) Chapters. Read their pages in the [TTS/18F Handbook](https://handbook.tts.gsa.gov/) for more information.
 
 
 18F/TTS staff can also participate in local communities of practice in by joining (18F/TTS access only):
@@ -144,7 +144,7 @@ We most commonly share our work via presentations. These presentations can vary
 - [Research presentation template](https://docs.google.com/presentation/d/1hB0tX65pHGRESHc2e_tGlO65Q4AGwSWFuqhSNImNuRk/edit#slide=id.g9af2006e6a_1_238)
 
 ## Additional reading
-
+- [Digital.gov: Understanding design in 10 questions](https://digital.gov/2023/03/03/understanding-design-in-10-questions/)
 - [GSA + the Lab@OPM’s Human-Centered Design Discovery Stage Field Guide ](https://www.gsa.gov/cdnstatic/HCD-Discovery-Guide-Interagency-v12-1.pdf)
 - [Lab@OPM's HCD Discovery Concept Guide](https://the-lab-at-opm.github.io/HCD-Discovery-Concept-Guide/)
 - [Lab@OPM's HCD Discovery Operations Guide](https://the-lab-at-opm.github.io/HCD-Discovery-Operations-Guide/)