Decision operations

Measuring decision log reuse across executive team meetings

A study design for checking whether a decision log is actually used to review and close decisions in later executive meetings.

4 min readHireExecutiveTeam research

Key takeaway Measure retrieval, review, action closure, and evidence of reuse separately rather than counting log entries.

Measuring decision log reuse across executive team meetings research illustration
Table of contents
  1. Key takeaways
  2. Question and scope
  3. What the sources establish
  4. Definitions and measures
  5. Sampling and collection
  6. Analysis and reporting
  7. Limits and sources of error
  8. Review and next action
  9. Sources
  10. Apply the research

Key takeaways

  • Count retrieval and review separately from entry creation.
  • Report closure evidence, not just an updated status.
  • Use one meeting-cycle change and compare the next sample.

Question and scope

This study asks whether an executive team can measure how often its decision log is reused in later meetings. The unit is one decision entry reviewed at a subsequent meeting. The review examines whether the entry was retrieved, discussed, assigned a next action, and closed with evidence. It does not evaluate whether the original decision was wise or whether the meeting was well run.

Set the scope to one executive team and a fixed number of meeting cycles. Record the log template, the meeting cadence, and the roles that can edit an entry. If the team changes its log or its meeting rhythm during the window, separate the periods. A new template can change reuse more than a change in individual discipline.

What the sources establish

The GAO Green Book describes internal control principles for setting objectives, monitoring performance, and addressing risk. NIST privacy guidance is relevant to limiting sensitive information in a shared leadership record. Harvard Business Review's meeting research describes the value of clear decision ownership and follow-through. None of these sources defines a decision-log reuse rate or supplies a local benchmark. Keep the source list with the review so a reader can see the boundary.

The team therefore needs local evidence for its own record. Public sources can explain why ownership and review matter, but they cannot show whether a specific entry was retrieved or whether a decision was closed. The study should define reuse in observable terms and preserve the meeting context. A local count is more useful than a general claim that the log is working.

Definitions and measures

Define a decision entry as a record of a choice, a deferral, or an assigned action created in the team's log. Define retrieval as the entry being opened, cited, or displayed in a later meeting. Define review as a substantive discussion of the entry and its current state. Define closure as the recorded completion of the next action with evidence.

Measure the number of entries, the number retrieved, the number reviewed, the number with an owner, and the number closed on time. Report the number of entries with no review date. Do not count an entry as reused merely because it still exists in the log. Existence is not evidence that anyone used it.

Sampling and collection

Sample decision entries rather than meetings, then review every meeting note attached to the selected entry during the observation window. Include decisions that were closed, deferred, and reopened. Stratify by decision type and by owner role. Record the sampling rule and the meeting cycles included. If the team has few decisions, extend the window rather than combining decision types, and report the count.

Collect the log entry, the meeting agenda, the minutes, the action tracker, and the closure evidence. Mask participant names in the analysis table where they are not needed. If a decision was discussed outside the meeting, record that channel as a separate event. A verbal update without a record is difficult to verify and should be reported as a limitation.

Analysis and reporting

Report the number of entries, the number retrieved, the number reviewed, the number with a named owner, and the number closed. Show the counts by decision type and by owner. Report the median time between the decision and the first review. A high retrieval count with a low closure count suggests that the log is read but not used to finish work.

Inspect the entries that were never reviewed. Was the review date missing, was the owner unclear, or did the meeting agenda omit the item? Group the causes and choose one change, such as a required review date or a standing agenda section. Do not rank owners by closure rate when the decision mix differs.

Limits and sources of error

The study cannot prove that a decision was correct or that the meeting used the log well. It can show whether the entry was retrieved and whether the action was closed with evidence. An entry may also be reviewed in a smaller group without a meeting note. Report that possibility rather than assuming the log was ignored. Pair the record review with a short owner interview when that question matters.

The log may not capture informal decisions, and the meeting notes may not name the entry. The reviewer may also interpret a brief discussion as a review when it was only an update. Use a short codebook and test agreement on a small sample. Report the disagreement instead of forcing a single reading.

Review and next action

Choose one change: add a required review date, add a standing decision-review agenda item, require closure evidence, or shorten the log template. Assign an owner and the next sample date. Keep the change small enough to test for one meeting cycle. Repeat the study with the same definitions. Write the change into the meeting template so it survives the next cycle.

Close the review when the team accepts the result and schedules the next check. Report the remaining uncertainty beside the reuse counts. The [decision log routine](/blog/building-a-decision-log-the-executive-team-actually-reuses/) describes the practice this study measures. Use the result to improve the record, not to judge an individual owner.

Sources

  1. Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
  2. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
  3. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
  4. Business Formation Statistics, U.S. Census Bureau.
  5. Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
  6. Productivity Statistics, OECD Data Explorer.
  7. World Development Indicators, World Bank DataBank.
  8. ILOSTAT Labour Statistics, International Labour Organization.
  9. 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
  10. The economic potential of generative AI, McKinsey Global Institute.
  11. Creating helpful, reliable, people first content, Google Search Central.
  12. Search Engine Optimization Starter Guide, Google Search Central.
  13. Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
  14. GAO Green Book.
  15. NIST Privacy Framework.
  16. Harvard Business Review, meetings.
  17. U.S. Small Business Administration.

Apply the research

Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.

Turn the finding into a support scope.

Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.

Talk through the role