How do I apply the idea that artifacts reflect culture?

The most direct way to practice is through a focused exercise: Walk through your workspace — physical or digital — and inventory the artifacts. For physical spaces: What does the office layout communicate about what the organization values? What do the meeting rooms look like — are they designed for presentation (projectors, podiums) or for collaboration (whiteboards, round tables)? What is on the walls — corporate messaging, employee work, nothing? For digital spaces: What does the Slack channel structure communicate? What does the documentation system look like — organized and maintained, or chaotic and abandoned? What tools does the team use, and what do the tool choices communicate about values? For each artifact, name the cultural schema it encodes. Then identify one artifact that encodes a schema you want to change. Can you modify the artifact to encode the desired schema instead?

Common pitfall: Treating artifacts as purely functional objects rather than as cultural encoders. When organizations redesign office spaces, choose collaboration tools, or restructure documentation systems, they typically evaluate options on functional criteria — cost, efficiency, features. They rarely ask: what cultural schema does this artifact encode? A tool that tracks individual productivity encodes individual competition. A tool that tracks team outcomes encodes collective accountability. Both are functional. Neither is culturally neutral. The failure mode is making artifact decisions without recognizing their cultural implications — and then being surprised when the artifacts shape behavior in unintended ways.

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