How do I apply the idea that organizational schemas are often implicit?

The most direct way to practice is through a focused exercise: Identify one implicit schema in your organization by looking for a behavior that 'everyone just does' without being able to articulate why. Common examples: Who gets invited to which meetings? What information is shared broadly versus held tightly? Which types of initiatives get funded without rigorous justification, and which require extensive business cases? Pick one pattern and interview three people at different levels about it. Ask each: 'Why do we do it this way?' If the answers are vague ('It is just how things work'), inconsistent ('I assumed it was a policy' versus 'I think the CEO prefers it'), or circular ('Because that is what everyone does'), you have found an implicit schema. Write it down as an explicit assumption: 'We assume that X.' The act of writing makes the implicit explicit — and once explicit, it can be examined.

Common pitfall: Assuming that implicit schemas are necessarily wrong or harmful. Many implicit schemas are adaptive — they encode accumulated organizational wisdom about what works. The problem is not that schemas are implicit but that implicit schemas cannot be examined, updated, or deliberately maintained. An implicit schema that was adaptive five years ago may be maladaptive today, but because it operates below conscious awareness, it never gets re-evaluated. The goal is not to eliminate implicit schemas (which is impossible — some level of shared tacit knowledge is essential for coordination) but to make the most consequential ones explicit enough to be examined and revised when the context that produced them changes.

This practice connects to Phase 82 (Organizational Schemas) — building it as a repeatable habit compounds over time.