DEV Community

Hive80-lab
Hive80-lab

Posted on Originally published at hive80-lab.github.io

The Decision Log: One Line per Decision (and the Revisit Date Everyone Skips)

#productivity #smallbusiness #operations #management

Small teams don't make too few decisions. They make the same decisions three times, because nobody remembers the first two. The backup-vendor debate, the "we'll revisit in Q3" answer, the tool rejected in March for the missing SSO — six months later, every one of those debates starts from zero because the decision and its reasoning lived in a chat thread everyone scrolled past.

A decision log fixes this with one line per decision. Not a wiki. Not a governance process. One line, five fields:

  1. Date — the day it was decided, not the day someone wrote it down.
  2. Decision — past tense: "We switched backups to X." If you can't phrase it as something that happened, it isn't logged yet.
  3. Owner — the person who made the call per your delegation-of-authority matrix, not whoever argued longest.
  4. Why — the decisive reason, one clause. "Vendor B costs 40% less per seat" beats "we compared options."
  5. Revisit — a date or a trigger. This is the field everyone skips, and the one that does the real work.

Why the revisit date is the whole game

"We decided to defer X" without a revisit date is a polite no — the topic resurfaces later as a fresh debate. "We deferred X, revisit 2027-03-01" is a scheduled decision: the debate is pre-paid, and whoever picks it up starts from the recorded reason instead of zero.

And when the revisit date arrives and the answer is still "keep as is"? Log a new line saying so. "Revisited VLAN decision 2026-10-15: still flat, scan-to-email still load-bearing, next look Q2" is a ten-second entry that prevents the eleventh re-debate. Decisions that survive their own review become decisions you stop paying attention to — which is the point.

What gets logged (and what doesn't)

Five triggers always earn a line:

  • Spend above your threshold — whatever your delegation matrix says ($200, $500)
  • Policy changes — password rules, maintenance windows, on-call rotation changes
  • Tool decisions — adopt, reject, or defer. The rejects are the most valuable entries; they kill repeat proposals
  • Every deferral — with a revisit date, or it doesn't count as decided
  • Accepted risks — "we know the printer VLAN is flat and accept it" is exactly what a postmortem needs to find later

Everything else stays in the task tracker. The test: would someone plausibly re-ask this in six months?

Where it plugs in

  • Weekly review (2 min): answer every revisit date that fell due this week
  • Postmortems: "what did we know and decide before this?" becomes a lookup, not an argument
  • Budget reforecast: the log's tool decisions and spend lines are the change history
  • Onboarding: a new hire reads the log in twenty minutes and skips re-opening every old fight

The two failure modes

The museum — entries take ten minutes, the log dies by November. Fix: five fields, one sentence each; link out for detail.

The diary — "discussed backups, good meeting." Fix: reject entries that can't be phrased in the past tense with an owner.

Full template with worked examples and a paste-in CSV starter on the site — link below. Five rows is a working log; the habit matters more than the tool.

Get the Full Ops Auditing Package

Turn your ops auditing from an annual fire drill into a daily habit with the complete **

Field-tested ops kits (instant download - Hive80 Lab)

Top comments (0)