What does it mean that 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.

Example: Satya Nadella's transformation of Microsoft is a case study in schema design as leadership work. When Nadella became CEO in 2014, Microsoft's operating schemas were well-established: 'We are a Windows company' (identity schema), 'We win by controlling the platform' (strategy schema), 'Internal competition drives performance' (values schema), 'We know better than our customers' (customer schema). Nadella did not begin by changing Microsoft's products, org chart, or strategy document. He began by changing its schemas. He replaced 'We are a Windows company' with 'We are a cloud and AI company.' He replaced 'We win by controlling the platform' with 'We win by empowering others.' He replaced 'Internal competition drives performance' with 'Growth mindset drives performance.' He replaced 'We know better than our customers' with 'We learn from our customers.' Each of these was a schema change — a revision of the shared mental model through which Microsoft's 120,000 employees interpreted situations and made decisions. The schema changes preceded and enabled the operational changes: Azure's rise, Office 365's transformation, LinkedIn's acquisition, GitHub's acquisition. The operational changes would have been impossible under the old schemas — an organization that identified as a Windows company would not invest aggressively in cloud infrastructure that competed with its own platform. Nadella's leadership was schema design: he identified the outdated schemas, designed their replacements, and invested years in propagating the new schemas through the organization's systems, incentives, and culture.

Try this: List three decisions you have made as a leader in the past month. For each decision, ask: Was this decision about what to do in a specific situation, or was it about how the team should think about a category of situations? Decisions about what to do are operational decisions — they solve the immediate problem but do not change the system that produces problems. Decisions about how to think are schema decisions — they change the mental model that the team uses to approach all similar situations. For each operational decision you identified, ask: What schema decision could I make that would prevent the need for this operational decision in the future? What shared mental model, if established, would enable the team to make this decision correctly without my involvement?