---
title: The Prioritization Problem Doesn't Respect Domains
synced_from_vault: true
vault_source: 03-living-docs/patterns/Prioritization-Problem-Doesnt-Respect-Domains.md
public: true
type: pattern
tags:
  - pattern
  - prioritization
  - personal
  - leadership
aliases:
  - Resource Allocation Is Universal
---

## Core Observation

The dynamics that make matrix orgs hard — competing stakeholders, finite resources, no clear hierarchy, everyone thinks their thing is most important, guilt about saying no — show up identically in personal life. A weekend with a brother-in-law who needs a friend, parents visiting, and a Final Four game is structurally identical to a product org where ROI, targeting, and digital banking all want the same engineer's time.

## Why It Matters

The tools that work at work also work at home, and vice versa:

- **Explicit prioritization** — name what's ON and what's parked (the Focus System pattern)
- **Make tradeoffs visible** — the prioritization meeting at work; the "here's what we're doing this weekend" conversation at home
- **Shield from context-switching** — protecting engineers from meeting overload = protecting your Saturday from overcommitment
- **The regret heuristic** — "what's the one thing I'd regret not doing?" cuts through both domains equally
- **Saying no is an act of respect** — parking something isn't abandoning it. It's being honest about capacity.

## Origin

Noticed on 2026-04-03 while juggling family obligations, a friend needing time, and a major sports event in the same weekend window: "It's the exact same thing as a matrix org."

---

## Cross-References