Resilient Identifiers for Underserved Populations WG Charter Approved

I’m pleased to announce that the Charter for the Resilient Identifiers for Underserved Populations work group (RIUP WG) was approved by the Kantara Initiative Leadership Council earlier this week. This work group combines the legacy work groups (WGs) from the Identity Ecosystem Steering Group, which was formed in 2011 to provide a trust registry under the White House’s National Strategy for Trusted Identity in Cyberspace and absorbed by Kantara in 2018. I was a member of the UX Committee and wrote the User Experience Guidelines and Metrics document for the ID Ecosystem Framework Registry.

For the RIUP WG, two groups, Federated Identifiers for a Resilient Ecosystem (FIRE WG) and Healthcare ID Assurance (HIAWG) were combined to address identity assurance concerns for underserved people, who are often referred to as “vulnerable populations” by healthcare sector.

1) WG NAME (and any acronym or abbreviation of the name):  Resilient Identifiers for Underserved Populations Work Group (RIUP WG) 

(2) PURPOSE:  The purpose of the Work Group is to support vulnerable and underserved populations in America. At a high level, these populations include those with physical and cognitive disabilities, or who are homeless, impoverished, senior citizens, immigrants, incarcerated, institutionalized and otherwise underserved minority groups that need digital credentials to access online resources; particularly, online healthcare and financial resources. Without an easily reusable identifier, it is nearly impossible for these individuals to gain secure access to the resources and services that may be available to them. 

We will work, in collaboration with other private sector and public agencies towards establishing identifiers and access management (IAM) solutions that respect privacy, promote efficiency, limit redundancy, reduce barriers to use/adoption, increase interoperability, improve security, enhance safety and trust, eliminate identification errors, support resiliency, and achieve greater empowerment across the entire spectrum of online transactions. The RIUP WG will identify, coordinate, innovate and harmonize with ongoing and emerging identity initiatives, standards, and technologies, and communicate our findings to all relevant stakeholders, both in the US and, selectively, with other countries, under the leadership of the Kantara Initiative.  

(3) A SCOPE – Guidelines for Cultivating a User-Centric Trust and Promoting Adoption within Underserved Communities 

About “Underserved Populations”

Why does the RIUP WG use “underserved” rather than “vulnerable” when discussing the needs of healthcare populations? The US Health and Human Services tends to use “vulnerable” or “vulnerable and/or underserved” when discussing needs of people who require healthcare services but do not reflect the typical healthcare technology user.

In human subject testing, the category generally includes the elderly, poor, pregnant women, children, and infants, and recently, incarcerated people have been included in this description. But for the purposes of access to healthcare services, it also includes rural populations, those with permanent and temporary disabilities, indigenous peoples and others who may object to being described as vulnerable, yet need services that may be difficult to find, therefore rendering them “underserved.”

I had a conversation with Dana Chisnell, a founding member of the US Digital Service now serving as Deputy Design Director at US DHS, who convinced me to use “underserved” as a descriptor for identifiers. While there will still be “vulnerable populations” requiring special services, “underserved” puts the onus of care on the service provider rather than the traits of an individual which may or may not reflect their needs, abilities or level of personal agency. This work follows my research interest at the Internet Safety Lab where we are changing the conversation around digital harms, where the outcome of a service or lack of service can be harmful.

What’s Next?

RIUP WG will begin by creating guidelines for cultivating a user-centric trust registry and promoting adoption within Underserved Communities. We will publish a Use Case for Trusted Identifiers for underserved populations. And with a universal design strategy we will emphasize, highlight and prioritize user scenarios/stories from vulnerable and underserved populations to improve services for all users. We will test the use case and user stories across different verticals and persons of varying backgrounds and cultures. And we will create a dictionary that is harmonized with industry terminology.

There are a lot of initiatives that we will be watching. NIST is drafting 800-63-4 Digital Identity Guidelines, so we will work on comments on how to incorporate the needs of underserved people. The HSS Office of the National Coordinator (ONC) referenced trust registries in its work on Social Determinants of Health for Medicaid and we are participating in its information forums. We also plan to update the MAAS draft to incorporate recommendations from these efforts.

Lots to do and a great time to get involved.

Great teamwork!

The Occasional Mentor: On Constraints in Service Design and Hiring Freelancers

THE OCCASIONAL MENTOR:
A monthly column based on questions I’ve answered on Quora, heard on Slack groups, and other career advice I’ve given over the prior month. Feel free to challenge me in the comments, if you have a different experience. Below are questions I answered in January.

What Projects Did You Create in a Hackathon? How Hard Was It to Create It in a Limited Time?

Answered 1/5/2018

Working within constraints is an important skill of any good product designer. At a hackathon, your constraints include time, of course, as well as available data, resources and the knowledge and skill of your team members. I try to join diverse groups that include at least one person who understands the underlying subject matter and available data, one strong open source developer and one designer/researcher type (usually that’s me). If you use and understand open source data and tools you likely have access to more resources than other teams, so unless the hackathon is restricted to proprietary tools and data, it gives you an edge.

Hackathon projects I’ve done (I try to do at least one per year):

The Nature Conservancy Stormwater Challenge: I hosted a service design hackathon in October 2018 with the goal to encourage private property owners to implement Stormwater mitigation technology.

Empathy Jam: My team created a prototype job training platform at the 2017 Empathy Jam.

United Nations Unite For Humanity: I co-chaired a weekend hackathon in 2016 with the goal to create anti terrorist projects. The winning project employed machine learning to disrupt terrorist networks. Other submitted projects included a stateless e911 network and a SMS based marketplace for emergency supplies.

NYPL Open Audio Hackathon: In 2016, my team created a tool to add multimedia content to audio podcasts.

NYPL Open Book Hack: I went twice. The first year, my team created a PDF to reflowable ePub converter for Supreme Court opinions. The next year, my team created a poetry recommendation tool. Based on poems and genres a user likes, it created a booklet with twenty poems.

Upcoming Hackathon: Escape from New York

I will be mentoring at MD5’s ‪Escape from New York Mass Evacuation hackathon in NYC the weekend of February 22-24. This Defense Department Hackathon features $45k in awards. Let me know if you’d like to bring a team or participate as a mentor. There are a few student and professional tickets left but you have to  have a promotional code to unlock them. Visit https://www.eventbrite.com/e/escape-from-new-york-a-massive-evacuation-hackathon-tickets-51211081724‬

Where do I find and hire freelance UI/UX designers?

Answered 1/5/2019

TL;DR: Good UX designers pass on any job description that says “UI/UX”. Don’t use it. Instead use a title that describes what the person is actually going to do.

For hiring designers, I’ve had good luck with TopTal, but I prefer to go on Slack groups and get out to meetups to really get to know people I want to work with. I don’t like Dribble or Behance for UX people. It’s typically a lot of eye-candy that shows very little of the designer’s process. If there is a designer I like who has a portfolio there, I’ll look, but I wouldn’t start there from scratch.

A good UX designer will show their process: the methods they use, the choices they made, even the designs they discarded. A good portfolio give you a sense of the problem space and challenges and will have a clear description of the person’s role. You can’t tell any of this from a glossy, finished product photo.

I strongly suggest that you not use the term “UX/UI” in the job description. As others have stated, it is too broad to really be meaningful. Most User Experience people will see that and read “visual design” which may or may not include everything from graphic design, animation, typography and stylesheets. Some good candidates may assume you want a front-end developer, and give the role a pass, because developers typically don’t do UX.

It’s better to use a title that describes what the person is actually going to do.

UI people typically are front-end designers and often are expected to know how to code. While UI fits into the UX umbrella, most UX Designers will be focused on user journeys, personas, user advocacy and may or may not do research. UI people use research, but don’t necessarily produce it themselves and may be a step or two removed from the user research process.

There is a rather hot debate going on as to whether UX Designers should know how to code. Most designers and researchers that identify as “UX” people do not code. I’m from the camp that says it helps, but if they are mostly coding (unless it’s to put together prototypes for testing and they don’t have devs to do that for them), they’re probably not a UX “designer”.

Bottom line: You need users to do UX design. You could make a case for researching logs and customer support database, but since it’s after release, that’s really user acceptance testing, not UX. The user experience design process starts with user testing way before you release a product and occurs along with development, launch and beyond. And if you aren’t applying user research and integrating users into your design processes or at least talking to them, its just not UX .