Difference between revisions of "Calligra/Usability and UX/Words/Personas"

Jump to: navigation, search
(Added a description of John)
(Mary: (added last chapter))
Line 25: Line 25:
  
 
In a word processor she is used to using styles, making her own styles and importing them from an document to another. A typical document she could make would be a multiple-page document with a separate title page, an automated table of contents and page numbering (excluding the title page), as well as an automated bibliography. She might also need the possibility to define parts of the text to be written with another language than the other parts of the document, and to be able to proofread the document.
 
In a word processor she is used to using styles, making her own styles and importing them from an document to another. A typical document she could make would be a multiple-page document with a separate title page, an automated table of contents and page numbering (excluding the title page), as well as an automated bibliography. She might also need the possibility to define parts of the text to be written with another language than the other parts of the document, and to be able to proofread the document.
 +
 +
Mary’s number one preference is the stability of the system, but also speed plays a big role. Mary is very oriented to just get the things done without a fuss. Sometimes she may do things inelegantly.
  
 
==John==
 
==John==

Revision as of 17:55, 19 February 2011

About personas

While using personas is an established usability practice, it's also not really applicable to a word processor. Most people expect to be able to do a lot of things, or at least be able to load documents they get from someone else.

So it doesn't make sense to define specific tasks for each persona. Everybody want to use all the various features from time to time (if only to view them). If Words doesn't support all of them then people will not find it attractive, and will not use Words as their day to day word processor either. This holds true even if their normal use may be very simple.

That said there are also features that are only useful for very select personas. But Susan the recreational user is not so simple as she might seem at first sight.

So using Personas is a rather poor design tool for a word processor. It's much more interesting to think of use cases. 50% of all use cases would belong to Susan anyway. Now for the remaining 50% we may want to invent many personas, but I think we are just going to have two personas Susan and A.D.Vance, with the latter collecting the advanced cases, for now.

End user read would then be when it's ready for Susan.

See a collection of use cases for Words , there is also a table that shows which use cases each persona should be able to do.

Personas for Words:

Susan

Is a recreational user with a sharp focus on web and social media Susan would use Words to write an fancy invitation for a party, and send that around as PDF or ODT or just print it. Susan would also use Words for the occasional letter, writing her resume, contribute to a document she recieved from an interest group she has joined (maybe online, maybe the local sports club).

On this link you can find open bugs/wishes related to her

Mary

Mary is a first year university student studying history. She is familiar with computers as a user of typical office products, e-mail, surfing the web and playing games. She uses mainly Windows, but at home she has a laptop with Linux that her sister has set up for her. Mary is quite comfortable using Linux with a GUI. She is not so interested in computers but rather uses them for studying, communicating with friends and family, and occasionally gaming for recreation.

For an office suite her basic need is to be able to produce the kind of documents that are required for her studies. She uses mostly word processors, but also spreadsheets and presentation programs. She has to be able to easily open the most common file formats and save her documents to those formats, including PDF.

In a word processor she is used to using styles, making her own styles and importing them from an document to another. A typical document she could make would be a multiple-page document with a separate title page, an automated table of contents and page numbering (excluding the title page), as well as an automated bibliography. She might also need the possibility to define parts of the text to be written with another language than the other parts of the document, and to be able to proofread the document.

Mary’s number one preference is the stability of the system, but also speed plays a big role. Mary is very oriented to just get the things done without a fuss. Sometimes she may do things inelegantly.

John

John is a technical writer that makes documentation and instruction manuals. He is an advanced user of computers and many kinds of programs. He also does some programming as a hobby. In his usage of programs he is eager to find ways to make his job more efficient, and e.g. he uses shortcut keys when available. For repeating tasks he makes macros. John is comfortable with many platforms. Ideologically he is devoted to FOSS.

When John needs a word processor /dtp, he is pretty much able to find all the solutions he might think of needing; that is if the program is able to do the task he is looking for. A typical document he might make would be a compilation of multiple-page documents that together form an instruction manual that could be printed out as a book. These documents typically have images, charts and diagrams that John has made. He uses cross-references and text-variables very often, and he needs review and commenting tools that can be used in collaboration with a workmate.

A. D. Vance

is a fictitional user where we for now collect use cases too advanced for Susan. In the future we might create personas for specific (set of) use cases.

Find the open tasks for supporting A.D.Vance on this link

Editing wrap and anchoring of images (shapes)

Setting up special wrap and anchoring so that the text flows in interesting ways


Content is available under Creative Commons License SA 4.0 unless otherwise noted.