From 536001f5151e3cbd684884c5cc508e7f630bad76 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Mon, 9 Dec 2019 09:44:57 -0500
Subject: [PATCH 01/50] Add harm prompts to Design Hypothesis
Added suggested harm prompts from issue #420. Removed the link to the 18F Example since it has been archived. Added detail to "Additional resources" link.
---
_methods/Design-hypotheses.md | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/_methods/Design-hypotheses.md b/_methods/Design-hypotheses.md
index 97384557..a3c58171 100644
--- a/_methods/Design-hypotheses.md
+++ b/_methods/Design-hypotheses.md
@@ -21,24 +21,20 @@ timeRequired: 1-2 hours
Here’s a common way to structure your hypothesis:
- *We believe that doing/building/creating [this] for [this user] will result in [this outcome]. We’ll know we’re right when we see [this metric/signal].*
+ *We believe that doing/building/creating [this] for [this user] will result in [this outcome].*
+ *We’ll know we’re right when we see [this metric/signal].*
+
+1. Once you've formulated your hypothesis, consider the following "harm prompt." These can help the team think about the potential unintended consequences of your work and the limitations of your knowledge.
-1. Identify the main entry points for the user need you're addressing. This could be external marketing, the homepage, a microsite, or another page.
-1. Build or do the thing, and measure. If you learned something unexpected, then create a new hypothesis and change course so you can continue working toward your goals.
+ *But, this could be harmful for [this user] if [this outcome happens].*
-
+1. Identify a user touchpoint that will allow you to test your hypothesis. This could be external marketing, the homepage, a microsite, or something else. Build or do the thing, and measure. If you learned something unexpected, then create a new hypothesis and change course so you can continue working toward your goals.
From 4b90dadfc3ec399d2d816e7647109601bc9da04e Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Mon, 9 Dec 2019 10:31:08 -0500
Subject: [PATCH 02/50] Change "government considerations"
---
_methods/stakeholder-and-user-interviews.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/stakeholder-and-user-interviews.md b/_methods/stakeholder-and-user-interviews.md
index 5b13158b..d2f79f89 100755
--- a/_methods/stakeholder-and-user-interviews.md
+++ b/_methods/stakeholder-and-user-interviews.md
@@ -31,7 +31,7 @@ timeRequired: 1–2 hours per interviewee
-## Applied in government research
+## Government considerations
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From 6bb9fb087f084917c164aefbe581e50c1598ce6f Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Mon, 9 Dec 2019 10:38:37 -0500
Subject: [PATCH 03/50] Update Design-hypotheses.md
---
_methods/Design-hypotheses.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/_methods/Design-hypotheses.md b/_methods/Design-hypotheses.md
index a3c58171..6200056c 100644
--- a/_methods/Design-hypotheses.md
+++ b/_methods/Design-hypotheses.md
@@ -24,11 +24,11 @@ timeRequired: 1-2 hours
*We believe that doing/building/creating [this] for [this user] will result in [this outcome].*
*We’ll know we’re right when we see [this metric/signal].*
-1. Once you've formulated your hypothesis, consider the following "harm prompt." These can help the team think about the potential unintended consequences of your work and the limitations of your knowledge.
+1. Once you've formulated your hypothesis, consider the following harm prompt to help the team think about and guard against potential unintended consequences of your work.
*But, this could be harmful for [this user] if [this outcome happens].*
-1. Identify a user touchpoint that will allow you to test your hypothesis. This could be external marketing, the homepage, a microsite, or something else. Build or do the thing, and measure. If you learned something unexpected, then create a new hypothesis and change course so you can continue working toward your goals.
+1. Identify a user touchpoint that will allow you to test your hypothesis, such as external marketing, the homepage, a microsite, or something else. Test your hypothesis. If you learn something unexpected, refine your hypothesis, test again, and continue to work incrementally towards your goals.
From afab141df184b0eadaf0033375b2f184e26f3e9a Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 16:57:45 -0500
Subject: [PATCH 04/50] Update Design-hypotheses.md
Considerations for use in government
---
_methods/Design-hypotheses.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/Design-hypotheses.md b/_methods/Design-hypotheses.md
index 97384557..dd03ea1e 100644
--- a/_methods/Design-hypotheses.md
+++ b/_methods/Design-hypotheses.md
@@ -43,7 +43,7 @@ timeRequired: 1-2 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 4f4d01f67a96a780e1205b069050251da6e4dc38 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 16:58:10 -0500
Subject: [PATCH 05/50] Update affinity-diagramming.md
Considerations for use in government
---
_methods/affinity-diagramming.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/affinity-diagramming.md b/_methods/affinity-diagramming.md
index f4a2f386..50a6bb15 100755
--- a/_methods/affinity-diagramming.md
+++ b/_methods/affinity-diagramming.md
@@ -28,6 +28,6 @@ timeRequired: 1 hour
-## Applied in government research
+## Considerations for use in government
No PRA implications. This method may use data gathered from members of the public, but does not require their involvement.
From 32d18b38d3574f5d7dbcd76d912e96b300b9d9c2 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 16:58:29 -0500
Subject: [PATCH 06/50] Update card-sorting.md
---
_methods/card-sorting.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/card-sorting.md b/_methods/card-sorting.md
index dc42bc2d..c12ba5c1 100755
--- a/_methods/card-sorting.md
+++ b/_methods/card-sorting.md
@@ -34,6 +34,6 @@ There are two types of card sorting: open and closed. Most card sorts are perfor
-## Applied in government research
+## Considerations for use in government
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. It also explicitly excludes tests of knowledge or aptitude, 5 CFR 1320.3(h)7, which is essentially what a card sort tests (though in our case, a poor result is our fault).
From 88f1738bf2024c26ffe6a51618fcabbacb86ddd7 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 16:58:50 -0500
Subject: [PATCH 07/50] Update cognitive-walkthrough.md
Considerations for use in government
---
_methods/cognitive-walkthrough.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/cognitive-walkthrough.md b/_methods/cognitive-walkthrough.md
index b7fe41e1..d967e545 100755
--- a/_methods/cognitive-walkthrough.md
+++ b/_methods/cognitive-walkthrough.md
@@ -28,7 +28,7 @@ timeRequired: 30 minutes to one hour per person
-## Applied in government research
+## Considerations for use in government
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation (e.g., not a survey) that a cognitive walkthrough entails, 5 CFR 1320.3(h)3.
If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
From 6519a3205cf635e4fcecc767566115b5d22bfc9a Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 16:59:10 -0500
Subject: [PATCH 08/50] Update comparative-analysis.md
Considerations for use in government
---
_methods/comparative-analysis.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/comparative-analysis.md b/_methods/comparative-analysis.md
index c88f02ce..d0505af6 100755
--- a/_methods/comparative-analysis.md
+++ b/_methods/comparative-analysis.md
@@ -27,6 +27,6 @@ timeRequired: 1–2 hours to analyze and write an evaluation about each competit
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 89d95716507d5bca1023ea7982a10974ddb5d8ba Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 16:59:57 -0500
Subject: [PATCH 09/50] Update comparative-analysis.md
---
_methods/comparative-analysis.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/_methods/comparative-analysis.md b/_methods/comparative-analysis.md
index d0505af6..4abd0c60 100755
--- a/_methods/comparative-analysis.md
+++ b/_methods/comparative-analysis.md
@@ -28,5 +28,6 @@ timeRequired: 1–2 hours to analyze and write an evaluation about each competit
## Considerations for use in government
+
No PRA implications. No information is collected from members of the public.
From 05a0028c58a20afa0a62830bc40d2acf0e63633a Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:00:19 -0500
Subject: [PATCH 10/50] Update comparative-analysis.md
---
_methods/comparative-analysis.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/_methods/comparative-analysis.md b/_methods/comparative-analysis.md
index 4abd0c60..843a8556 100755
--- a/_methods/comparative-analysis.md
+++ b/_methods/comparative-analysis.md
@@ -27,7 +27,8 @@ timeRequired: 1–2 hours to analyze and write an evaluation about each competit
-## Considerations for use in government
+
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From ba0f66d021af2402b0528523f66c4e99a0f999db Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:00:45 -0500
Subject: [PATCH 11/50] Update content-audit.md
Considerations for use in government
---
_methods/content-audit.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/content-audit.md b/_methods/content-audit.md
index 19881cb3..c849bbf9 100755
--- a/_methods/content-audit.md
+++ b/_methods/content-audit.md
@@ -47,6 +47,6 @@ timeRequired: 3-8 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 222ea6158fc87636dda26874733825ff4ca709cf Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:01:08 -0500
Subject: [PATCH 12/50] Update content-audit.md
---
_methods/content-audit.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/_methods/content-audit.md b/_methods/content-audit.md
index c849bbf9..62eaa7e4 100755
--- a/_methods/content-audit.md
+++ b/_methods/content-audit.md
@@ -39,7 +39,7 @@ timeRequired: 3-8 hours
-## Considerations for use in government
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 2b7d3db413d086dc178fe6cabb8206739e7a2e5f Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:02:21 -0500
Subject: [PATCH 13/50] Update content-audit.md
---
_methods/content-audit.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/_methods/content-audit.md b/_methods/content-audit.md
index 62eaa7e4..a62f0753 100755
--- a/_methods/content-audit.md
+++ b/_methods/content-audit.md
@@ -39,6 +39,7 @@ timeRequired: 3-8 hours
+
## Considerations for use in government
+
No PRA implications. No information is collected from members of the public.
From 3978182b04b29cd3cf254c619f03165800f087f6 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:03:03 -0500
Subject: [PATCH 14/50] Update affinity-diagramming.md
---
_methods/affinity-diagramming.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/_methods/affinity-diagramming.md b/_methods/affinity-diagramming.md
index 50a6bb15..8a817bac 100755
--- a/_methods/affinity-diagramming.md
+++ b/_methods/affinity-diagramming.md
@@ -21,13 +21,16 @@ timeRequired: 1 hour
-## Additional resources
+
+## Additional resources
- [An explanation of what affinity diagramming is and how to do it.](http://www.usabilitybok.org/affinity-diagram) The Usability Body of Knowledge, a product of the User Experience Professionals' Association.
- [An explanation of affinity diagramming.](http://infodesign.com.au/usabilityresources/affinitydiagramming/) Information and Design.
-## Considerations for use in government
+
+## Considerations for use in government
+
No PRA implications. This method may use data gathered from members of the public, but does not require their involvement.
From 255469cb7c94fff54704520fead048d1564caa5e Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:06:24 -0500
Subject: [PATCH 15/50] Update card-sorting.md
---
_methods/card-sorting.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/_methods/card-sorting.md b/_methods/card-sorting.md
index c12ba5c1..fec58920 100755
--- a/_methods/card-sorting.md
+++ b/_methods/card-sorting.md
@@ -33,7 +33,9 @@ There are two types of card sorting: open and closed. Most card sorts are perfor
- [Research plan including card sorting from 18F's C2 project](https://github.com/18F/C2/wiki/Sprint-5:-Interaction-model-June-2016)
-
-## Considerations for use in government
+
+
+## Considerations for use in government
+
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. It also explicitly excludes tests of knowledge or aptitude, 5 CFR 1320.3(h)7, which is essentially what a card sort tests (though in our case, a poor result is our fault).
From 1b222f8afc558ee4951437ca674871afee0271de Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:08:17 -0500
Subject: [PATCH 16/50] Update cognitive-walkthrough.md
---
_methods/cognitive-walkthrough.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/_methods/cognitive-walkthrough.md b/_methods/cognitive-walkthrough.md
index d967e545..fd8bd6e9 100755
--- a/_methods/cognitive-walkthrough.md
+++ b/_methods/cognitive-walkthrough.md
@@ -21,14 +21,17 @@ timeRequired: 30 minutes to one hour per person
1. Pay attention to expected outcomes and how quickly/easily participants are able to pick up a task.
1. Analyze the walkthrough results to highlight where the user struggled and what needs improvement.
-
-## Additional resources
+
+
+## Additional resources
- [An explanation of cognitive walkthroughs and how to conduct one.](http://www.usabilitybok.org/cognitive-walkthrough) The Usability Body of Knowledge, a product of the User Experience Professionals' Association.
-## Considerations for use in government
+
+## Considerations for use in government
+
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation (e.g., not a survey) that a cognitive walkthrough entails, 5 CFR 1320.3(h)3.
If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
From 5d1dcdb79a46932308537849af8d96a15a3c9d79 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:09:01 -0500
Subject: [PATCH 17/50] Update contextual-inquiry.md
---
_methods/contextual-inquiry.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/_methods/contextual-inquiry.md b/_methods/contextual-inquiry.md
index 6e0f5479..7b556f00 100755
--- a/_methods/contextual-inquiry.md
+++ b/_methods/contextual-inquiry.md
@@ -28,14 +28,16 @@ A pair of 18F team members visited two Department of Labor/Wage Hour Division in
-## Additional resources
+
+## Additional resources
- [Observational research: 5 Tips for Improving Your Approach](https://hodigital.blog.gov.uk/2019/01/18/observational-research-5-tips-for-improving-your-approach%e2%80%af%e2%80%af/)
-## Applied in government research
+
+## Applied in government research
No PRA implications, if done properly. Contextual interviews should be non-standardized, conversational, and based on observation. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From 2b34f4074553e44b1487f0c3a747528043992aa6 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:09:26 -0500
Subject: [PATCH 18/50] Update contextual-inquiry.md
---
_methods/contextual-inquiry.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/_methods/contextual-inquiry.md b/_methods/contextual-inquiry.md
index 7b556f00..89f84c38 100755
--- a/_methods/contextual-inquiry.md
+++ b/_methods/contextual-inquiry.md
@@ -21,7 +21,8 @@ governmentConsiderations:
1. Immediately after, write up your notes.
-## Example from 18F
+
+## Example from 18F
A pair of 18F team members visited two Department of Labor/Wage Hour Division investigators as they interviewed home health care workers who were subject to unpaid overtime and other infractions. Since it was a sensitive subject, the 18F team did not question the health care workers directly, but instead asked the investigators clarifying questions in private. 18F staff also made sure that photos did not include faces.
From 9b1c481acad641fe74ac648392052c384351a13f Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:10:18 -0500
Subject: [PATCH 19/50] Update design-pattern-library.md
---
_methods/design-pattern-library.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/design-pattern-library.md b/_methods/design-pattern-library.md
index 81d8964e..8e9400cf 100755
--- a/_methods/design-pattern-library.md
+++ b/_methods/design-pattern-library.md
@@ -21,7 +21,7 @@ timeRequired: 1–2 hours per pattern; ongoing maintenance.
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From d9771054512de4cea5b1bb1cb7e2a7a32a740674 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:10:55 -0500
Subject: [PATCH 20/50] Update design-principles.md
Considerations for use in government
---
_methods/design-principles.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/design-principles.md b/_methods/design-principles.md
index d9511c87..012b08fb 100755
--- a/_methods/design-principles.md
+++ b/_methods/design-principles.md
@@ -38,7 +38,7 @@ timeRequired: 1 week, plus occasional refresher meetings
-## Applied in government research
+## Considerations for use in government
No PRA implications. Generally, no information is collected from members of the public. Even when stakeholders are members of the public, the PRA explicitly exempts direct observation and non-standardized conversation (e.g., not a survey), 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From db54b82f2919d30b07e8eeb922ce43512b12ac82 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:11:29 -0500
Subject: [PATCH 21/50] Update design-studio.md
Considerations for use in government
---
_methods/design-studio.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/design-studio.md b/_methods/design-studio.md
index 98d4fede..15e8d6a7 100755
--- a/_methods/design-studio.md
+++ b/_methods/design-studio.md
@@ -31,7 +31,7 @@ timeRequired: 3–4 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. If conducted with nine or fewer members of the public, the PRA does not apply, 5 CFR 1320.5(c)4. If participants are employees, the PRA does not apply.
From 9086d237732c79db5533a0bab5bccd4637c8f24f Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:12:06 -0500
Subject: [PATCH 22/50] Update dot-voting.md
Considerations for use in government
---
_methods/dot-voting.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/dot-voting.md b/_methods/dot-voting.md
index fa568239..669e62bf 100755
--- a/_methods/dot-voting.md
+++ b/_methods/dot-voting.md
@@ -25,7 +25,7 @@ timeRequired: 15 minutes
-## Applied in government research
+## Considerations for use in government
No PRA implications: dot voting falls under "direct observation", which is explicitly exempt from the PRA, 5 CFR 1320(h)3. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From cf1ffdf0053553c5dc8d3ed91c4e9dde118213f8 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:13:39 -0500
Subject: [PATCH 23/50] Update heuristic-evaluation.md
Considerations for use in government
---
_methods/heuristic-evaluation.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/heuristic-evaluation.md b/_methods/heuristic-evaluation.md
index 996dc901..d00bedae 100755
--- a/_methods/heuristic-evaluation.md
+++ b/_methods/heuristic-evaluation.md
@@ -33,7 +33,7 @@ timeRequired: 1–2 hours
-## Applied in government research
+## Considerations for use in government
No PRA Implications, as heuristic evaluations usually include a small number of evaluators. If conducted with nine or fewer members of the public, the PRA does not apply, 5 CFR 1320.5(c)4. If participants are employees, the PRA does not apply. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From 2b193a6605116aa34c4374db28b4307fd1671421 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:14:07 -0500
Subject: [PATCH 24/50] Update hopes-and-fears.md
Considerations for use in government
---
_methods/hopes-and-fears.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/hopes-and-fears.md b/_methods/hopes-and-fears.md
index e4d18543..128a57cb 100644
--- a/_methods/hopes-and-fears.md
+++ b/_methods/hopes-and-fears.md
@@ -42,7 +42,7 @@ This format can be adapted to include other categories. For example, asking part
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From bb5408e04111914940c5e84457db0b7624239cb3 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:14:39 -0500
Subject: [PATCH 25/50] Update incentives.md
Considerations for use in government
---
_methods/incentives.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/incentives.md b/_methods/incentives.md
index f4564be3..d1f73512 100755
--- a/_methods/incentives.md
+++ b/_methods/incentives.md
@@ -18,7 +18,7 @@ timeRequired: N/A
-## Applied in government research
+## Considerations for use in government
- No PRA implications. Even when users are present, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3.
- If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
From 7eca791137bd1b1c85f2e7f147d61dd030e0f125 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:15:28 -0500
Subject: [PATCH 26/50] Update journey-mapping.md
Considerations for use in government
---
_methods/journey-mapping.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/journey-mapping.md b/_methods/journey-mapping.md
index 77f56964..02b9f2d0 100755
--- a/_methods/journey-mapping.md
+++ b/_methods/journey-mapping.md
@@ -34,7 +34,7 @@ timeRequired: 4–12 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/#recruiting) and [Privacy](/fundamentals/privacy/#privacy) for more tips on taking input from the public.
From 643f366a75fcf63930170dce067945960743c33c Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:16:04 -0500
Subject: [PATCH 27/50] Update kj-method.md
Considerations for use in government
---
_methods/kj-method.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/kj-method.md b/_methods/kj-method.md
index d4def2fe..49235761 100755
--- a/_methods/kj-method.md
+++ b/_methods/kj-method.md
@@ -36,7 +36,7 @@ timeRequired: 1–2 hours
-## Applied in government research
+## Considerations for use in government
At 18F, KJ participants are almost always federal employees. If there is any chance your KJ workshop could include participants who are not federal employees, consult OMB guidance on the Paperwork Reduction Act and the Privacy Act. Your agency's Office of General Counsel, and perhaps OIRA desk officers, also can ensure you are following the laws and regulations applicable to federal agencies.
From b8df481cc18e5aad5be551bd58ade1383994b285 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:16:31 -0500
Subject: [PATCH 28/50] Update kj-method.md
Considerations for use in government
---
_methods/kj-method.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/_methods/kj-method.md b/_methods/kj-method.md
index 49235761..cf16e21f 100755
--- a/_methods/kj-method.md
+++ b/_methods/kj-method.md
@@ -23,7 +23,8 @@ timeRequired: 1–2 hours
1. Combine duplicates and their points if the entire group agrees they're identical. Three or four groups usually rank higher than the rest - these are the priorities for the question.
-## Example from 18F
+
+## Example from 18F
18F conducted this exercise with 20 Federal Election Commission staff members to define priorities around conflicting requests. We used this method to get data from staff (not the decision makers) about what they saw as the most pressing needs. We synthesized and presented the data back to the decision makers.
From 35890829dd9289a6097f8afac1686c2c24570090 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:20:23 -0500
Subject: [PATCH 29/50] Update and rename mental-modelling.md to
mental-modeling.md
Considerations for use in government
---
_methods/{mental-modelling.md => mental-modeling.md} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename _methods/{mental-modelling.md => mental-modeling.md} (97%)
diff --git a/_methods/mental-modelling.md b/_methods/mental-modeling.md
similarity index 97%
rename from _methods/mental-modelling.md
rename to _methods/mental-modeling.md
index a579b295..79f56c0a 100755
--- a/_methods/mental-modelling.md
+++ b/_methods/mental-modeling.md
@@ -28,7 +28,7 @@ timeRequired: 1–2 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From d8e5f9a5f8fce1dbe47e69cd8f2213053fe30f54 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:22:11 -0500
Subject: [PATCH 30/50] Update multivariate-testing.md
Considerations for use in government
---
_methods/multivariate-testing.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/_methods/multivariate-testing.md b/_methods/multivariate-testing.md
index 964dff04..492426d0 100755
--- a/_methods/multivariate-testing.md
+++ b/_methods/multivariate-testing.md
@@ -28,7 +28,8 @@ timeRequired: 2–5 days of effort, 1–4 weeks elapsed through the testing peri
-## Applied in government research
+
+## Considerations for use in government
No PRA implications. No one asks the users questions, so the PRA does not apply. See the methods for [Recruiting](/fundamentals/recruiting/#recruiting) and [Privacy](/fundamentals/privacy/#privacy) for more tips on taking input from the public.
From db46ca5314eab59d36f4a051d1bf09649d3dbfa6 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:22:38 -0500
Subject: [PATCH 31/50] Update personas.md
---
_methods/personas.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/personas.md b/_methods/personas.md
index 411638ed..4e51d0c3 100755
--- a/_methods/personas.md
+++ b/_methods/personas.md
@@ -37,7 +37,7 @@ timeRequired: 2–3 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 40fa0be3a4b8b36f53e05b5f1204d4e6d7e2d8de Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:23:04 -0500
Subject: [PATCH 32/50] Update privacy.md
Considerations for use in government
---
_methods/privacy.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/privacy.md b/_methods/privacy.md
index cf1292d9..708beca5 100755
--- a/_methods/privacy.md
+++ b/_methods/privacy.md
@@ -28,7 +28,7 @@ timeRequired: N/A
-## Applied in government research
+## Considerations for use in government
The government's use of information about people is subject to a number of laws and policies, including: [the Privacy Act of 1974](https://www.justice.gov/opcl/overview-privacy-act-1974-2015-edition), the Federal Information Security Management Act of 2002, and the eGovernment Act of 2002.
From f948604e3517a008674ca1666f9bc047998f9cfa Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:23:49 -0500
Subject: [PATCH 33/50] Update prototyping.md
Considerations for use in government
---
_methods/prototyping.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/prototyping.md b/_methods/prototyping.md
index 3d92e581..7055055e 100755
--- a/_methods/prototyping.md
+++ b/_methods/prototyping.md
@@ -22,7 +22,7 @@ timeRequired: 4 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/#recruiting) and [Privacy](/fundamentals/privacy/#privacy) for more tips on taking input from the public.
From b587cfc9f8fbd02b05382b87481f114d9f576dcd Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:26:27 -0500
Subject: [PATCH 34/50] Update recruiting.md
Considerations for use in government
---
_methods/recruiting.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/recruiting.md b/_methods/recruiting.md
index 71992358..2335c130 100755
--- a/_methods/recruiting.md
+++ b/_methods/recruiting.md
@@ -28,7 +28,7 @@ timeRequired: 1–2 weeks for 5–10 participants
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 1616aed9bfc924cfd9fd5d4f6bddc77946c08193 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:27:03 -0500
Subject: [PATCH 35/50] Update site-mapping.md
Considerations for use in government
---
_methods/site-mapping.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/site-mapping.md b/_methods/site-mapping.md
index 6fff1adc..f60db7a9 100755
--- a/_methods/site-mapping.md
+++ b/_methods/site-mapping.md
@@ -20,7 +20,7 @@ timeRequired: 2–3 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 769067d9d54f23da72b953c9bcc3b7a53e75e8c4 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:27:36 -0500
Subject: [PATCH 36/50] Update stakeholder-and-user-interviews.md
---
_methods/stakeholder-and-user-interviews.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/stakeholder-and-user-interviews.md b/_methods/stakeholder-and-user-interviews.md
index d2f79f89..cbe18283 100755
--- a/_methods/stakeholder-and-user-interviews.md
+++ b/_methods/stakeholder-and-user-interviews.md
@@ -31,7 +31,7 @@ timeRequired: 1–2 hours per interviewee
-## Government considerations
+## Considerations for use in government
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From a8664b0d0477c7fd977700d1a49e93ae02bece72 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:28:27 -0500
Subject: [PATCH 37/50] Update storyboarding.md
Considerations for use in government
---
_methods/storyboarding.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/storyboarding.md b/_methods/storyboarding.md
index 01bf045e..206b59b1 100755
--- a/_methods/storyboarding.md
+++ b/_methods/storyboarding.md
@@ -30,7 +30,7 @@ timeRequired: 1–2 days depending on the complexity of the scenario(s)
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 2f5239f1ea01a79dc6334d18200a77c5755c4b4b Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:29:06 -0500
Subject: [PATCH 38/50] Update style-tiles.md
Considerations for use in government
---
_methods/style-tiles.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/_methods/style-tiles.md b/_methods/style-tiles.md
index a897a740..1a0458d4 100755
--- a/_methods/style-tiles.md
+++ b/_methods/style-tiles.md
@@ -18,8 +18,9 @@ timeRequired: 1–2 days depending on how many rounds of feedback the team offer
1. Create the appropriate number of style tiles based on the defined directions, which establish the specific visual language for the different directions.
1. Gather stakeholder feedback. Iterate on the style tiles, eventually getting down to a single style tile which will be the established visual language for the project going forward.
-
-## Additional resources
+
+
+## Additional resources
- Tool: Style Tiles: A Visual Web Design Process for Clients and the Responsive Web. Style Tiles.
- "Style Tiles and How They Work." Samantha Warren.
@@ -27,7 +28,7 @@ timeRequired: 1–2 days depending on how many rounds of feedback the team offer
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 9a7868f8d7d176d7c516305be99725e4effcf5da Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:29:33 -0500
Subject: [PATCH 39/50] Update task-flow-analysis.md
Considerations for use in government
---
_methods/task-flow-analysis.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/task-flow-analysis.md b/_methods/task-flow-analysis.md
index 30102663..ac0a7ea2 100755
--- a/_methods/task-flow-analysis.md
+++ b/_methods/task-flow-analysis.md
@@ -29,7 +29,7 @@ timeRequired: 2-3 hours per user goal
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 8e5229838c302e16a1aea0b806cf538cae4719ff Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:30:43 -0500
Subject: [PATCH 40/50] Update usability-testing.md
Considerations for use in government
---
_methods/usability-testing.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/usability-testing.md b/_methods/usability-testing.md
index ee6b1eb1..7488f44e 100755
--- a/_methods/usability-testing.md
+++ b/_methods/usability-testing.md
@@ -43,7 +43,7 @@ timeRequired: 30 minutes to 1 hour per test
-## Applied in government research
+## Considerations for use in government
No PRA implications. First, any given usability test should involve nine or fewer users. Additionally, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. It also specifically excludes tests of knowledge or aptitude, 5 CFR 1320.3(h)7, which is essentially what a usability test tests. See the methods for [Recruiting](/recruiting/) and [Privacy](/privacy/) for more tips on taking input from the public.
From ee80db5a708dad8d866e0330d0889b65e4ed12c2 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:31:27 -0500
Subject: [PATCH 41/50] Update user-scenarios.md
Considerations for use in government
---
_methods/user-scenarios.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/user-scenarios.md b/_methods/user-scenarios.md
index a9c3345d..787b90b7 100755
--- a/_methods/user-scenarios.md
+++ b/_methods/user-scenarios.md
@@ -36,7 +36,7 @@ timeRequired: 1-3 hours
-## Applied in government research
+## Considerations for use in government
No PRA implications. No information is collected from members of the public.
From 31c3e5b9106fec6833df2a90684bf342c0bbd3ec Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:32:03 -0500
Subject: [PATCH 42/50] Update visual-preference-testing.md
Considerations for use in government
---
_methods/visual-preference-testing.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/_methods/visual-preference-testing.md b/_methods/visual-preference-testing.md
index f4c313ca..0b60b769 100755
--- a/_methods/visual-preference-testing.md
+++ b/_methods/visual-preference-testing.md
@@ -23,13 +23,16 @@ timeRequired: |
1. Publish the results to the complete product team and decide which direction will guide future design efforts.
-## Additional resources
+
+## Additional resources
- [Rapid Desirability Testing: A Case Study.](http://www.uxmatters.com/mt/archives/2010/02/rapid-desirability-testing-a-case-study.php) Michael Hawley.
- [Preference and Desirability Testing: Measuring Emotional Response to Guide Design.](http://www.slideshare.net/pwdoncaster/preference-and-desirability-testing-measuring-emotional-response-to-guide-design) Michael Hawley and Paul Doncaster.
-## Applied in government research
+
+## Considerations for use in government
+
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/#recruiting) and [Privacy](/fundamentals/privacy/#privacy) for more tips on taking input from the public.
From e1f1f95be3a8a9557fdf6f4a2be6d08b35b75a55 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:32:28 -0500
Subject: [PATCH 43/50] Update wireframing.md
Considerations for use in government
---
_methods/wireframing.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/_methods/wireframing.md b/_methods/wireframing.md
index 8af12809..6b9db187 100755
--- a/_methods/wireframing.md
+++ b/_methods/wireframing.md
@@ -19,6 +19,8 @@ timeRequired: 1-3 hours
1. Use the wireframes to get the team's feedback on feasibility and structure.
-## Applied in government research
+
+## Considerations for use in government
+
No PRA implications. No information is collected from members of the public.
From bc65d0693ed444c53c7a117299d6fb63309a7300 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:37:14 -0500
Subject: [PATCH 44/50] Update contextual-inquiry.md
Considerations for use in government
---
_methods/contextual-inquiry.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_methods/contextual-inquiry.md b/_methods/contextual-inquiry.md
index 89f84c38..fadc1c87 100755
--- a/_methods/contextual-inquiry.md
+++ b/_methods/contextual-inquiry.md
@@ -38,7 +38,7 @@ A pair of 18F team members visited two Department of Labor/Wage Hour Division in
-## Applied in government research
+## Considerations for use in government
No PRA implications, if done properly. Contextual interviews should be non-standardized, conversational, and based on observation. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for [Recruiting](/fundamentals/recruiting/) and [Privacy](/fundamentals/privacy/) for more tips on taking input from the public.
From 26310e35626cac24a9f7199929e78c76aadc9ac7 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:37:43 -0500
Subject: [PATCH 45/50] Update incentives.md
---
_methods/incentives.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/_methods/incentives.md b/_methods/incentives.md
index d1f73512..46913890 100755
--- a/_methods/incentives.md
+++ b/_methods/incentives.md
@@ -20,7 +20,7 @@ timeRequired: N/A
## Considerations for use in government
-- No PRA implications. Even when users are present, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3.
-- If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
+No PRA implications. Even when users are present, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3.
+If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
From 8172e1a68cea25be90e673005fb27d61e23fdadd Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Tue, 10 Dec 2019 17:43:38 -0500
Subject: [PATCH 46/50] Update incentives.md
---
_methods/incentives.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/_methods/incentives.md b/_methods/incentives.md
index 46913890..52ef4f36 100755
--- a/_methods/incentives.md
+++ b/_methods/incentives.md
@@ -21,6 +21,7 @@ timeRequired: N/A
## Considerations for use in government
No PRA implications. Even when users are present, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3.
+
If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
From 477199653ba48d756a731a6b6ea164007cb31427 Mon Sep 17 00:00:00 2001
From: Elisa Chen
Date: Fri, 13 Dec 2019 11:55:47 -0500
Subject: [PATCH 47/50] Update user-scenarios.md
---
_methods/user-scenarios.md | 30 ++++++++++++++++--------------
1 file changed, 16 insertions(+), 14 deletions(-)
diff --git a/_methods/user-scenarios.md b/_methods/user-scenarios.md
index a9c3345d..857879ad 100755
--- a/_methods/user-scenarios.md
+++ b/_methods/user-scenarios.md
@@ -6,32 +6,34 @@ redirect_from:
- /user-scenarios/
description: A method for telling a conceptual story about a user's interaction with your website, focusing on the what, how, and why.
category: Decide
-what: A method for telling a conceptual story about a user's interaction with your website, focusing on the what, how, and why.
-why: To communicate a design idea by telling a story about a specific interaction that a system supports. Through creating user scenarios, you'll identify what the user's motivations are for coming to your site as well as their expectations and goals. User scenarios also help the team answer questions about what the product should do as well as how it should look and behave.
+what: A method for telling a story about a user’s interaction with your product, service, or website, focusing on the what, how, and why.
+why: To communicate a design idea by telling a story about a specific interaction for a specific user. Through creating user scenarios, you’ll identify what the user’s motivations are for using your product, service, or website, as well as their expectations and goals. User scenarios help teams consider both how the same user’s needs might vary depending on their context and how a diverse group of users in the same scenario might have different needs. By constructing user scenarios, you can help the team answer questions about how accessible, inclusive, and adaptive your product, service, or website is.
+
timeRequired: 1-3 hours
---
## How to do it
-1. Determine a [persona](/decide/personas/#personas) or user group to focus on.
-1. Begin to list out the user’s goals, motivations, and the context/environment in which they interact with your site.
-1. Put the details you came up with in step 2 into a story format that includes information about who they are (persona or user group), why they are using your site (motivations), where they are (context), what they need to do (their goal), and how they go about accomplishing their goal (tasks). Keep in mind, the more realistic details you add, the richer and more useful your story becomes for helping in understanding your user’s behaviors.
-1. Share the user scenarios you’ve written with the larger team for feedback and refinement.
-
-
+1. Determine a few [personas](https://methods.18f.gov/decide/personas/) or user groups to focus on. Consider what scenario(s) might be the most critical for that user, including scenarios in which users face limited [accessibility](https://accessibility.18f.gov/).
+1. For each user, list out their goals, motivations, and the context/environment in which they interact with your product, service, or website.
+1. Put the details you came up with in step 2 into a story format that includes the following information:
+ * who they are (persona or user group)
+ * why they are using your site (motivations)
+ * where they are (context)
+ * what they need to do (their goal)
+ * how they go about accomplishing the goal (tasks)
+Keep in mind, the more realistic details you add, the richer and more useful your story becomes for helping to understand your user’s behaviors.
-## Example from 18F
+1. Share the user scenarios that you’ve written with the user group (and other relevant team members) for validation, feedback, and refinement.
+1. Examine your product, service, or website in light of these user scenarios and identify opportunities to make adjustments that would improve users’ experiences.
-- ["Choose design over architecture"](https://18f.gsa.gov/2015/11/17/choose-design-over-architecture/) Kane Baccigalupi.
-
-
## Additional resources
-- Tool: [Scenarios.](http://www.usability.gov/how-to-and-tools/methods/scenarios.html) Usability.gov
-- ["How User Scenarios Help To Improve Your UX."](http://blog.usabilla.com/how-user-scenarios-help-to-improve-your-ux/) Sabina Idler.
+- [Example user scenarios from Usability.gov](https://www.usability.gov/how-to-and-tools/methods/scenarios.html)
+-
From 345c72984f63a7518efd0d80a56658bff3968adc Mon Sep 17 00:00:00 2001
From: Elisa Chen
Date: Fri, 13 Dec 2019 13:37:48 -0500
Subject: [PATCH 48/50] Update user-scenarios.md
---
_methods/user-scenarios.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/_methods/user-scenarios.md b/_methods/user-scenarios.md
index 857879ad..9a174ba3 100755
--- a/_methods/user-scenarios.md
+++ b/_methods/user-scenarios.md
@@ -33,7 +33,13 @@ Keep in mind, the more realistic details you add, the richer and more useful you
## Additional resources
- [Example user scenarios from Usability.gov](https://www.usability.gov/how-to-and-tools/methods/scenarios.html)
--
+- [Detailed explanation from usabilla.com](https://usabilla.com/blog/how-user-scenarios-help-to-improve-your-ux/)
+- [Talk by Eric Meyer that highlights the importance of user scenarios](https://aneventapart.com/news/post/compassionate-design-by-eric-meyeran-event-apart-video)
+- [“Personas, scenarios, user stories and storyboards: what’s the difference?” from Justinmind.com](https://www.justinmind.com/blog/user-personas-scenarios-user-stories-and-storyboards-whats-the-difference/)
+
+## Time required
+1-3 hours
+
From 5d21880f4aec0156ab7125f8f99f1edbf8b0b585 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Mon, 16 Dec 2019 09:16:18 -0500
Subject: [PATCH 49/50] Update user-scenarios.md
---
_methods/user-scenarios.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/_methods/user-scenarios.md b/_methods/user-scenarios.md
index 9a174ba3..6b613bae 100755
--- a/_methods/user-scenarios.md
+++ b/_methods/user-scenarios.md
@@ -7,7 +7,9 @@ redirect_from:
description: A method for telling a conceptual story about a user's interaction with your website, focusing on the what, how, and why.
category: Decide
what: A method for telling a story about a user’s interaction with your product, service, or website, focusing on the what, how, and why.
-why: To communicate a design idea by telling a story about a specific interaction for a specific user. Through creating user scenarios, you’ll identify what the user’s motivations are for using your product, service, or website, as well as their expectations and goals. User scenarios help teams consider both how the same user’s needs might vary depending on their context and how a diverse group of users in the same scenario might have different needs. By constructing user scenarios, you can help the team answer questions about how accessible, inclusive, and adaptive your product, service, or website is.
+why:
+ - To communicate a design idea by telling a story about a specific interaction for a specific user. Through creating user scenarios, you’ll identify what the user’s motivations are for using your product, service, or website, as well as their expectations and goals.
+ - User scenarios help teams consider both how the same user’s needs might vary depending on their context and how a diverse group of users in the same scenario might have different needs. By constructing user scenarios, you can help the team answer questions about how accessible, inclusive, and adaptive your product, service, or website is.
timeRequired: 1-3 hours
---
@@ -22,7 +24,8 @@ timeRequired: 1-3 hours
* where they are (context)
* what they need to do (their goal)
* how they go about accomplishing the goal (tasks)
-Keep in mind, the more realistic details you add, the richer and more useful your story becomes for helping to understand your user’s behaviors.
+
+ Keep in mind, the more realistic details you add, the richer and more useful your story becomes for helping to understand your user’s behaviors.
1. Share the user scenarios that you’ve written with the user group (and other relevant team members) for validation, feedback, and refinement.
1. Examine your product, service, or website in light of these user scenarios and identify opportunities to make adjustments that would improve users’ experiences.
From 9d45425f63469f91e176ada64e6c93e80898b817 Mon Sep 17 00:00:00 2001
From: Julia Lindpaintner
<42982184+juliaklindpaintner@users.noreply.github.com>
Date: Mon, 16 Dec 2019 09:22:07 -0500
Subject: [PATCH 50/50] Update user-scenarios.md
---
_methods/user-scenarios.md | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/_methods/user-scenarios.md b/_methods/user-scenarios.md
index 6b613bae..e997b313 100755
--- a/_methods/user-scenarios.md
+++ b/_methods/user-scenarios.md
@@ -7,9 +7,7 @@ redirect_from:
description: A method for telling a conceptual story about a user's interaction with your website, focusing on the what, how, and why.
category: Decide
what: A method for telling a story about a user’s interaction with your product, service, or website, focusing on the what, how, and why.
-why:
- - To communicate a design idea by telling a story about a specific interaction for a specific user. Through creating user scenarios, you’ll identify what the user’s motivations are for using your product, service, or website, as well as their expectations and goals.
- - User scenarios help teams consider both how the same user’s needs might vary depending on their context and how a diverse group of users in the same scenario might have different needs. By constructing user scenarios, you can help the team answer questions about how accessible, inclusive, and adaptive your product, service, or website is.
+why: To communicate a design idea by telling a story about a specific interaction for a specific user. Through creating user scenarios, you’ll identify what the user’s motivations are for using your product, service, or website, as well as their expectations and goals. User scenarios help teams consider both how the same user’s needs might vary depending on their context and how a diverse group of users in the same scenario might have different needs. By constructing user scenarios, you can help the team answer questions about how accessible, inclusive, and adaptive your product, service, or website is.
timeRequired: 1-3 hours
---