IFD:Designing For Action/Vera, Mischa, Max: Difference between revisions

Line 115:

Great job.

===Cennydd Bowles===

I like the focus of what you're tackling - it's a tighter problem than just 'bookmarking', and this often means you can be more confident about your solution. I can attest that managing citations and references is still very much an unsolved problem!

Your research mentions lots of user requirements. It would be useful to explain how you learned these - did participants simply ask for these explicitly, or did you draw these requirements out by prompting them and interpreting their answers?

The prototypes show a number of different ways to use the system; drag and drop, contextual menu etc. This allows flexibility but (counter-intuitively) can actually make systems harder to use if the user isn't sure which route they should use for which operation. Which methods do you think users will rely on the most? Which methods would they use the least? Are those methods still valuable if most people avoid them?

A bit more information on your paper prototyping would be useful, but it looks like you've responded well to your testing, and your solution shows some promise.

@@ Line 115: / Line 115: @@
 Great job.
+===Cennydd Bowles===
+I like the focus of what you're tackling - it's a tighter problem than just 'bookmarking', and this often means you can be more confident about your solution. I can attest that managing citations and references is still very much an unsolved problem!
+Your research mentions lots of user requirements. It would be useful to explain how you learned these - did participants simply ask for these explicitly, or did you draw these requirements out by prompting them and interpreting their answers?
+The prototypes show a number of different ways to use the system; drag and drop, contextual menu etc. This allows flexibility but (counter-intuitively) can actually make systems harder to use if the user isn't sure which route they should use for which operation. Which methods do you think users will rely on the most? Which methods would they use the least? Are those methods still valuable if most people avoid them?
+A bit more information on your paper prototyping would be useful, but it looks like you've responded well to your testing, and your solution shows some promise.