Align organizational systems (goals, metrics, incentives,
Align organizational systems (goals, metrics, incentives, daily tasks) with intended schemas to propagate those schemas effectively, because experience-based schema formation dominates message-based transmission.
Why This Is a Principle
Derives from Different functions develop different schemas as adaptive (schemas are adaptive responses to environments), Every system is perfectly designed to get the results it (systems are designed to get results they get), and Habits as Context-Response Associations (habits form from repeated behavior producing rewards). This is a principle about HOW to propagate schemas—through system alignment rather than communication alone. Actionable and applies broadly across organizational contexts.
Source Lessons
Schema alignment across hierarchical levels
Leaders and front-line workers often hold different schemas about the same reality — different mental models of what the organization does, why it does it, and what matters most. This vertical misalignment is not a communication failure. It is a structural consequence of the different information environments that each level inhabits. Executives see the strategic landscape. Front-line workers see the operational reality. Neither view is complete, and the gap between them determines how effectively strategy translates into execution.
Schema design as leadership work
One of the most important jobs of leadership is designing and updating organizational schemas — the shared mental models through which the organization perceives, interprets, and acts. Leaders who focus only on decisions and actions are managing the organization's output. Leaders who design schemas are managing the organization's cognitive infrastructure — the system that produces decisions and actions at every level, in every situation, whether the leader is present or not.
Culture is not aspirational posters
Culture is what people actually do when no one is watching, not what the posters on the wall proclaim. Every organization has two cultures: the espoused culture (the values statement, the mission poster, the CEO's keynote) and the enacted culture (the actual patterns of behavior that shape daily work). When these two cultures diverge, people learn to trust the enacted culture and discount the espoused one — producing cynicism, disengagement, and a collective understanding that the organization's stated values are performance rather than commitment.
Culture is built by repeated behavior
Culture is not declared — it is deposited, one behavior at a time. Every repeated action adds a layer to the cultural sediment: what gets rewarded, what gets tolerated, what gets punished, and what gets ignored. Over time, these accumulated layers become the bedrock assumptions that shape how everyone in the organization thinks and acts. Changing culture requires changing the behaviors that deposit it — not once, but consistently, until the new behavior becomes the new sediment.