One could say 'the applications that are easy to use are designed to be intuative'. Well, yes. That's almost a tautology. Except that the word 'intuative' is a little bit deceptive. Jeff Ruskin once pointed out that when we say 'intuative' in the context of software, we really mean 'familiar'. Computer mice arn't 'intuative' to someone who's never seen once (although a grizzly bear would be). There's nothing innate or instinctive in the human brain to account for it. But once you've taken 10 seconds to learn how to use a mouse, it's familiar, and you'll never forget it."

Leave signposts. Hyperlinks do this by default - they take you to where more information exists on the topic you have selected.

Good creative tool support leads to the absorbsion of the user in the activity. Time distorts - other distractions fall away. Much like in an embodied interaction.

Page organisation. Tidwell discusses Gestalt properties of similarity, proximity, continuity and closure.

Against Iconic controls (by this she means pictographic rather than textual) - the meaning generated may be cryptic.

Knowledge in the world is better than knowledge in the head. Present options rather than making the user remember information.

Prospective Memory: The ability to so organise data to make it easy to find again.

Advocation of colour coded areas. Hmmmm. The W3C accessability people don't like them and with good reason. I did initially think this would be useful for the ap. provide a third colour to sit with the black and white. I'm glad I didn't use one now. Just the blue for the hyperlinks which is not the only visual indicator of it's control status.

Center stage is the most important focal point. A lot of comic book artists would dissagree, this is discussed in Artists on Comic Art. But this maybe a practice based media consideration. I guess we'll see.

Scrollbars. I've not thought of them as a navigational device for the area mapping section of the interface

Data brushing: Or filtering as we otherwise know it - helpful when drilling down into a lot of data, like there is on this page.

Well that's true until it's used. After that learned experience *should* (as in I need to test it properly or find someone who has already done so empirically) kick in and make the image based control easier to use, that is if I'm reading closure right.