This sketch starts to flesh out some thoughts around a "pre-tool:" A tool that gathers some basic information about the prospective user from a friend or family member. The pre-tool user is not the eventual First Discovery tool user,

The goal of the tool is NOT to start creating a set of preferences; It is to gather just enough basic information about the user's capabilities to get past that initial hurdle of not knowing anything about the user's capabilities.

The information gathered will be used to define, control, direct and filter the flow of the First Discovery tool. For example, if the pre-tool establishes that the user does not understand sign language, then the First Discovery tool will not bother to ask the use if they would prefer sign language. Most information given by the friend/family member will be verified by the user during the First Discovery process.

This sketch separates the pre-tool information gathering from the First Discovery process. There is no assumption that the two will happen at the same time, or that the First Discovery tool user will be present when the pre-tool user is answering the questions. This arose from the use case prepared during the seniors break-out session, where our user was doing First Discovery at home, alone, using a machine her family had purchased and pre-configured for her. (How realistic is this scenario?)

 

Assumptions:

 

Notes:

 

In the sketch below:

 

 


 

1. Personal Identification of First Discovery Tool User

First name

Gender

Preferred language

(include caveats that this information is only for personalizing the wording in the following screens, e.g. name vs "the user," "his" vs "her," etc.)

 

2. System Identification (assuming a female user named Maude)

Is Maude going to be working on a particular type of system?

Has Maude ever seen/used this type of system before?

Has Maude ever seen/used other types of computers before?

 

3. Perception

Can Maude see?

If Maude can see: Can she read text?

Can Maude hear?

If Maude can't hear:

 

4. Operation

(perhaps accompany the options with example tasks that avoid speculation about potential capabilities but rather focus on known capabilities. For example: if Maude has never used a computer, the person can't say whether or not she can use a keyboard. The examples could refer to similar tasks that can be known at this point, for example using the buttons on a phone.)
(this might want to be check boxes rather than radio buttons, depending on the choices)

Can Maude speak?

(these options could be presented with examples)
(this might want to be check boxes rather than radio buttons, depending on the choices)