How to Remove Yourself from Operations & Build a Self-Running Team

Everything comes down to training quality. If you train team members poorly, unless they're absolute A-players, they simply won't perform. Here's what we've found works best.

Get Buy-In First

People need to understand why they're doing something. Just writing the reason at the top of your SOP isn't enough - you need to sell them on it. The same way you sell customers into working with your company, you need to sell your team on why this matters.

Break down the process in front of them. Show how everything ties together and what the consequences are when things aren't done right.

Progressive Reasoning with Relatable Analogies

When coaching someone on something complex, explain it in progressive, reasonable steps with constant confirmation they understand. Use relatable analogies to create a mental movie that makes it easy to see the whole picture.

Here's how progressive reasoning works in practice. Start with common ground everyone agrees on, then build from there:

Turn Data Into Stories

If you're very logical and try to explain things with reasoning and data, this will be a massive tipping point: break down data into stories.

The "I Do, We Do, You Do" Method

Think about how you learned to walk as a kid. An adult walked around, you watched. Then they held your hands and walked with you. Then you tried alone and got feedback - you fell or you didn't.

This sounds time-intensive but it's actually fast. Show them quickly, they do it in front of you, you check the output. Done.

This is where you actually remove yourself from the picture and let pre-written instructions do the work. The problem? Most company SOPs absolutely suck. They're too long, too complex, too boring - nobody wants to engage with them.

Write SOPs the Way You Speak

Have a training call doing everything I mentioned above, record it with a notetaker app (I use Fathom), then have GPT turn that transcript into an SOP. This is real - I do this for all our SOPs.

The output should be very straightforward: step one, do this; step two, click here; step three, enter this. One bullet at a time. Don't burst a lot of information at once - it's like fighting. You don't throw all your punches at once against a pro. One calculated hit at a time.

Match Detail Level to Talent Level

Include Troubleshooting Instructions

You want team members to solve problems without running to a manager every time they hit a bump. At the bottom of every SOP, include troubleshooting steps:

Now that you know how to write SOPs, you need to guarantee quality output. This requires feedback loops and approval systems.

Track Manager Intervention

Every time someone has a question on an SOP, log it. You want manager intervention below 10% weekly. If it's higher, your processes are broken or your team doesn't have buy-in.

Track: How many tasks were accomplished? How many needed manager intervention? How many errors occurred? Every error is an opportunity to improve the system.

The Three Types of Approval Points

Use Forcing Functions for Deadlines

If something has a rigid deadline, always set a call on the calendar to meet two days before, one day before, and sometimes the day of. Calls serve as forcing functions - they have to show up with the work done or face embarrassment.

The 5 Things That Must Be Clear

For every task, these five elements must be crystal clear:

Make It Nearly Impossible to Fail

There's a famous study about plane crashes. They found certain aircraft crashed more often - not because of pilot incompetence, but because critical handles were placed too close together. Under stress, even trained pilots hit the wrong one.

Your job is to put those "handles" as far apart as possible. Make it hard to make a mistake by design.

Diagnose the Real Problem

When someone makes a mistake, ask what really caused it:

Performance Improvement Plans

We implement PIPs after consistent underperformance for more than seven days. The structure:

Walk them through it on a call. They leave knowing exactly what to do, how it'll be measured, and by when.

Check-In Frequency Signals Importance

The amount of checking you put in equals the importance you signal for a task. Having issues with lead generation? Check in more often - not less. Daily if needed. They'll understand it's critical for the company.

Lead with Questions, Not Directives

Don't come in saying "This week we had this issue, I think we should fix it this way." Instead:

• "This week we had this issue - what do you think about it?"
• "How are you feeling about how that's going?"
• "How would you approach fixing this?"
• "Have you considered X?"
• "What if Y happens in your plan?"

You're leading them to the right answers with questions. It stays their idea. They're heard. They're on the front lines - they need to be heard.

Don't Fix Things for Them

The four basic human needs everyone has: being heard, being recognized, having the right to make honest mistakes, and feeling like they belong. When you fix their work, you accidentally reward them for not doing it right - they get your attention, you hear their excuse, you make them feel they belong by working through it together.

Explain the Trade-offs

Show your team the classic triangle: Quality, Price, Speed. You can have two, but not all three. If you toggle two on, one automatically goes off.

Tell them: "Right now we're focusing on quality and speed. Don't worry about cost - buy the tools. Next quarter we'll focus on price and quality, knowing we'll sacrifice speed." They need to understand where your head is at.

If It Wasn't Updated, It Didn't Happen

Big part of our culture: if it wasn't updated in the tracking system (Airtable for us), it wasn't done. I don't care if I saw it on Slack. If it's not in Airtable, we're checking in. "Why didn't you have this call?" "I had the call!" "I'm not seeing it."

You only have to do this once or twice until people realize they actually have to update the system.

Deadlines Are Real

They're called deadlines for a reason. If something wasn't done on time and wasn't communicated beforehand, it's a strike. Three strikes leads to termination.

This doesn't mean being ruthless. We assess capacity based on deadlines, communicate well, and don't overwhelm people. But when expectations are clear and agreed upon, deadlines are non-negotiable.

Reward Based on Personality

Types of rewards: compensation (bonuses, raises), genuine praise, coffee subscriptions, or simply meeting their four basic human needs - being heard, recognized, allowed honest mistakes, and belonging.

We reward people for delivering before deadline. Two days early? We message: "This was due Friday, awesome you finished Wednesday." We also reward 98%+ accuracy on everything - scripts, lists, campaign results. Always reward high competency.

Hire Slightly Above the Role

Build a recruiting funnel for higher-level talent. Have them start on tasks slightly below their perceived level with a clear growth path.

Why? You want people who feel offended by being micromanaged. When someone feels like a client success manager and you put them on lead generation, they're thinking "Don't keep checking on me for this - I've done this my whole life, I'm way beyond this." Those people perform because they want to get to the role they feel matches their skills.

You Get What You Pay For

If you look for someone with the mindset of a low-level data scraper, that's what you get. If you look for someone who feels they're beyond a role and give them a growth plan, you get someone who crushes the entry task.

We pay above market for all roles. We mention on-target earnings on top of base salary in job posts - it attracts better people. We promote on performance with target goals to earn more.

Tell People the Culture Before They Apply

Alienate the wrong people upfront. We say: "We focus on quality. We over-deliver. We do the extra. If this doesn't align with what you believe in, don't join us. You'll regret it, and you'll take the spot from someone who would have loved this."

The right people - the ones who love over-delivering - will self-select in.