I think it would be useful to look at where the target audience is coming from.

I was speaking with an instructor who recently taught Views to a group of old-school DBAs. They were like "AWESOME!" and got Views immediately, and were saying "This is great! I don't have to write this by hand!" The average Site Builder doesn't realize the word Views itself comes from database administration, and it rings no bells.

I think a design for a "simplified" version of the functionality Views offers needs to relate more closely to metaphors and functionality the target audience are familiar with. Then- ensure the new terms they see are practical and learnable.

I don't know what their background is myself- but it might involve looking at the lowest common denominators, and UIs the typical users are already familiar with. For example the "Smart playlist" options in iTunes are a good example of limiting a result set:
http://skitch.com/heatherjames/dxnfb/smart-playlist-limit-result-set

Narrowing the result set, and controlling how these appear are two different activities, and likely don't need to be managed in the same state of the UI. The display control can relate more closely to the client: the browser, the web page, etc. This is where the drag and drop WYSIWYG tools are helpful.

To me the sketches still look like too much candy. All good, but too much at once. Prep the result set, then let's talk about how it looks. Do we need to see the website while we analyze our content?

As with the terms used... To the Site builder, the notion of "simple views" might make no sense at all, and is meaningless out of the Drupal context. On the otherhand the use of the word "query" is different. While it my be an unfamiliar term, it's transferable and a learn-able concept. Displays is also a good term- because it relates to what it does.

Not to say the tool needs to be dumbed down- users are more than capable of learning the concept. However the UI can look and feel more friendly by starting at what people know -- > and then bring them into what they don't know.

I'd defer to Jeff Eaton's warnings about "dangers of Wizards"- since Buzzr uses them. It's a delicate balance between holding someone back or guiding then through. But I think breaking up the task into clearly defined stages would help: limit result set first, then control display.

Guess how often to Drupal instructors advise people to start on the "Right side" of the Views 2 interface? Likely, they all start this way. Filter first, then talk displays.

Heather James
Acquia Client Advisory Team