Keep an assumption register during virtual assistant onboarding

Keep an assumption register during virtual assistant onboarding

A new virtual assistant, Alex, was onboarded a month ago. Sarah, a marketing manager, was eager to delegate recurring social media report compilation. Her instruction was brief: "Please compile the weekly report for last week's social media performance. You'll find the template in the Marketing Team folder. Get it to me by Friday." Alex, keen to impress, found the template, filled it with data pulled from the analytics dashboard, and sent it off.

Come Friday, Sarah opened the report. The numbers were there, but the key engagement metrics she expected were missing. Instead, Alex had focused on follower growth and post reach, metrics Sarah rarely prioritized for this particular weekly review. The formatting was also slightly off, differing from the established brand guidelines. Sarah was frustrated. Alex was confused. A simple handoff had gone sideways, costing Sarah time and Alex a hit to her confidence. This scenario is a common symptom of unmanaged virtual assistant onboarding assumptions.

Diagnosing the disconnect: where assumptions lie hidden

The root of Sarah and Alex's misunderstanding was not a lack of effort but a gap in unstated beliefs. Sarah assumed Alex would instinctively know which metrics were most important for the "weekly social media performance report," based on her experience with previous in-house team members. Alex, coming from a different professional background, assumed the standard template fields were sufficient and prioritized easily accessible, high-level numbers. Neither assumption was malicious, but both were consequential.

Hidden assumptions are particularly prevalent in virtual assistant onboarding because of the inherent distance. There's less opportunity for spontaneous clarification or for the new hire to absorb organizational nuances through osmosis. Virtual assistants often work across different time zones and cultures, bringing diverse interpretations of common business terms or task expectations. The hiring manager might assume a basic level of tool proficiency or industry knowledge, while the virtual assistant might assume a different level of detail is required for initial instructions. These silent agreements, when unexamined, become fertile ground for errors, rework, and mounting frustration, directly impacting the effectiveness of your virtual assistant onboarding process.

Defining ownership boundaries for clarity

Preventing such disconnects requires a structured approach to identifying and addressing assumptions. This process is a shared responsibility, with clear roles defined for the onboarding team, the hiring manager, and the virtual assistant themselves.

The onboarding team owns the framework. They are responsible for establishing the expectation that assumptions will be surfaced and for providing the tools and guidance to do so. This includes introducing the concept of an assumption register during general onboarding and explaining its purpose.

The hiring manager owns the task-specific assumptions. For every significant task delegated, especially early in the virtual assistant's tenure, the manager must actively consider what they are assuming the virtual assistant already knows or understands. This involves articulating implicit knowledge, departmental conventions, and specific preferences that might not be obvious from a standard procedure document.

The virtual assistant owns their own understanding. Their role is to proactively document their own assumptions and ask clarifying questions. This takes courage and a supportive environment. They should be encouraged to question anything that is unclear, rather than proceeding with a guess.

An assumption register acts as the central record for these shared understandings. An assumption should be recorded and validated when its potential misinterpretation could significantly impact the quality of the output, delay a deadline, require rework, or lead to inefficient resource use. This register is a living document, not a static checklist.

The assumption register: a shared truth source

An assumption register is a simple, yet powerful, tool for externalizing and managing the implicit beliefs that drive our actions. For virtual assistant onboarding, it functions as a collaborative document where managers and virtual assistants can record, discuss, and validate what they believe to be true about a task, a tool, or an organizational process. This systematic approach transforms potential points of failure into opportunities for shared understanding.

The register typically includes fields that capture the essence of the assumption, who holds it, when it was identified, how it will be verified, its current status, and the agreed-upon resolution. It creates a transparent record, preventing either party from later claiming, "I thought you knew that."

Here is an example of what an assumption register might look like:

This register is more than a logging tool; it's a conversation starter. It prompts managers to articulate the unwritten rules and encourages virtual assistants to voice their uncertainties without fear.

Repairing the course: a step-by-step recovery

When an assumption leads to a misstep, as with Sarah and Alex, the assumption register provides a clear path for recovery. Instead of assigning blame, the focus shifts to identifying the hidden assumption and building shared understanding.

Let's revisit Alex and Sarah's scenario and outline a repair sequence:

1. Identify the specific failure point. Sarah explains to Alex that the initial social media report did not meet expectations, specifically regarding missing key engagement metrics and incorrect formatting. She provides concrete examples from the submitted report.
2. Manager and VA collaboratively identify the underlying assumptions. Sarah asks, "What did you understand to be the most important metrics for this report?" Alex responds, "I focused on follower growth and reach, as those were prominent in the template." Sarah then states her unstated assumption: "I assumed engagement rate and click-through rate were the default important metrics for a weekly review here." Similarly, they identify a formatting assumption.
3. Record these in the assumption register. Sarah, or the onboarding owner, enters the identified assumptions: "VA understands the key metrics for weekly social media report," and "VA understands preferred report formatting guidelines." Both are marked as "Open."
4. Manager provides explicit clarification, training, or resources. Sarah shares past examples of well-received reports, explicitly pointing out the preferred metrics and formatting elements. She clarifies that while follower growth is important, engagement metrics are central to this specific report's purpose. She also points to the brand guidelines document for formatting.
5. VA confirms understanding and revises work. Alex reviews the examples and documentation, asks any remaining questions, and then reworks the report based on the new information.
6. Manager validates the revised work and marks assumptions as "validated." Sarah reviews the corrected report. Once it meets expectations, she marks the relevant assumptions in the register as "Validated," adding a note about the shared examples and clarified expectations.

This repair sequence transforms a frustrating failure into a structured learning opportunity. The register is the record of this learning, preventing the same assumption from causing future issues. The decision criteria for marking an assumption as "validated" is when the task output meets the manager's explicit expectations and both the manager and virtual assistant confirm a mutual understanding of the requirements.

Preventing future missteps: proactive assumption management

The true power of an assumption register lies in its ability to shift from reactive problem-solving to proactive prevention. Integrating assumption identification into the standard virtual assistant onboarding process creates a culture of clarity and reduces the likelihood of misunderstandings before they occur.

Consider these steps for proactive assumption management:

• Pre-onboarding preparation: Before a virtual assistant even starts, the hiring manager should spend time listing potential assumptions for the core tasks the VA will handle in their first few weeks. What common knowledge do they implicitly expect? What jargon do they use? This initial list forms the foundation of the assumption register.
• Dedicated onboarding session: During the initial onboarding period, schedule a specific session with the virtual assistant and their manager to introduce and populate the assumption register. Explain its purpose and emphasize that it is a safe space to clarify uncertainties. Encourage the virtual assistant to add any assumptions they are making about their role, the team, or the company.
• Regular check-ins: The assumption register is not a set-it-and-forget-it document. During weekly or bi-weekly check-ins between the virtual assistant and their manager, make reviewing and updating the register a standing agenda item. As the VA takes on new tasks or gains more experience, new assumptions will naturally emerge. These regular reviews help both parties refine their shared understanding.

By consistently identifying, discussing, and validating assumptions, you build a reliable shared mental model for your virtual assistant and their manager. This proactive approach reduces rework, builds confidence, and fosters a more effective, productive remote working relationship from day one.

How is an assumption register different from a standard training plan?

A training plan details what knowledge or skills need to be acquired. An assumption register identifies what beliefs both parties hold about that knowledge or skill. It doesn't replace training but complements it by surfacing implicit understandings that might undermine even well-structured training if left unaddressed.

Who is responsible for maintaining the assumption register after onboarding?

While the onboarding team may introduce it, primary ownership shifts to the virtual assistant and their direct manager. They are the daily users and beneficiaries. Regular updates should occur during their routine check-ins, with the manager holding the responsibility for so its ongoing use and relevance.

What if the virtual assistant is hesitant to state their assumptions?

Managers must actively create a safe, non-judgmental environment. Frame it as a mutual learning tool, not a test. Emphasize that asking questions and documenting assumptions prevents errors and builds efficiency. Start by sharing your own assumptions first to model the behavior.

How often should we review the assumption register with a new virtual assistant?

Initially, review the register frequently, perhaps weekly for the first month or two, as new tasks and situations arise. After the initial onboarding phase, a monthly or quarterly review during regular performance discussions is appropriate, or whenever a significant new project or responsibility is assigned.

Schedule a 30-minute meeting with your next virtual assistant hiring manager to introduce the concept of an assumption register and identify three initial assumptions for their key tasks.