A Good Hire Still Needs an Operator

An overtime request arrives because work has backed up. Christer Umali, Ten80Ten’s Managing Partner, does not treat the extra hours as the answer. He asks how many items are waiting, caps the time, and requires another count when the work ends.

The scene is a composite. What matters is the operating choice. The operator ties extra time to a visible change. If the backlog falls, the team learns how much capacity the work needs. If it does not, more hours may only hide a broken route.

The choice tells you more about the operating job than a biography could. I first worked under Christer in 2021, and I now work beside him at Ten80Ten. He runs operations and client relationships. I build the software and automation that support them. Those roles meet after a VA starts, when a job that looked settled on paper begins changing under real demand.

Placement fills a role once. Client operations keeps the role useful as the work changes.

Qualitative role chart / 01

A live role drifts. A review brings the agreement back to the work.

• Expected work
• Actual work
• Role gap

1. 01 Launch

   The brief and the work agree.

2. 02 First signal

   A backlog or recurring exception appears.

3. 03 Role gap

   Workload and responsibility outgrow the brief.

4. 04 Operator review

   Measure, workload, authority, and agreement are reset.

5. 05 Renewed role

   The next scope is explicit.

The live role starts moving

A placement begins with a brief. The client names the work, the hours, the tools, and the result they expect. Recruiting finds a person who can carry it. Onboarding turns the brief into access and a starting routine.

Then the job meets Monday morning. The client remembers a recurring report that never reached the role description. One inbox produces more exceptions than anyone expected. A weekly meeting creates follow-up work across the rest of the week. The VA becomes the person who knows where a customer commitment sits, so people begin routing more of the account through them.

None of this automatically means the original brief was careless. A role becomes visible through use. The first weeks reveal where work really comes from and which decisions repeat. They expose work nobody had named.

Choosing work a virtual assistant can own is the owner’s first responsibility. Once the handoff is live, the staffing partner has a different one. Someone must compare what the VA now carries with the scope and measures everyone agreed on.

The operator works inside that gap. A client request may look small inside one message, then change the role every week. Client operations asks what the request adds, what it replaces, and what it changes for the VA. A new recurring responsibility may need more time. It may need access that the role never received, or authority to close a decision that keeps returning for approval. Sometimes the answer is a clearer instruction. Sometimes the role itself has changed.

Without that distinction, every addition looks small on the day it arrives. A report joins the routine, then another inbox follows. Soon another meeting claims part of every week. Months later, the person carries a different job while the client still believes the first brief describes it.

Work moved. The agreement did not.

The workflow must fit the work

One productivity score cannot describe every role. It flattens the parts that matter.

A coverage role exists so somebody is present when work arrives. Ask whether the team covered the agreed hours and responded to incoming work on time. Then check whether each handoff or exception reached an owner. A production role needs different proof. Count completed work. Measure accuracy. Track rework and the age of the queue.

Client management needs another kind of proof. The person keeps commitments from disappearing between conversations. They identify the next decision and follow up with its owner. They also preserve enough context that the client does not have to rebuild the account from memory. Counting sent messages would reward noise while missing the relationship work.

The review matches proof to responsibility. Use a few measures that both parties can understand and question, not one company-wide score.

This is where operations and software must keep their roles straight. I can build a shared operations record that shows workload and ownership without sending everyone back through old messages. It can also flag exceptions. The system can preserve the count. It cannot decide what a good count means for a specific client relationship. That judgment belongs with the operator close enough to know why the number changed.

The same design protects the VA. A vague standard lets a quiet day look unproductive and a noisy day look valuable. A role-specific measure defines good work before a review. When circumstances change, it gives the person a concrete record to bring into the conversation. The same rule shapes monitoring records that protect the worker too: evidence should work in both directions.

The client sees the work without hovering. The VA gets a fair definition of the job. The same measure serves both.

Review the role before judging the person

Consider a composite role that begins with administrative coordination. The assignment is clear: keep a shared inbox current and prepare a recurring report. Route unusual decisions to the client.

The person proves dependable. Soon they coordinate requests across teams and maintain the source documents behind the report. They also carry follow-up after client calls. Colleagues go to them because they know the history. The person still completes the original tasks, but the role now depends on their memory of past calls, source documents, and which promise belongs to whom when the next request arrives.

The wrong review asks whether the person can keep up. A useful review asks what they are actually responsible for.

That question changes the remedy. If the work is temporary, the role may need short-term capacity and a clear end. If the added responsibility will stay, the client and staffing partner need to correct the scope. The person may need more authority or a better measure. The role may also need a revised workload. When the value and responsibility have materially changed, compensation belongs in the same review.

The point is not to turn every busy week into a negotiation. Live work surges. A one-time deadline can justify a bounded response, like the overtime decision in the opening. A repeated obligation is different. Once the same added responsibility survives several cycles, the operating agreement should stop pretending it is an exception.

The correction protects the client too. They keep someone who understands the work and the history behind each commitment. They also see the cost of new capacity before the role starts to strain. Replacing somebody after months of quiet expansion would lose context that no job description contains.

The VA gets the same clarity. They know which results and decisions they own. They also know how the company will judge the expanded job. The added responsibility gets written into the job instead of arriving as an endless reward for being dependable.

This makes the Ten80Ten middle real. Ownership cannot mean absorbing every new request without review. It means carrying the agreed work through its middle, then reopening the agreement when the middle becomes a different job.

The operator cannot become the whole process

Hands-on judgment catches context that a process cannot. It can also make one desk the place where every unusual question waits.

If all client history lives in one operator’s head, the operation works only while that person is available. The answer is not to remove hands-on judgment from the relationship. It is to move repeated judgment into a shared working rule.

A recurring workload review should leave behind the measure that matters and the condition that triggers another review. The agreement should also record the authority it grants the role. A repeated exception should get an owner and a normal route. When a private conversation changes the work, the operating effect belongs in the team record even if the personal reason stays private.

The operator keeps decisions that depend on a client relationship or an unusual circumstance. The shared process carries decisions that have become ordinary. That split keeps attention where it changes the outcome without making one person the route for everything.

When the backlog returns to its normal count, the numbers no longer describe a rescue. They show what the role can carry with the right scope and capacity.

The next question is what the person is ready to own.

Frequently asked questions

Why does a good hire still need an operator?

A good hire still needs an operator because a role changes after it meets real work. The operator compares the live workload with the agreed scope, checks whether the measure still fits, and brings authority, capacity, or expectations back into alignment before a dependable person becomes the workaround for a broken process.

What happens after Ten80Ten places a virtual assistant?

Ten80Ten stays involved after the hire through onboarding, client check-ins, workload review, and role adjustments. Each review checks the live work against its scope, workload, and measure. It also keeps the client’s expectations attached to the job rather than treating placement as the end of the service.

How should a client measure a virtual assistant?

Match the measure to the responsibility the VA owns. Coverage work needs proof that the team covered the schedule, responded to incoming work, and routed each handoff. Production work needs proof of output and accuracy, with rework tracked separately. Client-management work needs visible commitments and a named owner for each exception. Hours and activity can support the record. Neither is a universal verdict.

When should a virtual assistant’s role or rate be reviewed?

Review the role when added responsibilities repeat, workload changes for more than a short surge, decision authority expands, or the person now carries business continuity that was absent from the original brief. Compare the live job with the agreed scope, then correct anything that no longer fits: workload, authority, measurement, or compensation.