Moo.com UX rules

Optimise for the common case
Build tools that focus on meeting one simple need
Build tools for users without experience
Users needs are not always the same as the features they ask for
One action per page
Context is more important than consistency
Optimise for average user's return rate
Make pages functionally readable
Only tell people things once per page
Contextual help is best
Let people teach themselves
Keep the user path as short as possible
Make decisions for people
Make people confident in their actions
Pages make sense before and after action
State should always be maintained between pages
Make sure pages content can be linked to forever

Help needed for "Moo.com UX rules"!

The following is missing from this set of principles:

Summary: Each design principle can have a brief summary, these could be a couple of lines or a detailed paragraph outlining how this principle is used or measured, e.g.

- principle: Strive to be universal
summary: Our aim is to be a resource that is helpful to everyone. We do this by strictly adhering to principles of progressive enhancement…

Tip! You may be able to find the missing information at the source URL:
https://blog.memespring.co.uk/2014/08/02/moo-ux-rules-circa-2008/.

It would be great if you could contribute and update this set of principles with anything that's missing!

Optimise for the common case

Build tools that focus on meeting one simple need

Build tools for users without experience

Users needs are not always the same as the features they ask for

One action per page

Context is more important than consistency

Optimise for average user's return rate

Make pages functionally readable

Only tell people things once per page

Contextual help is best

Let people teach themselves

Keep the user path as short as possible

Make decisions for people

Make people confident in their actions

Pages make sense before and after action

State should always be maintained between pages

Make sure pages content can be linked to forever