# The laws of simplicity

> ## Ten laws

## Ten laws

### Law 1. Reduce: The simplest way to achieve simplicity is through thoughtful reduction.

> The easiest way to simplify a system is to remove functionality. … The fundamental question is, where's the balance between simplicity and complexity? On the one hand, you want a product or service to be easy to use; on the other hand you want it to do everything that a person might want it to do.

하지만 [Simplicity is not the answer](https://wiki.g15e.com/pages/Simplicity%20is%20not%20the%20answer.txt)에 의하면 위 구분은 잘못된 프레임이다. 기능(features, functions)과 가능성(capabilities)은 다르다. 기능과 단순성 사이의 trade-off는 최후의 수단이어야 한다. 뻔한 옵션(기능 vs. 단순성) 중 하나를 고르는 건 디자인이 아니다:

> "Designing isn't about choosing among multiple options - it's about creating options, finding a third option instead of choosing between two undesirable ones." --[Dan Saffer](https://wiki.g15e.com/pages/Dan%20Saffer.txt), [Designing for interaction](https://wiki.g15e.com/pages/Designing%20for%20interaction.txt) [#ref](https://wiki.g15e.com/pages/Dan%20Saffer.txt#third-option)

### Law 2. Organize: Organization makes a system of many appear fewer.

### Law 3. Time: Savings in time feel like simplicity.

### Law 4. Learn: Knowledge makes everything simpler.

### Law 5. Differences: Simplicity and complexity need each other.

### Law 6. Context: What lies in the periphery of simplicity is definitely not peripheral.

### Law 7. Emotion: More emotions are better than less.

### Law 8. Trust: In simplicity we trust.

### Law 9: Failure: Some things can never be made simple.

### Law 10. The One: Simplicity is about subtracting the obvious, and adding the meaningful.

## 3가지 비법

- **멀리 보내기**: 단순하게 멀리, 멀리 보내면 많은 것이 적어 보인다
- **개방**: 개방해서 복잡함을 단순화하기
- **힘**: 덜 쓰고 많이 얻기

## See also

https://lawsofsimplicity.com/