Onboarding And Retention Research

How often do virtual assistant task briefs lack a definition of done?

A measurement design for counting task briefs without a testable finish line and separating a missing outcome from a missing approval.

| 4 sources

How often do virtual assistant task briefs lack a definition of done?
6weeks observed
4task types
1intake form version
On this page
  1. Key takeaways
  2. Question and scope
  3. Definitions and evidence standard
  4. Sampling and measurement
  5. Findings and interpretation
  6. Limitations
  7. Practical next step
  8. Comparing task types
  9. What the evidence does not show
  10. Using the result in a manager conversation
  11. Sources and methodology
  12. Related research
  13. Questions about the findings

Key takeaways

  • A definition of done must let a reviewer accept or reject the output.
  • Separate a missing finish line from a missing example or approval.
  • Track late clarifications because they show who solved the ambiguity.
  • Test one task type before making an acceptance field mandatory.

Question and scope

This study asks how often a task brief given to a virtual assistant lacks a definition of done. It treats the brief as the unit and the written outcome as the standard. The scope is one role, one client, and a fixed review window. The result describes that setting and should not be treated as a universal benchmark.

A brief is eligible when it assigns a task to the assistant and names an expected output. A brief that only asks for help or asks a question is excluded. A definition of done exists when the brief states what a completed output must contain or satisfy. The definition can be short, but it must be testable.

The study also records whether the brief named a reviewer or an approver. A brief can have a clear outcome and still lack a route for acceptance. Report the two conditions separately so the result does not merge a content gap with an authority gap. A brief that names neither leaves the assistant to infer both the standard and the route.

Brief qualityWhat is presentWhat to add
TestableOutput and acceptance checkKeep the reviewer
PartialOutput but no checkAdd the acceptance test
MissingActivity onlyAsk for the finished result

Definitions and evidence standard

Define a testable finish line as a statement a reviewer could use to accept or reject the output. A request to prepare a summary is not testable, while a request for a one-page summary with three named sections and a source list is testable. The definition should describe the output rather than the effort. Effort is not a finish line.

Use the written brief, the intake form, and any follow-up messages as the evidence. A definition given verbally after the work started is not part of the original brief, though it can be recorded as a later clarification. Report the clarification separately. The timing matters because it changes who had to solve the ambiguity.

Separate a missing definition from a missing example. A brief may describe the output clearly without providing a sample, or it may provide a sample without stating the rule. Code the two conditions separately. An example can help, but it does not replace a finish line.

Sampling and measurement

Collect briefs from a defined period and freeze the list before coding. Include briefs from more than one requester and more than one task type. If the period contains a launch or a seasonal peak, report it separately. Record the number of briefs and the number of requesters.

Measure the number of eligible briefs, the number with a testable definition, the number with a partial definition, and the number with no definition. Add the number that named a reviewer and the number that named a due date. Report the counts by requester and task type. A rate without these counts can make a small sample look precise.

If a brief was revised after the work started, record the revision and the reason. A late definition may still be useful, but it should not be counted as part of the original brief. Report late clarifications as a separate category. The distinction shows whether the intake process or the requester is creating the gap.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of missing definitions in one task type may mean the work is hard to describe or the requester does not know the output. A cluster under one requester may mean that person relies on conversation instead of a brief. Read the actual briefs behind the largest cluster before naming a reason.

Compare the definition rate with the rework rate for the same tasks. A task without a finish line may be reworked because the assistant and the requester imagined different outputs. Report the comparison as a pattern rather than a proof. A correlation in one setting is a prompt for a closer review.

Check whether briefs with a definition also named a reviewer. A definition without an acceptance route can still leave the work waiting. Report the combination of definition and reviewer. The pair is a better indicator of a complete brief than either field alone.

Limitations

The study measures the written brief, not the full understanding between the requester and the assistant. A brief may be thin because the two people have a long working relationship. It also cannot show whether a clear definition produced a better output. The result describes the presence of a finish line, not its quality.

The sample may be biased toward briefs that were easy to retrieve. A request made in a chat message may be missing from the record. The period may also include unusual work that is not representative of the role. These limitations should be reported with the counts.

Coding a definition as testable requires judgment. Two reviewers may disagree about whether a phrase is specific enough. Record the disagreements and resolve them with examples. A calibration set of ten briefs before the full review improves consistency.

Practical next step

Add three fields to the intake form: the output, the acceptance check, and the reviewer. The output field describes what the finished item is, the acceptance check says how it will be judged, and the reviewer names who decides. Three fields are short enough to complete and specific enough to use. The form should show an example for each.

Ask the assistant to route a brief with no acceptance check to the requester before starting. This is a small stop rule that prevents the assistant from inventing a standard. Record how often the route is used. A high count may mean the form or the training needs work.

Test the change on one task type for a month and compare the rework rate with the baseline. Keep the fields only if they improve the acceptance conversation. If the form becomes too long, combine the output and acceptance fields into one prompt. The goal is a testable finish line, not a longer form.

Comparing task types

Compare briefs for recurring tasks with briefs for one-off tasks. A recurring task may rely on an established template, while a one-off task needs a written finish line. The definition rate may differ for reasons that are legitimate. Report the task type so the reader can see whether the comparison is fair.

Look at briefs for client-facing work separately from internal work. Client-facing work usually needs a named reviewer and a clearer acceptance check. An internal task may tolerate a lighter brief. Pooling the two can hide a risk that only appears in client work.

Compare briefs that arrived through the intake form with those that arrived through chat. A form may prompt a definition while a chat message may not. The channel is part of the process and should be reported. A difference between channels points to a simple repair at intake.

What the evidence does not show

The study does not show that every task needs a formal brief. A small, familiar task may be clear without a document. It also does not show that a written definition guarantees a correct result. The definition can be wrong or incomplete. The result measures the presence of a testable standard, not the quality of the work.

It does not prove that the requester is at fault when the definition is missing. The form may not ask for one, or the team may reward speed over clarity. The gap is a process signal, not a personal judgment. The review should look at the form and the incentives together.

It cannot predict how a different team would perform. The task mix, the client expectations, and the review culture all affect the result. A local study should be repeated rather than generalized. The value is in the questions it helps the team ask.

Using the result in a manager conversation

Show one brief with a clear finish line beside one without it. Ask the manager which one they would rather receive as an assistant. The comparison makes the cost of ambiguity visible without blaming anyone. The manager can then decide which field to add first.

Ask the assistant which brief was hardest to complete and why. The answer may point to a missing example or an unstated approval. Use that example to revise the form or the role guide. A single concrete case is more persuasive than a percentage.

Close with a small test and a date to review it. The test might be one task type with a required acceptance check for three weeks. Record the baseline and the result. If the change does not help, remove it rather than keeping a field that only adds friction.

Sources and methodology

The study codes written task briefs against a testable finish-line definition and reports full, partial, and missing definitions with reviewer and due-date fields.

  1. U.S. Small Business Administration — Hire and manage employees current.
  2. U.S. Office of Personnel Management — Training and development current.
  3. U.S. Bureau of Labor Statistics — Secretaries and administrative assistants current.
  4. U.S. Cybersecurity and Infrastructure Security Agency — Secure Our World current.

Source count: 4. Last verification date: November 9, 2026.

Questions about the findings

Is a checklist the same as a definition of done?

Not always. A checklist can help, but the brief still needs a statement of what the completed output must satisfy.

Can an example replace a written definition?

An example helps, but it leaves the rule implicit. The team should state the rule and use the example to illustrate it.

Does this apply to small tasks?

The formality can be lighter, but the assistant still needs to know when the task is finished.

Put the finding to work

Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.

task briefsdefinition of donevirtual assistant research