LGBTI UN Staff Platform UX Portfolio Piece


*last revised on 8 April 2016

Context in international development is important. Please view the background info on this project before continuing. A more detailed portfolio piece is available as a PDF. Please email me to receive a copy; a signed NDA will be required.

 

The Research

User Interviews – Key Quotes

There are other uses for a platform like this, such as sample language to put in contracts.

With this historical marginalization, I think you’ll have a stronger user base.

Crowdsourcing can help frame the idea, but…I couldn’t see it being a legal basis.

It’s worth exploring a mobile version of the platform because with personal privacy, mobile is better.

I usually have a 90% response rate from people in the field.

 

Card Sorting and Affinity Mapping

As an international development practitioner who has focused on the role of technology for the past six years, I combined UX-oriented methods with my qualitative research skills.

CardSortingCard sorting
FeatureMappingAffinity Mapping

Card sorting and affinity mapping led to the following insights:

  • Some people find grouping by feature type more useful, others find grouping my administrative level (i.e. country, continent, etc.) more useful
  • A lot of features will need to be reached in tandem to achieve needed security and functionality (MVP)
  • Some anonymity in responses is okay

 

Paper Prototyping and Low/Med-Fidlity Wireframes

PaperPrototype

Paper Prototypes

 

MedFi_HomepageMedium-fidelity wireframe

Equipped with preliminary research, I worked out paper prototypes and medium-fidelity wireframes that led the following additional insights:

  • Design everything with privacy in mind
  • Add onboarding
  • Test user types and primary users flows further
  • Test display of trends (location, prominence, depth) further
  • Test commonly used symbols in designs for North America/Europe on people of and responding from Africa, Latin America and South Asia
  • Actual language of onboarding, surveys, prompts will be critical

 

Research Synthesis

Personas

Three personas emerged:

  • Lifelong Field Staffer – someone who has dedicated all or a significant part of their career to field operations and identifies as LGBTI
  • UN Policy Maker – someone who writes, changes or directly influences UN policies that affect UN staff.
  • Human Resources staff – someone who works on HR issues, such as contract administration, securing visas, processing annual leave.
Persona_LifelongFielder Persona_HRRep Persona_PolicyMaker

Taxonomy

Taxonomy
  • Event/layer – set of questions
  • EqualDex layer – pulled from EqualDex
  • Survey question – individual question
  • Incident report – open-ended prompt to document specific incident OR Sentiment report – open-ended prompt to document general feelings
  • Keyword – tag associated to question or report

User Flows

Screenshot 2016-02-07 13.57.07

 

UX Design Analysis

Information Architecture

 Validated (so far)

  • “Shallow” interactions – max 3 page loads, 3-4 actions to do any given task from any given part of the platform
  • Repeat onboarding information throughout with pop-ups/prompts; keep onboarding information accessible in a menu at the bottom of all pages
  • Use breadcrumbs for navigation help
  • Sub-categories: keywords, timeframe, demographics (as meta-data)
  • Demographics associated with responses should only be available if multiple responses fit a criteria in order to preserve anonymity

 

Ongoing Discussion

  • Responsive site versus native app for mobile
  • Use of dropdown menus
  • Top level classification
  • Incident versus sentiment report
  • Specific layers and questions, specific incident/sentiment report prompt wording
  • Data anonymization versus data integrity

Screenshot 2016-02-09 00.58.47

Usability Testing Next Steps

  • New homepage layout – tiles
  • Specific language on onboarding, survey questions, sentiment/incident prompts
  • Specific tasks – adding survey question responses, sentiment/incident reports
  • Export views (front-end)
  • Back-end

 

Pivots

  • Incident to (possible) sentiment reports
  • Ongoing discussion of users being required to have a profile
  • Design of homescreen as a map or as tiles
  • Onboarding information – length, availability, and addition of module/test
  • Removing dots in timeslider to indicate an incident was reported
  • Changing Equaldex layers as a dropmenu to a separate bar

 

Annotated Wireframe

Screenshot 2016-04-08 12.51.04
  1. Want users to always have these four options up here
  2. Click here to go home
  3. Events/layers about which this platform will collect
  4. Layers that are pulled from external source, EqualDex
  5. Export screens in coming design steps
  6. Anticipating a lot of discussions how this is actually deciphered
  7. Slider will change map view above
  8. Have gotten a lot of feedback that this needs to be in the header. Keeping it here for now for space concerns. Will probably move it up to the header eventually.
  9. This is the same information in the new user onboarding
  10. Debating whether to if/how this will change with user selection

Click here to view prototype