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!
Research alignment workshop (Gdoc)
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.
Design research participant agreement (GDoc)
Our agreement for anyone participating in moderated design research.
Note: This document is a template; you can customize it however you like so long as your agreement includes an Antideficiency Act clause.
Please note that you should run substantial customizations by your supervisor, GSA’s Privacy Office, and GSA’s Office of General Counsel. See also: (Legal, and links to GSA’s Privacy Act Statement and Privacy Impact Assessment for Design Research.
Researcher introduces themselves to a participant (GDoc)
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.
You can also participate in local communities of practice in by joining:
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 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 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 for additional pointers and guidance.
- Check out the Project resources folder for reusable content and templates; browse project artifacts from previous 18F engagements 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
- Project Start Guide
- List of prior path analyses
- Project resources folder
- Six weird tips for protecting PII
- Usability test quality heuristics
- Artifacts from design-led projects
- Checklist of requirements for federal government websites
- Quickstart: Intercept (pop-up) research in GSA buildings
- How to design a better deck
- What is design?
- Introduction to design
- Writing research questions
- Research presentation template