Cross-reference domains in weekly review: do priorities match time? Do goals match commitments?
During weekly reviews, cross-reference externalized domains to detect contradictions—compare stated priorities against time allocation, goals against commitments, assumptions against failure analyses—because isolated review of each domain misses the conflicts that degrade decision quality.
Why This Is a Rule
Reviewing domains in isolation — checking priorities, then checking time allocation, then checking goals — produces a false sense of alignment because each domain looks coherent on its own. The contradictions live between domains: your stated priorities say "deep work is most important" while your time allocation shows 60% in meetings. Your goals say "ship the feature" while your commitments have you on three other projects. Each domain passes its own review; the cross-reference reveals the conflicts.
These cross-domain contradictions are the primary source of the feeling that "I'm working hard but not making progress." You're executing efficiently within each domain while the domains themselves are misaligned — the system is coherent locally but contradictory globally.
Three specific cross-references catch the most common contradictions: Priorities vs. time allocation (are you spending time on what you say matters?), Goals vs. commitments (have you committed to enough capacity for your goals?), and Assumptions vs. failure analyses (do your failures disprove assumptions you're still operating on?).
When This Fires
- During weekly reviews after checking individual domains
- When effort feels high but progress feels low
- After making new commitments that might conflict with existing priorities
- Any review session where cross-domain alignment is uncertain
Common Failure Mode
Reviewing each domain sequentially without comparison: "Priorities look good. Time allocation looks reasonable. Goals are on track." Each assessment is done in isolation, so the contradiction between them (priorities and time allocation don't match) is invisible. The cross-reference must be explicit: put the two domains side by side and check for alignment.
The Protocol
During weekly review, after individual domain checks: (1) Priorities vs. time: put your stated priorities next to your actual time allocation. Do they match? If your #1 priority got 10% of your time, there's a contradiction. (2) Goals vs. commitments: put your goals next to your active commitments. Is there enough capacity committed to each goal? If not, something must be cut or deferred. (3) Assumptions vs. failures: check whether any failures this week disproved assumptions you're still operating on. If an assumption failed, update it. These three cross-references take 5 minutes and catch contradictions that isolated reviews miss entirely.