-
Notifications
You must be signed in to change notification settings - Fork 29
Goals
As our vision for this guide has evolved, our goals have become more resolute. This document contains section-specific goals to orient 18F staff in making contributions.
By reading the UX guide, 18F staff will be able to:
- Identify the UX team’s values and principles
- Describe the UX team’s preferred ways of working
- Describe how UX research and design happens at 18F (for example, the contexts in which we employ the 18F Methods)
- Create more consistent work products (such as research plans and prototypes)
By participating in the creation of the UX guide, members of 18F’s UX team will be able to:
- Grow as practitioners and colleagues
- Discuss and document what we already know (tacit knowledge)
- Describe the UX team as it works today, and as we would like it to work
- Identify reusable templates, case studies, checklists, etc.
- Determine what design-related material lives where (for example, 18F Methods vs. this guide)
By reading the About this guide article, 18F staff will be able to:
- Determine if this guide is relevant to them, and, if not, know where to go
- Read this guide more effectively (vs. just going to a random section)
- Know that 18F has no regulatory authority (over things like the Paperwork Reduction Act of 1995, etc.)
- Know how to share, fork, and contribute to this guide
By reading the Resources article, 18F staff will be able to:
- Identify reusable templates, presentations, checklists, etc. when doing UX design
By reading articles in the Our Approach section 18F staff will be able to:
- Identify the UX Team’s values and principles, and make more consistent values-based, principled decisions
- Describe and discuss design (with our colleagues and agency partners) using similar words and concepts
- Identify predictable areas where our approach to UX design may differ across engagements (in response to our partner agency), and how we might respond
- Promote continuous learning with a lean experiment framework (assumption and hypothesis testing)
By reading the Clarify the basics article, 18F staff will be able to:
- Identify the activities involved in 18F research
- Educate their team about research (at a high level)
- Describe the types of research 18F conducts
- Identify our preferred practices for doing research
By reading the Plan article, 18F staff will be able to:
- Identify important decisions when planning research (for example, background information about the research, research questions, desired outcomes)
- Make more predictable, consistent, appropriate choices when planning research in various project contexts
- Involve their partners in research planning
- Create more consistent research records, and control access to those records
By reading the Do article, 18F staff will be able to:
- Conduct useful and important activities in advance of designing their sessions (such as reviewing what’s already known and understanding users’ context)
- Correspond with participants (invite their participation, collect their informed consent, and schedule them)
- Prepare session materials with participants in mind, and run a pilot of their session
- Moderate research effectively in a government context
- Debrief with their colleagues after sessions
By reading the Analyze, synthesize, and share article, 18F staff will be able to:
- Involve their team in analyzing research
- Thoroughly analyze result results, and synthesize Share/socialize research findings with team members, stakeholders, and the public
By reading the Privacy, Legal, Bias, and Ethics articles, 18F staff will be able to:
- Identify how 18F accounts for legal considerations in research
- Identify how 18F accounts for privacy considerations in research
- Identify how 18F accounts for ethics considerations in research
- Identify how 18F accounts for bias considerations in research
- Know where to go with further questions
By reading the Design section, 18F staff will be able to:
- Create prototypes of appropriate fidelity with 18F-sanctioned tools
- Know when to build or reference a design system