> How can you distribute responsibility for design through all levels of a large hierarchy, while still maintaining consistency and harmony of overall design?

> How can you distribute responsibility for design through all levels of a large hierarchy, while still maintaining consistency and harmony of overall design? This how the author summaries the intent of Christopher Alexander's work. I have not read "A Pattern Language" so it's difficult to say if this is accurate or not. However this is such an important issue in software engineering that I would welcome any ideas to reduce the problem. I agree when the author that the GoF addressed a lower level problem. However, I'm also disappointed by these slides that provide not hints for a better high-level approach. The GoF patterns form a language for developers speaking to developpers. We also need a language across roles.