Lesson 65 - Distributed Strategy of Enterprise Architecture

Summary

In this lesson, Mark Richards discusses the distributed strategy in enterprise architecture. This approach delegates decision-making and standards to individual business units, while maintaining minimal shared enterprise standards. Key examples include security and hardware standards. Although this strategy allows for flexibility and tailored solutions per unit, it can lead to high costs and synchronization challenges. Richards also outlines the benefits and drawbacks of this model, emphasizing the need for balance in enterprise standards. Further resources and related lessons are available on his website, developerToArchitect.com.

Takeaways

• 🏢 The video discusses the 'Distributed Strategy' as part of enterprise architecture, where decisions and standards are delegated to individual business units with minimal shared enterprise standards.
• 📜 Enterprise architects in the central organization define minimally shared standards that all business units must adhere to, despite their autonomy.
• 🔒 Security, hardware, and network concerns are highlighted as examples of enterprise standards that might be centrally defined and minimally shared across the business units.
• 🛠 Each business unit has the freedom to define its own standards and technologies, leading to a diverse range of architectures within the same company.
• 🔄 The distributed strategy allows for flexibility and control at the business unit level, enabling faster response to user requests and better overall satisfaction.
• 🔗 However, this approach can lack synchronization between business units, which might be suitable for fully autonomous units with no need for synchronization.
• 💰 The strategy can be costly as each unit operates independently, making it difficult to standardize on licensing or achieve economies of scale.
• 📊 The difficulty in governing minimally shared enterprise standards can lead to an overreach, potentially turning the strategy into a more prescriptive approach.
• 🔑 The video suggests that the distributed strategy is best for businesses with diversified units that do not require synchronization, like a trucking company and a pie shop within the same organization.
• 📈 The script provides a comparison with other enterprise architecture strategies, suggesting viewers refer to previous lessons for a comprehensive understanding.
• 📚 Mark Richards, the presenter, offers further learning opportunities through his website, including private training classes and analysis of software architecture.

Q & A

What is the main focus of lesson 65 in the Software Architecture Monday series?

The main focus of lesson 65 is on the distributed strategy of enterprise architecture, which involves delegating decisions and standards to individual business units with minimally shared enterprise standards.

What is the difference between centralized and distributed strategies in enterprise architecture?

Centralized strategies involve a central governing body that defines and enforces standards across the entire enterprise, while distributed strategies delegate the decision-making and standard-setting to individual business units, with only a few minimally shared enterprise standards.

What are some examples of minimally shared enterprise standards in a distributed strategy?

Examples of minimally shared enterprise standards include security standards, hardware and network concerns, and possibly databases for integration and information sharing.

How does the distributed strategy benefit business units in terms of flexibility?

The distributed strategy allows each business unit to define and implement their own standards, technologies, and methodologies that best fit their specific needs, providing greater flexibility and control.

What is a potential disadvantage of the distributed strategy regarding synchronization?

A potential disadvantage is the lack of synchronization between business units, as each unit operates independently with its own standards, which can complicate coordination and integration across the enterprise.

How can the distributed strategy lead to higher costs?

Higher costs can result from each business unit making independent decisions about platforms, technologies, and licensing, which prevents the enterprise from benefiting from economies of scale and bulk licensing discounts.

Why might enterprise standards in a distributed strategy go overboard?

Enterprise standards might go overboard as central organizations try to manage costs and control by adding more and more shared standards, which can gradually turn the strategy back into a more prescriptive or centralized approach.

What are the advantages of the distributed strategy in terms of tool selection and user satisfaction?

The distributed strategy allows each business unit to select the tools that work best for their specific context, leading to better business unit control and higher user satisfaction due to faster response times and tailored solutions.

In what type of organizational structure is the distributed strategy best suited?

The distributed strategy is best suited for organizations where business units are fully autonomous and do not require tight synchronization, such as a diversified company with units operating in different industries.

How can the lack of synchronization in a distributed strategy affect economies of scale?

The lack of synchronization can prevent business units from agreeing on common platforms and technologies, making it difficult to achieve economies of scale in purchasing and licensing, leading to higher overall costs.