Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Kevin, Grek, hi all!

I've planned to stay away from the computer today, but I think that
thread is reason enough to answer nevertheless ;-)

Am Freitag, den 25.11.2011, 19:29 +0100 schrieb Kévin PEIGNOT:
I agree, but One think is sure : We must try to do an ergonomic AND sexy
interface. And a survey could help us find what people like.

Yes, a simple mockup survey does tell us what people might like
(theoretically), but it doesn't tell us whether a complex design is
ergonomic, usable, or does fit to user's real needs ... I assume that's
what Greg wanted to say.

By the way, thanks Greg for your kind offer ... it would be great to
hear what you think how we could (pre-)validate Citrus (or any other

From my point-of-view - with regard to Citrus and surveys:
      * Either you are an experienced interviewer (listening to what
        people usually not say), or ...
      * We use a survey to get a very general indication whether it
        makes sense to continue working on Citrus (that would help a
        bit, but since most people don't like the current UI we don't
        need to ask that *g*), or ...
      * We focus on carefully selected areas of Citrus. In such cases,
        one could e.g. describe show pictures and describe workflows
        people need to rate. Then you get feedback on "design
        decisions" (not: visual design).

There are lots of examples where surveys asked for product feedback
(with a good intention), whilst making the updated product worse.
Whether it is a special magazine (the publisher asked what topics are
missing, people added lots of ideas, it became a "general purpose"
magazine without focus and much less user interest) or cars (the
manufacturer asked what configuration options users wanted to have,
people wanted all kinds of stuff, and disliked the product finally
because it was hard to use).

One last thing: If you ask people, then you have to make sure that you
use the right ones. Otherwise you get feedback that seems to be valid,
but is not, unfortunately.

So back to the initial question - do we need a user survey (now), or
should we continue whether we (as the Design Team) think that its

If the latter, then I think it would be helpful to have all contributors
speak up (and provide a yes/no with some explanation).



2011/11/25 Greg <>

I don't want to rain on your parade but (as a UX practitioner of 20 yrs),
surveys are almost the least effective means to validate a UI design,
especially if UI behaviour is included in the investigation. A dozen face
face interviews supported by static or even active prototypes, conducted
a variety of users would yield much more useful and reliable results.

If you want to pat yourself on the back and tell everyone that 9 out of 10
users prefer the new LibreButtonOMatic, then a survey will give you that
whether 9 out of 10 users actually do will be unrelated to that statistic.

Surely the UXers in the team know people who use these type of products (in
fact a sprinkling of users of competitive products would add value). I'd be
happy to work with other UXers to plan the investigation  and conduct a
of structured interviews.



Completely agree :)


---- On Fri, 25 Nov 2011 09:38:22 +0100 Charles-H. Schulz
&lt;; wrote ----

A survey would be a great idea; in fact, it would help with asking
ourselves the right question for the spec; in short, it would be a real
work of User Experience.

Even better news: I think Christoph Noack and Bjoern Balazs know just
how to set up such a survey, but I might be perhaps too optimistic :-)



On 25/11/2011 00:00, Kévin PEIGNOT wrote:
&gt; Maybe we could publish a survey asking, for each part of Citrus UI
&gt; (explained in a few word) what people think about it ? As we did
our &gt; first survey ?
&gt; On each page a part of the survey, with a brief summary and if
possible a &gt; mockup. And why not at the end asking a "global
impression" note. It's not &gt; spec, but it permit to know what people
think of the globals ideas ? &gt;
&gt; Kévin
&gt; 2011/11/24 Andrew Pullins &lt;;
&gt;&gt; Charles, Kevin, every one,
&gt;&gt;&gt; Citrus looks good. But as we explained, if there's no one
wrting &gt;&gt;&gt; specicications for eaxh part of citrus nothing will
get done. &gt;&gt;&gt;
&gt;&gt; ok yes we do need to start on some specifications so that we can
get &gt;&gt; started, but we have not talked about it all that much.
we need &gt;&gt; to decide on what we all agree on and change what we do
not. if we get more &gt;&gt; people to agree with some things I would
start some specifications, but I &gt;&gt; still don't know exactly what
needed to write one. could someone write a &gt;&gt; templet on what needs
to be written. that would really help. till then &gt;&gt; there are still
some people that have not said what they do not like about &gt;&gt;
Citrus. if you wait any longer we'er going to have to just go with
&gt;&gt; It looks like we need to blog so that people don't get their
up. :-/ &gt;&gt;
&gt;&gt; all the more reason to get this started NOW. and before you guys
say it ONE &gt;&gt; MORE TIME. I know that we can not get this done in
shot, and that we &gt;&gt; need to do this ONE STEP AT A TIME. but now
that we have some press on this &gt;&gt; and people know that we are
working on this we NEED to get things rolling. &gt;&gt;
&gt;&gt; Andrew
&gt;&gt; --
&gt;&gt; Unsubscribe instructions: E-mail to &gt;&gt; Problems?
&gt;&gt; Posting guidelines + more: &gt;&gt; List archive: &gt;&gt; All messages
sent to this list will be publicly archived and cannot be &gt;&gt;

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.