Measuring cycle time for role brief from request to verified close

Key takeaways

• A grounded executive hiring note for executive hiring teams: role brief with explicit evidence, decision rights, and a verified close.
• Report denominators and limitations.
• Keep the decision with the named owner.

Question and scope

The question should name the unit, the start event, the stop event, and the decision the result is meant to inform. The population should include cases handled by every owner and channel in scope, not only the queue with the cleanest records. A case is complete only when the executive search CRM shows the approved destination value and the role brief supports it. State whether the study covers one team, one client, or all cases in the defined service. Record this decision in the study log with the case key, the review date, and the person who approved the classification.

Write the primary question and one supporting question, then stop; a long list of questions usually hides an undefined unit. The population should include cases handled by every owner and channel in scope, not only the queue with the cleanest records. Distinguish an administrative pause from a failure: a pause waits for a named decision, while a failure leaves the next action unowned. Write the decision the study is meant to inform before choosing the measure. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.

Population and unit

Test the unit definition on a case that crosses owners, a case that is still open, and a case that was reopened. A case that moves between owners stays one case unless the process defines a new requirement at the handoff. The start event should be the first recorded request, not the first time the team opened the case. Separate cases opened before the window from cases opened and closed inside it, and report both counts. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.

Include cases opened before the window but closed inside it only when the protocol says they belong to the population. A denominator that changes during the window should be reported separately for each period. The definition should make it possible to classify a case without asking the person who did the work. If a request was reopened after the window, keep it in the original population and report the later event separately. At Hire Executive Team, the reviewer should be able to explain this step to hiring committee from the case record alone.

Definitions and measures

A pause should have a reason, an owner, and a review date; otherwise it is an unowned case with a different label. Use a stable case key and a separate identity crosswalk stored in an approved system. Define whether a case that waits for a third party is open, paused, or excluded, and apply that rule to every owner. Keep a change log for every definition adjustment and the date it took effect. Use the same note in the case file and the study extract; do not create a second version in a personal document.

If the definition of completion changes, keep the old and new rules side by side for the transition period. Use a stable case key and a separate identity crosswalk stored in an approved system. If a case is outside the scope rule, record the rule and the date of exclusion rather than removing it silently. Give one concrete example and one boundary case to each reviewer before collection begins. When a case needs an exception, record the reason, the owner, and the date before continuing the review.

Data dictionary and evidence

Keep free-text notes separate from coded fields so the analysis does not depend on inconsistent wording. Keep the identity crosswalk in the approved system and restrict it to the review owner. Keep the source reference and the coded value in the same row, and do not overwrite the original with a later correction. Define who may change a coded value and how the change is logged. Keep the measurement note short enough to read with the case and specific enough to support the reported slate completion.

Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. Test the dictionary on a case with a missing reference packet and a case with a corrected value. A missing value should have a reason code, not a blank cell or a zero. Define who may change a coded value and how the change is logged. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.

If the source is a document, record the page or field; if the source is a system, record the record identifier and extraction time. Name the required fields for each article type and mark conditional fields in the dictionary. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. Do not use a zero or an empty string to represent missing evidence. Link the observation to the exact field in the offer approval system and to the onboarding plan that supports it.

Sampling and collection

A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. If a source cannot be accessed, mark it unavailable and record the access problem rather than asking the operator to reconstruct it from memory. Include reopened, unresolved, and exception cases in the sample frame. Include at least one case from each owner in scope when the frame allows it. Do not let a summary written later replace the evidence that was available at the first decision.

Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Keep the collection window and the number of collectors in the report; both affect how the result should be interpreted. Use a random or systematic start rule and then take consecutive cases within each stratum. A case that is difficult to access is still part of the frame; report the access failure rather than replacing it silently. If the case moved between owners, include both owner periods in the review note and name the handoff time.

Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. Keep the collection window and the number of collectors in the report; both affect how the result should be interpreted. If a stratum has fewer cases than planned, report the smaller count instead of replacing it with a convenience case. Include at least one case from each owner in scope when the frame allows it. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.

Analysis and reporting

Separate observation from interpretation; a high completion rate on a small easy sample is not evidence of a strong control. Use case-level review to explain an outlier before treating it as a process signal. Record the sample date, the denominator, the numerator, and the exclusion count for every reported rate. Report the number of cases that drive a small-sample result and the direction of the effect. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract.

If the sample is small, report the instability and the cases that drive the result instead of a precise-looking percentage. Compare periods only after checking the case mix, the definitions, and the queue rules. Write the finding in plain language and separate what was observed from what the team believes caused it. When a rate changes, check whether the case mix or the evidence standard changed at the same time. At Hire Executive Team, the role brief review should end with a dated note and a named owner for the next check.

Limitations

The record may be incomplete, delayed, or maintained outside the team, so the method cannot infer missing work from a clean summary. The study cannot determine whether a professional judgment was correct, only whether the record supports it. State that the result describes the observed sample and not the entire industry or every team in the service. If the queue changed during the window, explain how the change affects the denominator. If the evidence is sensitive, record the approved reference and access path rather than copying the content.

The record may be incomplete, delayed, or maintained outside the team, so the method cannot infer missing work from a clean summary. The study cannot determine whether a professional judgment was correct, only whether the record supports it. Do not treat a missing record as proof that the work did not happen; it is evidence about the record. State what a follow-up study would measure and which population it would include. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.

Review and next action

Keep the review note with the role brief evidence so the next reviewer can see why the process changed. If the result is inconclusive, say so and choose a narrower question rather than claiming a trend. Record the owner, the due date, and the exact change that will be tested at the next review. If the action needs approval, record the approver and the date before the change is applied. Record this decision in the study log with the case key, the review date, and the person who approved the classification.

If the action affects missing reference, route it to hiring committee and record the approval before implementation. Choose one change and one measure to test it; a long action list is hard to evaluate. Report the action result even if the change did not work; a failed test is still evidence. Report a failed action with the same detail as a successful one so the team can learn from it. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.

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. U.S. Department of Labor - recordkeeping.
15. U.S. Small Business Administration - manage your business.
16. NIST Cybersecurity Framework.
17. U.S. Equal Employment Opportunity Commission.

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.