Introduction | Technical personnel often have a tendency to focus on digging coal (working on technical architecture) without understanding the context of coal mining (the business background and organizational structure of the company). They do not know the organizational structure, business background and technology of the company. There is an implicit mapping relationship between architectures, and this relationship sometimes directly determines the success or failure of technical architecture transformation. |
This article attempts to establish this contextual background for technical personnel (especially architects), improve the technical personnel's vision, and allow technical personnel to promote the improvement and upgrading of the system architecture on the premise of understanding the enterprise's business background and organizational structure, with a view to Be more successful.
Economic BackgroundThe picture below is called the bathtub curve, which comes from Niels Pflaeging's book "Organize for Complexity" [Appendix 2]. It mainly reflects the changes in the Western economic model from the last century to the present. The shape looks like a bathtub, hence the name.
The organizational structure cannot be simply designed by the leadership. Different economic models require different organizational structure support. There is an implicit mapping relationship between the organizational structure and the economic model.
The picture above is the mainstream Taylor-type organizational structure in the Taylor Industrial Era, also known as the Command & Control organization. The leadership of the organization observes the market and formulates target plans, which are passed down by middle-level managers and implemented by lower-level employees.
The advantages, disadvantages and suitable scenarios of this organizational structure are as follows:
The Taylor Industrial Age lasted for more than a century and had a profound impact on our society. Even today, Taylor-type organizations are still the mainstream organizational structure of various enterprises in our society.
The picture above is a beta-type organization that is gradually emerging in the post-industrial era. It is common in some emerging industries such as mutual benefit network business companies. This type of organization still has leaders who focus on observing the market and formulating shared goals and constraints, but the organizational structure is relatively flat and the team organization favors cross-functional mixing and collaboration to respond quickly to market changes.
The advantages, disadvantages and suitable scenarios of this organizational structure are as follows:
Beta-type organizations are a model of modern leadership models and the direction of learning and transformation for many, especially traditional companies.
The complex adaptive organizational structure in the picture above, also known as the control feedback organizational structure (Cybernetic Organization), is currently relatively rare among established companies (only seen in a few startups), but it is a new trend in future organizational structures. This structure does not have centralized goal setting. The cross-functional mixed and collaborative team directly connects with the market, continuously communicates with the market to obtain needs, and responds quickly and flexibly to market changes.
The advantages, disadvantages and suitable scenarios of this organizational structure are as follows:
Conway’s LawMel Conway proposed the so-called Conway's Law [Appendix 3] in 1967, which pointed out that there is an implicit mapping relationship between organizational structure and system architecture:
Organization which design systems […] are constrained to produce designs which are copies of the communication structures of these organizations.
The design of the organization of the design system is equivalent to the communication structure between organizations
Conway's law can also be stated in reverse:
Conway’s law reversed: You won’t be able to successfully establish an efficient organization structure that is not supported by your system design(architecture).
You cannot build an efficient organizational structure if your system architecture does not support it. You can't build an efficient system architecture if your organizational structure doesn't support it.
Conway's Law gives us a good inspiration. There is an implicit mapping relationship between system architecture and organizational structure. You cannot unilaterally change the structure of one side, and both sides must be linked when adjusting. As shown in the figure below, if the system architecture is monolithically coupled, it will be difficult to organize a decentralized cross-functional market-oriented team structure. The two sides cannot be mapped, and friction and fights between teams are inevitable. Therefore, we generally first decouple and split individual applications according to business line boundaries, and at the same time make corresponding organizational structural adjustments. This is the motivation behind the microservice architecture that has become popular in recent years.
Mapping of organizational and technical architectureTechnical architecture cannot exist and be designed unilaterally independently. It has an implicit mapping relationship with the organizational structure and supports the core driving elements of the organization. The following two figures respectively illustrate the core architecture driving elements of Taylor-type organizations and complex adaptive organizations, as well as the resulting application architecture characteristics.
From the technology stack and application architecture characteristics adopted by an organization, you can also quickly infer the organization's business model and organizational structure, as shown in the figure below. Monolithic architecture, centralized database, and layered architecture are common in Taylor-type organizations; while cloud computing, REST microservices, and DevOps technologies are common in Beta and complex adaptive organizations. The figure below also reflects the synchronous evolution trend of organizational structure and technology stack.
The above is the detailed content of The impact of an enterprise's organizational structure on its technical architecture. For more information, please follow other related articles on the PHP Chinese website!