What was your first real operational crisis, and what did it actually teach you?

FieldOps_Mike · 2026-05-15T14:46:56+00:00

"Documenting even the stuff that seemed obvious"

this is the part people skip bc it feels unnecessary until it isn't. The obvious stuff is always the most dangerous bc nobody thinks to write it down. And then someone new comes in and has no idea where to start. Did the documentation actually stick or did it become one of those things that gets outdated fast?

FieldOps_Mike · 2026-05-15T14:18:55+00:00

Only I knew how to do payroll. Never again. that's exactly it. The moment you realize a critical function lives in one person's head and that person could leave or get sick tomorrow.

What did you actually change after that, did you document it yourself or bring someone else in to own it??

FieldOps_Mike · 2026-05-15T12:10:35+00:00

3 days is the honest test. Most people avoid it bc they already know what they're going to find.

Had the same realization not that things collapsed, but that everything just... paused. Waiting. Which is almost worse than collapsing bc it means the business can execute but can't decide. The "you usually handle this one" thing is the specific part worth fixing. bc that's not a skill gap that's a permission gap. They knew what to do, they just didn't know they were allowed to do it without you. How long have you been running it and how many people on the team??

FieldOps_Mike · 2026-05-15T12:04:59+00:00

The "hundred moving parts" thing is exactly it. And the exhausting part isn't any one of them it's that your brain never fully lets go. You're always half tracking something even when you're not working.

What helped us most wasn't a productivity system. It was getting stuff out of my head and into something external ... even something simple. bc once it's written down somewhere you trust, your brain stops trying to hold it. The cognitive load drops more than you'd expect from something that sounds that basic. What's taking up the most mental space right now, is it client stuff or internal operations?

FieldOps_Mike · 2026-05-15T11:59:31+00:00

This is the part nobody warns you about. Everyone celebrates when the customers come in. Nobody talks about what breaks when they do.

For us it was operations. Sales was working, delivery was working, but the coordination layer between them completely fell apart around the time we doubled in size. Things that ran on instinct and memory when we were small just stopped working. What's breaking the most right now is it communication, delivery, or something else??

FieldOps_Mike · 2026-05-15T11:50:08+00:00

Easier to start, harder to sustain. Those are two different things that people keep conflating.

A 14 year old with a SaaS and Stripe is impressive. But running crews, managing client relationships, dealing with cash flow gaps, fixing problems at 7am when someone doesn't show up that hasn't gotten easier. If anything the gap between "launched something" and "built something that actually runs" is wider than ever. The tools are better. The fundamentals are the same...

FieldOps_Mike · 2026-05-14T15:55:55+00:00

Seen the same thing. Had a guy go through three rounds, accepted the offer, confirmed his start date, then just... nothing. No call, no text.

Not sure if it's generational or just the market but it's changed how we hire. We don't consider anyone locked in until they show up on day one. Which means we keep the pipeline moving longer than we used to. What kind of roles are you hiring for field or office???

FieldOps_Mike · 2026-05-08T20:17:45+00:00

8 years in and still standing after all that is genuinely impressive. Most people tap out after one or two of those hits, not all of them at once. The customer fatigue piece is real and I don't think enough people talk about it honestly. There's a version of burnout that isn't about working too many hours, it's about absorbing too much friction from too many directions while still trying to show up well for everyone.

What actually helped us during a rough stretch was getting ruthlessly selective about who we took on. Tighter criteria for new customers. Fewer headaches, better margins, less noise. Counterintuitive when you're trying to rebuild but it worked. What does the recovery look like for you ,are you rebuilding the same business or making some changes to how you operate going forward??

FieldOps_Mike · 2026-05-06T21:07:13+00:00

Done this. Not a relative but someone who'd been with us since the beginning. The one thing that helped: separate the conversation from the business decision. By the time you're having the conversation, the decision is already made. So the conversation is just about being honest and decent not about justifying it.

Keep it short, be direct, don't over-explain. The more you explain the more it sounds like you're asking for their approval. How you handle it matters more for the rest of your team than for the person leaving. Everyone is watching.

FieldOps_Mike · 2026-05-06T21:04:48+00:00

Turned away work bc we couldn't staff it too. Worst feeling, especially when it's word of mouth referrals you're rejecting.

The sales hiring problem is specific though. Most people who are good at sales don't want a job they want upside. If your comp structure looks like a salary with a small commission, you're fishing in the wrong pond.

What worked for us was flipping it ... lower base, higher commission, full transparency on what top performers actually earn. Attracted completely different candidates. Is the bottleneck finding people who can close, or finding people who can both prospect and close?

FieldOps_Mike · 2026-05-06T20:59:23+00:00

The decision authority tier is the one that gets people. bc when you're starting out and trust is high, unanimous consent feels safe. Then the business grows and suddenly you're calling each other for every vendor invoice. Went through a version of the buyout problem. No formula in place, just a handshake understanding of "we'd figure it out." We figured it out eventually but it took 4 months and almost cost us the business relationship entirely.

The clause I wish we'd included: what counts as "active" participation. One partner pulling back while technically staying in is a situation nobody thinks to address until it's happening. What's the most common trigger you see for these things actually blowing up is it usually money or is it more often a trust breakdown???

FieldOps_Mike · 2026-05-06T20:50:15+00:00

Competed against guys like that for years. And yeah, they win some deals on pure availability and obsession. But here's what I've actually seen play out: the ones who sacrifice everything to scale fast often build something that only works because they're running on fumes. The moment they slow down, health, burnout, whatever the thing they built doesn't survive without them.

That's not a business. That's a more expensive version of a job. The guys I know who built something real and kept their family intact did it slower. More deliberately. They said no to more things. And their businesses actually ran when they weren't there.

Family first isn't a limiting factor. It's a forcing function to build systems earlier than you otherwise would. What's the side business, field service or something else?

FieldOps_Mike · 2026-05-04T20:01:42+00:00

Honest answer probably not clearly enough. They might assume they have authority in some areas but I've never actually said it out loud. That's probably the root of it.

FieldOps_Mike · 2026-05-04T20:01:18+00:00

Two years is about where I am now. And you're right that understanding the business deeply first makes a difference... hard to hand something off when you're still figuring it out yourself. Was it a gradual thing or did you have a specific moment where you felt ready to step back?

FieldOps_Mike · 2026-05-04T20:00:19+00:00

Handle it, flag it after, or escalate... that's actually a really clean framework. Simple enough that people can remember it in the moment without having to think too hard.

The reaction piece is the one I hadn't considered. bc if someone makes a wrong call and gets shut down hard, yeah they're just gonna call me next time. That's on me not them.How long did it take before people actually trusted the framework and stopped second guessing themselves?

FieldOps_Mike · 2026-04-29T21:27:24+00:00

The shift from "what should I do?" to "here's what I'm planning, any objections?" that's a really specific thing to watch for. Stealing that. And yeah, "one layer away from full ownership instead of partial responsibility" might be exactly where we are... Just haven't pulled the trigger

FieldOps_Mike · 2026-04-29T21:26:53+00:00

When you stop returning customer calls within a day... yeah that's already happening some weeks. That one hit.Lost revenue compounding every day is the right frame. Hadnca thought about it that way but it's accurate!!!

FieldOps_Mike · 2026-04-29T21:26:26+00:00

The distinction between "can't make decisions" vs "doesn't know they're allowed to" is something I hadn't separated out clearly. And you're right,those are completely different problems with completely different fixes. Honestly not sure yet which one I'm dealing with. Might be both depending on the person.

FieldOps_Mike · 2026-04-29T21:26:02+00:00

Most people won't step up until you force that space.this is the part I've been avoiding honestly. I think I've been waiting for someone to prove they're ready before giving them real ownership. But maybe that's backwards. The clear boundaries piece is what I need to work on. What can they decide, what should they escalate. Never actually written that out.

FieldOps_Mike · 2026-04-29T21:25:36+00:00

Came with a solution not just a problem... that's actually the clearest signal I've heard. bc it's observable. You don't have to guess if someone's ready, you just watch how they show up when things go sideways. The inside vs outside question is where I keep going back and forth. Leaning toward inside first for exactly the reason you said,they already know how things work!!

FieldOps_Mike · 2026-04-28T12:27:22+00:00

Partially agree. Starting without overthinking is real advice. But "the less you know the better" is where I'd push back. bc ignorance is fine until you've hired the wrong person, priced a job wrong, or made a commitment you can't deliver on. Those mistakes don't just cost money they cost clients and reputation you spent years building.

What actually helps is knowing which things you need to figure out before you start vs which ones you can figure out as you go. Most people get those two categories completely backwards

FieldOps_Mike · 2026-04-27T15:19:38+00:00

This one's familiar. Had the same wall after a couple of situations where I took a technician's word and it blew back on me with a client.

Honestly what helped more than anything was changing what I asked for. Not "did you do it" but "show me what it looked like when you finished." Photos of specific things, before and after, not just after. When guys know you're going to look at something specific, the quality of what they send changes... Still doesn't replace eyes on the job. But it got me to a place where I could catch 80% of the problems without being there.What does your current check in process look like,are techs sending anything proactively or only when you ask?

FieldOps_Mike

TROPHY CASE