Becoming an Operations Lead.

Also posted as

Operations manager, OBM, chief of staff, delivery manager, integrator

The shift

From "did you get my message" to "here is the number and what I am doing about it"

Core loop

Map, document, measure, delegate, review

What you stop doing

Being the fastest hands. That is now somebody else's job and your responsibility

Hardest part

Holding someone else to a standard when you could just do it yourself in ten minutes

Progress is saved in this browser only. Nothing is sent anywhere.

1. 01

   The shift from tasks to outcomes

   You can describe your job as a set of outcomes you are accountable for, and you know which behaviours you have to give up.Time splitRatesRed/green flags24 min

   • A VA is measured on whether they did what was asked. An ops lead is measured on whether the thing worked, including when nobody asked.
   • The first behaviour to drop is waiting. If you find yourself thinking "I told them and they did not reply", that is now your unresolved problem, not theirs.
   • The second is heroics. Fixing a broken process yourself at 11pm feels like ownership and is actually the thing preventing the fix.
   • Claim the role deliberately. The transition guidance from people who train OBMs is consistent: many VAs are already doing operations work and stay underpaid because they never renamed what they do or asked to be paid for it.
   • Outcomes must be countable or dated. "Improve client onboarding" is not an outcome. "Every new client is live within five business days" is.
   • You will feel less productive for about a month. Your output moves from things you made to things other people shipped, and that shows up later.

   Worked example — The same job, rewritten as outcomes

   Before

   Manage the project board

   Follow up with contractors

   Send the weekly report

   Onboard new clients

   Help with anything else needed

   After

   Every active project has an owner and a next action, checked daily. Target: zero stale cards over 3 days.

   Contractor deliverables land by the agreed date. Target: 90 percent on time, measured monthly.

   The founder gets a decision-ready report every Friday by 9am, without asking.

   New clients are fully live within 5 business days of signing. Target: median 4 days.

   Anything outside these four is a change request with a time estimate, not "anything else needed".

   The second list can be graded by someone who was not in the room. That is the whole difference, and it is also why it pays more.

   Where the hours go

   How an ops lead's week differs from a senior VA's

   The same 40 hours, redistributed. Notice the largest slice is now other people's work rather than your own.

   • Managing people: 1:1s, reviews, unblocking26%

     The job you didn't apply for and now can't avoid. Get good at it.

   • Systems: building and fixing processes22%

     The actual product. Every hour here saves someone ten later.

   • Measuring and reporting16%

     You can't run what you can't see, and the founder decides based on what you show them.

   • Managing upward and stakeholders14%

     Underrated. Most ops people fail here, not on the operations.

   • Doing the work yourself12%

     Should keep shrinking. If it's growing, you're a senior VA with a title.

   • Hiring and onboarding10%

     Bursty, and the highest-consequence thing on this list.

   Only 12% is you doing tasks. The hardest part of this transition is emotional — task completion feels productive, and you have to give up that feeling to do the job you're now paid for.

   What this pays

   What ops leadership pays

   This is the top of the ladder that starts at $3/hr data entry. The jump from senior VA to ops lead is the largest single pay step in this career, and it's about scope of responsibility, not hours.

   Swipe the table sideways →

   Experience	Hourly (USD)	Monthly (USD)	What changes it
   Senior VA (owns their own work)	$11–16	$1,800–2,600	Reliable, unsupervised, deep in one lane. The launchpad.
   Ops coordinator	$13–18	$2,100–2,900	You own a process end to end and other people follow it.
   Ops manager	$16–24	$2,600–3,900	You manage 2–5 people and own a set of numbers. First real management role.
   Ops lead / head of ops	$20–32	$3,200–5,200	You own the operating rhythm of the whole company. You're in the strategy conversations.
   Fractional ops (2–3 clients)	$30–60	$1,500–3,000 per client	The highest-earning shape. Sell 10 hrs/week to three companies, not 40 to one.

   This table has 4 columns and scrolls horizontally on small screens.

   Same skill, different client

   • Verse's job board (ops/PM median)$5.40

     But the top of that range reaches $29/hr. Ops posts have the widest spread on the whole board.

   • Promoted internally+30–60%

     The most common path, and usually the easiest. Become indispensable, then ask.

   • Hired directly as ops$18–30

     Needs a portfolio of systems you've built. This course is that portfolio.

   • Fractional / consulting$30–60

     Highest ceiling, most instability. Do it after you've done it in-house once.

   Sources: Verse's live board (ops/PM listings show the widest range of any category), plus 2026 offshore ops rate benchmarks. The spread is enormous because 'ops' means both 'admin with a nicer title' and 'runs the company'.

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   You've been promoted to ops lead and something urgent breaks

   Red flag

   Rolling up your sleeves and fixing it yourself at 11pm, because you're fastest and it needs doing. Then doing the same next week, and the week after.

   This feels like leadership and is the opposite. You've taught the team that escalation means you'll absorb it, guaranteed yourself a second full-time job, and learned nothing about why it broke.

   Green flag

   Fix it with the person whose job it is, on a call, while they drive. Then the next day: "Why did this reach us at 11pm? What would have caught it at 4pm?" Change the process, not just the outcome.

   The failure gets fixed AND the class of failure gets fixed. Your value isn't that you can do everyone's job faster — it's that problems stop recurring.

   Do this

   Rewrite your current job description, real or imagined, as four to six outcomes with a target attached to each.

   Hand in: A one-page outcomes list you would be comfortable being reviewed against.≈ 40 min

   Check before you call it done

   • Every outcome has a number or a date
   • None of them begin with the words manage, help, or assist
   • You deleted or converted the catch-all line
   • You could be graded on this list by a stranger

   Mark module done
2. 02

   Map the business before you change it

   You can produce a process inventory that shows where work enters, where it stalls, and where money leaks.Workflow1 template30 min

   • You cannot improve what you cannot see. Before touching anything, list every recurring process, who runs it, how often, and what it produces.
   • Follow the money and the customer. Map lead to cash: enquiry, quote, sale, delivery, invoice, payment, review. Most of the damage is in the handoffs between those steps.
   • Every handoff is a place work can die. Count them, then ask what happens if the person on the receiving end is on leave.
   • Look for the four classic leaks: work waiting on one person, work done twice, work with no owner, and work nobody checks.
   • Ask each person the same two questions: what takes longer than it should, and what do you redo most often. You will get the real map in an afternoon.
   • Rank by cost, not by annoyance. The loudest complaint is rarely the most expensive problem.

   Worked example — Wilder and Co: lead to cash, with the leaks marked

   1. Enquiry lands in a shared inbox. Nobody owns the inbox. LEAK: median first reply 19 hours.

   2. Account manager writes a quote from scratch each time. LEAK: the same six services re-priced by hand, inconsistently.

   3. Client signs by email reply. No countersignature, no start date recorded. LEAK: onboarding starts whenever someone notices.

   4. Work assigned in Slack DMs. LEAK: no board, so nothing is visible when someone is sick.

   5. Delivery reviewed by the founder personally. LEAK: single point of failure, average 3-day wait for approval.

   6. Invoice raised manually at month end from memory. LEAK: two projects last quarter were never invoiced at all.

   7. No review request is ever sent. LEAK: 4 reviews in 18 months for a company that finishes 15 jobs a month.

   Ranked by cost: step 6 first, it is literal lost revenue. Then step 1, then step 5.

   Seven steps, seven leaks, and the most expensive one had never been mentioned by anybody because nobody could see the whole line.

   Workflow

   Mapping a business in your first 30 days

   New ops role, or a promotion into one. Resist the urge to change anything yet.

   1. 1

      Change nothing for two weeks. Just watch.

      Every obviously stupid process has a reason. Change it before you know the reason and you'll break something invisible and lose credibility in week three.

   2. 2

      Follow the money end to end

      How does a stranger become a customer, and how does the cash arrive? Walk the whole path. Everything else is downstream of this.

   3. 3

      Ask everyone the same four questions

      What takes longest? What do you redo most? What do you wait on? What breaks when you're off? The overlaps between people's answers are your real backlog.

   4. 4

      Find the single points of failure

      Which processes live only in one person's head? Which tool has one admin? Which client only talks to one person? Write the list. It's usually alarming.

   5. 5

      Draw the actual process, not the official one

      There's always a gap between the documented flow and what people really do. The gap IS the finding — people route around processes for reasons.

   6. 6

      Present findings before proposals

      "Here's what I see" earns trust. "Here's what you're doing wrong" earns resistance. Get agreement on the diagnosis before you offer a cure.

   Where this breaks: Arriving with a plan from your last job. Every business is weird in its own specific way, and the fastest route to being ignored is proposing solutions to problems this company doesn't have.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Process discovery interview

   Run with every person in the business, 30 minutes each. Same questions, so you can compare answers.

   Copy template to clipboard

   PERSON: [name, role] | Date: [date]
   
   THEIR WORK
   1. Walk me through a normal day. Start to finish.
   2. What's the thing you do most often?
   3. What takes the longest, and what makes it take that long?
   
   WHERE IT HURTS
   4. What do you find yourself redoing?
   5. What are you usually waiting on, and who from?
   6. What breaks when you're on leave?
   7. What's the thing that would make you actually happy if it went away?
   8. What do people ask you that they could find out themselves?
   
   THE HIDDEN STUFF
   9. Is there anything you do differently from how it's officially supposed to be done?
      [Ask gently. Promise you're not policing. This answer is usually the single most valuable thing in the interview.]
   10. What's the workaround everyone knows about?
   11. What did someone try to change before that didn't work? Why not?
   
   TOOLS
   12. What do you use daily? What do you hate about it?
   13. Anything you're paying for and not using?
   14. What are you doing in a spreadsheet that probably shouldn't be?
   
   CLOSING
   15. If you could change one thing, what?
   16. Who else should I talk to?
   
   AFTER EVERY INTERVIEW, NOTE:
   • Their #1 pain in their own words: "[quote]"
   • Single point of failure risk: [what only they know]
   • Quick win I spotted: [something fixable in under a day]
   
   AFTER ALL INTERVIEWS — look for these patterns
   • The same pain named by 3+ people → that's your first project
   • A process nobody describes the same way → it isn't documented, it's folklore
   • A tool everyone complains about → check the contract renewal date
   • A person named as a blocker by several people → usually overloaded, not obstructive

   Do this

   Map lead to cash for a business you know, real or the Wilder and Co scenario. Mark every handoff and every leak, then rank by cost.

   Hand in: A one-page process map plus a ranked leak list with an estimated cost for the top three.≈ 60 min

   Check before you call it done

   • Every step names an owner, even if the answer is nobody
   • Handoffs are explicitly marked
   • The ranking is by cost, with your estimate shown
   • You noted at least one process that exists only in one person's head

   Mark module done
3. 03

   The SOP library

   You can build documentation that people actually use, and you know why most SOP projects die.WorkflowTools1 template30 min

   • SOP projects fail for three reasons: they were written all at once, they live somewhere nobody opens, and nobody owns keeping them true.
   • Write them in the flow of work. The person doing the task writes the draft the second time they do it, and you edit. Never assign someone a week of writing documentation.
   • Link the SOP from the task, not from a folder. If reaching the document takes more than one click from where the work happens, it will not be read.
   • Every SOP needs an owner and a review date. An SOP nobody owns becomes wrong within three months and then actively harmful.
   • Pair the doc with a Loom. Reading suits some people, watching suits others, and the recording takes four minutes to make.
   • Test by handing it to someone who has never done the task. If they can complete it without messaging you, it is finished. If they ask one question, that question is the missing step.

   Worked example — The SOP header that keeps a library alive

   Title: Monthly invoicing run, Wilder and Co

   Owner: Ops lead. Reviewed: 1 Aug 2026. Next review: 1 Nov 2026.

   Purpose: every completed project is invoiced within 3 business days of month end. No project ever goes unbilled.

   Trigger: last working day of the month, 9am.

   Prerequisites: access to the delivery board, QuickBooks, and the signed scope folder.

   Steps: numbered, one verb each, with screenshots.

   Failure branch: if a project has no signed scope on file, do not invoice. Flag it to the account manager and log it in the Exceptions tab that day.

   Done when: every card in Delivered has an invoice number recorded, and the Exceptions tab is empty or explained.

   Loom: 4 minutes, linked at the top.

   The owner line and the review date are what separate a living library from a graveyard of documents written in one enthusiastic weekend.

   Workflow

   Building an SOP library people actually use

   Once you've mapped the business. Prioritise ruthlessly — you cannot document everything.

   1. 1

      Rank by (frequency × pain × bus-factor)

      Document the daily thing only one person knows first. Not the annual thing everyone can do.

   2. 2

      Have the person who does it write the first draft

      You edit. This is faster, more accurate, and it means they own it rather than resenting your version of their job.

   3. 3

      Test it on someone who's never done the task

      The real test. If they can complete it without asking a question, it works. If they ask three questions, those three answers are what's missing.

   4. 4

      Store everything in ONE place with a naming convention

      Six SOPs in one findable folder beat sixty scattered across Drive, Notion and someone's desktop.

   5. 5

      Put a review date and an owner on every single one

      An SOP with no owner rots. A rotten SOP is worse than none because people follow it into a wall.

   6. 6

      Make following them the default, visibly

      Link the SOP in the task. Reference it in the 1:1. If you don't use them yourself, nobody else will either.

   Where this breaks: Spending six weeks building a beautiful library that nobody opens. Documentation that isn't linked from where the work happens is a filing cabinet in a locked room.

   Tool comparison

   Where to put the documentation

   The tool matters far less than the discipline. But pick badly and you add friction to something already unpopular.

   Swipe the table sideways →

   Tool	Best for	Learning curve	Cost	Verdict
   NotionLearn first	Most small teams. Databases, templates, and a search that works.	Easy — a weekend	Free tier, $10/user/mo	Best default for a company under 50 people. Build one SOP database with owner, review date and status as properties, and you have a management system, not a folder.
   Google Docs + Drive	Teams already deep in Workspace who won't adopt anything new.	None	Free	Underrated. A well-named Drive folder with a single index doc beats an abandoned Notion. Adoption beats features.
   LoomLearn first	Anything faster to show than to write.	Instant	Free tier	Pair every fiddly SOP with a 2-minute video. Video plus a five-bullet checklist is the highest-adoption format there is.
   Scribe / Tango	Auto-generating click-by-click guides with screenshots.	Instant	Free tier	Genuinely magic for software walkthroughs — records your clicks and writes the steps. Cuts SOP writing time by more than half.
   Slite / Confluence	Larger orgs with compliance requirements.	Medium	$8–15/user/mo	Only if you're required to. Heavier than a small team needs and adoption suffers accordingly.
   ClickUp / Asana docs	Keeping the SOP inside the task tool.	Easy if you already use it	Bundled	Real advantage: the SOP sits where the work happens. Real risk: it's mediocre as a document tool. Fine for short procedures.

   This table has 5 columns and scrolls horizontally on small screens.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   SOP library index

   One table, the front door to everything. Without an index, a library is a pile.

   Copy template to clipboard

   #	Process	Owner	Frequency	Bus factor	Last reviewed	Review due	Status	Link
   01	Client onboarding	Maria	Per new client	1 ⚠	Mar 2026	Sep 2026	Live	[link]
   02	Weekly invoicing	Ben	Weekly	2	Feb 2026	Aug 2026	Live	[link]
   03	Monthly reporting	Me	Monthly	1 ⚠	Mar 2026	Jun 2026	Draft	[link]
   04	New VA onboarding	Me	Ad hoc	1 ⚠	—	—	Not written	—

   BUS FACTOR = how many people could do this if someone vanished tomorrow.
   Anything at 1 is a live risk to the business. Fix those first, in frequency order.
   
   PRIORITISATION SCORE = frequency × pain × (4 − bus factor)
   Score everything, sort descending, work down the list. It stops you documenting
   the interesting thing instead of the important thing.
   
   RULES
   • Every SOP has ONE named owner. Not a team. A person.
   • Review date on every one — 6 months default, 3 for anything volatile
   • Status: Not written → Draft → Tested → Live → Needs update
   • "Tested" means someone who'd never done it followed it successfully
   • Anything not reviewed in 12 months gets archived, not left to mislead people

   Do this

   Write two SOPs for your mapped process, using the header format. Then have someone unfamiliar run one and note every question they ask.

   Hand in: Two SOPs, one tested, plus a list of the gaps the tester found.≈ 75 min

   Check before you call it done

   • Both have an owner and a review date
   • Both have a failure branch
   • The tester completed the task without messaging you, or you fixed the step that made them
   • Each is linked from the actual task or board it belongs to

   Mark module done