The Zen of 80|20 for designing content, programs, screens, bundles of packages, and whole systems.
Companion: Zen for agents.
Deliver the requested value with the smallest complete solution. Extra features and stronger promises bring costs; add them for real needs, not imagined ones. Simplicity must preserve correctness and trust.
Combine and reuse what already works. Introduce a new concept only for a current need that existing concepts cannot meet simply, and keep it focused on that need. Let further uses earn their complexity when they arrive.
Choose a small set of capabilities that delivers most of the practical value. Simplicity should make the system useful, coherent, and dependable.
Organize packages and bundles around meaningful areas of responsibility. Make each part's purpose and its relationship to the whole easy to explain.
Make the important concepts and relationships easy to explain. Content, programs, and screens should reinforce that understanding.
Use conventions to make ordinary work easy while leaving clear ways to adapt and extend the design. Useful defaults should support different approaches as needs evolve.
Connect parts through what their responsibilities require. Allow each part to evolve without forcing unrelated parts to change.