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

Hi Greg,

sorry for keeping an answer rather short ... the general idea is very
good, but the project lacks information being a pre-condition for
creating user stories, scenarios, ...

Am Samstag, den 13.08.2011, 18:39 +0100 schrieb Greg:
I want to do two things to strengthen the UI design choices being made here. I 
haven't seen anyone tackling these so far? These activities should provide 
both structure and more objective & specific evidence:

True. But working on these things requires for example:
      * knowing what users you have
      * knowing what their use cases are
      * having design choices like "removing stuff" / "restricting
        functionality" (e.g. implementation via Extensions)

The first things are currently being addressed by Björn, Isabel,
Irmhild, ... Once we have that information, it should be easier to back
up decisions / proposals. Anything different will be treated as
guesswork and (according my experience) will fail if you want to
convince others - e.g. teams or individuals.

So, it is not ignored, but the preconditions are not yet fully met. So
far, I always suggested to have a look at the OOo User Experience
Project or Project Renaissance. There, we collected some information
that should still be helpful for us.

Collate all the (Agile*) themes, epics and user stories we have for LO. (or 
the nearest analog we have for these.)

Mmh, what do you mean with "we have for LO"? As far as I know, there is
no further information on that at the moment.

[... explanation how this works ...]

If anyone, with usability experience wants to help support this effort, then 
let me know. International testing is particularly important for cultural and 
language design considerations.
Anyone interested in creating/joining a working group on this?

What might work well at the moment, is to pick known issues and create
user stories based on that - one of the lowlights of Writer for example
is the mail-merge functionality. There, it is possible to guess its
users (because we have trainers within LibO) and their use cases
(because we get quite some feedback for that. Or, Ricardo proposed some
days ago (sorry for not commenting) to revise how indexes are made -
also something where such methods and tools might work.

So far - just comments. I don't know if these comments do have any
value ... but I know that everything is precious that helps to get
better design decisions. So you may be interested to join the survey
team (Björn asked for help on the analysis), or to help others to turn
requirements into user stories (or such stuff).


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.