Link Search Menu Expand Document

Build polite software

The principle of polite software is a great cheatsheet while improving your product design skills.

You learn a lot about UI/UX and interaction design

Even if you are already experienced in product development, you’ll learn a lot on the job. Particularly about the requirements of users in your niche.

But, building polite software is a shortcut

The book “Inmates are Running the Asylum” is a great help. In particular, the rules of “Polite Software” are very useful. They’re as follows:

  1. Polite software is interested in me
  2. Polite software is deferential to me
  3. Polite software is forthcoming
  4. Polite software has common sense
  5. Polite software anticipates my needs
  6. Polite software is responsive
  7. Polite software taciturn about it’s personal problems
  8. Polite software is well informed
  9. Polite software is perceptive
  10. Polite software is self-confident
  11. Polite software stays focused
  12. Polite software is fudgeable
  13. Polite software provides instant gratification
  14. Polite software is trustworthy

But remember to apply different principles to different users

Depending on what the user’s job is, they might place more or less value on each of the principles.

For example, the finance department places a very high value on accuracy and a negative value on fudgability.

Buyers, on the other hand, require good responsiveness and a great deal of common sense.

And the customer service department might value interfaces that are forthcoming and allow them to see the whole picture.

Ognjen Regoje

I make things that run on the web (mostly).

Further reading

Suggest an improvement to this page (