Skip to content
#Design

The laws of simplicity (The Laws of Simplicity) (Category Design)

#Design #Leadership #Management #SelfDevelopment #Processes

The other day I read John Maeda's book on the laws of simplicity. John himself is an outstanding American designer, scientist and educator who is known for his work at the intersection of business, design and technology. He is currently Vice President of Design and Artificial Intelligence at Microsoft. Interestingly, this is the second book I liked, the first being ReDesisting Leadership. ("Leadership Redesign.")Which I'm talking about. wrote in the channel. If you go back to the book about the laws of simplicity, it is interesting that he wrote it almost completely. 20 Years ago, before iPhones came to market. Then it became a bestseller, but designers have since moved more towards complexity:)

John proposed using the following list of laws to strike a balance between complexity and simplicity in various aspects of life and work, making systems more intuitive and efficient. 1. Reduction (Reduce) - The easiest way to achieve simplicity is through conscious contraction. Remove the excess, but be careful not to remove something important. 2. Organization (Organize) - Organization helps to make a system with many elements more understandable and manageable. The right structure makes the complicated easier. 3. Time. (Time) - Saving time creates a sense of simplicity. The less time it takes to complete a task, the easier it is perceived. 4. Training (Learn) - Knowledge simplifies everything. The more you know about a system or process, the easier it is to work with them. 5. Differences (Differences) Simplicity and complexity are interrelated. To appreciate simplicity, you need to be able to compare it to something more complex. 6. context (Context) - What is on the periphery of simplicity is not insignificant. Context is important for understanding and perceiving the system. 7. Emotions. (Emotion) - More emotions are better than less. An emotional connection to a product or system makes them more attractive and understandable. 8. Trust. (Trust) - Simplicity requires trust. Users need to trust the system to make it seem easy to use. 9. Failure. (Failure) - Some things cannot be simplified. Not all attempts at simplicity will succeed, but it is important to learn from mistakes. 10. One. (The One) Simplicity consists in subtracting the obvious and adding the meaningful. This is the unifying principle of all previous laws.

After reading it, I didn’t feel like it was a law. I would rather call it interesting aspects, from the point of view of which you need to look at the system in order to balance the complexity and capabilities in it so that for users it looks simple:)

#Design #Leadership #Management #SelfDevelopment #Processes