Decision Calendar¶
Artifact — instantiates Decision Load Management
An artifact that places recurring decisions onto an intentional cadence.
A Decision Calendar is a standing schedule that assigns each recurring decision a time — not just when it will be made, but when in the rhythm of available attention it will be made. Its defining move is temporal placement matched to decision energy: high-stakes, judgment-heavy decisions are booked into protected high-attention windows, while routine ones are parked in low-energy slots or fixed light-touch reviews. Where other load mechanisms decide whether a decision needs fresh judgment or who makes it, the calendar decides when — turning a formless stream of "we should decide that sometime" into a cadence where each decision has a slot proportionate to its weight and each demanding call lands when the decider is actually sharp. It is an artifact, a schedule you can look at, not a workflow that reacts to a queue.
Example¶
A city planning department made its big calls whenever they bubbled up — a contentious rezoning debated at the tail end of a four-hour Friday meeting when everyone was spent, a routine permit-fee update eating a prime Monday-morning slot that could have hosted real deliberation. The director builds a Decision Calendar for the year. She sorts the department's recurring decisions by stakes: the annual capital-priorities call, major rezonings, and the budget are high-stakes; fee re-indexing, routine variance approvals, and vendor renewals are low. Then she places them by energy. The heavy decisions get first-hour slots on protected mornings, one per session, with no competing agenda items. The routine ones are clustered into a standing quarterly "administrative review" in an afternoon slot where deep focus is not required.
The artifact is a shared annual grid, visible to the whole department. Its effect is not to reduce the number of decisions but to stop the mismatch — no more landmark rezoning decided on fumes, no more prime attention spent on fee arithmetic. This is time-blocking[n1] applied to an organization's judgment rather than an individual's tasks.
How it works¶
Building the calendar is two joined moves. First, sort recurring decisions by stakes so that consequence, not habit or squeaky-wheel urgency, determines priority for the scarce good slots. Second, map slots to an energy profile: identify which windows in the working rhythm carry high, fresh attention (often early, undistracted, uninterrupted) and which are naturally low-focus, then place each decision where its demand matches the slot's supply. High-stakes decisions get protected, single-item windows; low-stakes ones get clustered into light standing slots. The finished artifact makes the whole cadence visible so people can see when each decision recurs and defend the protected windows against encroachment. The calendar assigns times and protects windows; it does not itself group items for processing or route them by owner.
Tuning parameters¶
- Cadence granularity — whether decisions are placed daily, weekly, at milestones, or by season. Finer cadence keeps things current but fills the schedule; coarser cadence protects focus but can let a decision go stale before its slot.
- Energy-matching aggressiveness — how strictly high-stakes decisions are reserved for peak windows. Strict matching maximizes judgment quality but constrains scheduling flexibility.
- Protected-window count — how many high-attention slots are fenced off for consequential calls. More protection guards quality; too many starve routine work of time.
- Stakes cut for prime slots — where the line falls between "deserves a protected window" and "goes in the light standing slot." Set high and prime slots sit empty; set low and they crowd.
- Visibility and defensibility — how public the calendar is and how hard it is to bump a protected slot, trading responsiveness against the integrity of the reserved windows.
When it helps, and when it misleads¶
The calendar helps most when decisions recur predictably and the harm is timing-driven — important calls made when attention is depleted, or trivial ones consuming prime windows. Making the cadence an explicit, shared artifact lets an organization defend its best attention for its weightiest judgments.
Its failure mode is rigidity: a calendar is a forecast, and a decision that becomes urgent between slots either waits harmfully for its scheduled window or blows up the schedule. A calendar can also decay into theater — protected windows that everyone books over until the "high-attention slot" is as fragmented as everything else. And a purely time-of-day energy model is a heuristic, not a law; people's real peaks vary. The guarding discipline is to keep the cadence as a default rhythm rather than a cage, pair it with an out-of-band path for genuine urgency, and periodically check that protected windows are actually staying protected rather than being quietly colonized.
How it implements the components¶
decision_stakes_classification— the calendar sorts recurring decisions by consequence to decide which earn scarce protected windows and which go in light standing slots.decision_energy_budget— it treats high-attention time as a finite budget and allocates decisions to windows whose energy matches each decision's demand.
It does not preselect a safe option to skip deliberation (default_or_delegation_rule) — that is Default Option Design — and it does not group similar decisions to amortize setup cost (batching_rule), which is the Decision Batching Workflow.
Related¶
- Instantiates: Decision Load Management — the calendar realizes the "place recurring decisions on an intentional cadence" component.
- Sibling mechanisms: Decision Batching Workflow · Decision Triage Queue · Fatigue Check Protocol
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Decision Calendar operates as a non-executable information artifact that externalizes static or prospective structure because it an artifact that places recurring decisions onto an intentional cadence.
Independent corroboration: The frozen evidence defines Decision Calendar as 'An artifact that places recurring decisions onto an intentional cadence', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Executive and meeting management cohered standing decision cadences that assign recurring governance choices to protected calendar windows.
Related originating lineages:
- Psychology — Attention and decision-fatigue research supplied the matching of high-stakes judgment to higher-energy periods.
Review resolution: Executive and meeting management cohered standing decision cadences that assign recurring governance choices to protected calendar windows.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The archetype is explicit that a calendar alone is not the pattern — cadence without stakes classification, load treatment, and safeguards is just a schedule. This mechanism earns its place only because it carries the stakes-and-energy matching; strip that out and it degrades into a bare list of dates.
[n1] Time-blocking — the practice of assigning specific tasks to protected windows rather than working from an open to-do list, popularized in knowledge-work productivity writing. A decision calendar applies the same principle to an organization's recurring decisions, matching each to a window sized for its cognitive demand. ↩