What goes wrong when you ignore that organizational schemas are often implicit?

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.

The fix: 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.

The underlying principle is straightforward: The most powerful organizational schemas are the ones nobody talks about — the assumptions so deeply embedded in how the organization operates that they feel like facts rather than choices. These implicit schemas determine behavior more reliably than any explicit policy, precisely because they operate below the level of conscious examination.