Tag Info

Here is my theory: Its about the ROI. Its not that there is a good reason for the passive ui for help sections, by all rights every part of a system should have an excellent and active ui. But we tend to focus harder on the core customer experience, because that's where the money is. And just tack on documentation / help sections. The effort that help ...

I don't see any disconnect at all between the two. Most people will have a faster response to objects on the right side of their visual field. So that applies to moving balls; tigers that want to eat you; etc. It is about a tiny increase in visual perception. This has nothing to do with learned importance. Reading from left to right has taught us that ...

I would say No, not entirely. There is of course the System Usability Scale which measures: effectiveness (can users successfully achieve their objectives) efficiency (how much effort and resource is expended in achieving those objectives) satisfaction (was the experience satisfactory) The measurement coming closest to your question would be ...

I already have seen different kinds of interactive help at multiple websites. However, it were always used in context with a guided tour to introduce the features of a system to a novice user. One example is an online route planner - the tour can be started immediately after the page is loaded. Furthermore, facebook usually makes a short interactive tour ...

In simple terms no. Task complexity can be determined through user testing, preferably using an approach such as contextual enquiry. All scales will be based upon interpreting the user feedback and if a user can successfully carry out a task. Common 'scales' are series of grades ranging from everyone completes the task with no problems through to tasks ...

Here's one way to do it, assuming that permissions are the same for each object group. (ie If User01 can edit an object under group X, then he can also edit the 500 other objects in group X). Rather than defining role as a group of users, define the role as a group of permissions. For example: Role 1 (admin) can edit, delete, and view Role 2 (author) can ...