We’ve collected the following templates, presentations, checklists, etc. as starting points — feel free to contribute to this guide and help us keep this list up-to-date!
As indicated below, some of these resources are available only to staff of GSA (General Services Administration) or TTS (Technology Transformation Services).
Research alignment workshop. (18F/GSA access only).
A workshop template for publicizing team questions and prioritizing research themes, setting you up to create a research plan that drives maximum value for your team.
Privacy and informed consent
18F’s Design Research is covered by GSA’s Privacy Act Statement for Design Research.
Privacy Act Notice Example. (18F/GSA internal version).
Example of a statement to include in your participant agreement.
Please note: you should run substantial customizations by your supervisor, GSA’s Privacy Office, and GSA’s Office of General Counsel.
Design research participant agreement. (18F/GSA internal version).
Design research participant agreement in Spanish.
Example agreement for people participating in moderated design research.
Note: You can customize this template, but it must include a Privacy Act statement. If the interview is with a Federal employee, or otherwise will not include compensation, the agreement must also include an Anti-deficiency Act clause.
Looking for PRA (Paperwork Reduction Act) information? See the UX Guide Legal page.
Research findings presentation template (18F/GSA access only) A starting point for sharing what you learned during a path analysis or discovery sprint. (Report templates for 18F/GSA access only: template 1, template 2)
Researcher introduces themselves to a participant. (18F/GSA internal version).
An email for introducing yourself to potential participants (for example, people who responded to your invitation to participate in the research) and finding a good time for them to participate in a moderated research session.
Doing UX at 18F can involve working with Content and Visual Designers, or people in our Acquisition, Product Management and Engineering Chapters. Read their pages in the TTS/18F Handbook for more information.
18F/TTS staff can also participate in local communities of practice in by joining (18F/TTS access only):
If you’re in need of a particular skill — help with a presentation or design deliverable; writing and content strategy; or development tasks — 18F’s microrequest staffing team can provide support. You can request assistance from 18F colleagues for help on billable projects in the #microrequests (18F/TTS access only) channel. Each discipline is represented at any time in the channel.
Any billable project work is eligible for assistance via a microrequest. The only limitation is that microrequest tasks must typically take fewer than 8 hours of work a week, over no more than 3 weeks, for the person providing the assistance. You may post non-billable requests in the #helpwanted (18F/TTS access only) channel.
Presenting the work
We most commonly share our work via presentations. These presentations can vary widely based on the audience. Here are a few presentation-building tips:
- Utilize our 18F-branded templates to maintain consistency and save time.
- The presentation deck should tell a compelling story and be easy to read. Make sure to include enough content so those not able to attend the presentation can view the deck later and understand what you’re aiming to communicate. Refer to this presentation on How to design a better deck (18F/GSA access only) for additional pointers and guidance.
- Check out the Project resources folder (18F/GSA access only) for reusable content and templates; browse previous 18F Path Analysis project artifacts for inspiration; or view the Design wiki for additional examples.
- Consider making a microrequest if you’re unsure how to articulate or visualize an idea.
- Feel free to include references or links to further reading at the end of your presentation.
- 18F Handbook
- 18F Methods
- USDS Playbook
- New Hire README (18F/GSA access only)
- Project Start Guide (18F/GSA access only)
- List of prior path analyses
- Project resources folder (18F/GSA access only)
- Six weird tips for protecting PII (18F/GSA access only)
- Artifacts from design-led projects (18F/GSA access only)
- Checklist of requirements for federal government websites
- Quickstart: Intercept (pop-up) research in GSA buildings (18F/GSA access only)
- Project Start Guide (18F/GSA access only)
- 18F Content Guide
- TTS Engineering Guide Front-end practices
- 18F Analytics standards
- 18F Accessibility Guide
- Agile Principles and 18F Practices
- Before You Ship: TTS guide to launching software
- 18F De-risking Government Technology
- How to design a better deck (18F/GSA access only)
- What is design? (18F/GSA access only)
- Introduction to design (18F/GSA access only)
- Writing research questions (18F/GSA access only)
- Research presentation template (18F/GSA access only)