So last week I took a look at this stupid oven in my apartment, and figured that the best way to make it not-so-sucky would be to put a keypad into the interface (which would be pretty easy). Then I did a mock-up of my idea by sticking post-its onto the oven.
This week: programming something! We’ve been tasked to redo the interaction test with the IPAC and some simple programming to get the desired testing — without us needing to mediate in the process, thereby getting a better feel for what the user really feels
The rules go as follows:
1. A description of the device and the particular task/s that you’ll be testing for.
2. A paper prototype session with a third-party user; document this with video and than write up a summary of your conclusions.
3. An operational prototype. First make a video of the prototype being operated by you, and describe its capabilities. Then record a session with a third-party user; document this with video, and write about the differences between the paper-session and this one. Was it worth the effort? Did you learn something that the paper prototype could not reveal?
I’m still working out the deets on how I’ll actually do this — making a functional keypad is a teensy bit much (10 switches?), but I should figure out some way to actually test the interaction. Maybe have a switch for on, and a switch for enter, and we’ll assume that people’s button-pushing just works? I need to think this out a bit more… but there’s options, anyway. I’ll post updates as I think them up.
Post a Comment