What does it mean that schema inventory?

List your most important schemas so you can maintain and improve them systematically.

Example: A senior product manager realizes she has been making resource allocation decisions using a 'best team wins' schema — the belief that talent density matters more than process. She has never named it, never tested it, and never noticed it conflicting with her other schema that 'systems beat heroics at scale.' Both have been silently governing decisions for years. Only when she writes them both down as explicit entries in an inventory does she see the contradiction — and recognize that the 'best team wins' schema has been winning by default in every hiring discussion, even when the decision is really about process design.

Try this: Set a 30-minute timer. List every schema you can identify that governs how you make decisions in your primary domain — career, relationships, health, money, or craft. For each one, write: (1) the schema as a single sentence, (2) where you acquired it, (3) when you last tested or updated it, and (4) your current confidence level (high/medium/low). Aim for at least 15 entries. When you finish, look at how many you rated high-confidence but have never actually tested. That gap between confidence and verification is the entire reason inventories matter.