Good design is vulnerable to _rot_. Unconstrained/uncoordinated acquisitions/additions, will erode the key benefits of your design, whether it be in the realm a _business EA design_, _application design_, _interior design_, or _life design_. You don't have the luxury of going and doing "whatever", and ending the day with something as [[Cohesion|cohesive]] and workable as you started. As you add moveable elements, you add points of friction and failure. Maintaining [[Conceptual Integrity]] is **not** just a coding practice, it's a continual one in any arena you have to maintain. What changes you choose to make, and most crucially what _new components_ you choose to add must be in alignment with the design decisions you've made, or they will add complexity. [[Simple is Maintainable|Complexity is the Enemy]]. Good design means having [[A Place for Everything]], and that everything make sense in the place it is. Runaway additions, _especially_ those made by multiple people, will result in a big mess. You need to be confident and well-practiced in using [[A Firm & Polite “No”]]. Your design also needs to be present & clear - hidden or vague designs are forgotten or disregarded. [[Collocation of Strategic Artifacts with Daily Work Tools Keeps Strategy Relevant|Collocating your design with work tools]], when possible, is a good way to maintain [[Goal Presence]]. # Examples - When it comes to [[Enterprise Architecture]], you must consider your [[Project-to-Architecture Linkage]]. - When it comes to life design, it should be [[Hell Yes or No]]. - When it comes to coding projects, sometimes [[Worse is Better]]. - When it comes interior design, I'm not really qualified. Probably have less stuff, though. **** # More ## Source - self ## Related - [[Project-to-Architecture Linkage]]