Version 65 (modified by linda, 4 years ago) (diff)


UX team

Welcome to the UX team page! ٩(◕‿◕)۶


We're on a mission to make Tor more accessible, easier to use, and gorgeously designed. Send an email to this UX mailing list to get involved.

User Experience (UX) is an intersection of many disciplines and non-standardly defined. This is because the field is new, and also because the term describes both the professional practice (interaction design, visual design, or user research), but also the resulting outcome ("easy to use," "pain in the butt").

There are many, many sub-disciplines that make up UX, and even more job titles (they aren't standardized yet). But ultimately, these roles fall into one of just a few categories:

  • Interaction design: designing the structure and detailed interactions of an application of a product, deciding screens, interactions, workflows, information structure, and controlled and uncontrolled data.
  • Visual design: designing the visual layer of an application or product, deciding the color palette, typography, hierarchy of information, visual elements, and the layout. If an interaction designer is an architect, the visual designer is the interior designer.
  • Content strategy: crafting the message delivered to users, being careful to voice, tone, when the content is presented, and consistent messaging. A big part of this is internationalization, which involves translating literally and culturally to appropriately communicate with the audience.
  • User research: conducting research about user needs and behavior, which could be quantitative (studies to explore reasoning and behaviors) or quantitative (measuring statistics about the user). Research is performed to validate ideas, test prototypes, or brainstorm new features.

There are some professionals who choose to specialize in one of these categories. Others usually work as a UX engineer and perform a combination of these tasks.


Here are the people on the UX team at Tor, who choose to work as multi-disciplinary UX engineers:

No image "literal-profile-pic.jpg" attached to org/teams/UxTeam
Linda Lee, team lead (@linda | linda@…)

interaction design ████████
visual design █████
content strategy ██████
user research ██████████

No image "isa.jpg" attached to org/teams/UxTeam
Isabela Bagueros, project manager (@isabela | isabela@…)

interaction design ████████
visual design ██████
content strategy ██████████
user research █████

The UX team currently consists of two employees, who work with a generous team of volunteers. You're a part of the team if you contribute to the team!

UX references

If you have the skillset, but are just getting started on applying them to UX work, we recommend checking out Nielsen Norman's group's articles, which are all about a ~7 min read, but very informative. Starting out with their introduction to usability article, and then read their most popular articles. We've listed the introduction article and a couple selected popular articles below:

Our favorite resource is Usability book of knowledge, which has professional, detailed information. Not only is the breadth cover the comprehensive list of methods to use for UX work, but the articles are very detailed. Each page has related links to publications, a detailed description of what the method along with is advantages and disadvantages, a how-to guide with a complete procedure, stakeholders, and common pitfalls, and special considerations before using the method. For instance, look at this page on heuristic evaluation, and be impressed. If you want to find more pages like that, go and browse their categories:

There are also some great academic papers at select conferences for additional reading.We personally recommend starting with SOUPS, CHI, and PETS papers.


If you want to read about what we have done, what we are doing, and what we are going to do, it's all here.


We fill in the roadmap with future work we anticipate doing. For instance, work related to funders will start and end on a specific deadline, and that is captured here. We also try to capture any dependencies between the work that we do and work that we do on other teams. If you see something that we should add to the list, please inform linda@….

See the roadmap here:


We document each project on a wiki page on trac (just like this page you are reading now). The information on the wiki pages are public, and is able to be shared.

Current projects:

Past projects:

We document our work because it makes it easy to share information with various project stakeholders, funders, and project team members. We do our best to keep all of the project pages current.


These are the tickets with the term "user experience" in the ticket:

Ticket Status Summary Owner Reporter
No tickets found

Currently, the team does not track much of their work through tickets, so this is an incomplete overview of the things that need to be done. You can get a better idea of what we are currently up to by reading the wiki pages for the current projects in the previous section. But these tickets are still good to look at, so that we can be reminded of some of the things that we need to do.