forked from 18F/methods
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #13 from Chicago/18F-master
18 f master
- Loading branch information
Showing
168 changed files
with
1,920 additions
and
6,320 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| # 18F Methods Product Team | ||
|
|
||
| As a member of the 18F Methods Product Team, you will be expected to spend an average of two hours a week working towards the following objectives: | ||
|
|
||
| ## Objective A: Maintain the 18F Methods | ||
|
|
||
| - Collaboratively set an achievable, year-long vision for the 18F Methods | ||
| - Identify, prioritize, and address short-term goals and known issues | ||
| - Establish a decision-making process(es) for merging contributions into the Methods | ||
|
|
||
| ## Objective B: Ensure the 18F Methods support and reflect 18F’s current practices | ||
|
|
||
| - Collect data around the value 18F Methods provides across the organization | ||
| - Revise and augment the Methods as needed, to keep in sync with 18F’s practice | ||
| - Add to and maintain the connections between the Methods and other content (such as other guides and resources produced by 18F or issued by the government) | ||
|
|
||
| ## Objective C: Ensure usability and encourage adoption of the 18F Methods | ||
|
|
||
| - In collaboration with TTS Outreach, promote the methods outside of 18F | ||
| - Offer periodic support and solicit input for methods on venues like the UX-COP Mailing list | ||
| - Optional: Conduct research around the use of the Methods in order to increase usability. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| - category_name: Discover | ||
| category_description: Build a greater understanding of your problem and the people it impacts. | ||
| category_info: Use the Discover Methods to build context for the problem you’re investigating. Get to know your potential users better and understand your stakeholders’ main concerns. The work you do during this phase will inform everything that follows, so take your time. | ||
| methods: | ||
| - Cognitive walkthrough | ||
| - Contextual inquiry | ||
| - Design studio | ||
| - Dot voting | ||
| - KJ method | ||
| - Stakeholder and user interviews | ||
|
|
||
| - category_name: Decide | ||
| category_description: Elaborate on research from your Discovery phase. | ||
| category_info: The Decide Methods help you derive insights from the information gathered during the Discovery phase. You’ll validate initial assumptions, develop a deeper understanding of workflows and processes, and develop design hypotheses. | ||
| methods: | ||
| - Affinity diagramming | ||
| - Comparative analysis | ||
| - Journey mapping | ||
| - Personas | ||
| - Task flow analysis | ||
| - User scenarios | ||
|
|
||
| - category_name: Make | ||
| category_description: Create a testable solution. | ||
| category_info: Once you’ve learned more about your users’ expectations, use the Make Methods to create testable designs. Sketching, wireframing, and prototyping will help you ensure your product reflects your users’ needs. | ||
| methods: | ||
| - Design pattern library | ||
| - Prototyping | ||
| - Wireframing | ||
|
|
||
| - category_name: Validate | ||
| category_description: Test a design hypothesis. | ||
| category_info: Testing (and re-testing) your designs with users will help you build the best possible product. Our Validate Methods cover varied testing scenarios and potential user groups. | ||
| methods: | ||
| - Card sorting | ||
| - Multivariate testing | ||
| - Usability testing | ||
| - Visual preference testing | ||
|
|
||
| - category_name: Fundamentals | ||
| category_description: Foundational methods for practicing design research. | ||
| category_info: Our Fundamentals Methods, which combine government-specific protocols and industry best practices, lay the groundwork for successful research, no matter what you’re testing. For best results, review them before you start recruiting. | ||
| methods: | ||
| - Incentives | ||
| - Privacy | ||
| - Recruiting |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,22 +1,22 @@ | ||
| <!DOCTYPE html> | ||
| <html lang='en'> | ||
| {% include head.html %} | ||
| <body class="layout--card"> | ||
| {% include category-setup.html %} {% include header.html %} | ||
| <main id="main" role="main"> | ||
| <section class="category category--{{page.category | downcase }} usa-section" id="{{page.category | downcase }}"> | ||
| <header class="category--header"> | ||
| {% include head.html %} | ||
| <body class="layout--card"> | ||
| {% include category-setup.html %} {% include header.html %} | ||
| <main id="main" role="main"> | ||
| <section class="category category--{{page.category | downcase }} usa-section" id="{{page.category | downcase }}"> | ||
| <header class="category--header"> | ||
| <div class="usa-grid"> | ||
| {% assign method_category = site.pages | where: "title", page.category | first %} | ||
| <h1 class="category--title">{{method_category.title | capitalize }}</h1> | ||
| <p class="category--subtitle">{{method_category.description}}</p> | ||
| </div> | ||
| </header> | ||
| <div class="usa-grid"> | ||
| {% assign method_category = site.pages | where: "title", page.category | first %} | ||
| <h1 class="category--title">{{method_category.title | capitalize }}</h1> | ||
| <p class="category--subtitle">{{method_category.description}}</p> | ||
| {% include method-print-header.html %} {% include method.html %} | ||
| </div> | ||
| </header> | ||
| <div class="usa-grid"> | ||
| {% include method-print-header.html %} {% include method.html %} | ||
| </div> | ||
| </section> | ||
| </main> | ||
| {% include footer.html %} | ||
| </body> | ||
| </html> | ||
| </section> | ||
| </main> | ||
| {% include footer.html %} | ||
| </body> | ||
| </html> |
Oops, something went wrong.