Summary
Forms are the front door to government services—for everything from getting a job to a COVID-19 vaccine—yet their current design creates systemic barriers for LGBTQ+ people. Forms shape how our government understands, prioritizes, and addresses the needs of its people, but for LGBTQ+ communities, many government forms include demographic questions that are unnecessarily invasive, inadequate, and unclear in their purpose. This deepens mistrust, creates barriers to critical benefits, and prevents collection of data needed to provide effective, equitable services. In this talk, U.S. Digital Service team members will share lessons learned from direct engagement with an intersectional group of LGBTQ+ nonprofit organizations and researchers and statisticians across government and standards organizations as well as an examination of underlying policies and tech systems. We’ll provide a framework for navigating sexual orientation and gender identity, as a first step toward designing equitable forms for all.
Key Insights
-
•
Over 10 times more people from Gen Z identify as LGBTQ+ compared to earlier generations, yet federal forms largely fail to capture this data.
-
•
Current major federal surveys like the American Community Survey cannot identify bisexual or transgender individuals accurately.
-
•
The removal of medical requirements for gender marker changes on U.S. passports marks a historic and affirming policy shift.
-
•
Self-attestation and the introduction of an X gender marker on passports improve visibility and affirm identity in federal ID documents.
-
•
Conducting inclusive user research within tight timelines is difficult but essential to capture intersectional LGBTQ+ voices.
-
•
There is a tension between providing flexible, multi-select options for identity on forms and the challenges these pose for data standardization and statistical analysis.
-
•
The two-step question (sex assigned at birth and current gender identity) is statistically effective but may not be appropriate for all federal forms, especially benefits applications.
-
•
Interoperable backend systems across agencies are crucial to provide a seamless one-government data experience and prevent harm from inconsistent data collection.
-
•
Inclusive, trauma-aware research protocols with centralized reviews ensure safer participation for LGBTQ+ individuals in government research.
-
•
Language evolves quickly; governmental data collection must avoid locking in terminology that may become offensive or outdated.
Notable Quotes
"If you don’t collect data on somebody, they become invisible and nobody should be invisible."
"Government forms need to represent identity and respect privacy so we can better serve all people."
"The LGBTQ+ population is increasing rapidly with each generation, but federal data collection has not kept pace."
"We want to do no harm — collecting sensitive data requires care about how it’s used, shared, and stored."
"Community is not a monolith; we must engage a broad intersection of voices, not just one perspective."
"Change in government moves slowly, but we can pilot and iterate to serve evolving needs more quickly."
"The State Department removed burdensome medical requirements, allowing people to self-attest their gender on passports."
"People use gender and sex interchangeably, but as identities evolve, that creates complications for medical and benefit forms."
"It’s critical that research does not cause distress to participants; trust must be fostered with transparency and safety."
"Users want a one-government experience — they don’t care about separate agencies with different questions or terminology."
Or choose a question:
More Videos
"Having a back office support in place made it much easier to convince new researchers to join the team."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Think about who decides what, when, where, by which criteria and how these decisions connect—this helps influence decision making."
Silke Bochat5 Antifragile Strategies for a DesignOps 2.0
September 23, 2024
"Starting from scratch is really hard, but also a cool opportunity to throw away painful patterns."
John DonmoyerShipping your code generation experiments to production
June 11, 2025
"What is going wrong? What’s the matter? What’s the cause of that?"
Christian CrumlishIntroduction by our Conference Chair
December 6, 2022
"You don't want to hide away for six months and try to build the perfect documentation. It won't work."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"DesignOps needs to work more horizontally to bridge silos between product, marketing, engineering, and research."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"What are your assumed greatest strengths, and how might they prevent you from moving into new spaces?"
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
"Empathy is essential now more than ever in measuring and supporting designer happiness during remote work."
Kristin Skinner Kamdyn Moore8 Types of Measures in Design Operations
April 16, 2020
"Design teams don’t want a design ops drill, they need a quarter inch hole that requires a little bit of program management."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
Latest Books All books
Dig deeper with the Rosenbot
Why is design ops sometimes viewed as a luxury in smaller organizations and how does scaling change that?
How does introducing AI as a designer complicate the moral evaluation of deception in design?
How do designers train AI tools like Midjourney to generate visuals consistent with their studio’s style?