Do not miss your opportunity to enter Christoph's time machine, if you could not attend this years OOoCon in Orvieto. Even if you have attended, it gives you the possibility to see the conference from a non-developers point of view. Enjoy!

Best regards,

Frank

tags: ooocon oooocon2009 renaissance user-experience

Thinning out process for the existing OOo user interface has started. Focus for OOo 3.3 will be on Impress. Please find the October status update presentation for Project Renaissance at the OOo Wiki (1 MB).

Feedback welcome.

Best regards,

tags: renaissance user-experience

The OpenOffice.org conference will start in a few days. Two cappuccino and one espresso, per favore :-)

The OOo User Experience Team will give two presentations and two workshops:

Wednesday: (11-04)

• 12:15 PM: Project Renaissance - Designing a new user interface for OpenOffice.org; Building; Palazzo dei Sette; Room: Sette 3; (Andreas Bartel, Frank Loehmann)

Thursday:  (11-05)

• 11:15 AM: Getting usagetracking data, technical and security aspects and a look in the future how to provide the data; Building: Palazzo dei Sette; Room: Sette 1; (Frank Mau, Frank Loehmann)
• 04:15 PM: UX Workshop I - The role and the methods of user experience in product design
  Building: Palazzo dei Sette, Room: Sette 1 (Andreas Bartel)
  
• 05:15 PM: Workshop II - User Experience Done "Live" Based on Expertise and Usage Data
  Building: Palazzo dei Sette, Room: Sette 1 (Christoph Noack, Frank Loehmann)
  

We are calling for topics for the second UX workshop. So everybody who wants to attend please give us input what you want us to discuss at the workshop. Up till now, nobody officially responded to our annoucement earlier this week.

We'll see us at the OpenOffice.org conference.

Best regards,

OpenOffice.org User Experience Team

tags: ooocon2009 renaissance user-experience

Project Renaissance has created a special spreadsheet with the Impress User Feedback Data.

This spreadsheet is easier to use than the full version (no filtering needed) and will be used for the thinning out process of the Impress user interface.

The spreadsheet provides data for:

• Shortcuts
• Menu Entries
• Toolbars
  
• and new: A list of not called events

• Undo
• Text
• Position and Size dialog
  

Best regards,

The Renaissance Team

tags: renaissance user-experience

The Renaissance Project has started the announced thinning out process of the Impress user interface.

The goal of this process is to improve the most common interactions for Impress 3.3. This process is based on data from the User Feedback Program, customer interviews, surveys and usability issues.

The following visualization of the most clicked icons on toolbars of Impress 3.1 is a good point to start this process. A larger version of this click map can be found on the User Feedback Program home page.

More details, visualizations and reports will follow soon. 

Best regards,

The Project Renaissance Team

tags: renaissance user-experience

The user feedback program is still running and provides tons of data about what features are being used by our users in real live. This usage data is used within Project Renaissance.

The updated version from October now consists of five times more samples than the last version.  The spreadsheet provides separated data for Writer, Calc, Impress, Draw and a summary for all applications.

A visualization of this data for the Impress user interface and additional reports will follow later this week.

Best regards

tags: renaissance user-experience

Those of you who tested the Renaissance prototypes may have also responded to the survey that popped up afterwards. All in all, there were 1596 complete responses. (There were approx 1800, but the others were not complete) Thanks to Frank's hard work, the results have been compiled, evaluated and presented in a Calc file, however, omitting the comments from the text boxes which sometimes contained personal information that cannot legally be made public. (This has proven to be a continual problem with text boxes, so we are hoping to avoid this dilemma in future surveys by coming up with a solution that will comply with European data privacy laws and let us present all the data). The results in the Calc file be viewed on the Renaissance wiki.

Here are the results from three of the statements in the survey. Just to make you curious to see more ;-)

53% answered that they agree or agree totally that the current version of OpenOffice.org need a UI redesign. 32% answered that they disagree or disagree totally. This tendency supports the idea of project Renaissance.

66% responded that they agree or agree totally with this statement about the prototypes, whereas only 14% said they disagree or disagree totally. That means, that in these early stages of the project, conformity with user expectations is pretty good. From the comments (see Calc file), the live previews for formatting changes seem to have been especially well received.

Aside from the "Neutral" responses, the "Agrees" vs "Disagrees" are about equal. That shows that the prototypes don't yet have a polished UI (which was never in scope for the prototypes up till now) and that there are still too many clicks necessary to complete tasks.

The fact that there are still too many clicks is okay, because this was to be expected. We had planned to address exactly that by way of the OOo Improvement program data. Frank Loehmann has begun to analyze this user feedback data under the aspect of performing the most common tasks and will report on his findings when they are ready. The idea is to figure out how to reduce the number of mouse clicks or keyboard actions on the way to completing a task in the OpenOffice.org office suite. Stay tuned!

Thank you to everyone who filled out the survey. We really appreciate the feedback. Please continue to support our step by step effort to reach an improved UI.

The Renaissance Team

tags: renaissance survey user-experience

Since we have been rather silent lately, some might think that not much is happening in the project anymore. Therefore I would like to give all those who are interested a short update about what else, besides prototyping, keeps us busy.

In addition to going through gazillions of feedback regarding the prototypes on different channels, thinking and discussing further UX engineering initiatives, analyzing the data collected using a new, office productivity specific version of the IsoMetrics usability questionnaire, there are two university projects that we give advice to in parallel.

A study project team at the University of Osnabrueck, Department of Work and Organizational Psychology, has been working in the context of Project Renaissance since April 2009. This spring semester, the students were busy with getting into the basics of UX engineering from a theoretical and a practical perspective. Their goal for the first half of the project was to design alternative solutions of how to handle charts in OpenOffice.org Impress.

In July, the team under the supervision of Prof. Dr. Kai-Uwe Hamborg visited us in Hamburg and the students were given the opportunity to present their redesign ideas to the UX team and the whole Imress team. We had a great discussion about current usability problems and how the designs proposed by the students might resolve the issues. For further details, please visit the project’s Wiki page. In the coming winter term, the students will be busy conducting a usability study in order to validate the designs. We will keep you updated about their progress.

The second project was also initiated this spring with the support of Prof. Hamborg who is by the way one of the creators of the IsoMetrcs usability questionnaire. Our goal was to collect detailed information about the usage of office productivity applications in a university context. An intern of the Department of Work and Organizational Psychology conducted interviews to collect information regarding the tasks the students use office tools for. The task inventory was then used as input for a survey. This survey was conducted in several universities using the freely available LimeSurvey software which is also used by several OpenOffice.org teams. Data collection was just finished, so for now no detailed information is available. They only data that is available at the moment is that over a thousand students participated in the study, OpenOffice.org seems to not to be the leading (by numbers) office productivity tool in university context and Linux, as an operating systems, seems to be ahead of Apple Mac. A detailed analysis is what follows and as soon as the data has been processed, results will be posted here or in the Wiki of Project Renaissance.

The results of the cooperation directly support Project Renaissance. The data from the user feedback program gives us a clue about frequently used commands but with little task context, whereas detailed information from the task inventory survey will help us to map usage frequency on tasks. In addition, the study project might give us the opportunity to validate a few specific design solutions (e.g. sidepanes) with users. However, this is up to the study project team.

Best,

Andreas

tags: impress renaissance user-experience

The prototype phase didn't end on July 4 after as originally planned. It is still going strong and eliciting a great deal of enthusiasm and feedback. In this blog post we want to provide answers to some of the negative comments we've received. Of course we have been thrilled by all the positive comments, too, but the nay-sayers have been vocal, so we need to be vocal, too.

Some of the negative comments posted after in our July status update post were:

a) Oh no! Not like Microsoft!
b) My monitor gets wider not higher (horizontal vs. vertical UI)
c) Do not copy ribbons. Innovate do not imitate!
d) Why are you killing menus?
e) I/Everyone hate/s 'ribbons'!
f) Make it optional. Keep classic interface as an option.
g) 'Ribbons' are only for beginners/newbies.
h) Professionals (like me) are distracted by the new interface/'ribbons' because I/they already know were to find the desired functionality.
i) It is so ugly!

Before providing answers, we want to remind everyone of our goals and a tidbit about doing such development work in public.

Our mission:
“Create a User Interface so that OpenOffice.org becomes the users' choice not only out of need but also out of desire”

and our project goal:
"... to know and to understand our users as they are, and to help them accomplish what they want to, by providing efficient access to valuable functionality through a desirable user interface."

Please trust us that we will not implement anything that has not been tested and validated in real-life situations.

Working in the "open" can be tough. It seems that everyone under the sun already knows what we should do. Regardless of what we present we will always get at least one comment saying our idea is wrong/stupid (See a, c, e). The team always has to keep in mind that many comments are not from average users of OOo. The UX team has to weigh all comments carefully. Presenting a mid-fidelity prototype means risking that people do not understand the purpose and think the next product will look like this (i).

We also created a survey, that shows up when the prototype gets closed. (This requires Java 6 installed, because the system's web browser is called). The survey has more questions now since last Friday. New Prototype, new survey. ;-) The results of the survey are different from the negative comments on GullFoss. We think because those users who fill out the survey give the prototype a test drive at least for a moment. But who reads our blogs and tries the prototype? The average OOo user? No! So only real live testing can show us if a new UI is suiteable.

Developing a user interface (UI) for office sorftware is not an easy job, because this software is used by unique users with all skill levels and a huge range of tasks. Nobody wants to be a beginner, at least not for long :-) , so we have to focus on intermediate users while not distracting expert users.

When you analyse office documents, you see that most users only use a very basic set of features out of what OOo offers. So it seems that we are already done, because OOo could do so much more. Really? But why do those office documents look so basic even if they are made by experienced users? We only know a few people who are good in techniques and design at the same level. So users should concentrate on what they are the experts in: the document content, and not have to design/define/layout each and everything inside their document on their own.

Most expert users stated that they already know where to find the fucntionality (h) and that no new UI is needed, so that only beginners (g) would take any advantage of a new UI. We want to provide rich formated document pieces like tables, header, footer, indexes, etc. in galleries, so that the user can easily choose from professionally designed ones. This allows all users to create powerful and beautiful documents.We need some kind of new UI to offer those galleries.

This new UI needs a home. So the question was where to place it. The reading direction in western countries is from top left to bottom right and users are used to finding the interface on top of the document area. Furthermore the height available for a bar on, e.g. the left side, is too low for the amount of functions, especially on small displays like netbooks. Also we did not want to spread the functionality all around the application. So the team decided to go with a horizontal on top even if monitors are getting wider (b) these days. Most users use the software as it is out of the box, so we have to focus on a good default. But  there is nothting to say that the user can't configure it to fit their specific screen or work needs. It is a clear requirement that the new UI must support a minimized visualisation (fold open or change to float) and it should support a vertical visualization in a second step. Configuration possibilities could be added in future versions.

Our prototype did not kill the menus (d). They are still there! Even the new prototype, which is in the making, will keep at least the same structure (File, Edit, View, Insert, Format...) users are used to these days, but it will provide new graphical possibilites where we need it to provide rich formatted document pieces. The next prototype will also implement a context-sensitive interface approach.

tags: impress renaissance user-experience

It was really interesting to follow the media in the last days where discussion around the latest Renaissance prototype took place. And many many people commented on the blog from Frank a colleague of mine and other public sources.

First of all i am not really involved in this project, i am more an interested observer and see the opportunity in a new UI to improve the extensions infra-structure as well. But hey that is a different story.

The noise signals that people don't like an interface like ribbon or better where concepts similar to ribbon are used. I am not sure i have my own opinion but i agree at least that OpenOffice.org need it's own identity. It should be known as easy to use, highly productive and intuitive office suite with all the well known advantages (platform independent, standardized document format, free in terms of license costs for end users, etc.). And not only as a free alternative or clone of a well known other office application. The are many things that we will probably never achieve in the same quality. And the questions is if we need it or if it is maybe enough to make that what we have and what we can better, faster and easier to use? Means provide the tons of features in a new fresh way that people find it and can make use of it. How many office users can really work with styles, data pilots, etc.? I am sure you know what i mean.

Anyway i think the discussed prototype was not intended to demo an early development snapshot of a future office. No i think the intention was to experiment with concepts, give users the chance to play live with different settings and see what works best. And yes one thing of the prototype is the new toolbar concept that is similar to ribbon. I personally think that it is not bad to reuse ideas or concepts that are already accepted. Like it or not ( i personally don't like it very much but that is unimportant because i am no typical office user) but ribbon is based on a very good research work. And the Renaissance team planned their work based on the user data of a survey and they don't put simply their own opinions or preferences in a prototype. I recommend to all people who don't like the shown toolbar concept to join the UX mailing list, discuss it with the team and bring in your own ideas. It's even better as simply complaining publicly. Where do you have the chance to actively participate in such a planning ...?

Also surprising was that all the other good concepts and features were a little bit lost in all this blame war around the toolbar concept. What about the live previews, the drag and drop feature in the sorter view, the 3DView that shows probably one approach usable for small devices ... Many many other things are in the prototype, maybe you should give the prototype a further try with a new fresh attitude, free to explore the other stuff in it. And again if you feel competent to help in a constructive way join the UX team and bring in your ideas, your man power and help to make OpenOffice.org the best office suite of choice.

The prototype shows ideas and concepts and give you the chance to play with them live nothing more. It doesn't show the OpenOffice.org from tomorrow nor does it mean that the new OpenOffice.org UI will be implemented in Java. But Java was a perfect choice for the really fast prototyping and what i have heart the developers really liked it and especially the fast progress they made with the tooling around.

Prototyping is really a good approach to test concepts and get an impression how things work live. All the feedback is very important and i am sure that it will help the team for the future work. But as i mentioned there is much more in the prototype that needs attention and is worse to play with and where feedback is also welcome.

Please don't misinterpret a prototype and make too much noise about only one part of the prototype that of course is very visible ;-) There is again much more in it!!!

tags: user-experience