How do I apply the idea that onboarding transmits culture?

The most direct way to practice is through a focused exercise: Audit your team's onboarding process by mapping what a new member actually experiences in their first two weeks. List every interaction, meeting, task, and resource they encounter, hour by hour. Then classify each experience: (T) Technical onboarding — learning tools, systems, and processes. (C) Cultural onboarding — learning how the organization actually works, what behaviors are expected, how decisions are made. (S) Social onboarding — building relationships, understanding the social network, finding allies and mentors. Count the hours in each category. Most onboarding processes are heavily skewed toward T, with minimal C and S. Identify one cultural onboarding experience you could add in the first week — something that would explicitly teach new members an important aspect of the enacted culture that they would otherwise have to discover through trial and error.

Common pitfall: Confusing orientation with onboarding. Orientation is an event — a day or week of introductions, paperwork, and presentations. Onboarding is a process — a sustained, multi-month integration that shapes the new member's cultural schema through repeated exposure to the enacted culture. Organizations that treat orientation as onboarding communicate a cultural message in itself: 'We believe that a brief introduction is sufficient for you to figure out how things work here.' This message is received accurately — and the new member proceeds to learn the culture informally, acquiring whatever schemas the informal channels happen to transmit, which may or may not align with the organization's intended culture.

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