Board Technology Oversight

The Repeated Agenda Topic Needs a New Question

A recurring technology topic can return without repeating the same discussion. Name the question for this meeting rather than relying on last quarter's heading.

A person writing on a wall calendar.

The agenda says "technology update" for the fourth time. The heading is consistent. The question the group is supposed to discuss is less clear.

A recurring topic and a repeated conversation are different things. Keeping the topic while changing the question can make an ordinary meeting agenda more informative. This is a communication suggestion, not a statement about board duties or a required oversight calendar.

Key takeaways

  • A topic names the area; a question names the discussion.

  • Keep the current question visible beside the recurring heading.

  • Distinguish explanation, clarification and decision.

  • A meeting format should not imply requirements it does not establish.

Step 1: Keep the topic, specify the question

In a fictional quarterly agenda, "document library" is the recurring topic. One meeting asks which labels readers find confusing. The next asks whether the revised glossary explains those labels. The heading stays useful while the purpose moves forward.

The questions do not need to be dramatic. Their value is that a participant can tell why the subject is back and what kind of preparation would help.

Step 2: Make the discussion type clear

An explanatory slot asks the group to understand something. A clarification slot asks it to resolve a question. A decision slot asks it to choose. A generic update heading can hide the distinction.

Atlassian's meeting-notes template separates discussion, decisions and action items. An agenda can use the same distinction before the meeting begins, without creating a new reporting framework.

Step 3: Carry the open question forward, not the whole meeting

A short note can say "Last time we clarified the term; this time we are reviewing the sample explanation." That gives a returning participant context without replaying the entire history.

Google's audience guidance also applies to participants who missed a meeting. They need enough background to understand the current question, not an assumption that the repeated heading tells the whole story.

The resulting agenda may still be short. The change is in specificity: each recurrence has a purpose the reader can name. Whether the meeting should occur, who must attend and what responsibilities it serves remain separate questions.

Sources for the definitions and writing principles discussed here: Google, Technical Writing One: Audience, last updated March 28, 2025; Atlassian, meeting-notes template. The examples and suggested discussion formats are illustrative.

Frequently asked questions

Does every recurring topic need a decision?

No. A focused explanation or clarification can be a legitimate purpose. Name it honestly.

Is this an annual board calendar?

No. It concerns the wording of a recurring agenda item, not the frequency or scope of required oversight.

What if the same question remains open?

Say that it remains open and explain what the current discussion adds. Do not invent progress to make the agenda look different.

A practical next step

Look at one recurring agenda heading. Add the question the group is meant to discuss this time. Book a Decision-Clarity Call for help making technology work easier to explain.

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

Concentration Risk in One Cloud Region

When most workloads sit in one cloud region, one failure reaches everything. A dependency heat map shows where the blast radius is bigger than intended.