When applying UCD to sanitation, describe a problem your organization was trying to solve?
How to reduce the effects of vandalism on the performance of our system
What solution did you design to solve the problem?
- Hide expensive components
- Tuck all possible sub-systems within the larger structure
WHAT WORKED WELL
What part(s) of the UCD process did your organization do very well?
- Observations of users interacting with system
- Systems with users
WHAT DIDN'T WORK
What part(s) of the UCD process did not go well?
- No second prototype
- Difficult to make quick iterations
- Different approaches (.i.e. making components beautiful, or desired by community was not tried (surveys around validating don't really work))
- Creating a system - "it was a one time thing"
TOOLS AND FRAMEWORKS
What UCD tools or analytical frameworks did you use?
WHAT WAS REALLY HARD
What were your biggest struggles?
- Because we had little experience of working in the actual environment, ideation was hard
- Balancing client & end-user desires
- Lack of transparency with implementors regarding their own failures
What was your biggest a-ha moment?
- Young children vandalize for little or no reason
- Client has wealth of experience that should have been tapped into
So then what? What did you do? Discard the idea? Change course?
Remove all external items from outside unit (including stickers and plants) that are accessible to children
What advice would you give other organizations?
- As a tech developer communicate often with implementers
- Take every opportunity to visit and talk to end users
- Employ modular design of prototypes for faster, cheaper iterations