Universal Principles of Design
Hierarchy of Needs
Design must serve the low-level needs (function) before the higher-level needs
- Functionality → meet basic design requirements
- Reliability → stable and consistent performance
- Usability → ease of use
- Proficiency → empowering people to do more
- Creativity → shit gets crazy
Follow four stages of creation:
- Requirements → design requirements gathered
- Design → requirements translated into specs
- Development → actual product built
- Testing → ensure product works
Products progress through four stages of existence:
- Introduction → product is created
- Growth → scale supple & performance to meet demand
- Maturity → enhance & refine for customer retention/satisfaction
- Decline → minimize maintenance & migrate customers
divide large systems into smaller, interdependent, self-contained module
- modules should hide internal complexity, interact with other modules through simple interfaces
- Involve tackling a problem by breaking in down in stages, parts, etc.
- Some terms deal in absolutes “In order for a design to be successful…a design must…” – this can lead designers to view this principles as absolute laws that must be followed in every case, rather than guidelines that should be applied when appropriate.
- Terms that involve steps or have hierarchal structure don’t take into account the iterative cycle of most successful products. Often, these steps are not milestones to be achieved and then forgotten, but rather revisited and considered during every iteration.