MIGO-B

M-IGO-B

Learn people. Lead behaviour. Manage better.

For PDF, choose “Save as PDF” in the print dialog.

Unit I — Foundations of OB / Chapter 05

Organizational Culture

M-IGO-B · 2026 Teaching Edition

Learning outcomes

  1. Explain organizational culture and distinguish the chapter's central concepts.
  2. Use Artifacts, Espoused values, Basic assumptions to frame a workplace diagnosis.
  3. Interpret the reported indicators while distinguishing observation, inference and missing evidence.
  4. Compare the case alternatives and justify a decision using theory, trade-offs and an evaluation plan.

Understanding the concept

Culture is learned through repeated experience. Employees notice not only a company's declared values but also what earns promotion, whose objections are heard and what happens after an error. Visible symbols matter because they point toward these deeper patterns, not because a slogan can independently create commitment.

Schein's model describes organizational culture as three layers: visible artifacts (dress, rituals, office layout), espoused values (stated principles), and underlying basic assumptions (taken-for-granted beliefs driving behaviour). Culture strength reflects how widely and deeply shared these are, and person-organization (P-O) fit captures how well an individual's values align with the culture, predicting satisfaction and retention, especially critical during mergers and acquisitions.

Artifacts are observable arrangements and practices. Espoused values are the principles an organization says it supports. Underlying assumptions are the taken-for-granted beliefs that make a practice seem normal. A strong culture may aid coordination, yet it may also suppress disagreement or resist necessary change. Person–organization fit should not be confused with hiring only people who resemble existing employees. Shared ethical commitments can coexist with different backgrounds, work styles and constructive dissent.

  1. 1Concept: explain the mechanism
  2. 2Construct: define what matters
  3. 3Evidence: examine the signals
  4. 4Decision: weigh and justify
  5. 5Review: learn from consequences
Figure 5.1 — The M-IGO-B diagnostic learning cycle. A conceptual guide, not a validated scoring instrument.

Core components and theoretical lenses

Use the following distinctions to unpack the chapter's central idea. Each identifies a different aspect of the problem; their relationships matter as much as the labels themselves.

  1. 01

    Artifacts: visible symbols, rituals, dress codes, physical layout

  2. 02

    Espoused values: officially stated principles and mission statements

  3. 03

    Basic assumptions: unconscious, taken-for-granted beliefs

  4. 04

    Culture strength: degree of consensus and intensity of shared values

  5. 05

    Person-organization fit: alignment between individual and organizational values

Conceptual constructs

A construct names an idea used to interpret behaviour. It is not directly interchangeable with a survey score or a single incident. In this chapter, the constructs below organize the diagnosis; examine how they could explain the observations before deciding what to change.

  • Artifacts
  • Espoused values
  • Basic assumptions
  • Culture strength
  • Person-organization fit

Observable and measurable indicators

Indicators connect an abstract explanation to something that can be observed. Check the operational definition, reporting period and comparison group. A survey average can conceal differences between teams, and an administrative record can reflect willingness to report as well as underlying behaviour.

  • Culture survey consensus score — standard deviation of values ratings across employees, lower means stronger culture
  • Voluntary attrition post-merger — resignations in first 12 months post-deal, by legacy company
  • Ritual participation rate — attendance at town halls/culture events, quarterly
  • P-O fit score — survey measuring value alignment, at onboarding and 6 months
  • Cross-legacy collaboration index — proportion of cross-team projects mixing both legacy companies' staff

Storytelling / hypothetical teaching case

A workplace decision

Global engineering firm Meridian Systems acquired Pragati Precision, a 600-employee Indian precision-tooling company known for its hierarchical, engineering-excellence-first culture with rigid quality rituals and formal titles. Meridian's own culture, espoused in its mission statement as 'move fast, empower everyone,' relies on flat structures, casual dress, and rapid prototyping with tolerance for early-stage errors. Six months after the acquisition, Pragati's engineers report discomfort with Meridian's informal decision-making, feeling that corners are being cut on quality documentation, while Meridian's project managers find Pragati's approval chains frustratingly slow. Voluntary attrition among senior Pragati engineers has hit 18% in six months, well above Meridian's historical 7%. The integration lead, Ananya Sen, must decide how to manage the cultural clash before the joint product roadmap launch in four months.

The organization, characters and reported figures are supplied teaching material, not a verified corporate case report.

Reading the case evidence

Separate what the case reports from what you infer. A figure can establish the scale of a problem without establishing its cause. Note what information is absent and how that gap affects your confidence in a recommendation.

Table 5.1 — Evidence supplied in the existing learning module
SignalReported teaching-case evidence
Pragati engineer voluntary attrition (6 months post-merger)18%
Meridian historical attrition7% annually
Culture survey: 'decisions feel documented and controlled'Pragati 4.3/5 vs Meridian 2.1/5
Culture survey: 'I can move fast without excessive approval'Meridian 4.5/5 vs Pragati 1.8/5
Cross-legacy project collaboration9% of active projects
Joint roadmap launch deadline4 months

Decision alternatives and trade-offs

Alternatives represent different priorities and assumptions. The advantages and limitations below are the existing module's analytical prompts. Compare them against the same evidence rather than choosing first and finding a theory afterward.

AImpose Meridian's culture uniformly

Standardize all processes, rituals, and decision-making norms on Meridian's flat, fast-moving model across the combined entity.

Potential advantages

  • Simplifies integration and branding
  • Matches acquirer's stated strategic identity

Limitations and risks

  • Likely to accelerate Pragati engineer attrition given the stark P-O fit mismatch
  • Risks losing valued quality-documentation rigor important for precision tooling

BPreserve Pragati's culture as a protected unit

Keep Pragati operating largely autonomously with its own approval chains and rituals, integrating only at the product-roadmap level.

Potential advantages

  • Reduces immediate attrition risk among Pragati engineers
  • Preserves quality rigor critical to precision tooling

Limitations and risks

  • Undermines the strategic rationale for a unified, fast-moving combined culture
  • Perpetuates 'us vs them' divide, limiting collaboration

CDeliberate hybrid culture-building with negotiated norms

Convene joint workshops to identify which artifacts and assumptions from each side should be retained, blended, or replaced, creating an explicitly negotiated hybrid culture with a shared new set of rituals.

Potential advantages

  • Directly addresses the P-O fit gap through co-created values
  • Can preserve Pragati's quality rigor while adopting selective speed practices

Limitations and risks

  • Takes longer than a top-down mandate, risking the 4-month roadmap deadline
  • Requires strong facilitation to avoid decisions defaulting to the louder/acquirer voice

Evidence-based discussion

In an acquisition, map the routines that each workforce regards as legitimate before announcing one shared culture. A conflict over reporting or customer service may reflect different assumptions about accountability. Ask which practices protect important outcomes, which are merely familiar and which can be jointly redesigned. Evidence of integration should include cooperation and voice across the former boundary, rather than attendance at a launch event alone.

Theory-linked interpretation from the module

Schein's model suggests deep cultural change requires addressing basic assumptions, not just artifacts, so a purely top-down mandate to 'move fast' is unlikely to shift Pragati engineers' underlying beliefs about quality and risk. Person-organization fit theory predicts that the current mismatch (documented control versus fast autonomy) explains the attrition spike, and a defensible answer should propose a way to raise P-O fit for both groups without erasing the quality-first assumptions that make Pragati's tooling valuable, ideally via negotiated hybrid practices tested against the roadmap timeline.

Your managerial judgement

Should Ananya impose Meridian's culture, preserve Pragati's culture separately, or build a deliberate hybrid, given the four-month roadmap deadline and rising attrition?

Write a recommendation that identifies a preferred alternative, uses the reported evidence, acknowledges uncertainty and specifies a review point. Another choice can be defensible when its assumptions and trade-offs are made explicit.

Possible consequences

The module offers the following projections for discussion. They depend on implementation and context; they are not guaranteed effects or verified forecasts.

  • Short-term: a hybrid workshop approach may slow early integration decisions, testing the four-month deadline
  • Short-term: imposing Meridian's culture unilaterally risks losing more senior Pragati engineers before the roadmap launch
  • Long-term: a negotiated hybrid culture, if well-facilitated, tends to improve long-term retention and cross-legacy collaboration
  • Long-term: preserving cultures in silos indefinitely undermines the strategic value of the acquisition
  • Risk: whichever path is chosen, culture surveys should be re-run to track whether the P-O fit gap is closing

Reflection questions

  1. Which of Schein's three culture layers is easiest to change quickly, and which is hardest?
  2. How would you measure whether a 'hybrid culture' initiative is succeeding rather than just delaying conflict?
  3. What early signals would tell Ananya the merger integration is failing culturally?
  4. How does person-organization fit differ between individual hiring decisions and post-merger integration?

Practice: Know → Analyse → Decide

These are the original module questions. Reading or printing this textbook does not change quiz scores, completion or certificate eligibility.

Know Question 5.1

In Schein's model of organizational culture, which layer is hardest to observe and change?

  1. Artifacts
  2. Espoused values
  3. Basic assumptions
  4. Dress code
Answer and explanation

C. Basic assumptions are unconscious, taken-for-granted beliefs and are the deepest, hardest-to-change layer of culture.

Analyse Question 5.2

What does the 18% Pragati attrition rate versus Meridian's historical 7% most likely reflect?

  1. Random turnover unrelated to the merger
  2. A significant person-organization fit gap following the cultural clash
  3. Pragati engineers being generally less committed employees
  4. Meridian's culture is objectively superior
Answer and explanation

B. The attrition spike aligns closely with survey evidence of a stark values mismatch, indicating a P-O fit problem triggered by the merger.

Decide Question 5.3

Given the four-month roadmap deadline and rising attrition, which approach best balances integration goals and retention risk?

  1. Impose Meridian's culture uniformly overnight
  2. Leave Pragati fully separate indefinitely with no integration
  3. Run deliberate hybrid culture-building workshops now, with an accelerated timeline tied to the roadmap deadline
  4. Wait until after the roadmap launch to address culture at all
Answer and explanation

C. A deliberate, accelerated hybrid approach addresses the root P-O fit issue while respecting the business timeline, unlike unilateral imposition or indefinite delay.

Continue with interactive learning