A grounded sales development note for B2B sales leaders: lead intake with explicit evidence, decision rights, and a verified close.
Question and scope
The question should name the unit, the start event, the stop event, and the decision the result is meant to inform. If one request produces several lead intake updates, define whether the unit is the request or each update before sampling. Write the primary measure and one supporting measure; a measure without a denominator or observation window is not ready. Separate the operational question from the compliance question; this method does not certify either outcome. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 lead intake exception log should show the reason code, owner, and release decision.
The protocol does not estimate an industry benchmark; it produces a local description that B2B sales leaders can review. State how duplicate requests are identified and whether they are merged, linked, or counted separately. The definitions should be short enough to use at the queue and precise enough to defend in a review with SDR. Record the exclusions in advance so a difficult case cannot be removed after the result is known. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 lead intake recovery test should record the restore point and the sequence approval cycle result.
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 denominator that changes during the window should be reported separately for each period. If the definition of meeting show rate changes, keep the old and new values side by side for the transition period. Keep a list of requests closed as duplicates and show which case survived. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Sales Development Rep should name the lead intake source, the owner, and the next review time.
Test the unit definition on a case that crosses owners, a case that is still open, and a case that was reopened. If duplicate requests are merged, keep the duplicate count and the merge rule in the dataset. The stop event should be the verified destination update, not the last message in the thread. If the queue was archived during the window, report the loss and exclude the affected period rather than assuming the cases were resolved. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for lead intake should show the source version and the prospect decision.
Definitions and measures
Define how a correction after close is linked to the original case and whether it creates a new case. Do not store sensitive content in the analysis file when a reference to the approved repository is enough. A correction is a change to a closed record; a clarification that does not change the record is a note, not a correction. If two reviewers disagree, preserve both classifications until the definition is clarified. Use the same note in the case file and the study extract; do not create a second version in a personal document. The lead intake review at Sales Development Rep should state whether the sequence approval was current on October 28.
If the definition of completion changes, keep the old and new rules side by side for the transition period. Record the source system, the record identifier, the extraction time, and the reviewer for every extracted value. A correction is a change to a closed record; a clarification that does not change the record is a note, not a correction. A definition that depends on the reviewer’s memory is not reproducible enough for this study. Keep the measurement note short enough to read with the case and specific enough to support the reported reply rate. The October 28 lead intake note should distinguish a missing meeting handoff from a confirmed negative.
Data dictionary and evidence
The data dictionary should name the allowed values for status, exception reason, owner, and close evidence. Give every case a study key that is not the client name, member number, or candidate email. Record the data extraction date and the version of the calendar used for the population count. A case key should remain stable if the case moves between owners or changes status. Link the observation to the exact field in the calendar and to the meeting handoff that supports it. The account executive decision on lead intake should be dated October 28 and linked to the meeting handoff.
Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. 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. A case key should remain stable if the case moves between owners or changes status. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 lead intake close should name the destination field, the approver, and the sequence approval cycle check.
Each case needs the source, the observation time, the field supported, the owner, and the reviewer. Version the dictionary and report which version was used for each observation period. Record the source identifier, the field name, the observation time, and the reviewer for every extracted value. Define who may change a coded value and how the change is logged. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 lead intake exception log should show the reason code, owner, and release decision.
Sampling and collection
Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Use the same collection form for every case and keep the original record linked to the extracted fields. Keep the sample selection reproducible by recording the export date, filter, and random seed or start rule. Include at least one case from each owner in scope when the frame allows it. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 lead intake recovery test should record the restore point and the meeting show rate result.
Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Collect the case from the opt-out register, the opt-out record, and the approval record, and stop at the verified close. Keep the sample selection reproducible by recording the export date, filter, and random seed or start rule. Record the date of the sample and the version of the queue export. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Sales Development Rep should name the lead intake source, the owner, and the next review time.
Record the eligible count, the sample size, and every exclusion so another reviewer can reproduce the sample. A second reviewer should re-extract a small subsample and record disagreements before the full analysis. Record the eligible count and every exclusion before the sample is drawn. Use a random start and a fixed interval when the frame is ordered, and record both. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for lead intake should show the source version and the account executive decision.
Analysis and reporting
Keep case-level detail available for review, because a summary chart without records cannot support a decision. For lead intake, report the age distribution and the share of cases waiting on a named owner. Show the unresolved cases by owner, age, and dependency instead of reporting a single completion percentage. Keep descriptive findings separate from causal claims and label exploratory results. Use the same note in the case file and the study extract; do not create a second version in a personal document. The lead intake review at Sales Development Rep should state whether the opt-out record was current on October 28.
Keep case-level detail available for review, because a summary chart without records cannot support a decision. A small sample should be reported with the number of cases that drive the result. If the result is unstable, say which cases create the variation and what a larger sample would test. When a measure is based on a small sample, state the case count and avoid ranking owners by the result. Keep the measurement note short enough to read with the case and specific enough to support the reported reply rate. The October 28 lead intake note should distinguish a missing lead intake from a confirmed negative.
Limitations
The method also cannot observe work that never entered the queue, which may be the most important missing population. Changes in staffing, access, or the CRM during the window can create a difference that is not a process effect. If the queue changed during the window, explain how the change affects the denominator and the interpretation. If the reviewer performed the work, use a second reviewer for a subsample and report the disagreement. Link the observation to the exact field in the CRM and to the lead intake that supports it. The sales manager decision on lead intake should be dated October 28 and linked to the lead intake.
The cited public sources frame recordkeeping, privacy, security, or control practice; they do not provide a local result. Report the unknown population and the evidence that would be needed to describe it. Report the limits of the sales engagement platform data, including fields that were unavailable or changed during the window. Record the access problems that prevented a case from being reviewed. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 lead intake close should name the destination field, the approver, and the sequence approval cycle check.
Review and next action
Record the decision and the next check so the study does not end as an archive. Keep the review note with the lead intake evidence so the next owner can see why the process changed. Record the owner, the due date, and the exact change that will be tested at the next review. Schedule the next review before the action begins, not after the result arrives. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 lead intake exception log should show the reason code, owner, and release decision.
If the action affects missed opt-out, route it to prospect and record the approval before implementation. A quality review should end with a testable next step, not a general instruction to improve. 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. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 lead intake recovery test should record the restore point and the opt-out closure result.
Sources
Apply the operating question
Use the finding to define one source, output, review owner, and exception path inside a real workflow.
Discuss the workflow