Subject for usability testing

[Boudewijn Rempt]

On Monday 24 January 2011, Jaroslaw Staniek wrote:
> On 24 January 2011 17:59, Boudewijn Rempt <boud at valdyas.org> wrote:
> > On Sunday 23 January 2011, Jaroslaw Staniek wrote:
> >
> >> I think dockers are more intensively discussed these weeks, with some
> >> code appearing here ant there. So the answer IMHO would be: dockers.
> >> Regarding startup, asking them about the current startup dialog would
> >> result in notes we already more or less have (and probably some new).
> >> So after we collect all the expected observations regarding the
> >> startup, e.g. on the wiki pages like [1], the students' usability test
> >> will be more than useful to validate correctness of the observati
> >
> > I would very much prefer to start from scratch here -- not try to fix issues with the current startup screen, or even with
> > mockups based on the current mechanism, but go back to the roots.
> 
> Boud,
> We yet have to know what it means to get back to the roots...

First define what the problem is -- i.e., what the user wants to do when he starts an application. That's the first question to answer. 


-- 
Boudewijn Rempt | http://www.valdyas.org, http://www.krita.org