How to Train a Remote EA or Operations Coordinator

Most founders who ask how to train a remote EA are asking the wrong question. They are looking for a documentation system, a course, a set of SOPs, some technical solution to the training problem. The actual training of a senior operator is not primarily about documentation. It is about feedback, judgment transfer, and building the relationship that lets the operator absorb your standards and apply them autonomously.

The right mental model is closer to apprenticeship. The operator learns from real work, real feedback on that work, and gradual expansion of scope as judgment develops. This happens over months, not days, and it never fully stops. The founders who succeed at this view training as a permanent part of how they work with their operators, not a phase that ends.

Context documents, short notes on the people, partners, and clients the operator interacts with. Not org charts. Useful context. 'Tom is the head of sales at our biggest customer. He prefers direct communication, hates BCCs.'

Decision rules, the specific decisions you want made the same way every time. Process guides for recurring work. Voice and style guides for how you communicate.

What does not matter as much: long-form 20-page SOPs that get read once and ignored. Generic 'how to be an EA' training. Short, specific, and frequently used beats long, comprehensive, and shelved every time.

A specific tactic worth calling out separately: video documentation outperforms written documentation for most training scenarios, and senior remote operators absorb it faster.

The setup is simple. When you have a recurring decision pattern or process that the operator needs to learn, record yourself doing it. Talk through what you are doing, why, and what the edge cases are. Save the video in a shared library. Five to ten minutes is the sweet spot.

What works well for video: how you triage your inbox, how you decide which meetings to accept or decline, how you handle a specific recurring report or analysis, how you onboard a new client or vendor, and how you run a particular type of meeting.

What does not work as well for video: decision rules that are short and crisp (those should be written), reference data like contact details, account numbers, or standing preferences (also written), and anything that needs to be quickly searchable later.

The combination that works best is short written reference for crisp facts and rules, video for context-heavy how-it-works walkthroughs. Most senior operators say they retain video walkthroughs much better than long written documents.

Tools that make this easy: Loom for screen and webcam recording, Tella for slightly more polished video, or just QuickTime or the macOS screen recorder for simplicity. The technical setup does not matter much. What matters is that the founder actually does it.

Daily micro-feedback. When the operator does something well or something off, mention it briefly in the moment. This takes 30 seconds per instance and compounds over weeks.

Weekly structured feedback in the one-on-one. What worked. What did not. What you want to see more of. Be specific. Generic feedback like 'you did great this week' gives the operator nothing to work with.

Monthly pattern feedback and quarterly career feedback. The biggest mistake is doing none of these. The second biggest is doing them inconsistently. The third is making feedback only negative.

Documentation cannot teach judgment. Reading about how to handle a situation does not develop the instinct to handle the situation well. Judgment transfers through real work, real consequences, and real conversation about what worked and what did not.

The operator handles a real situation. You let the decision play out, even if you would have made a different one. Afterward, you debrief together. The conversation is not about pointing out their mistake, it is about surfacing the reasoning behind a decision and comparing it to a more experienced reasoning pattern. Done over enough situations, their judgment converges on yours.

Write SOPs for work that happens often enough, monthly, weekly, recurring. Not one-off situations. Have the operator write the SOP. An SOP written by the operator is followed. An SOP written by the founder and handed down is ignored.

Keep SOPs short, two pages maximum. Update SOPs when they break. Review them quarterly. Treat them as living documents, not stone tablets.

How you handle mistakes is one of the most important parts of training a senior operator. Done well, mistakes become accelerators of judgment. Done poorly, they damage the relationship without producing learning.

The pattern that works:

Acknowledge the mistake matter-of-factly. Do not soften it into nothing, do not amplify it into a bigger deal than it is. "That email was sent to the wrong person. Let's talk through what happened."

Ask before telling. Let the operator walk through their reasoning before you give yours. What did they think they were doing? What information did they have? What were they trying to optimize for? This surfaces the actual gap in judgment, which often is different from what you assumed.

Share your reasoning. Now you walk through how you would have approached it. Not what you would have done, but how you would have thought about it. The "how to think" is what transfers; the "what to do" is just this one example.

Codify the learning. If the mistake was based on a pattern that will recur, update the relevant documentation or decision rule. If it was a one-off, just note the learning and move on.

Move on. Once the conversation is done, the mistake is closed. Do not bring it up again. Do not let it color your view of the operator going forward. Senior operators make mistakes, just like you do. The relationship that lets mistakes happen without long-term damage is the one that lasts.

The pattern to avoid: treating every mistake as a major event, building a mental file of every error, or letting frustration leak into the regular working relationship. Operators read this and start hiding mistakes rather than surfacing them. Once that dynamic sets in, the relationship is functionally over.

The operator needs to be fluent in the specific tools your business uses, HubSpot, ClickUp, Slack, whatever it is. The right approach is recorded walkthroughs of how you use each tool, what conventions matter, and what they should never touch. A 15-minute Loom is worth more than a written guide.

If they are unfamiliar with a tool you use, give them time and access to learn it. Most senior operators pick up new tools fast. The constraint is access and time, not capability.

A remote operator who only knows you ends up isolated. A remote operator who knows your team, key partners, and top clients ends up embedded.

In the first 90 days, introduce the operator to everyone they will interact with, real 15-minute video calls, not just Slack hellos. After 90 days, encourage them to build their own relationships. Founders who isolate their remote operator by routing every interaction through themselves end up with operators who never reach full effectiveness.

Senior operators get sick. They take vacation. They have family emergencies. From around month six onward, document the work in enough detail that another person could cover the operator for a week.

The other side is encouraging the operator to take their leave. Operators who never take vacation burn out and leave the role within two years. Treating coverage as a shared planning problem keeps them rested and engaged.

The best-trained remote operators are the ones whose work includes built-in learning, not the ones whose training is a separate activity from the work.

Specific practices that build learning into the work:

Weekly retro of one decision. In the weekly one-on-one, pick one decision the operator made in the past week and walk through it together. Not to evaluate it positively or negatively, but to surface the reasoning and compare it to your reasoning. Over a year, that is fifty deep judgment conversations. The cumulative effect is enormous.

Monthly anti-pattern review. Once a month, identify a pattern of decisions that did not go well, even if individually they were fine. Are we consistently saying yes to meetings that should be no? Are we under-prioritizing one type of communication? Are we missing follow-ups in a specific category? Surface the pattern, design a fix, implement it.

Quarterly skill stretch. Each quarter, identify one area where the operator wants to grow and design a small project that stretches them in that direction. Owning a new function, running a meeting they have not run before, taking responsibility for a new metric. Growth happens through stretch, not through repetition.

Annual scope expansion. Once a year, formally review the role. What has the operator outgrown? What new scope makes sense? What old responsibilities should be transitioned to someone else? This conversation prevents the role from going stale.

These four practices add maybe two hours per month to the management cadence. The return is an operator whose judgment is constantly sharpening and who is constantly seeing a path forward in the role. Both of these compound over years.

Expanded scope over years, year one is calendar and inbox, year two adds vendor and project work, year three adds team-wide operations coordination or chief-of-staff lite responsibilities. Compensation growth of 5–15% per year for performing operators, with larger jumps when scope expands meaningfully.

Title growth that reflects real authority changes. Leadership opportunities managing junior operators. Equity where possible for long-term hires in early-stage businesses. Founders who treat their EA hire as a long-term partnership keep good operators for years.

Too much documentation, not enough conversation. Feedback withheld out of misplaced kindness. No structured feedback cadence. Flat growth path. Treating training as a phase that ends after the first three months.

The first three months are intensive. Months 4–6 are still intensive but lighter. Months 7–12 are steady-state collaboration. Year two and beyond, the relationship is a partnership, the operator is a colleague more than a hire. This is the long arc that the founders who get training right end up on.

A useful set of leading indicators that the training is producing the right outcomes:

The operator is making decisions faster. In month one, every decision had a check-in. In month six, decisions are happening without you. In month twelve, the operator is making decisions you would not have made the same way, and most of the time they are correct.

The operator is disagreeing with you more often. This is counterintuitive but real. A trained operator with strong judgment will disagree with you. They will point out things you are missing. They will tell you when you are about to do something dumb. This is what trained judgment looks like. Operators who never disagree are either deferential by nature or have not yet developed the judgment to spot when you are wrong.

The operator is teaching you. A year into a strong relationship, the operator will surface things about your business you did not know. Patterns in customer behavior. Issues with vendors. Friction in processes. They are now an information source, not just an executor. This is the highest signal that training is working.

Other people on the team trust the operator. When team members start treating the operator as a credible source on your behalf, not just a messenger from you, the operator has built their own standing in the business. This is a multiplier on every other contribution they make.

The operator is taking initiative without prompting. They are suggesting improvements, flagging issues before being asked, proposing new ways of doing things. This is the difference between an executor and an operator.

If you see these signs by month nine to twelve, the training has worked. If you do not, something in the system needs to change. Either the operator's seniority does not match the role, or the training cadence is not consistent enough to produce these outcomes.