pinkaku 組織病理学研究所

現場から生まれた「社腸」という組織論で、会社の詰まりを言語化する

タグ: system behavior

  • Case 48: When Systems Cannot Distinguish Between Appearance and Function

    Case 48: When Systems Cannot Distinguish Between Appearance and Function

    Concept Inversion

    Well-structured appearance is assumed to indicate proper function.

    It does not.

    Appearance can be optimized independently of actual functionality.


    Structural Decomposition

    Systems produce observable structures.

    Processes are documented.
    Workflows are defined.
    Roles are assigned.
    Outputs are formatted.

    These create the appearance of order.

    However, functionality depends on execution.

    Decisions must occur.
    Information must flow.
    Responsibility must be exercised.

    When appearance is prioritized, structure becomes performative.

    Forms exist.
    Functions degrade.

    The system cannot distinguish between looking organized and operating effectively.


    Pathology Progression

    Structure is introduced.

    Documentation increases.

    Processes are formalized.

    Appearance improves.

    Function begins to lag.

    Issues emerge.

    More structure is added.

    Appearance improves further.

    Function declines further.

    The system becomes structurally visible but operationally ineffective.


    Cold Diagnosis

    An organization that evaluates itself based on structural appearance rather than functional outcomes cannot detect its own failure.

    It confuses representation with execution.


    Structural Definition

    This case defines a condition where systems maintain structural appearance while functional performance deteriorates.

    One-Line Summary

    This case describes how systems become operationally ineffective when appearance is mistaken for function.


    Explore the full case index

    This article is part of the Organizational Pathology case archive.
    All published cases can be found here:

    Organizational Pathology — Case Index

  • Case 47: When Signals Replace Reality

    Case 47: When Signals Replace Reality

    Concept Inversion

    Metrics are assumed to represent reality.

    They do not.

    Signals are abstractions, not the underlying condition.


    Structural Decomposition

    Systems generate signals to represent performance.

    Metrics quantify activity.
    Dashboards visualize status.
    Reports summarize outcomes.

    These signals are used for decision-making.

    Over time, reliance increases.

    Signals become the primary reference.

    Direct observation decreases.
    Context is ignored.
    Nuance is lost.

    The system begins to treat signals as reality itself.

    Representation replaces condition.


    Pathology Progression

    Signals are introduced.

    They simplify complexity.

    Dependence grows.

    Decisions are based solely on metrics.

    Reality begins to diverge.

    Signals remain stable.

    Confidence increases.

    Failures emerge unexpectedly.

    The system cannot explain the discrepancy.


    Cold Diagnosis

    An organization that substitutes signals for reality loses situational awareness.

    It operates on representations rather than actual conditions.


    Structural Definition

    This case defines a condition where performance signals replace direct understanding of reality.

    One-Line Summary

    This case describes how systems lose alignment with reality when signals are treated as reality itself.


    Explore the full case index

    This article is part of the Organizational Pathology case archive.
    All published cases can be found here:

    Organizational Pathology — Case Index