Inventory what you actually do — not what you should do — before redesigning your operating schemas
Before attempting to design better schemas, inventory your current operating schemas by writing what you actually do (not what you should do) across professional, relational, and self-concept domains.
Why This Is a Rule
You can't redesign what you haven't inventoried. Most people's operating schemas — the actual rules they follow in professional, relational, and self-concept domains — are invisible to them because they've never been externalized. They operate from schemas like "I should always be available for my team" or "asking for help means I'm not capable" without having articulated these schemas or chosen them deliberately.
The inventory must capture what you actually do, not what you should do or want to do. The aspirational version ("I balance work and rest") and the actual version ("I work until I collapse, then take forced recovery") are usually different — and only the actual version drives behavior. Designing better schemas requires knowing the starting point, which is the actual operating schema, not the aspirational one.
Three domains provide coverage: professional (how you work, lead, collaborate, handle conflict), relational (how you communicate, set boundaries, give/receive), and self-concept (what you believe about your own abilities, limitations, and worth). Each domain has its own operating schemas, often contradicting each other.
When This Fires
- Before any deliberate attempt to change how you think or operate
- During major self-reflection or personal development planning
- When you sense a gap between your intentions and your behavior
- At the start of any schema inspection or mental model redesign process
Common Failure Mode
Writing the aspirational inventory instead of the actual one: "I prioritize deep work and protect my time." Check the calendar — is that what you actually do? The actual inventory requires honesty that feels uncomfortable: "I say yes to every meeting request and rarely protect deep work time." The discomfort is diagnostic — it reveals the gap between the schema you want to have and the schema you actually run.
The Protocol
Before schema redesign: (1) Write your actual operating schemas across three domains. Use the format: "In [domain], I actually [behavior], especially when [trigger]." (2) Professional: how do you actually handle deadlines, conflict, requests, ambiguity? (3) Relational: how do you actually communicate needs, set boundaries, respond to criticism? (4) Self-concept: what do you actually believe about your abilities, your limits, your worth? (5) Read the inventory. The gap between actual and aspirational schemas is your redesign target. You can only change what you've acknowledged.