The afternoon was more interactive. We had some very interesting discussions on design and user interface issues regarding Sakai. Here are some current and future challenges for Sakai I would like to mention here, that came up during the afternoon.
- We have, what was called the Microsoft Office effect: there is a proliferation of functionality within a tool (e.g. Resources tool) and therefore tool get less and less usable, certainly for the first-time user of a tool.
- There are tool-silo's. Newcomers are asking questions like "Why is it that I should put all stuff into the Resources tool?" Wouldn't it be great that we would have Flickr Uploadr tool (a litte desktop application), with the same user friendliness, to upload stuff into Sakai?
- Sakai technology is complex. Sometimes small changes seem to take forever. For example the Schedule: why is it so hard to display the title of the Month in the right place. Or another big user (support) issue: why are we still having the problem of the Back button, that doesn't behave as expected?
- Shouldn't user interface issues be part of QA?
- We should focus more on user scenario's (what does the user want to accomplish?) if we (re)build Tools
- Sakai as a product is mirroring the community, maybe... It is very difficult for different (working) groups to come to terms with other groups, and that is what you see reflected in the tool-silo's.