Board Technology Oversight

The Meeting Parking Lot: Keep Technical Questions Without Losing the Agenda

A question parking lot can keep a technology discussion focused without discarding useful questions. Make each note understandable and easy to revisit.

Business colleagues seated around a meeting table reviewing documents and taking notes

A technology discussion takes a detour. The question is reasonable, but answering it would take the room away from the purpose of the meeting. Saying "we will come back to that" is easy. Remembering what "that" meant is harder.

A meeting parking lot is a visible place for those questions. Its value comes from the note and the follow-up, not from moving a conversation out of sight.

Key takeaways

  • State the purpose of the meeting before sorting questions.

  • Write the actual question, not a vague topic label.

  • Agree on a useful place to revisit it.

  • Close the loop rather than accumulating abandoned notes.

Step 1: Make the question legible

"Search" is not enough of a note. "Does the demonstration include a search by neighborhood?" preserves what the person wanted to know. Include the relevant document or example when that helps someone answer later.

Atlassian's meeting-notes guidance describes a parking lot as a way to retain topics while keeping the current meeting focused. It also connects useful notes with owners and follow-up dates.

Step 2: Distinguish a detour from missing context

Some questions belong in the discussion because the answer is needed to understand the material. Others can wait for a separate walkthrough. Ask which kind this is before parking it.

A parking lot should not become a way to avoid an uncomfortable question. If the group cannot continue without the answer, the agenda may need to change.

Step 3: Use a small, illustrative note

Question: where does the branch list come from in this example? Context: the fictional library-search demonstration. Place to revisit: the demo-notes thread. Follow-up: the presenter will add an explanation before the next practice session.

This fictional note is deliberately ordinary. It preserves the question and a route back to it without turning a meeting aid into a complicated tracking system.

Step 4: End by reviewing what was parked

Before closing, read the parked questions back to the room. Some will already have been answered. Others need a follow-up conversation, an addition to the notes or no further action. Make that distinction visible.

Do not schedule another meeting automatically. A short written explanation may be enough, and it gives later readers the same context as those who were present.

Make the question legible

"Search" is not enough of a note. "Does the demonstration include a search by neighborhood?" preserves what the person wanted to know. Include the relevant document or example when that helps someone answer later.

Atlassian's meeting-notes guidance describes a parking lot as a way to retain topics while keeping the current meeting focused. It also connects useful notes with owners and follow-up dates.

Distinguish a detour from missing context

Some questions belong in the discussion because the answer is needed to understand the material. Others can wait for a separate walkthrough. Ask which kind this is before parking it.

A parking lot should not become a way to avoid an uncomfortable question. If the group cannot continue without the answer, the agenda may need to change.

Use a small, illustrative note

Question: where does the branch list come from in this example? Context: the fictional library-search demonstration. Place to revisit: the demo-notes thread. Follow-up: the presenter will add an explanation before the next practice session.

This fictional note is deliberately ordinary. It preserves the question and a route back to it without turning a meeting aid into a complicated tracking system.

End by reviewing what was parked

Before closing, read the parked questions back to the room. Some will already have been answered. Others need a follow-up conversation, an addition to the notes or no further action. Make that distinction visible.

Do not schedule another meeting automatically. A short written explanation may be enough, and it gives later readers the same context as those who were present.

Frequently asked questions

Who maintains the parking lot?

Choose a note-taker for the discussion. The person presenting does not have to capture every question while also explaining the material.

What if a question never gets answered?

Revisit whether it is still useful. Record a deliberate decision to leave it aside rather than letting an unexplained note linger indefinitely.

A practical next step

Try the parking lot in one routine technology discussion. At the end, check whether the notes preserve the questions well enough for someone who was not in the room to understand them.

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 Changed Since the Last Technology Update?

A useful technology update helps readers see what changed, what stayed the same and what remains an open question without rereading the whole history.