Merge pull request #418 from 18F/staging

Merging updates from staging to master

Author: juliaklindpaintner

Gemfile.lock

@@ -61,10 +61,10 @@ GEM
       rb-inotify (~> 0.9, >= 0.9.7)
       ruby_dep (~> 1.2)
     mercenary (0.3.6)
-    mini_portile2 (2.3.0)
+    mini_portile2 (2.4.0)
     minitest (5.11.3)
-    nokogiri (1.8.5)
-      mini_portile2 (~> 2.3.0)
+    nokogiri (1.10.4)
+      mini_portile2 (~> 2.4.0)
     pathutil (0.16.1)
       forwardable-extended (~> 2.6)
     posix-spawn (0.3.13)

_methods/content-audit.md

@@ -43,6 +43,7 @@ timeRequired: 3-8 hours
 
 - <a href="http://uxmastery.com/how-to-conduct-a-content-audit/">"How to Conduct a Content Audit."</a> UX Mastery.
 - <a href="http://blog.braintraffic.com/2012/04/auditing-big-sites-doesn%E2%80%99t-have-to-be-taxing/">"Auditing Big Sites Doesn't Have to Be Taxing."</a> Christine Anameier.
+- <a href="https://www.usability.gov/how-to-and-tools/methods/content-inventory.html">"Content Inventory."</a> usability.gov
 </section>
 
 <section class="method--section method--section--government-considerations" markdown="1" >

_methods/hopes-and-fears.md

@@ -0,0 +1,48 @@
+---
+layout: card
+title: Hopes and fears
+permalink: /discover/hopes-and-fears/
+redirect_from:
+  - /hopes-and-fears/
+description: An exercise that quickly surfaces a group’s hopes and fears for the future
+category: Discover
+what: An exercise that quickly surfaces a group’s hopes and fears for the future
+why: To establish a baseline understanding of a group’s expectations and concerns about a project and to give each person an opportunity to voice their perspective
+
+timeRequired: 30–60 mins
+---
+
+## How to do it
+
+  1. Ahead of the session, establish what you want to elicit hopes and fears about. For example, you could ask participants to focus on the whole project or that day’s workshop.     
+  2. At the beginning of the session, create two columns labeled “Hopes” and “Fears” on a white board or large sticky pad. 
+(In a remote setting, you can do this online using collaboration software such as Mural or Google Docs)
+  3. Ask participants to take 1-2 mins to write down their hopes on sticky notes (one hope per sticky note). 
+  4. Invite participants to come up one at a time and add their “hopes” sticky notes to the board and say more about what they wrote. Have participants group their sticky notes as they add them to the board to illustrate emerging themes.
+  5. Repeat steps 3 and 4 with fears.  
+  
+This format can be adapted to include other categories. For example, asking participants to write down skills and experiences can help contextualize each person’s place in the group.
+
+<section class="method--section method--section--18f-example" markdown="1" >
+## Example from 18F
+
+- [Three small steps you can take to reboot agile in your organization](https://18f.gsa.gov/2016/10/25/three-small-steps-you-can-take-to-reboot-agile-in-your-organization/)
+
+</section>
+
+<section class="method--section method--section--additional-resources" markdown="1">
+
+## Additional resources
+
+- Step-by-step with images from [ibm.com](https://www.ibm.com/design/thinking/page/toolkit/activity/hopes-and-fears)
+- Video tutorial from [freshtilledsoil.com](https://www.freshtilledsoil.com/design-sprint-shorts-episode-6-hopes-and-fears/)
+- Detailed instructions from [iamnotmypixels.com](https://www.iamnotmypixels.com/design-sprints-hopes-and-fears/)
+
+</section>
+
+<section class="method--section method--section--government-considerations" markdown="1" >
+
+## Applied in government research
+
+No PRA implications. No information is collected from members of the public.
+</section>