Board Technology Oversight

A Simple Decision Log for Technology Discussions

A short decision log keeps technology choices findable after the meeting ends. Record what was decided, when it happened and where to revisit the choice.

Rows of dated brown bound volumes with gold lettering on wooden shelves

A meeting ends with agreement. Two weeks later, someone asks what was actually decided. The answer exists somewhere between memory, a chat thread and a set of notes that summarized the discussion without naming its outcome.

A decision log is a small habit that prevents this search. It is a running list of what was decided, when, and where the decision will be revisited. It does not need special software or ceremony.

Key takeaways

  • Write each decision in one plain sentence.

  • Date every entry.

  • Keep the log in one findable place.

  • Revisit entries at a natural checkpoint.

Step 1: Write the decision in one sentence

"We discussed the search example" describes a conversation. "The demonstration will use the branch-search example with fictional opening hours" records an outcome. The second sentence lets a reader act without reconstructing the meeting.

If a sentence cannot be written yet, the decision may not actually be finished. Recording "open" is more honest than recording a vague outcome.

Step 2: Borrow the idea, not the ceremony

Software teams use architecture decision records: short documents that each capture a single decision and its rationale. The ADR project describes a collection of these records as a project's decision log.

A technology discussion among colleagues does not need that full structure. The useful idea is smaller: one decision, one entry, kept where the group can find it again.

Step 3: An illustrative log entry

Decision: the walkthrough will keep the fictional library-search example. Date: November 9. Context: the example worked in the practice session and needs no new material. Revisit: before the next practice session, if the example changes.

This fictional entry is deliberately short. It names the outcome, the date and the point at which the group expects to look at it again.

Step 4: Review the log at a checkpoint

A log that nobody reads becomes a drawer. Choose a natural checkpoint, such as the start of a planning session, and skim recent entries together. Some will be confirmed, some will need a new entry and some can be closed.

When a decision changes, add a new dated entry rather than editing the old one away. The history explains how the group arrived at the current position.

Frequently asked questions

Who writes the entries?

The same person who takes notes for the discussion. One entry per decision keeps the task small.

What belongs in the log?

Decisions the group will need to find later. Routine scheduling and task assignments usually live elsewhere.

A practical next step

After the next technology discussion, write one log entry with a decision, a date and a revisit point. If that takes more than two minutes, the entry is trying to hold too much.

Next step

Get Board-Ready on AI and Cyber Risk

A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.

Stop Guessing. Start Scoring
Tyson Martin

Written by Tyson Martin, NACD.DC

Chief Trust, Security & AI Officer. CISO of record at MIO Partners; former CISO & CTO at Lumber Liquidators and Orvis; advisor to 200+ Fortune 500 boards and C-suites at AWS.

See the track record
Keep reading

More on Board Technology Oversight

All CISO Insights
Board Technology Oversight

What an API Does Without the Jargon

An API gives software a defined way to interact with other software. The concept through a fictional catalog example, without code or setup steps.