Latest / The Remote Revolution / The Remote Revolution Episode 122: The Doctor Who Was Working 70-Hour Weeks — and How Remote Staff Gave Back 20 of Them

Transcript

The Remote Revolution Episode 122: The Doctor Who Was Working 70-Hour Weeks — and How Remote Staff Gave Back 20 of Them · The Remote Revolution

• 0:00
  SPEAKER_00: Hello and welcome to the Remote Revolution, a podcast by Virtual Mojo.
• 0:04
  SPEAKER_00: This is where we explore how modern businesses are transforming the way they work through remote teams, virtual support, and smarter operational strategies.
• 0:13
  SPEAKER_00: In each episode, we bring you insights, conversations, and practical ideas to help entrepreneurs, leaders, and growing companies build efficient, scalable, and future-ready organizations.
• 0:24
  SPEAKER_00: If you're looking to work smarter, scale faster, and unlock the power of remote talent, you're in the right place.
• 0:30
  SPEAKER_00: Let's begin.
• 0:31
  SPEAKER_02: Welcome to season one, episode 22 of the Remote Revolution with your host Aniki Numaima as our guest.
• 0:37
  SPEAKER_02: Today we're exploring the story of a busy physician whose workload had grown to nearly 70 hours a week.
• 0:43
  SPEAKER_02: We'll look at how strategic remote staffing helped reduce administrative pressure, reclaim valuable time, and create a more sustainable balance between patient care and practice operations.
• 0:52
  SPEAKER_02: Right.
• 0:53
  SPEAKER_02: So imagine running a highly profitable multi-million dollar medical practice, but your actual day-to-day existence is dictated by printer jams.
• 1:03
  SPEAKER_01: Yeah, printer jams and resetting passwords.
• 1:05
  SPEAKER_02: Exactly.
• 1:06
  SPEAKER_02: And rewording out-of-ice replies.
• 1:08
  SPEAKER_02: That was the hidden reality for the doctor in our source notes today.
• 1:11
  SPEAKER_02: And uh for this deep dive, our mission is to challenge a very controversial, deeply ingrained business myth.
• 1:18
  SPEAKER_01: The idea that working yourself to the bone is somehow a badge of honor.
• 1:22
  SPEAKER_02: Right.
• 1:22
  SPEAKER_02: We are looking at a stack of notes regarding this incredibly successful practice that was, you know, secretly suffocating its owner.
• 1:28
  SPEAKER_02: We want to extract actionable things to try so you don't become the bottleneck in your own life or organization.
• 1:34
  SPEAKER_01: And the disconnect between public success and private operational collapse.
• 1:40
  SPEAKER_01: Um, it's a recurring theme in the source material.
• 1:43
  SPEAKER_01: On paper, this medical practice was the picture of health.
• 1:47
  SPEAKER_02: Right.
• 1:47
  SPEAKER_02: The financials were strong.
• 1:49
  SPEAKER_01: Incredibly strong.
• 1:50
  SPEAKER_01: Patient volume was growing quarter over quarter, reputation was stellar.
• 1:54
  SPEAKER_01: Anyone looking from the outside would assume, like, oh, this operation is a well-oiled machine.
• 1:59
  SPEAKER_02: But then you look at the internal notes.
• 2:01
  SPEAKER_01: Yeah, and the operator was trapped in this perpetual cycle of firefighting.
• 2:05
  SPEAKER_01: I mean, 70 hours a week isn't just a busy schedule.
• 2:07
  SPEAKER_02: It's uh 10 hours a day, seven days a week.
• 2:09
  SPEAKER_01: Exactly.
• 2:10
  SPEAKER_01: It means zero time for strategic growth, no physical or mental recovery, and your personal life just, well, completely evaporates.
• 2:18
  SPEAKER_02: It's like an elite Michelin star chef who insists on not only cooking the meals but also um scrubbing the floors.
• 2:26
  SPEAKER_01: And answering the reservation phone.
• 2:27
  SPEAKER_01: Yeah.
• 2:28
  SPEAKER_02: And fixing the plumbing in the restroom.
• 2:29
  SPEAKER_02: We call it dedication, but isn't it actually just terrible management?
• 2:33
  SPEAKER_01: It really is.
• 2:34
  SPEAKER_01: Hustle culture often masks severe operational dysfunction.
• 2:38
  SPEAKER_01: Many professionals, um, especially founders and solo practitioners, they view those long hours as proof of their moral character.
• 2:46
  SPEAKER_02: Like a flex.
• 2:47
  SPEAKER_01: Right, a flex.
• 2:48
  SPEAKER_01: But excessive workloads are a depreciating asset.
• 2:51
  SPEAKER_01: The cognitive load of switching from a high-level medical diagnosis to, you know, arguing with an insurance provider over a billing code.
• 2:58
  SPEAKER_02: And then right back again.
• 2:59
  SPEAKER_01: Yes, and back again.
• 3:00
  SPEAKER_01: It destroys executive function.
• 3:02
  SPEAKER_01: Eventually, productivity drops off a cliff, the quality of the high-level work suffers.
• 3:07
  SPEAKER_01: Being indispensable in this manner isn't a flex, it's a systems failure.
• 3:11
  SPEAKER_02: So if we accept that this is a systems failure, we have to look at the mechanics of how to fix it.
• 3:17
  SPEAKER_02: Because the instinct for most businesses when they hit this wall of 70 hour weeks is to, well, panic higher.
• 3:23
  SPEAKER_01: Oh, absolutely.
• 3:24
  SPEAKER_01: You assume that because you're drowning in work, you just need a bigger boat.
• 3:26
  SPEAKER_02: Or more bodies in the office, right.
• 3:28
  SPEAKER_02: But realizing you're wasting time on insurance emails doesn't magically get them out of your inbox.
• 3:34
  SPEAKER_02: So before they hired anyone, they tried something vastly different.
• 3:38
  SPEAKER_02: A granular workload review.
• 3:40
  SPEAKER_01: Right, because you don't just throw money at a leaking operation.
• 3:43
  SPEAKER_01: You have to find the hole first.
• 3:45
  SPEAKER_01: The practice needed a diagnosis before prescribing a cure.
• 3:49
  SPEAKER_02: So they did a ruthless time audit.
• 3:51
  SPEAKER_01: For a couple of weeks, yeah.
• 3:52
  SPEAKER_01: And this wasn't just some vague estimation, like, oh, I spend a lot of time on emails.
• 3:57
  SPEAKER_02: No, the physician had to track their daily activities in 15-minute increments.
• 4:01
  SPEAKER_01: Right, to see where the bleeding was actually happening.
• 4:04
  SPEAKER_01: Because people frequently lie to themselves about how they spend their time.
• 4:08
  SPEAKER_01: We remember the one hour we spent saving a critical patient, but we totally block out the three hours we spent formatting a spreadsheet.
• 4:17
  SPEAKER_02: It's so true, and the numbers in the audit are staggering.
• 4:20
  SPEAKER_02: I mean, a massive percentage of this doctor's 70 hours was consumed by tasks requiring absolutely zero medical expertise.
• 4:27
  SPEAKER_01: Yeah, reviewing staff schedules, answering routine emails, managing basic patient communication, dealing with insurance claim questions, running daily reports, things literally anyone with good administrative training could do.
• 4:41
  SPEAKER_01: Valuable, highly specialized clinical hours were being eaten alive.
• 4:44
  SPEAKER_02: Hours that should have been spent with patients or developing the practice's long-term strategy.
• 4:50
  SPEAKER_01: Exactly.
• 4:50
  SPEAKER_01: When you break down the hourly rate of a specialist physician and apply it to data entry, it is catastrophic financial mismanagement.
• 4:59
  SPEAKER_02: Not to mention the personal toll it takes on the individual.
• 5:02
  SPEAKER_02: Think about your calendar yesterday or last week.
• 5:05
  SPEAKER_02: How much of your day is spent doing high value work versus just putting out operational fires?
• 5:11
  SPEAKER_01: That's the million-dollar question.
• 5:13
  SPEAKER_01: Are you doing tasks that require your specific, unique expertise?
• 5:18
  SPEAKER_02: Or are you just clearing a digital desk of low-tier problems because they happen to be in front of you?
• 5:24
  SPEAKER_01: And highly skilled professionals fall into this trap all the time because the low-tier tasks offer immediate dopamine hits.
• 5:31
  SPEAKER_02: Right.
• 5:31
  SPEAKER_02: Answering a simple email feels productive.
• 5:33
  SPEAKER_01: Fixing a scheduling conflict feels like solving a problem, but it is destructive to long-term efficiency.
• 5:39
  SPEAKER_01: The realization that they were spending 20 to 30 hours a week on tasks that didn't require a medical degree forced the practice to pivot.
• 5:46
  SPEAKER_02: But they didn't just dump these tasks on a new hire.
• 5:49
  SPEAKER_01: No, they moved to the second crucial mechanism in our notes, which is documentation before delegation.
• 5:55
  SPEAKER_02: Okay, I have to push back here because that sounds completely unrealistic on a human level.
• 6:00
  SPEAKER_01: How so?
• 6:01
  SPEAKER_02: Well, if I'm working 70 hours a week and barely keeping my head above water, someone telling me to sit down and write a standard operating procedure manual sounds like a great way to push me to an 80-hour work week.
• 6:13
  SPEAKER_02: Right.
• 6:14
  SPEAKER_02: Where does a person who is already stretched to the breaking point physically find the time to document their processes?
• 6:21
  SPEAKER_02: It's like refusing to spend five minutes sharpening at dull acts because you're too busy chopping wood, you have to slow down to speed up.
• 6:27
  SPEAKER_02: But when?
• 6:28
  SPEAKER_01: It is the ultimate paradox of productivity, and it's where most delegation attempts fail.
• 6:34
  SPEAKER_01: The practice realize that if you just hand a messy, undocumented inbox to a remote worker, they're going to fail.
• 6:41
  SPEAKER_02: You aren't delegating, you're abdicating responsibility.
• 6:43
  SPEAKER_01: Exactly.
• 6:44
  SPEAKER_01: But you are right, the friction of creating a manual is huge.
• 6:48
  SPEAKER_01: So the mechanism they used to bypass this friction was asynchronous documentation.
• 6:53
  SPEAKER_02: Meaning they didn't ask the doctor to spend their Sunday writing a textbook.
• 6:57
  SPEAKER_01: No, they utilized screen recording software.
• 7:00
  SPEAKER_02: Wait, so instead of stopping work to write about the work, they just recorded themselves doing the work they already had to do anyway.
• 7:06
  SPEAKER_01: Precisely.
• 7:06
  SPEAKER_01: When the physician had to process a specific type of complex insurance claim or, you know, format the weekly schedule, they simply hit record on their screen and narrated their thought process out loud.
• 7:18
  SPEAKER_02: Just talking through it.
• 7:20
  SPEAKER_01: Yeah, like I'm clicking here because of X.
• 7:22
  SPEAKER_01: I always check this box because of Y, and if this error popped up, here is how I resolve it.
• 7:28
  SPEAKER_01: They did this over the course of a few weeks.
• 7:30
  SPEAKER_02: So the work still got done.
• 7:31
  SPEAKER_01: Right, but a video library of standard operating procedures was being built simultaneously.
• 7:36
  SPEAKER_02: That's amazing because delegating without documenting is like giving someone the steering wheel to your car while you keep your feet on the gas and the brake.
• 7:44
  SPEAKER_01: That's a great analogy.
• 7:45
  SPEAKER_02: You haven't actually given them control, you've just made the driving infinitely more dangerous.
• 7:49
  SPEAKER_02: You're just moving the chaos from your desk to someone else's desk.
• 7:54
  SPEAKER_01: And it will inevitably bounce right back to you when they crash the car.
• 7:57
  SPEAKER_01: Technology alone doesn't create efficiency.
• 8:00
  SPEAKER_02: Right.
• 8:00
  SPEAKER_02: You can hire the smartest remote support staff in the world, but if the knowledge of how your specific practice runs only exists inside your head, delegation is literally impossible.
• 8:12
  SPEAKER_01: The video recordings became the baseline.
• 8:14
  SPEAKER_01: A remote team member could watch the video, write out the step-by-step text manual themselves, and then present it back to the physician for approval.
• 8:22
  SPEAKER_02: So the physician offloaded the actual creation of the training manual to the person being trained.
• 8:28
  SPEAKER_01: Yes.
• 8:28
  SPEAKER_02: Okay.
• 8:29
  SPEAKER_02: If the mechanics of this are as straightforward as narrating a screen recording, we have to ask why so few leaders actually pull this off.
• 8:37
  SPEAKER_01: Psychological roadblocks.
• 8:38
  SPEAKER_02: Yeah, our source material points heavily to that.
• 8:41
  SPEAKER_02: We love to convince ourselves that our email answering skills are somehow magical.
• 8:45
  SPEAKER_01: And completely unreplicable by mere mortals.
• 8:47
  SPEAKER_02: Right.
• 8:48
  SPEAKER_02: Like, oh, only I can word this out-of-office reply with the precise nuance required.
• 8:53
  SPEAKER_02: But really, only I can do it is usually just code for I haven't bothered to write the instructions down.
• 8:58
  SPEAKER_01: The ego is the single biggest bottleneck in business growth.
• 9:02
  SPEAKER_01: The notes show this physician heavily hesitated.
• 9:05
  SPEAKER_01: They feared a drop in quality control.
• 9:07
  SPEAKER_02: They worried the patient experience would suffer.
• 9:09
  SPEAKER_01: And they were terrified of losing their grip on the practice.
• 9:12
  SPEAKER_01: We build our professional identities around being the ultimate problem solver.
• 9:16
  SPEAKER_02: The hero of the office who swoops in to fix the jammed printer or salvage a scheduling conflict.
• 9:22
  SPEAKER_01: Exactly.
• 9:23
  SPEAKER_01: Relinquishing that hero status is incredibly difficult.
• 9:27
  SPEAKER_02: But how do they actually get over that fear?
• 9:29
  SPEAKER_02: Because the fear of a new remote staff member accidentally sending the wrong medical file or messing up billing is a very real tangible risk.
• 9:39
  SPEAKER_01: They mitigated the risk through a structured gradual transfer of responsibility, sometimes referred to as a shadow system.
• 9:46
  SPEAKER_02: So they didn't hand over the keys to the kingdom on day one.
• 9:49
  SPEAKER_01: No, definitely not.
• 9:50
  SPEAKER_01: For the first two weeks, the remote staff member would draft the emails or prepare the reports, but the physician had to review and hit send.
• 9:57
  SPEAKER_02: Okay, making sure it's perfect.
• 9:59
  SPEAKER_01: Right.
• 9:59
  SPEAKER_01: Once the physician saw that the remote worker was following the documented system flawlessly, the trust was established, they then moved to a system of managing by exception.
• 10:11
  SPEAKER_02: Managing by exception, meaning um the remote worker handles 95% of the routine volume and only escalates the weird, unpredictable 5% back to the doctor.
• 10:22
  SPEAKER_01: Exactly.
• 10:23
  SPEAKER_01: The routine work is heavily filtered.
• 10:25
  SPEAKER_01: And what the notes reveal is a highly counterintuitive phenomenon.
• 10:29
  SPEAKER_02: Which is.
• 10:30
  SPEAKER_01: The physician assumed that giving up tasks meant giving up control, but effective delegation actually improves visibility and control.
• 10:38
  SPEAKER_02: Wait, how does giving the steering wheel to someone else give you more control?
• 10:42
  SPEAKER_01: Think about it.
• 10:42
  SPEAKER_01: When a process lives entirely in your head, it's a black box.
• 10:45
  SPEAKER_01: Even you don't really know how long it takes or how many steps it involves.
• 10:48
  SPEAKER_02: You just do it on autopilot.
• 10:50
  SPEAKER_01: Right, based on your subjective energy levels that day.
• 10:52
  SPEAKER_01: But the moment you are forced to document it so a remote staff member can execute it, that process becomes measurable.
• 10:59
  SPEAKER_02: You can track turnaround times.
• 11:00
  SPEAKER_01: You can optimize the steps, you gain objective control over the business because it is no longer reliant on how much sleep the founder got the night before.
• 11:09
  SPEAKER_02: Ah, so you shift from executing the work to managing the system that does the work.
• 11:15
  SPEAKER_02: You aren't losing control, you are upgrading your control panel.
• 11:18
  SPEAKER_01: That's a perfect way to put it.
• 11:19
  SPEAKER_02: Let's talk about the actual tangible payoff of running these experiments by auditing the workload, capturing the processes as they happened, and systematically handing them off to targeted remote support.
• 11:31
  SPEAKER_01: That crushing 70-hour work week shrank to 50 hours.
• 11:35
  SPEAKER_02: That is wild.
• 11:36
  SPEAKER_02: Nearly a part-time job's worth of time, 20 hours, reclaimed every single week.
• 11:41
  SPEAKER_01: And you didn't get 20 hours back by working faster or by adopting some new aggressive time management philosophy.
• 11:47
  SPEAKER_02: Or by chugging more espresso.
• 11:48
  SPEAKER_02: You got it back by redesigning the flow of work itself.
• 11:52
  SPEAKER_01: The practice didn't try to squeeze more efficiency out of a human being.
• 11:55
  SPEAKER_01: They built a more efficient operational machine.
• 11:58
  SPEAKER_02: And the cascading effects noted in the source material are profound.
• 12:02
  SPEAKER_02: The physician's stress levels plummeted.
• 12:04
  SPEAKER_01: Their clinical decision making sharpened because they were no longer suffering from chronic decision fatigue.
• 12:09
  SPEAKER_02: Right, caused by micromanaging administrative trivia.
• 12:12
  SPEAKER_02: And they were finally able to exist as a human being outside of the practice walls.
• 12:17
  SPEAKER_01: What also really stands out in the documentation is the reaction of the in-house staff.
• 12:22
  SPEAKER_01: The common fear is that bringing in remote workers or heavily restructuring workflows will create resentment.
• 12:29
  SPEAKER_02: Or fear of replacement among the local team.
• 12:32
  SPEAKER_02: But the in-house staff here reported a massive increase in job satisfaction.
• 12:37
  SPEAKER_01: Because clearer workflows eliminated the operational traffic jams.
• 12:41
  SPEAKER_01: When the doctor was working 70 hours and insisting on touching every single process, they became the ultimate bottleneck.
• 12:48
  SPEAKER_02: If a nurse needed an approval or an administrator needed clarification on a complex insurance policy, they had to wait for the doctor to have a free minute.
• 12:56
  SPEAKER_01: The entire staff was constantly waiting for permission to do their jobs.
• 13:00
  SPEAKER_01: By routing those routine tasks to dedicated remote support via clear systems, the bottleneck was removed.
• 13:12
  SPEAKER_02: So we want to leave you with a diagnostic checklist based on everything we've extracted today.
• 13:16
  SPEAKER_02: If you are listening to this and you feel like taking a two-week vacation is functionally impossible because the business would burn down without your daily intervention.
• 13:25
  SPEAKER_01: You are suffering from a systems failure.
• 13:27
  SPEAKER_02: If your calendar is entirely reactive, meaning you arrive at your desk with a plan, but your entire day is immediately hijacked by endless interruptions.
• 13:36
  SPEAKER_01: Small emergencies, inbound requests, your workflows are broken.
• 13:41
  SPEAKER_02: If every single problem, no matter how trivial, eventually lands on your desk for a final decision, you have abdicated your responsibility to build a self-sustaining team.
• 13:50
  SPEAKER_01: And critically, if you spend a significant portion of your day doing tasks that are drastically below your actual level of specialized expertise, you are actively harming the growth of your organization.
• 14:01
  SPEAKER_02: To quickly recap the actionable things to try, first, audit your time ruthlessly for one week and 15-minute increments.
• 14:08
  SPEAKER_02: Second, isolate the low-value routine tasks from your specialized high-value work.
• 14:13
  SPEAKER_01: Third, bypass the friction of documentation by recording yourself doing the work asynchronously.
• 14:18
  SPEAKER_02: And finally, utilize remote staff to take over those systems gradually, building trust through a shadow system.
• 14:26
  SPEAKER_02: Growth should not require sacrificing your life indefinitely.
• 14:30
  SPEAKER_01: We've talked about how reclaiming those 20 hours saved this doctor from burnout, but consider this.
• 14:35
  SPEAKER_01: If you suddenly got 20 hours back next week, because you finally documented and delegated your routine tasks, would you actually know what to do with that freedom?
• 14:45
  SPEAKER_02: That's a heavy question.
• 14:46
  SPEAKER_01: Right.
• 14:47
  SPEAKER_01: Or has being too busy become a comfortable place to hide from doing the truly challenging, high-level strategic work you know you should be focusing on.
• 14:54
  SPEAKER_02: Are you holding on to the mob because you're afraid to actually run the restaurant?
• 14:58
  SPEAKER_02: Something to think about as you review your calendar this week.
• 15:01
  SPEAKER_02: Thanks for joining us on this deep dive, and we'll catch you next time.
• 15:04
  SPEAKER_00: Thank you for listening to the Remote Revolution.
• 15:06
  SPEAKER_00: If you enjoyed this episode, make sure to subscribe and share it with other professionals who are building the future of work.
• 15:12
  SPEAKER_00: To learn more about how VirtualMojo helps businesses grow with highly trained virtual assistants and remote support teams, visit www.virtualmojo.com.
• 15:22
  SPEAKER_00: For inquiries or collaborations, reach out to us at contact at virtualmojo.com.
• 15:28
  SPEAKER_00: Until next time, keep building smarter systems and embracing the future of work.