pinkaku 組織病理学研究所

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

タグ: management systems

  • Case 30: When Collapse Is Recognized but Not Acted Upon

    Case 30: When Collapse Is Recognized but Not Acted Upon

    Structural Observation

    Collapse is visible.

    Signals are clear.
    Data is available.
    Awareness exists.


    Action does not follow.


    The organization recognizes failure.

    It discusses risk.
    It acknowledges decline.
    It anticipates consequence.


    It does not intervene.


    The system understands.

    It does not respond.


    Awareness Without Action

    In functional systems, recognition triggers response.

    It initiates correction.
    It drives change.
    It alters trajectory.


    In pathological systems, recognition becomes passive.

    It remains cognitive,
    not operational.


    Structural indicators include:

    • Clear awareness of critical issues without decisive action
    • Repeated acknowledgment of decline without intervention
    • Strategic discussions disconnected from execution
    • Acceptance of outcomes previously considered unacceptable



    The organization knows.

    It does not act.


    The Acceptance of Collapse

    Collapse becomes normalized.

    It is anticipated.
    It is explained.
    It is absorbed.


    Urgency disappears.

    Intervention becomes optional.


    The system stabilizes in decline.


    Individuals adapt.

    They reduce expectation.
    They accept limitation.
    They disengage from outcome.


    The organization continues—
    toward termination.


    Structural Conclusion

    Recognition without action
    cannot prevent collapse.


    When collapse is recognized but not acted upon,
    the organization retains awareness
    and loses survival.


    Structural Definition

    This case defines collapse being recognized but not acted upon as a state where awareness does not translate into structural intervention.

    One-Line Summary

    This case describes how recognition fails to produce action.


    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 29: When Organizations Lose the Ability to Stop

    Case 29: When Organizations Lose the Ability to Stop

    Structural Observation

    Activity continues.

    Projects proceed.
    Processes operate.
    Decisions accumulate.


    Stopping does not occur.


    Signals emerge.

    Warnings appear.
    Concerns are raised.
    Risks become visible.


    They do not interrupt action.


    The system detects issues.

    It does not halt.


    Motion Without Control

    In functional systems, stopping is part of control.

    It prevents escalation.
    It enables reassessment.
    It preserves capacity.


    In pathological systems, stopping becomes impossible.

    Momentum overrides judgment.


    Structural indicators include:

    • Ongoing initiatives despite clear failure signals
    • Inability to pause or terminate ineffective processes
    • Escalation of commitment without reassessment
    • Continuous activity detached from outcomes



    The organization moves.

    It does not regulate.


    The Fear of Interruption

    Stopping becomes threat.

    It exposes failure.
    It interrupts continuity.
    It requires accountability.


    Continuation becomes safety.

    It preserves appearance.
    It avoids confrontation.
    It delays consequence.


    The system prioritizes motion.

    It avoids interruption.


    Individuals adapt.

    They continue execution.
    They suppress concern.
    They avoid escalation.


    The organization accelerates.

    It loses control.


    Structural Conclusion

    A system that cannot stop
    cannot correct.


    When organizations lose the ability to stop,
    they retain activity
    and lose control.


    Structural Definition

    This case defines organizations losing the ability to stop as a state where continuation persists regardless of outcome or purpose.

    One-Line Summary

    This case describes how systems continue without justification.


    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 28: When Structure Becomes Self-Preserving

    Case 28: When Structure Becomes Self-Preserving

    Structural Observation

    The structure persists.

    It maintains form.
    It maintains process.
    It maintains hierarchy.


    It resists alteration.


    Decisions are evaluated
    based on their impact on the structure.

    Not on their impact on outcomes.


    Changes are filtered.

    They are assessed for compatibility.
    They are adjusted for acceptance.
    They are reduced for stability.


    The system protects itself.


    Function Reversed

    In functional systems, structure supports purpose.

    It enables action.
    It adapts to conditions.
    It serves outcomes.


    In pathological systems, the relationship reverses.

    Purpose adjusts to structure.


    Structural indicators include:

    • Changes rejected for disrupting existing systems
    • Processes maintained despite inefficiency
    • Decisions optimized for stability over effectiveness
    • Preservation of roles and hierarchy over results



    The organization maintains its structure.

    It modifies its purpose.


    The Priority of Survival

    Structure becomes central.

    It absorbs attention.
    It dictates behavior.
    It defines limits.


    Outcome becomes secondary.

    It is negotiated.
    Adjusted.
    Deferred.


    The system behaves as a closed entity.

    It prioritizes continuity.


    Individuals adapt.

    They align with structure.
    They avoid disruption.
    They reinforce preservation.


    The organization continues to operate.

    It ceases to evolve.


    Structural Conclusion

    A structure that exists to preserve itself
    ceases to serve its purpose.


    When structure becomes self-preserving,
    the organization retains existence
    and loses function.


    Structural Definition

    This case defines structure becoming self-preserving as a state where systems prioritize their own continuity over organizational purpose.

    One-Line Summary

    This case describes how structure protects itself instead of serving outcomes.


    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 27: When Adaptation Becomes Performance

    Case 27: When Adaptation Becomes Performance

    Structural Observation

    Adaptation is visible.

    Changes are announced.
    Initiatives are launched.
    Adjustments are reported.


    Conditions remain unchanged.


    The organization appears responsive.

    It signals movement.
    It demonstrates awareness.
    It communicates alignment.


    Underlying structures persist.


    The system performs adaptation.

    It does not execute it.


    Change Without Transformation

    In functional systems, adaptation alters structure.

    It modifies behavior.
    It updates processes.
    It shifts outcomes.


    In pathological systems, adaptation becomes representational.

    It exists in communication,
    not in operation.


    Structural indicators include:

    • Announced changes without measurable impact
    • Repeated initiatives addressing the same issues
    • Visible activity without structural modification
    • Communication emphasizing responsiveness over results



    The organization changes its narrative.

    It does not change its function.


    The Performance of Responsiveness

    Adaptation becomes display.

    It reassures stakeholders.
    It maintains legitimacy.
    It deflects scrutiny.


    Transformation becomes risk.

    It disrupts stability.
    It exposes failure.
    It requires commitment.


    The system prefers performance.

    It avoids change.


    Individuals adapt.

    They learn to signal alignment.
    They present participation.
    They avoid disruption.


    The organization continues to evolve—
    in appearance.


    Structural Conclusion

    Adaptation that does not alter structure
    is not adaptation.


    When adaptation becomes performance,
    the organization retains responsiveness
    and loses transformation.


    Structural Definition

    This case defines adaptation becoming performance as a state where visible change replaces meaningful structural adjustment.

    One-Line Summary

    This case describes how adaptation becomes superficial display.


    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 26: When Problems Are Redescribed Instead of Solved

    Case 26: When Problems Are Redescribed Instead of Solved

    Structural Observation

    Problems exist.

    They are identified.
    Documented.
    Discussed.

    They are not resolved.


    Instead, they are reframed.

    Reworded.
    Reclassified.
    Recontextualized.


    The issue remains.

    Its description changes.


    The system processes problems.

    It does not eliminate them.


    Resolution Without Resolution

    In functional systems, problems lead to intervention.

    They trigger action.
    They produce correction.
    They alter conditions.


    In pathological systems, problems lead to reinterpretation.

    They are adjusted linguistically,
    not structurally.


    Structural indicators include:

    • Issues redefined rather than addressed
    • Terminology shifts without operational change
    • Persistent problems described as “improving”or“manageable”
    • Language used to neutralize urgency


    The organization acknowledges problems.

    It does not confront them.


    The Substitution of Language for Action

    Language becomes adaptive.

    It absorbs tension.
    It reduces visibility.
    It preserves stability.


    Action becomes disruptive.

    It introduces risk.
    It exposes failure.
    It demands ownership.


    The system prefers language.

    It avoids intervention.


    Individuals adapt.

    They learn to describe effectively.
    They avoid solving directly.


    Problems persist.

    They become narratives.


    Structural Conclusion

    A problem that is only redescribed
    remains a problem.


    When problems are redescribed instead of solved,
    the organization retains awareness
    and loses capability.


    Structural Definition

    This case defines problems being redescribed instead of solved as a state where language changes replace structural resolution.

    One-Line Summary

    This case describes how reframing problems substitutes for solving them.


    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 25: When Authority Exists Without Ownership

    Case 25: When Authority Exists Without Ownership

    Structural Observation

    Authority exists.

    It is visible.
    Defined.
    Exercised.

    Ownership does not.


    Decisions are made.

    Directions are issued.
    Approvals are given.
    Instructions are enforced.


    Consequences are not held.


    When outcomes fail,
    authority is not questioned.

    Responsibility is redirected.


    The system contains authority.

    It does not contain ownership.


    Power Without Consequence

    In functional systems, authority carries ownership.

    It links decision to consequence.


    In pathological systems, authority detaches.

    Power is exercised

    without absorbing outcomes.


    Structural indicators include:

    • Individuals with decision power lacking accountability
    • Outcomes attributed downward despite upward authority
    • Decisions enforced without ownership of results
    • Escalations that reinforce authority rather than resolve failure



    The organization centralizes power.

    It distributes consequence.


    The Preservation of Position

    Authority becomes protective.

    It maintains status.
    It avoids exposure.
    It resists consequence.


    Ownership becomes risk.

    It is avoided.
    Redirected.
    Deferred.


    Individuals adapt.

    They seek authority without ownership.
    They avoid visibility of consequence.
    They comply without commitment.


    The system remains controlled.

    It ceases to be responsible.


    Structural Conclusion

    Authority without ownership
    cannot govern.


    When authority exists without ownership,
    the organization retains control
    and loses accountability.


    Structural Definition

    This case defines authority existing without ownership as a state where decision power is present but responsibility is absent.

    One-Line Summary

    This case describes how authority operates without accountability.


    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 24: When Feedback Becomes Noise

    Case 24: When Feedback Becomes Noise

    Structural Observation

    Feedback exists.

    It is collected.
    Requested.
    Encouraged.

    It is not processed.


    Voices are present.

    They are recorded.
    Reviewed.
    Acknowledged.

    They do not alter direction.


    Input accumulates.

    It does not converge.


    The system receives signals.

    It does not interpret them.


    Signal Without Effect

    In functional systems, feedback modifies behavior.

    It identifies deviation.
    It corrects trajectory.
    It enables learning.


    In pathological systems, feedback becomes residual.

    It is absorbed into process
    without producing change.


    Structural indicators include:

    • Feedback collected but not reflected in decisions
    • Repeated reporting of the same issues without resolution
    • Input acknowledged without structural response
    • Mechanisms for feedback that function without consequence



    The organization listens.

    It does not respond.


    The Collapse of Meaning

    As feedback loses effect,
    its meaning degrades.


    Signals become repetition.

    Repetition becomes noise.


    Individuals adapt.

    They reduce clarity.
    They reduce effort.
    They reduce input.


    Eventually,
    feedback persists as activity.

    It ceases as communication.


    Structural Conclusion

    Feedback that does not alter behavior
    cannot function as feedback.


    When feedback becomes noise,
    the organization retains communication
    and loses learning.


    Structural Definition

    This case defines feedback becoming noise as a state where signals are generated but not structurally integrated into decision-making.

    One-Line Summary

    This case describes how feedback loses meaning when it does not affect outcomes.


    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 23: When Expertise Becomes Irrelevant

    Case 23: When Expertise Becomes Irrelevant

    Structural Observation

    Expertise exists.

    It is present.
    Identifiable.
    Accessible.

    It is not utilized.


    Decisions are made
    without reference to those who understand the problem.

    Knowledge is available.
    It is not consulted.


    Individuals with expertise
    provide input.

    It is acknowledged.
    Then disregarded.


    The system recognizes expertise.

    It does not depend on it.


    Competence Without Influence

    In functional systems, expertise shapes decisions.

    It informs direction.
    It constrains error.
    It enables adaptation.


    In pathological systems, expertise becomes ornamental.

    It is included in process,
    not in outcome.


    Structural indicators include:

    • Experts present but excluded from decision authority
    • Technical input overridden by hierarchical preference
    • Repeated failure despite available knowledge
    • Decisions justified without reference to expertise


    The organization contains knowledge.

    It does not apply it.


    The Displacement of Capability

    Authority detaches from competence.

    Decisions align with position,
    not understanding.


    Expertise becomes advisory.

    Authority remains absolute.


    Over time, individuals adapt.

    Experts reduce engagement.
    Non-experts assume control.


    The system continues to operate.

    Its capacity declines.


    Structural Conclusion

    Expertise that does not influence outcomes
    ceases to function as expertise.


    When expertise becomes irrelevant,
    the organization retains knowledge
    and loses intelligence.


    Structural Definition

    This case defines expertise becoming irrelevant as a state where knowledge no longer influences outcomes due to structural disregard.

    One-Line Summary

    This case describes how expertise loses impact in misaligned systems.


    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 22: When Responsibility Dissolves into Process

    Case 22: When Responsibility Dissolves into Process

    Structural Observation

    Responsibility exists.

    It is assigned.
    Documented.
    Distributed.

    No one holds it.


    Tasks are completed.

    Processes are followed.
    Reports are submitted.
    Approvals are recorded.

    Outcomes remain unowned.


    When failure occurs,
    it is traced through steps,
    not held by individuals.


    Responsibility is present in structure.

    It is absent in practice.


    Accountability Without Ownership

    In functional systems, responsibility concentrates.

    It connects action to consequence.


    In pathological systems, responsibility disperses.

    It is segmented across roles,
    fragmented across processes,
    and diffused across layers.


    Structural indicators include:

    • Multiple stakeholders without clear ownership
    • Tasks completed without accountable outcomes
    • Failures explained through process, not decision
    • Escalation paths that redistribute rather than resolve


    The system manages responsibility.

    It does not contain it.


    The Distribution of Blame

    Responsibility becomes procedural.

    Each step is justified.
    Each role is fulfilled.
    Each action is compliant.


    No single point absorbs consequence.

    Blame circulates.


    The organization learns to explain failure
    without locating it.


    Individuals adapt.

    They learn that:

    • Following process protects them
    • Ownership creates risk
    • Visibility without authority is exposure


    Responsibility dissolves into process.


    Structural Conclusion

    Responsibility that cannot be located
    cannot function.


    When responsibility dissolves into process,
    the organization preserves activity
    and eliminates accountability.



    Structural Definition

    This case defines responsibility dissolving into process as a state where ownership is fragmented across procedures, eliminating accountability.

    One-Line Summary

    This case describes how responsibility disappears within procedural complexity.


    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 21: When Decision-Making Becomes Ritual

    Case 21: When Decision-Making Becomes Ritual

    Structural Observation

    Decisions continue.

    Meetings occur.
    Approvals are granted.
    Documents are produced.

    The process remains active.

    The outcomes do not.


    Decision-making persists as activity,
    not as intervention.

    Choices are framed, reviewed, and endorsed—
    but rarely executed in a way that alters conditions.


    Repetition increases.

    Decisions are revisited.
    Revalidated.
    Rearticulated.

    Not because reality has changed,
    but because resolution has not.


    The system maintains motion.

    It does not produce movement.


    Process Without Consequence

    In functional systems, decisions modify trajectories.

    In pathological systems, decisions preserve continuity.


    Action becomes optional.

    Completion of process becomes sufficient.


    Structural Signals:

    • Decisions that do not produce observable change
    • Recurrent discussion of previously “ resolved ” issues
    • Approval structures that validate without enforcing
    • Execution detached from decision authority


    The organization continues to decide.

    It does not converge.


    The Substitution of Form for Function

    Decision-making becomes representational.

    It signals governance.

    It does not enact it.


    Participation replaces accountability.

    Alignment replaces commitment.

    Documentation replaces outcome.


    The structure rewards compliance with process.

    It does not require consequence.


    Over time, individuals adapt.

    They learn that:

    • The act of deciding is sufficient
    • The result is secondary
    • Closure is procedural, not real


    Decision-making becomes ritual.


    Structural Conclusion

    A decision that does not alter behavior
    is not a decision.


    When decision-making becomes ritual,
    the organization retains form
    and loses agency.



    Structural Definition

    This case defines decision-making becoming ritual as a state where formal processes continue without influencing actual outcomes.

    One-Line Summary

    This case describes how decisions become procedural repetition without impact.


    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