Decision Clock¶
Metric or dashboard — instantiates Decision Commitment and Closure
Makes the closure deadline, elapsed deliberation time, delay cost, and pending prerequisites visible while the decision is still open.
The Decision Clock is a live display that keeps a still-open decision honest about time. It shows four things at once: the deadline by which closure must happen, how long deliberation has already run, the accruing cost of continuing to wait, and which prerequisites still block a clean close. Its defining move is that it faces only the open decision — it is a pressure instrument, not a memory. It never records what was chosen and never watches a decision after it has closed. By turning "we need more time" into a claim checkable against a countdown and a readiness list, it lets a group tell the difference between deliberation that is still buying information and deliberation that has quietly become avoidance.
Example¶
A newsroom is sitting on a corruption story. The reporting is strong but not airtight, a rival outlet is sniffing the same lead, and legal review is still open. The editor puts a Decision Clock on the wall of the situation room. It shows the publish window — the story loses most of its value if it doesn't run before the morning cycle, so the closure deadline is 5:00 a.m. It shows that the team has already deliberated for six hours. It shows a rising delay cost: each hour raises the odds the rival breaks it first. And it shows the two prerequisites still unmet — legal sign-off pending, and a second independent source not yet confirmed — against the standing evidence bar of "two independent sources before we publish."
Nothing on the clock makes the call. But it stops the team from mistaking a stalled conversation for careful work: the sufficiency bar is explicit, the two blockers are named, and the countdown makes the cost of dithering concrete rather than felt. By 3:00 a.m. the second source confirms, legal clears, and the clock's readiness line goes green with two hours to spare.
How it works¶
The clock aggregates three feeds into one view. A countdown runs to the closure deadline, sourced from whatever fixes it — an external event, an expiring option, or a chosen review date. A readiness panel lists the prerequisites for closure and their status, so a green board means "you may now close," not "you must." A sufficiency gauge shows the standing evidence bar and whether the current evidence meets it. Overlaid on all three is a delay-cost indicator that translates elapsed time into what waiting is costing. Crucially the clock displays state; it does not adjudicate it. The judgment of whether to close stays with people; the clock only removes the excuse of not knowing where things stand.
Tuning parameters¶
- Deadline source — whether the closure date is a hard external constraint or a chosen internal target. Hard deadlines create real pressure; self-set ones can be gamed, so mark which is which.
- Delay-cost model — how elapsed time is converted into cost. A steep curve pushes toward fast closure; a flat one tolerates deliberation. Overstating it manufactures false urgency.
- Readiness granularity — how finely prerequisites are itemized. Fine lists catch hidden blockers but can make closure feel perpetually one item away.
- Refresh cadence — how often the board updates. Real-time suits fast-moving calls; a daily refresh suits slow ones and avoids twitchy over-reaction.
- Escalation threshold — the point at which an approaching deadline forces the decision up to a named owner rather than letting it lapse.
When it helps, and when it misleads¶
Its strength is that it makes the cost of delay legible — the quantity a group feels but rarely names — so that analysis paralysis has to argue against a visible number rather than hide behind "let's be thorough."[n1] It also separates two things that get conflated: whether the evidence bar is met, and whether time is running out. Those are different questions, and the clock shows both.
Its failure mode is that a countdown can stampede a group into premature closure. The classic misuse is the manufactured deadline — an artificial closure date set precisely to force a predetermined answer before dissent or evidence can catch up, which the archetype flags as premature closure driven by urgency rather than basis. The guarding discipline is that the clock reports pressure but must never lower the sufficiency bar on its own, and non-waivable legal, consent, or safety prerequisites are marked as un-compressible: the countdown can run out against them, but it cannot dissolve them.
How it implements the components¶
closure_readiness_threshold— the readiness panel is exactly this threshold rendered as a live checklist: which prerequisites remain unmet before closure is permitted.evidence_sufficiency_rule— the sufficiency gauge displays the standing evidence bar and whether current evidence clears it.decision_expiry_or_review_date— the countdown to the closure deadline is the clock's centerpiece.
It does not watch a decision after it closes: reopening_trigger and rationale_and_assumption_record belong to Reopen Trigger Monitor, its post-closure twin. The clock faces the still-open decision; the monitor faces the closed one.
Related¶
- Instantiates: Decision Commitment and Closure — the clock supplies the time-and-readiness pressure that keeps deliberation from becoming avoidance.
- Sibling mechanisms: Reopen Trigger Monitor · Go/No-Go Commitment Gate · Option Comparison Matrix · Precommitment Challenge Session · Decision Record Log · Signed Commitment Authorization · Execution Handoff Checklist · Reversibility and Exit Check
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Decision Clock operates as an ongoing sensing arrangement that repeatedly observes actual state and surfaces changes or alerts because it makes the closure deadline, elapsed deliberation time, delay cost, and pending prerequisites visible while the decision is still open.
Independent corroboration: The frozen evidence defines Decision Clock as 'Makes the closure deadline, elapsed deliberation time, delay cost, and pending prerequisites visible while the decision is still open', so its operative form is Monitoring, Sensing & Alerting.
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: Product and project management cohered time-boxed decision tracking that makes deadline, elapsed deliberation, and unresolved prerequisites visible to accountable owners.
Related originating lineages:
- Economics & Finance — Cost-of-delay analysis supplied valuation of the loss accruing while commitment remains open.
- Operations Research — Scheduling and queueing analysis supplied elapsed-time, prerequisite, and accumulating-delay-cost measures.
Review resolution: Product and project management cohered time-boxed decision tracking that makes deadline, elapsed deliberation, and unresolved prerequisites visible to accountable owners.
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¶
[n1] Cost of Delay — Don Reinertsen's product-development concept for the economic loss incurred per unit time a decision or delivery is postponed. It is what makes delay a quantity you can weigh rather than a vibe you argue about. ↩