Skip to main content

The Organizational Chart and the VSM: How Does One Get from One to the Other?

  • Chapter
  • First Online:
The Viability of Organizations Vol. 3

Abstract

One of the most intricate and yet not entirely resolved questions regarding the VSM is its conceptual relationship to the organizational chart. This chapter tries to shed light on this fundamental question. It clarifies firstly, the function of the organizational chart and secondly, illustrates how the organizational chart is generated from the VSM. The reader will learn in-depth how the formation of the corporate functions and organizational chart structure causes the fragmentation of the viable systems and leads to the fundamental tension between specialization and the preservation of a holistic perspective on the organization. How should one deal with this polarity? Is a holistic approach already the solution or do “silos” that mark our organizations also have a positive value? One thing is certain: A more nuanced approach is required.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 54.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 89.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    All figures in this chapter related to the VSM are or contain and if not stated otherwise, adapted (detail) views from Beer (1995, p. 136, Fig. 37).

  2. 2.

    In the meantime, one might even assume that some of the standard management functions can be replaced by computer programs and that the “boss” might no longer be a human being but an algorithm dictating what to do (see O’Connor, 2016).

  3. 3.

    See Schewe (2018), for whom the job design is a process in the creation of the organizational chart structure, in which tasks are aggregated to be taken over by a human agent (“[die Stellenbildung ist ein] Vorgang zur Gestaltung der Aufbauorganisation, bei dem durch Aufgabenanalyse gewonnene Teilaufgaben im Wege der Aufgabensynthese für jeweils einen gedachten Handlungsträger zu einem Aufgabenkomplex bzw. zu einer Stelle zusammengefasst werden.”)

  4. 4.

    The deliberate choice in the organizational chart to reduce accountability to one line creates its inherent problems: Often, one finds that the responsibility for a specific decision and action is distributed among many employees, managers and executives. Decisions in organizations are usually the result of a collective reflection and discussion process than just of one individual. Organizations should thus be better viewed as “networks of shared responsibility.” Here, the organizational chart masks an ambiguity that can result in residual variety (e.g., in the form of unjust accusations).

    The VSM is sometimes criticized for not providing a place for the concrete employees. However, its purely systemic and thus somewhat impersonal perspective also has its advantages, since it reminds us that the exercise of a system function can be larger than just the nominated person in the organizational chart. A system function comprises all who exercise it or contribute to it and not just the person named in the organizational chart.

  5. 5.

    The term “area of responsibility” that is frequently used in organizations merits a deeper analysis since it also is the source of numerous tensions. The term leaves the specific responsibilities of an employee relatively unspecified, and so, the employees must adjust their job profiles accordingly to the concrete needs and issues. The advantage for the organization is clear: It relieves the organization from the duty to continually (re-)adjust all job profiles.

    It also alleviates the organization from its own incalculability and lack of transparency: It is one of the great fallacies to believe that an organization knows what it is doing (i.e., what tasks need to be accomplished). Unfortunately, this is not the case and the concept “area of responsibility” here helps the organization to temporarily regain some of its calculability. It leaves the incalculable and spontaneous part to the individual employee. Being the owner of an area of responsibility, he or she then becomes responsible for processing the spontaneously emerging issues that cannot be defined by the organization in advance.

    The problem, however, is only deferred, since the understanding of what is part of an area of responsibility and what not might differ between the employee(s) and the organization. Widespread are the cases where no or, to take the opposite case, too many employees see themselves simultaneously responsible for a particular issue. The result of this ambiguity is conflicted. Organizations quickly resort to making the individual employee(s) responsible. This might be justified in some cases, but in many others not. They are only the visible symptoms for the underlying incalculability and lack of transparency that the organization tries to mask through the construct “area of responsibility.”

    At this point, a fundamental tension between two extremes in which organizations find themselves becomes visible: Either organizations formalize every task and responsibility and, consequently, become buried under their own bureaucracy, or they judge any kind of formalization as futile and refuse to keep track of changes in the job profiles. The latter extreme, however, increases the lack of transparency even further: No one knows who is doing what.

  6. 6.

    This does not imply that in specific contexts, other tasks might also be necessary.

  7. 7.

    As a general model the VSM does not and cannot specify the tasks for each factual aspect and context (e.g., what specific audits are necessary for the finance department). This would exceed the nature of such models. The VSM only demands that, for example, there be an audit for each aspect of an organization, whatever this might be in the concrete case, such as for the finance, production, or procurement function. It is then the task of those designing the organizational structure to verify for each factual aspect (see Chap. 1) that all the necessary systemic tasks are defined, developed, and executed.

References

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Wolfgang Lassl .

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Lassl, W. (2020). The Organizational Chart and the VSM: How Does One Get from One to the Other?. In: The Viability of Organizations Vol. 3. Springer, Cham. https://doi.org/10.1007/978-3-030-25854-2_2

Download citation

Publish with us

Policies and ethics