diff --git a/content/methods/decide/content-audit.md b/content/methods/decide/content-audit.md index dbb47d26..0dc7c342 100644 --- a/content/methods/decide/content-audit.md +++ b/content/methods/decide/content-audit.md @@ -19,15 +19,15 @@ method: ## How to do it{#how-content-audit} -1. Identify a specific user need or user question that you'd like to address. +1. Identify a specific user need or user question that you’d like to address. 1. Create an inventory of content on your website. Navigate through the site from the home page and note the following about every piece of content. (For repeated items like blog posts, consider capturing just a sample.) - 1. Title used in the site's navigation for that page + 1. Title used in the site’s navigation for that page 1. Title displayed on the page or item itself 1. URL 1. Parent page -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. 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. From each entry point, trace the pages and tasks a user moves through until they address their need. 1. For every piece of content they might come across on that task flow, note: diff --git a/content/methods/discover/kj-method.md b/content/methods/discover/kj-method.md index 16aa973e..2a5bfefc 100644 --- a/content/methods/discover/kj-method.md +++ b/content/methods/discover/kj-method.md @@ -20,13 +20,13 @@ method: ## How to do it{#how-kj} 1. Gather four or more participants for 90 minutes. Provide sticky notes and markers. -1. Create a focused question about the project's needs and select a facilitator to run the exercise. +1. Create a focused question about the project’s needs and select a facilitator to run the exercise. 1. Give participants five minutes to write at least three responses to the question, each on its own note. -1. Give participants 15 minutes to put their answers on the wall, read everyone else's, and make additions. Have participants cluster similar answers without discussion. +1. Give participants 15 minutes to put their answers on the wall, read everyone else’s, and make additions. Have participants cluster similar answers without discussion. 1. Ask participants to write names for each cluster on their own - this is mandatory. They may also split clusters. 1. Put each name on the wall by its cluster. Exclude word-for-word duplicates. 1. Reiterate the question and have each person rank their three most important clusters. Visually tally points. -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. +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.
@@ -37,4 +37,4 @@ method: ## Considerations for use in government{#con-kj} -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. +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. diff --git a/content/methods/make/wireframing.md b/content/methods/make/wireframing.md index 3f4941c5..7c1a2c86 100644 --- a/content/methods/make/wireframing.md +++ b/content/methods/make/wireframing.md @@ -22,7 +22,7 @@ method: 1. Build preliminary blueprints that show structure, placement, and hierarchy for your product. Steer clear of font choices, color, or other elements that would distract both the researcher and the reviewer. Lightweight designs are conceptually easier to reconfigure. A few helpful tools for building wireframes are OmniGraffle and Balsamiq, which purposefully keep the wireframe looking like rough sketches. 1. Use this opportunity to start listing what UX/UI patterns you will need. 1. Review your wireframes with specific [user scenarios]({{ "/methods/decide/user-scenarios/" | url }}) and [personas]({{ "/methods/decide/personas/" | url }}) in mind. Can users accomplish their task with the wireframe you are sketching out? -1. Use the wireframes to get the team's feedback on feasibility and structure. +1. Use the wireframes to get the team’s feedback on feasibility and structure.