<div class="gmail_quote">On Sun, Jan 17, 2010 at 5:52 PM, Simon Schampijer <span dir="ltr"><<a href="mailto:simon@schampijer.de">simon@schampijer.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 01/17/2010 11:35 PM, Christian Marc Schmidt wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Gary, these look really good! In particular, I think having the journal<br>
in the ring is a huge improvement.<br>
<br>
Still on the fence about "resume" vs. "start new". Either solution seems<br>
well solved for from a design standpoint--it is more a question of usability<br>
and cognitive model. I'm wondering if we should defer making "start new" the<br>
default until we have more test evidence.<br>
<br>
One interesting possibility that just came up is to work with Gerald's<br>
deployment in Westchester, NY. I hope to have the chance to talk to him<br>
about the possibility of running a few qualitative studies on the current<br>
release. Until we have, I'd personally feel more comfortable to leave the<br>
home view as is for the next build, adding only the journal to the ring,<br>
until we have further insight into how kids use activities.<br>
<br>
How would everyone feel about that?<br>
<br>
<br>
Christian<br>
</blockquote>
<br></div>
I can run studies in my school, too.<br>
<br>
Though, I am not so sure how exactly we would measure resume vs 'start new'. I guess you would need to test that with users that are not familiar with Sugar yet. And then let half use 'start new' as default and half resume and give them the same task to do. Of course you would need to do that over a period of time to not get 'false' results.<br>
</blockquote><div><br></div><div>The best way to test these things is to have the subject talk through what they are trying to do, and how they are attempting to do it facilitated by the user interface. That alone should be quite insightful. For instance, if you observe students deleting the content of a previous activity to start a new activity, the culprit may not necessarily be the way the activity was invoked, but rather a lack of functionality inside the activity itself. The staging/timing of features relative to the experience as a whole is particularly significant.</div>
<div><br></div><div>I don't think we necessarily need to test new users only, though as a subset that would be interesting. But it can be equally, perhaps even more insightful to observe the behavior patterns kids have developed while using Sugar over a period of time, since that may reveal workarounds and shortcuts that point out inefficiencies in the UI.</div>
<div><br></div><div>I think a task-based questionnaire should be enough to gather some useful insights. Since you work with children, would you interested in helping me develop a questionnaire? Your first-hand perspective would be invaluable.</div>
<div><br></div><div><br></div><div>Christian</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Regards,<br><font color="#888888">
Simon<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><a href="mailto:anything@christianmarcschmidt.com">anything@christianmarcschmidt.com</a><br>917/ 575 0013<br><br><a href="http://www.christianmarcschmidt.com">http://www.christianmarcschmidt.com</a><br>
<a href="http://www.linkedin.com/in/christianmarcschmidt">http://www.linkedin.com/in/christianmarcschmidt</a><br><a href="http://twitter.com/cms_">http://twitter.com/cms_</a><br>