Key takeaways
- Define the buddy role and the questions the buddy is expected to answer.
- Track repeat questions by topic, not only by total volume.
- Use the result to improve written guidance so the role does not depend on one person.
Question and scope
This study asks whether an assigned onboarding buddy changes the number of repeat questions a virtual assistant asks during the first month. It focuses on questions that have already been answered in a written guide or a prior session. The scope is one role, one client team, and a fixed cohort. The result describes the local question pattern, not the friendliness or competence of the buddy.
The unit is one question logged by the assistant or observed in a support channel. A question that contains several unrelated requests is split before counting. A repeat is the same topic asked again within fourteen days after an answer was given. Exclude questions about a new client request that did not exist earlier. Report the number of assistants and the number of weeks in each group so a small cohort is not overinterpreted.
| Record | Evidence of completion | Common gap | Use |
|---|---|---|---|
| Question | Text and date | Chat only | Add to log |
| Topic | Task or system named | General label | Group |
| Repeat | Same topic within 14 days | No link to prior | Compare |
| Resolution | Answer and source | Verbal answer only | Update guide |
Defining the buddy role
Define what the buddy is expected to do before the cohort starts. A buddy may demonstrate a task, explain local context, and help the assistant find the right source. A buddy should not become the permanent answer desk for every exception. Write the boundary in the onboarding plan and give the buddy a way to redirect a question to the written process. Without that boundary, a helpful person can accidentally create a dependency.
Set a time limit for the buddy assignment, such as the first two or four weeks. Record the expected response window and the topics the buddy owns. Tell the new assistant how to ask a question and what information to include. A buddy program with no scope becomes an informal friendship with unpredictable support, which is hard to compare or improve.
Method and sample
Build the question log before the first cohort starts. Ask the assistant to log the question, the topic, the source they checked first, and the answer they received. Review the support channel for questions that were never logged. Use the same template for both the buddy and no-buddy groups. If the groups differ in role complexity or start date, report those differences rather than adjusting them away.
A comparison group is useful but not always available. When a team cannot run two groups at once, compare the same role across two consecutive cohorts and state the change in conditions. Record any change in manager, client, or tooling that could affect the result. The study can describe an association between the buddy and the question count, but it cannot prove that the buddy caused the difference.
Measures and findings
Report the total number of questions, the number of repeat questions, and the share of repeats by topic. Show the result by week and by task family. Include the number of questions answered by the written guide without help, because that is the outcome a buddy program should eventually improve. A drop in total questions with a rise in repeats may mean the assistant has stopped asking and started guessing.
Inspect the topics behind the repeats. A cluster around access requests may point to a missing approval step, while a cluster around client tone may point to an incomplete example. Compare the buddy's answers with the written guide. If the buddy consistently gives a better answer, the guide is the problem. If the buddy gives a different answer each time, the buddy role needs a standard.
Interpreting a reduction
A lower repeat count can mean the buddy helped the assistant learn, or it can mean the assistant found the questions too costly to ask. Check the support channel and the error log before celebrating. Ask the assistant whether they felt comfortable raising a question. A program that reduces questions by making people quiet is worse than one that leaves a visible backlog.
A higher question count in the early weeks can be healthy if the questions are specific and the answers are captured. The useful trend is fewer repeats over time and a growing share of answers found in the written guide. The study should report both the quantity and the quality of the questions, not only the total. Otherwise a team may optimize for silence rather than understanding.
Limitations
Question logs are incomplete by nature. People ask in passing, in a direct message, or not at all. The buddy's own workload and availability can change during the cohort. The comparison may also be affected by a new client, a tool migration, or a manager change. These factors make the result a local signal rather than a general finding about buddy programs.
The study does not measure the buddy's performance or the assistant's ability. It measures whether questions were asked and repeated under a defined support arrangement. It also cannot show whether a question was good or whether the answer was correct. Pair the count with a small quality review of the answers and the written guidance before drawing a conclusion.
Practical next step
Choose one change based on the most common repeat. If the repeat is about access, fix the request path and the approval owner. If it is about a client task, add a worked example to the guide. If it is about local context, give the buddy a short script and a place to record the answer. Keep the buddy role time-limited and review the log weekly.
Recheck the same measures with the next cohort and keep the written fixes even if the buddy program changes. The goal is not to eliminate questions; it is to make the answers easy to find and consistent. Record the change and the date so the next review can compare the same evidence. A buddy is most useful when the role transfers judgment and improves the documentation, not when it becomes the only place where the process lives.
Selecting and preparing buddies
Choose a buddy who does the task the same way the written guide describes. A fast expert who relies on personal shortcuts can transfer habits that do not scale. Give the buddy the guide, the question template, and the boundary of the role. Explain that the goal is to make the answer findable, not to become the permanent source.
Prepare the buddy before the assistant starts. Walk through the first week's tasks and the questions that usually appear. Agree on how the buddy will record an answer that is not in the guide. A short preparation session prevents the buddy from improvising a different process under pressure.
Measuring the buddy's own workload
Track the time the buddy spends answering questions and demonstrating tasks. A program that looks free usually shifts cost to a senior person who already has a full queue. Include the buddy time in the capacity plan for the first month. If the time is excessive, the written guide or the role scope needs attention.
Ask the buddy which questions repeated and which answers took the longest. Their view can reveal a gap that the assistant's log misses. Do not use the time as a performance score. Use it to decide whether the program is properly staffed and whether the documentation is doing its job.
When the program should end
End the formal buddy period on a stated date and review the evidence. The assistant should know which questions now go to the guide, which go to the manager, and which go to the buddy as an exception. A program that fades without a review leaves ownership unclear. A short close-out note is enough.
Keep the buddy available for a limited exception window if the role is complex. State the limit and the route for urgent issues. Review the exceptions after the window closes. The program has succeeded when the assistant can find most answers without the buddy and knows where to go for the rest.
Rechecking the finding
Repeat the question log with the next cohort and keep the same definitions. If the buddy changes, record the new person's preparation and availability. Compare the repeat rate by topic rather than only the total. A topic that improves while another worsens is a useful finding, not a failure of the program.
Ask the assistants in both cohorts whether they felt able to ask questions. A program that reduces repeats by reducing trust is not an improvement. Keep the written fixes even if the buddy changes. The goal is a process that learns, not a program that depends on one helpful person.
Sources and methodology
A bounded comparison of question logs for virtual assistant cohorts with and without an assigned onboarding buddy. The review uses an explicit definition of a repeat question and reports local patterns only. Public guidance frames the questions but does not validate a local program or supply a performance conclusion.
- U.S. Office of Personnel Management — Training and Development current.
- U.S. Small Business Administration — Hire and manage employees current.
- NIST Cybersecurity Framework 2.0 current.
- CISA Secure Our World current.
Source count: 4. Last verification date: November 6, 2026.
Questions about the findings
What is a repeat question?
The same topic asked again within fourteen days after an answer was given. A new request that did not exist earlier is not a repeat.
Does a lower question count prove the buddy worked?
No. It may mean the assistant is more comfortable or less willing to ask. Check the error log and ask the assistant before drawing a conclusion.
How long should a buddy assignment last?
Set a fixed period such as two to four weeks, with a defined scope and a route for questions outside that scope.
Put the finding to work
Review the full research library, compare cluster coverage inside Manager Enablement Research, and pair these findings with our VA candidate screening support.
