fewer-features-development-resources-time-features-users-really-fewer-features

Developing fewer features allows you to conserve development resources and spend more time refining those features that users really need. Fewer features mean fewer things to confuse users, less risk of user errors, less description and documentation, and therefore simpler Help content. Removing any one feature automatically increases the usability of the remaining ones.

0/5 (0)

Jakob Nielsen's Popular Quotes

0 Comments

Login to join the discussion