How do I apply the idea that sub-cultures within organizations?

The most direct way to practice is through a focused exercise: Map the sub-cultures in your organization. Start by identifying the groups: functions (engineering, marketing, sales, support), geographies (if applicable), hierarchical levels (leadership team, middle management, individual contributors), and tenure cohorts (founding team, early hires, recent hires). For each group, answer: (1) What does this group value most? (2) What behaviors are normal within this group that would be unusual in other groups? (3) What assumptions does this group hold about how work should be done? Then assess alignment: where are the sub-cultures aligned with each other and with the organizational primary culture? Where are they misaligned? For each misalignment, determine: is this a productive differentiation (the sub-culture is adapted to its specific context) or a harmful divergence (the sub-culture is pulling the organization in a conflicting direction)?

Common pitfall: Attempting to eliminate sub-cultures in the name of cultural unity. Sub-cultures are not symptoms of cultural failure — they are adaptations to the different demands of different roles. Engineering needs a sub-culture that values precision and rigor because engineering mistakes can break production systems. Sales needs a sub-culture that values speed and relationship-building because the sales context requires rapid response and personal connection. Forcing both groups into the same cultural norms would undermine both: engineers forced into sales-speed mode produce unreliable systems, and salespeople forced into engineering-rigor mode lose competitive deals. The failure mode is confusing cultural alignment (shared core values) with cultural uniformity (identical behavioral norms).

This practice connects to Phase 83 (Culture as Infrastructure) — building it as a repeatable habit compounds over time.