OpenSource Usability Labs

We need your answers!

Please take 10 minutes to answer a few questions about how you use calendars.

All answers will be used to make the new Tine calendar fit everbody’s needs perfectly!

The survey is in two languages:

English version: http://tiny.cc/calendarsurvey_en

German version: http://tiny.cc/calendarsurvey_de

We really appreciate your contribution.

Hurray! Tine 2.0 has qualified as a finalist in the  Trophées du Libre. Congratulations to the whole team! Good work gets appreciated

Footnote:
I am in the jury of Trophées du Libre, but as I am juror in the category “Education”, I had no influence on the nomination of Tine in the category “Professional”.

I am very happy that Anne decided to join the Tine 2.0 Team. Anne studies international media informatics at the FHTW Berlin. She is doing her bachelor work on the Tine 2.0 calendar. In this scope she will analyse personas and use-cases for the calendar as well as other existing calendars. She will develop the interaction- and interface-design and do some surveys and usability-tests. Of course she will regularly blog about her work.

Welcome, Anne!

Seeing the upcoming surveys: if you haven’t registered for participating in these tests yet, you shouldn’t wait any longer. This is your chance to feedback on the Tine 2.0 calendar and other Tine 2.0 development! Also feel invited to discuss any issue on the calendar in our forum!

After Conny asked me to, I moved the introduction of Tine 2.0 Concepts into the Tine 2.0 Wiki today. When I did this I was shocked to see how old most information in the Users-section was. So additionally to adding the introduction I ended up updating some more pages in the wiki. But as time is always a little short there is still some work to do. So if you feel competent, please add some features to the description of the Tine 2.0 applications.

Today I have started an introduction on the main concepts of Tine 2.0. I hope this will be helpful to new and experienced Tine-users.

I have chosen not to post this introduction as blog-post, since I will try to keep them up-to-date. So you will have to take a look at the static articles in our blog.

So far there is:

• Tine 2.0: concepts and ideas
  • Choosing an application
  • Filtering Lists
  • Places - or how to manage visibility
  • Working with records

I am very happy about comments since I will try to keep working and improving the articles.

We were in the lucky situation to conduct a usability-test with seven volunteers of a German company. They are using Tine 2.0 mainly as CRM-Tool to coordinate their sales-department. Consequently they are using contacts, CRM and tasks, but not the other apps of Tine 2.0. All user were regular, but not frequent users of Tine 2.0 and moderately comfortable with computers in general.

The tests were concepted as semi-structured, task-oriented interviews. I lead all interviews, while Conny Weiß was participating as an active observer. He was allowed to ask and answer any questions during the interview.

The scenario was as follows:

1. Users had to log-in and explain their general impressions and understanding of Tine 2.0.
2. Users had to find and modify an existing contact. Focus of this task was the use of the filter-system as a quick-filter, the short-view of a contact and the modification of an item.
3. Users then had to export a list of contacts to .pdf, that had to be composed by a rather complex filter-setting.
4. Next they were asked to create a to-do-list which only a certain group of people was allowed to see.
5. Finally they were asked to show how they manage a typical task of their daily work with Tine 2.0.

The interviews were very informative. The results were aggregated and transformed into tasks for further development. The detailed results can be found in the bug-tracking-systems of Tine 2.0. Following I will give an overview of the most important findings:

1. General understanding of Tine 2.0 is good
   All users were able to explain the general concepts of Tine 2.0 and were competent to solve even complex tasks. This encourages us to stay with the chosen general approach of Tine 2.0, namely keeping the general screen-estate, the filter-list-view, the application-pile etc.
2. Sometimes Tine 2.0 gets in the users’ way
   In some details Tine 2.0 is not enough consistent, predictive or supportive for the user. We have found heaps of these small Usability-Bugs, showing us that we have to be even more precise with all those little things. Examples for this category are:
   * The addressbook-container has not been correctly pre-selected when adding a new contact
   * Some wording was not understood
   * Not sufficient feedback when filtering caused no results
   * Number of elements in lists are not configurable
   * …
3. Notes should be editable
   The concept of notes was appreciated by the users, but they wanted notes to be editable and they wanted notes to show up at more then one place.
4. No connection between CRM and Tasks
   Users had the problem that they cannot see which CRM-Lead a certain task belongs to.
5. Use of Right-Mouse-Buttons is confusing
   Users were not able to predict where and how they could use the right-mouse-button-menu.
6. Selection of a person is confusing
   The dialogue to select e.g. the responsible person for a task lead to some irritation for the user.

This is just a short summary of the most important findings. A lot of the issues have already been fixed for the upcoming Tine 2.0 Lara release. All other issues are integrated into the further development schedule.

Summing it up: the user test was well worth it and helped us a lot to loose our expert view and once again see Tine 2.0 through the eyes of a “normal user”.

We want you - for Tine 2.0:

If you are interested to support Tine 2.0 development, then join our mailing list for voluntary usability-testers. Your help is very much appreciated and taking part in these tests only takes a little time and is fun! Take a look at our Icon Test demo to get a feeling what these usability-tests could look like.

I have decided to provide some hints how to efficiently work with Tine. And I will do this as a series of blog posts within the next time, accompanying the upcoming spring 2009 release of Tine. Let us start with

Question #1: If Tine 2.0 is so usable, why is there a need for a tutorial?

Tine has been developed with a strong focus on usability. Usability experts and interaction designer have been integrated into the development from day 1 on. We regularly conduct usability tests to improve the product even further. Nevertheless usable does not equal simple or easy to learn. Both attributes are important aspects of a usable product - and of course we try to make Tine as simple and easy to learn as possible. But these attributes are not the foremost criteria for optimizing the user-experience of Tine.

When setting the scope for Tine we have decided that interactions and dialogues of Tine should always be

1. enjoyable - Tine is designed to be fun to use. So everyone should like to use Tine.
2. efficient - Working with Tine must always be efficient. Tine should never come into your way.

In opposite you can say Tine does not maximize the power for a first-time-user. We do not try to oversimplify the rather complex process of a groupware: different, cross-depending applications, a very detailed rights-management,…

So there is a need for some tips how to work efficiently with Tine. These will follow in later posts and hopefully help you to enjoy business collaboration with Tine even more!

Our family of companies (OpenSource-Usability-Labs, Apliki and binaere bauten) has finally moved from eGroupware to Tine 2.0 as our leading groupware system. Only for the in Tine 2.0 still missing calender we continue to use the eGroupware calendar.

I was quite nervous promoting and pushing the decision to do so. The dialogues and workflows of Tine show to a very great extent my handwriting. Therefore everything that does not yet work as expected falls back on me. And one thing is for sure: Tine 2.0 is still a young project, having many bugs and lacking features at this point of time.

So why did I promote the change? First of all I was always very unhappy about eGroupware. It is feature rich, but - many complex technical product have this problem - most users could not use more than perhaps 20% of these features. We had eGroupware running for more than 2 years now - still whenever I talked to Conny or Lars telling them that I failed to do this or that with eGroupware the answer was always the same: It is possible. Just this did not help me in my daily life. So in my eyes the lacking features of Tine 2.0 compared to eGroupware are to a great extent only virtually missing, because for the normal user eGroupware is not feature-rich, it is confusing.

The second reason to change to Tine 2.0 in productive use is of course to get feedback. I am in charge for the usability part of the development - but until now we did not have the chance to actually test the concepts we have thought out. So now is the time to get back to earth and see whether things work out the way we hope. Next to using Tine 2.0 ourselves, we will start doing active usability testing from February on.

So what is my intermediate result after about 3 weeks of active Tine usage?

Honestly, I am overwhelmed. There are a lot of bugs. To a great extent these are not severe bugs - they just get in your ways here and there - but hey: we are working on a development snapshot. What should one expect? But the integration of different aspects of groupware is just great. The filter-list-system is working well (of course: it still needs a little polishing). Still more than this: Using Tine is just fun. Working with eGroupware I always felt like: ok, this is the application we use, so teeth together and do what you need to do. So I always did what I really had to do, but never more than that. With Tine 2.0 it is just the opposite. I really enjoy working with Tine. I have caught myself just playing around with Tine, exploring the possibilities. This way I did what is most important for a groupware: I used it. I put all the information in Tine that never found their way into eGroupware.

Summing it up: except for the painfully missing calendar, I think Tine 2.0 is a great groupware. It has less features than eGroupware, but overcompensates this by being straight forward and fun to use. The decision to change from eGroupware to Tine 2.0 was a good one! I hope the usability tests we conduct in the next time will confirm this picture.

Last week we had a closer look at the filter settings for Tine 2.0. Filters are a central part of the user interface concept, because interacting with Tine 2.0 follows a clear structure:

1. John picks the sub-app, e.g. Contacts he wants and needs.
2. He then gets a list of available item, which he needs to narrow down.
3. He identifies the item he was looking for and is doing some action with it.

This workflow is true for almost all kinds of sub applications. Filters come in play in step 2. Here John needs some easy way to narrow down the list of items. We want to achieve this by the use of a strong and still easy to use set of filters. Take a look at a working draft of how these filters could look like:

The operator in the middle will be only active, when it is needed, e.g. for narrowing down dates or postal codes, so it does not come into John’s way when he uses <TAB> for navigating.

In the default view John will see only one filter line showing a quickfilter. This would be

[Contact|V] contains [____________________]

for address book. This way he always has a one-click search-like filter setting available for doing the 95% of the searches he needs to do. Still, the other 5%, where John needs to do a complex filtering are available just as easy!

One the fascinating ideas of this concept is the possibility to save these complex, but powerful and often needed filter sets. So John can do frequent searches with one click faster then ever before! And there is no limit to individualisation. Susan, Paul and James can define and access their most needed tasks this way. Tine 2.0 will be just right and powerful for all of them - and for you!

Only one week left to LinuxTag in Berlin (28th to 31st of May)! It is always a great event and I am looking forward to meet all the great people that are engaged in the OpenSource community! And of course I am personally happy that this event has settled in Berlin - and I do not need to travel for it anymore

Unfortunately the OpenSource Usability Labs will - this year - not have there own booth on LinuxTag. But you will find me most of the time at the Tine 2.0 booth. It is located in hall 7.2a booth no. 115.

I am very happy to get feedback on the ideas we can present up to now with Tine 2.0. Feel free to discuss the concepts in User-Interface- and User-Interaction-Design with me. As well I am looking forward to discuss any issues related to usability in OpenSource in general - be it in the scope of the OpenUsability-Initiative or a matter of the OpenSource Usability Labs.

See you on LinuxTag!