Hi Steve,
Should we be using this usability study to test / compare new UI ideas
vs. our current UI? Or just get feedback on the old to see where we
need work? Or is the focus more on functionality of our UI and the
ability for users to get to that functionality? If that is the case, I
think the areas of the server that management would like to see best
exposed (web services? montioring? etc.) be identified by management.
If we're focusing on the UI itself (vs. content), then I'd like to
prototype a couple alternate navigation schemes and get feedback on what
is intuitive to users (i.e. tree vs. tabs vs. menus). We might also get
some feedback on displaying graphs via jMaki vs. images vs. an applet
(i.e. JavaFX). Just some thoughts.
Thanks,
Ken
Stephen Wolf wrote:
> Hi all,
>
> I'm putting together a usability study plan for Glassfish.
>
> Anissa and I had staked out "mid-June" for a usability study and it
> looks like the week of June 25-29 will work best for the usability lab
> in MPK where we will run the study.
>
> What I'd like to do is get our candidate set of goals for the study,
> review it internally, then send it out for community review.
>
> Then I'll design the methodology and we'll review that with the
> community as well.
>
> So what I need from you all now is a list of your goals and priorities
> for the study as a starting point.
>
> Of course the study will be constrained to a human limit of around 3
> hours (max), preferably 2 hours so some items will get in and some
> won't but I'll make you decide that rather than I. :-)
>
> What would you like to see get tested? Or re-tested?
>
> I'll collate the responses I get and we'll do some prioritization.
>
> Thanks,
>
> Steve