Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor
Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor Dr. Famous, content expert
DavidCTO
Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor Dr. Famous, content expert
David, CTO
5 + 3 Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor Dr. Famous, content expert
David, CTO
Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor Dr. Famous, content expert
Audrey, design & project manager
Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor Dr. Famous, content expert
Audrey, design & project manager
Greg, interaction designer
Kevin, engineering manager Eliot, voice interaction designerClaire, “front end” engineer
Howard, local doctor Dr. Famous, content expert
Audrey, design & project manager
Greg, interaction designer
Hugh, principal
?
?
?
?
?
?
?
?
?
?
?
??
?
?
?
?
?
?
??
??
??
?
?
?
??
?
?
?
?
?
? ?
??
?
?
?
?
?
?
???
?
?
?
?
??
?
?
?
?
?
?
?
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
- studies
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
- studies - detail
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
- studies - detail- document
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
- studies - detail- document
1. Analyze 2. Define 3. Ideate 4. Select 5. Implement
1. Define 2. Measure 3. Analyze 4. Design 5. Verify
1. Plan 2. Learn 3. Specify 4. Produce 5. Evaluate
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
- studies - detail- document
1. Research 2. Model 3. Prototype 4. Test 5. Specify- studies- reviews
- analysis- synthesis
- maps- wireframes- comps
- studies - detail- document
Admit/Xfr/DschgDiet
Regular diet as tol.Soft dietFull liquid dietClear liquid dietNPOMore Consistencies
Mechanical Soft DietPureed DietSips of WaterIce chps
Common / Diabetic DietsMore Modified Diets
Low / High / Amount Per DayFood AllergyRestrictedFluid RestrictionDisease / ConditionSpecial
Advance as tol.Advance as tol. to…
Regular diet as tol.Soft dietMechanical soft diet
?
?
?
?
?
?
?
?
?
?
?
??
?
?
?
?
?
?
??
??
??
?
?
?
??
?
?
?
?
?
? ?
??
?
?
?
?
?
?
???
?
?
?
?
??
?
?
?
?
?
?
?
✔
✔
✔
✔
✔
✔✔
✔
✔
✔
✔
✔
✔
Design Issue Priority DefinitionsP1: Global or core issue that prevents a
significant number of other issues from being resolved.
Design Issue Priority DefinitionsP1:
P2:
Global or core issue that prevents a significant number of other issues from being resolved.Prevents some issues from being resolved, but not a large number.
Design Issue Priority DefinitionsP1:
P2:
P3:
Global or core issue that prevents a significant number of other issues from being resolved.Prevents some issues from being resolved, but not a large number.Isolated issue, must be resolved but does not prevent other work.
Design Issue Priority DefinitionsP1:
P2:
P3:
P4:
Global or core issue that prevents a significant number of other issues from being resolved.Prevents some issues from being resolved, but not a large number.Isolated issue, must be resolved but does not prevent other work.Detail, does not prevent other work.
Design Issue Priority DefinitionsP1:
P2:
P3:
P4:
P5:
Global or core issue that prevents a significant number of other issues from being resolved.Prevents some issues from being resolved, but not a large number.Isolated issue, must be resolved but does not prevent other work.Detail, does not prevent other work.Detail, resolution not required for beta.
Good:
1. Efficient, meaning…a. intuitiveb. fast (application)c. quick access to information
2. Meets expectations; consistent, no surprises.
Good:
1. Efficient, meaning…a. intuitiveb. fast (application)c. quick access to information
2. Meets expectations; consistent, no surprises.
3. Keeps users from getting lost.
Good:
1. Efficient, meaning…a. intuitiveb. fast (application)c. quick access to information
2. Meets expectations; consistent, no surprises.
3. Keeps users from getting lost.
4. Minimal barriers and constraints.
Issue List Issue Priority Definitions: P1 - global or core issues that prevents a significant number of other issues from being resolved P2 - prevents some other issues from being resolved, but not the bulk of issues at hand P3 - isolated issue, must be resolved at some point, but does not prevent other work P4 - detail, does not prevent other work P5 - detail, resolution not required for beta
# Priority Title Description Resolution Notes 1 P1 Form Navigation Decide how to
navigate within the hierarchy of forms.
From 8/19 brainstorm.
5 P1 Order Navigation Decide how to navigate to new, saved, and placed orders.
From 8/19 brainstorm.
2 P1 Navigation Size Problems
Deal with long form names in navigation.
From 9/3 meeting.
3 P2 Forms States If a user visits a form, fills it out, navigates away and then navigates back , is the form still populated? What if it is added to the order?
From 8/19 brainstorm. To be addressed at 9/15 meeting.
4 P3 Logout time What if the user loses the handheld? Personal information could be compromised.
From 9/3 meeting.
Design Issue Priority DefinitionsP1:
P2:
P3:
P4:
P5:
Global or core issue that prevents a significant number of other issues from being resolved.Prevents some issues from being resolved, but not a large number.Isolated issue, must be resolved but does not prevent other work.Detail, does not prevent other work.Detail, resolution not required for beta.
Good:
1. Efficient, meaning…a. intuitiveb. fast (application)c. quick access to information
2. Meets expectations; consistent, no surprises.
3. Keeps users from getting lost.
4. Minimal barriers and constraints.
Issue List Issue Priority Definitions: P1 - global or core issues that prevents a significant number of other issues from being resolved P2 - prevents some other issues from being resolved, but not the bulk of issues at hand P3 - isolated issue, must be resolved at some point, but does not prevent other work P4 - detail, does not prevent other work P5 - detail, resolution not required for beta
# Priority Title Description Resolution Notes 1 P1 Form Navigation Decide how to
navigate within the hierarchy of forms.
From 8/19 brainstorm.
5 P1 Order Navigation Decide how to navigate to new, saved, and placed orders.
From 8/19 brainstorm.
2 P1 Navigation Size Problems
Deal with long form names in navigation.
From 9/3 meeting.
3 P2 Forms States If a user visits a form, fills it out, navigates away and then navigates back , is the form still populated? What if it is added to the order?
From 8/19 brainstorm. To be addressed at 9/15 meeting.
4 P3 Logout time What if the user loses the handheld? Personal information could be compromised.
From 9/3 meeting.
Log out when inactive. Let inactivity period be set by user in preferences.
Middle-Out Design:
1. priority definitions
2. “good” definition
3. tracking issues
4. assigning priorities
5. important things first
6. document solutions
Thank You.
Audrey [email protected]
Dubberly Design Office
Thumb twiddling images from artwork by Naomi Roberston.
Top Related