Work / Windows Hello

Windows Hello, step 1 of 3. The recognition volume drawn as a shape around a person: face detected across 20–100cm at a 60° field, iris only at ~27cm across 29°. Everything outside is hatched as out of range.
1The recognition volume drawn as a shape around a person: face detected across 20–100cm at a 60° field, iris only at ~27cm across 29°. Everything outside is hatched as out of range.

Windows Hello

A face unlock has to decide how sure is sure enough. What does the screen do while it decides?

Role
Lead interaction designer
Stack
Windows · Iris and face recognition
Dates
2015
Based on
My own project artifacts, published at will-jenn.com/work/windows-hello

Windows Hello arrived as a research project with a spec: field of view, working distance, false accept rate. My job was to work out how those numbers might feel to somebody holding a phone.

Recognition is not a yes or a no. It is a rising confidence, and the honest design question is what to show while it rises.

Metered unlock was the answer. Personal content arrives in steps as certainty firms up. A stranger standing near your phone gets a clock on black. You get your name, then your notifications, then your face.

That is a privacy control that never mentions privacy. Nobody reads a setting; the screen simply declines to say your name to someone it does not recognise.

The other half is failure. Iris recognition fails for dull physical reasons — glare, glasses, eyelids, distance — and each one has a different fix. So each one got its own sentence: “Something is reflecting off your eyes. Try moving slightly.” Never “authentication failed”, which tells you nothing and blames you for it.

What is not here: no adoption or accuracy figures, and these are project artifacts rather than shipped screens. This was 2015; I have kept asking the same question since, most recently of language models.

What this proves

Shipped product. The role is self-reported, backed by artifacts published at will-jenn.com.