Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of kevingrignon.oo@gmail.com
 designates 209.85.210.47 as permitted sender)
References: 
 <CAF-Tss-Rk-BpYrfsW6xcqW_r6v+0efxOjw10ujttbY+az+jCeQ@mail.gmail.com>
 <CAJvPf9gVFUm0vhZzMBNvg_bSYFoMRLJ_7rVAcf2+j0oLN5Yd1A@mail.gmail.com>
 <CAF-Tss8bNNp=hTcoeg2quG2EVT9gFi+0odtNK2+Ma6z56ZCO+g@mail.gmail.com>
 <CALRLYEmObRND0shQH+XFam-LF6ZvENgYi3cn=Z5198QE49fTNQ@mail.gmail.com>
 <4FBCFEC3.1020204@gmail.com>
 <CAO4+hqPEFFbny_wDkwr7LCqQVmySG5K=MgoHChCwEG0u0vWqDA@mail.gmail.com>
 <CAP-ksoi0nqHre7x6K9tMShrPMDUFQuDP=k_TEQz5OrwiP-p5Aw@mail.gmail.com>
In-Reply-To: 
 <CAP-ksoi0nqHre7x6K9tMShrPMDUFQuDP=k_TEQz5OrwiP-p5Aw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <21AFB0D2-6FD7-463F-9F83-E537861B4A66@gmail.com>
Cc: "ooo-dev@incubator.apache.org" <ooo-dev@incubator.apache.org>
From: Kevin Grignon <kevingrignon.oo@gmail.com>
Subject: Re: [UX] Questions for users
Date: Fri, 25 May 2012 10:36:20 +0800
To: "ooo-dev@incubator.apache.org" <ooo-dev@incubator.apache.org>


On May 25, 2012, at 2:42 AM, Rob Weir <robweir@apache.org> wrote:

> On Wed, May 23, 2012 at 11:07 PM, Kevin Grignon
> <kevingrignon.oo@gmail.com> wrote:
>> Hey All,
>>=20
>> Great thread, many great research questions in here.
>>=20
>> Overall, we are moving in the right direction. We need to understand who
>> uses AOO, and what they use it for. What works, what doesn't . Context of=

>> use, when and where is also important.
>>=20
>=20
> I bet almost all of our users (> 95%) are using OpenOffice as a
> Microsoft Office substitute.   So their expectations and tasks are
> highly influenced by the feature set and UI of Microsoft Office.   But
> not necessarily the latest version of MS Office.  There is a lag.  So
> Office 2003 might be more influential in expectations than the
> "ribbon" UI of Office 2007 and later.  But this will shift over time.
>=20
> There have been various attempts to re-imagine the basic editors, some
> more successful than others.  Lotus tried with its Improv application
> to take the spreadsheet to the next level.   Some users got it, but
> the network effect of 1-2-3 (and later Excel) compatibility was too
> great.   This is a huge effect in this market.  The value of user
> training in the predominate editors as well the benefits of
> interoperability with other editors that have a very similar feature
> set -- these factors conspire to keep us in a narrow orbit around a
> conventional view of personal productivity apps.
>=20
> That said, it is possible to be bold and strike gold.  Prezi and their
> unique view of a presentation is one example:  http://prezi.com/.   In
> such cases the new feature set might be intrinsically so valuable to
> the user that it more than compensates for the learning curve and
> lower interop with other editors.  They re-base their expectations on
> the new thing, and that defines the new normal.
>=20
> So that is something we'll need to figure out:  What relative
> attention should we give to:
>=20
> 1) improving the conventional set of features we already have in AOO?
>=20
> 2) Adding new features to achieve greater parity with MS Office?
>=20
> 3) Being bold and adding new features that don't exist anywhere else?
>=20
> If you survey users, I bet you won't get many requests for #3.  And if
> you queried users the day before the electronic spreadsheet was
> invented no user would have asked for one either.
>=20
> -Rob
>=20

KG02 says:

Rob, thanks for sharing you thoughts. Some good historical considerations he=
re.=20

Agreed, we need to understand our users stated and unstated needs. Herein li=
es the opportunity for design leadership. Any research should seek to balanc=
e exploitation (incremental enhancements) and exploration (break through inn=
ovation).=20

Let's get started.=20

Kevin


>> Let's move the conversation to the UX wiki, and capture some our research=

>> question candidates.
>>=20
>> Also, let's look at previous research efforts to help us quickly build a
>> strong survey. Sun, Oracle, IBM and the OO community have performed user
>> research in the past. Let's leverage this content, where possible.
>>=20
>> In addition to a capturing a series of research questions, let's capture
>> our thoughts in the UX wiki on our research strategy. Beyond email list a=
nd
>> forums, we may want to consider how we might use social media channels to=

>> drive traffic to the user research questions.
>>=20
>> Finally, let's think about how we take the output of the research data an=
d
>> turn the data into UX work products that will help drive informed design
>> and development decisions. Harvesting data to create user roles and usage=

>> scenarios would be a logical start.
>>=20
>> I volunteer to create some UX wiki pages to help capture this content.
>>=20
>> Regards,
>> Kevin
>>=20
>>=20
>> On Wed, May 23, 2012 at 11:14 PM, Kay Schenk <kay.schenk@gmail.com> wrote=
:
>>=20
>>>=20
>>>=20
>>> On 05/20/2012 11:54 AM, Wolf Halton wrote:
>>>=20
>>>> On Sun, May 20, 2012 at 1:33 PM, Albino Biasutti Neto
>>>> <biasuttin@gmail.com>wrote:
>>>>=20
>>>>  Hi.
>>>>>=20
>>>>> 2012/5/20 Paulo de Souza Lima<paulo.s.lima@varekai.org>
>>>>>=20
>>>>>  I think you mean "How old are you?" =3D)
>>>>>>=20
>>>>>>=20
>>>>>>  Sorry, thanks.
>>>>>=20
>>>>>=20
>>>>>  Maybe we could contribute to improve those questions. My 2 cents:
>>>>>>=20
>>>>>> Are you using it at your work (ask where does he/she work) or at home=
,
>>>>>> or
>>>>>> both?
>>>>>> Do you think you have enough support? Where do you use to get support=
?
>>>>>> (manuals, friends, forum, mailing lists, etc)
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>  Good!
>>>>>=20
>>>>> Open to suggestions. :-)
>>>>>=20
>>>>> Albino
>>>>>=20
>>>>>=20
>>>> Where will these questions be asked? During the download process? Durin=
g
>>>> the registration process? A poll on the web site?
>>>>=20
>>>> -Wolf
>>>>=20
>>>=20
>>> I'll throw my .02 in here.
>>>=20
>>> Assuming we could get them to "register" somehow and supply an e-mail
>>> address, would it be an idea to send them an e-mail like a month later a=
nd
>>> get feedback *after* they've used the product for a bit?
>>>=20
>>> No ideas about questions except for the general items like performance
>>> issues, etc.
>>>=20
>>>=20
>>>=20
>>>> PS Website polls 1 to 2 question open-ended questions (questions withou=
t a
>>>> set choice of answers) have been known to produce very useful data-sets=

>>>> among users of public library services, and I would suggest that model a=
s
>>>> an interesting way to find out our own blind spots, regarding usage
>>>> trends.
>>>> Closed-end questions such as "do you like seagulls" can only get 3
>>>> responses, "yes," "no" and "no response at all."
>>>>=20
>>>>=20
>>>>=20
>>> --
>>> ------------------------------**------------------------------**
>>> ------------
>>> MzK
>>>=20
>>> "The reports of my death are greatly exaggerated."
>>>                              -- Mark Twain
>>>=20