Repository navigation
UX Design Principles
🚧 The document is evolving at https://docs.google.com/a/recruiterbox.com/document/d/1nlD8HU82oFDSxnVbz7YTCpb80meVENWdJneKswKSiw4/edit?usp=sharing (private to Recruiterbox employees). Once stable, it will be updated here.
Users love automation as long they understand what's going on, and have a sense of control. When a product does something unexpected, it erodes my confidence in using the system.
Related blog post: http://inside.recruiterbox.com/magic-vs-delight-zen-is-in-the-balance/
You should provide a default behavior based on the stock use case, at least for repeated actions.
However, deciding whether the user should be able to override it is tricky. There are two conflicting things to be considered:
- Not all users are same, so you should provide ways to override the default behavior (without cluttering the interface for stock use-cases).
- Don't make users make choices they don't care about.
Whether or not a user would care about a choice depends on the particular business scenario and context. So balance these two appropriately. Defining different personas of your audience might help.
If a functionality requires the user to understand new UI artefacts, new concepts or a new way of doing things, then users might choose not to use the feature and might find work-arounds.
Do not introduce new artefacts, unless absolutely necessary. If you think it's absolutely necessary, validate it with other UX people.
Most people remember things visually. A user should be able to identify a particular type of object no matter where it is.
Examples:
- I should be able to spot an interview whether it is embedded in a candidate profile, listed in calendar, or rendered inside email. It should look the same everywhere.
- Whenever I have to select an opening from a dropdown, the list should look the same