Measuring Briefing-Folder Retrieval Time During Executive Travel

Key takeaways

• Test retrieval of a meeting page, a metric, and a prepared answer.
• Measure both time and accuracy, and report errors separately.
• Run the test on the device the executive will actually use.
• Repeat the same tasks on the next trip before drawing a broad conclusion.

Question and scope

This study asks how quickly an executive can retrieve a specific piece of information from a travel briefing folder under realistic time pressure. The unit is one retrieval task tied to one folder and one meeting. The review measures the time to find a meeting page, a metric, and a prepared answer. It does not judge the quality of the underlying business content.

Set the scope to one executive, one roadshow or travel cycle, and a defined folder format. Record the device, the file structure, and the meeting sequence. If the folder format changes during the trip, separate the periods. A format change mid-trip makes the retrieval times incomparable.

Choose retrieval tasks that the executive would actually perform: finding the next meeting, checking a number before a call, and locating the approved answer to a likely question. A task that no one would attempt under time pressure is not a useful test. The executive should agree that the tasks represent the real need.

Record whether the executive had seen the folder before the test, because prior familiarity changes the retrieval time. A first-time user and a repeat user answer different questions. If the sample mixes both, report the groups separately. The comparison should not credit the folder for knowledge the executive already had.

What the sources establish

Microsoft's Work Trend Index describes information load and the pace of the working day, which frames the retrieval problem without measuring a specific folder. BLS occupational data describes the assistant role but not a retrieval benchmark. GAO data-reliability guidance supports careful observation and record keeping. NIST guidance supports attention to access and integrity when the folder contains sensitive material.

The sources do not establish a target retrieval time or prove that a faster retrieval improves a meeting outcome. A fast but wrong answer can be worse than a slower correct one. The study therefore measures both time and accuracy, and reports the errors separately.

Use the sources to frame the questions: how much time does the executive have, which document is authoritative, and how does the assistant know the folder is current? Those questions keep the review focused on usability and control. They do not require a general theory of executive productivity.

Definitions and measures

Define a retrieval task as a request for a specific item, such as a meeting page, a metric, or an answer. Define success as finding the correct item within the agreed time limit. Define an error as finding an outdated or wrong item. Define a failure as not finding the item within the limit.

Measure the time from the request to the correct item, the number of clicks or page turns, and the accuracy of the result. Record the device and the folder version. Repeat each task more than once to reduce the effect of learning. Keep the order of tasks consistent across participants.

Record whether the executive used the index, the search function, or manual browsing. The path matters because a folder that works only through search may fail offline. A folder that works only through an index may fail when the meeting order changes. The study should show which path was used.

Record the number of wrong items opened before the correct one, because a fast wrong path is not a success. The path shows where the index or the labels misled the reader. Report the error type, such as an old version or a different meeting. That detail is more useful than a single accuracy percentage.

Sampling and collection

Sample retrieval tasks across the meeting sequence, including the first meeting, a middle meeting, and a meeting after a travel leg. Include a task that requires a metric and a task that requires a prepared answer. Do not sample only the pages the executive already knows. Include a page the executive has not reviewed, because that is where navigation fails.

Collect the folder, the task list, the timing record, and a short note on any error. If the executive is unavailable, use a colleague who is unfamiliar with the folder as a proxy, and report that substitution. A proxy can reveal navigation problems but may not represent the executive's prior knowledge.

Run the test in the environment the executive will use, such as a phone, a tablet, or a printed pack. A desktop test can overstate usability. If the actual environment is not available, record the difference and treat the result as a lower bound.

Test the folder on the first day of travel as well as the middle, because fatigue and time pressure change retrieval. A test conducted only at a desk misses the conditions the folder was built for. Record the time of day and the time until the next meeting. Those conditions are part of the result.

Timing pathway

Start the clock when the request is complete, not when the executive begins to move. Stop the clock when the correct item is visible on the screen or page. Record any wrong item opened along the way. The path is part of the result, not a separate anecdote.

Report the median and the tail of retrieval time for each task type. A single average across meeting pages and metrics can hide a serious problem in one type. The tail is where the executive will feel the folder fail. Report the failures separately from the slow successes.

Compare the results with the folder's design intent. If the index was meant to make the meeting page the first stop, check whether the executive actually used it. A design that is not used is not a control. The study should show the gap between the intended and the observed path.

Record whether the executive asked the assistant for help during the task, because a folder that requires a guide is not self-service. The assistance is a finding, not a failure of the executive. Report the number of tasks that needed help and the point where help was requested. That point often reveals the design problem.

Analysis and reporting

Report the number of tasks, the success rate, the median and tail of retrieval time, and the error rate. Break the results down by task type, device, and meeting position. Report the failures with the item that was sought. A completion rate that excludes errors is not a usability measure.

Inspect the errors for patterns. A recurring wrong metric may point to two versions in the folder, while a recurring failure to find a meeting page may point to an index that does not match the schedule. Choose one fix and test it on the same tasks. Do not redesign the whole folder after one bad run.

Keep the executive's comments separate from the measured result. A comment such as I could not find the number is useful context, but the time and the path are the evidence. The report should present both without turning the comment into a score.

Report the tasks that were not attempted, because a folder can fail by discouraging a search. An executive who does not try to find the answer may be relying on memory instead of the folder. The report should note the skipped tasks and the reason. A completion rate that ignores them overstates usability.

Limits and next action

The study cannot prove that a faster retrieval improved a meeting or that the proxy participant represents the executive. It also cannot capture the value of a page the executive never needed. A folder can be slow on a test task and still be useful in practice. The report should distinguish a navigation problem from a content problem.

The sample may be too small to support a broad claim, especially with one executive and one trip. Repeat the test on the next trip with the same tasks and definitions. A second run is more useful than a larger opinion survey.

Choose one change and assign an owner. The change might be a meeting-first index, a single metrics page, or a printed quick card. Set a repeat test date and keep the definitions stable. A useful result is a folder that the executive can use without the assistant sitting nearby.

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. Microsoft 2024 Work Trend Index Annual Report.
15. BLS, Secretaries and Administrative Assistants.
16. GAO, Assessing Data Reliability.
17. NIST Cybersecurity Framework.

Related research

• Studying document retrieval time in executive support work
• Preparing a CEO Briefing Folder for an Investor Roadshow
• Measuring the cost of context switching in an executive calendar

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.