← Back to course
5/6
Week 02 Β· Asking Good Questions

Friday

Impact Friday: Wrong guesses about users
// Choosing how to collect data that can fairly answer the question
⏱ about 20 min

Friday: Impact Friday: Wrong Guesses About Users

Keeper Ines is watering the plant by the front desk when the crew arrives. "Can I share something I have noticed?" she asks.

"Lots of morning members walk right past the screen at the desk. They never look at it."

Comet blinks. "But our plan puts the whole survey on that screen. I thought everybody used it."

Wren writes the word "assumption" on his clipboard. "What do you notice? We guessed about our users without checking."

Nova glows softly. "Would you like a hint?" she asks. "Keeper Ines sees members you rarely see. More points of view catch more mistakes."

Comet turns to you. "Data analyst, how do we fix our guess?"

Bias in what people build

Computing innovations can reflect human biases through their algorithms or through their data.

Bias can enter at every level of building something. Programmers should take action to reduce it.

One kind of bias is a wrong assumption developers make about their users.

Equity deficits include little exposure to computing and less access to education and training.

More points of view

Collaboration that includes diverse perspectives helps avoid bias.

The crew only visits in the afternoon, so it never saw the morning members walk past the screen. Keeper Ines did.

In the story, the crew prints paper forms as a backup. On day 3 of the survey week, Wren sees the morning members walk past the screen himself, and the forms go out.

Made-up guess the crew madeWhat could go wrongA possible fix
Every member reads the front-desk screenMembers who skip the screen are never heardOffer paper forms too
Members visit at the same times the crew doesMorning and weekend members are missedAsk at four different times
Everyone reads the questions the same waySome answers mean something differentTry the questions on a few members first
SPOT THE BIAS
  • Read the question.
  • Tap your answer.
The crew assumed every member uses the front-desk screen. What kind of bias is that?
Who helped the crew catch its wrong guess?
Why does a team with diverse perspectives help avoid bias?
Where can bias enter when people build something?

Week review

Week reviewTrue or false?
Surveys, interviews, direct observation and user testing are ways to find out what people need.?
A census asks only some members of a group.?
Open-box answers may not be uniform.?
Collecting more data removes bias that comes from the source.?
Collaboration that includes diverse perspectives helps avoid bias.?
WHY THIS EXERCISEFair questions and fair methods come before any fair answer.
OUR WEEK, IN ORDER
  • ?We compared four ways to find out what people need.
  • ?We decided Commons Count will be a sample, not a census.
  • ?We drafted survey questions and ran a trial with Nova.
  • ?We compared two trials and found a lean toward evening answers.
  • ?We found a wrong assumption about who uses the screen.
WHY THIS EXERCISEEach step made the survey fairer before a single real answer came in.
On paper, sketch the front desk with its screen. Add a second way a member could answer the survey, and label both ways.

A strong week, data analyst. Tomorrow's Mission Quest turns your family into a tiny survey.

← Thursday