News from Apr 09, 2008

UX Project Feedback - Open Call

Several data points came out of the meeting:

A. The design should incorporate some ideation around a "Sandbox" site type as an option that lets instructors (and possibly other users) take Sakai for a test spin before committing to building a site of their own.

This is a good starting point, but it would be helpful to get specific use-cases around this idea.

B. There was a desire to see the design present more "real world" examples. There was some concern that the direction might not scale well when, for example 50+ sites or tools are added to a user's layout.

In general, there was a desire to see more detail. One request had to do with how tools might be ordered more elegantly so that once added to the layout, they would offer more options than just a first in first out ordering method.

Someone put the request for more details it in terms of seeing a before and after – like an "extreme makeover"!

My fumbling response to that was (sorry guys, I'm on practically no sleep at the moment due to exams) that the design is all broad strokes at the moment. I'm still dealing with the basic building blocks of this thing, so please be patient about the details. Believe me, I am just as anxious to dive into details and see how they fan out. So as soon as I get beyond a few more larger chunks of the product, I'll make it a point to come up with several mock-ups that show more real world examples and use-cases in action.

In part, that's the reason why we're talking implementation at the moment. We'd like to get a prototype track going where users can begin to interact with real data so we can see where the leaks are and be in a better position to address them.

C. There were comments that touched on what appears to be a recurring concern about the design offering too much!

Folks shared a bit of skepticism that the design is impractical in a real-world deployment where instructors or other users are NOT given access to build and manage sites in such a free-form way. Instead, the more common scenario is that instructors are given a site or two that are designed by someone else (like an instructional designer) and they often have little need (or ability) to dramatically modify it – much less build a site from scratch.

This point is well taken and certainly has not escaped my attention. There are two things I want to say about this issue:

1. We're not yet at a point where we're packing this thing up and driving it into the trunk. This design is just that, a design. More over, it's a design happening in real-time. You're seeing it emerge and in the process are privy to the toiling involved in the the trial and error. It's natural to be concerned that this is what the finished product will be, but let me assure you, it's far from it!

Before this project started, I thought quite extensively about how to approach the process. Either behind a curtain or out in the open. I opted for the latter as I think it better mirrors the spirit of this community. But that approach introduces confusion – so I apologize if I haven't managed the communications better.

I'll continue to emphasize this point as the process moves along.

Also, keep in mind, the reason I wanted to do it in the open was to make sure everyone who wants to have a say into the design will be given the chance to. So try not to feel skeptical, but rather look at it as a work in progress with your feedback playing a significant role!

2. I realize that the design presents MUCH functionality in the UX. There are several reasons I chose this route:

• Not all institutions lock things down for their users.
• Sakai does not necessarily (albeit it mostly is today) used only in the academic context. <-- This is not a principle driver, so don't get too hung up on this point.
• It's easier to scale down than up. If I designed a limited solution, it would be much harder to envision something more robust for those that need it. It's easier to go the other way.

And on that last point, keep in mind that there will certainly be an admin side to all of this that should allow for extensive configurations! So much of what you see will be very much controlled from institution to institution by the system admin. Ideally, I'd like to see an admin control panel that is cleaned up to support ease of use and efficiency for the admin – but that often comes down to a trade-off in priorities

D. There was a question about Fluid and involving their efforts.

Yes, I agree. This has been one of the main goals from the outset of this project. Once they get some more time, I'm confident we'll be collaborating much more.

E. And finally, a few folks had questions about Paris and any workshops there that could be offered around this project.

Unfortunately, my phone or my ears seem to be going (probably a combination of both) and I missed much of what was said, but John Norman mentioned something about preparing an event either during or after – as well as something during the JASIG conference. But again, I didn't fully catch everything so if someone can add those details here, I'd appreciate it.

Personally, my only plans for Paris are to discuss the UX Improvement Initiative and give a brief showing of progress being done. The format will be a 1 hour presentation. I'd prepare more of a brainstorming and planning workshop, but unfortunately, I just won't have the time this go-around.