The Operator Every Founder Is Looking For

How to deal with delay when the decision isn't yours.

You’ve sent the reminder. Maybe even more than one. You’re waiting on something that needs to be done by now, and you know exactly why it isn’t. It’s not waiting on you. It’s sitting with someone you can’t really give a deadline to.

If it was a team member you manage, a quick check-in could move it along. But this is waiting on someone above you, or outside your authority. A decision only leadership can make, an approval only the founder can give, or a task that only an owner can complete. And this is where your hands are tied.

If this belonged to you, you’d take care of it. You’d follow up, clear what’s getting stuck, and reset the deadline. But you can’t manage up the way you manage down. There’s a bottleneck; you can see exactly where, and you feel stuck.

So you do what all supportive operators do. You take it home.

Not because you don’t know how to disconnect from your job, but because you’re the kind of person who takes ownership, and ownership doesn’t work a 9-5. You try to go to sleep, but you’re still thinking about it. It’s not the thing you should do. It’s just honest.

This is a real tension of operating well: you go above and beyond because you care, and you’re still figuring out where caring ends and carrying too much begins. Most operators I’ve met live somewhere on that line.

Seeing a problem you feel like you can't do anything about is incredibly frustrating. When something really matters to you, and you're stuck, something in you wants to rise up—and before you know it, you've moved from "I care, and I wish I could help" to "I should just be in charge. Why can't they just decide? How do they not see the issue here?”

An attitude of pride will begin to creep in as you think of all the ways you would do it right and how they are doing it wrong. Left unchecked, that's what turns a good leader sour. A supportive operator has to keep their heart in the right place and stay in their lane.

So what’s the better option here? What’s better than tossing and turning at 2am because a project is delayed even though it’s not your fault? What’s better than growing irritated with someone you serve because they don’t always see things as you do?

First, you have to stop treating the delay like a personal failure. Operators take personal responsibility for anything that feels broken in their world, and that instinct is part of what makes you good at this. As fixers, we don’t like seeing broken things on our watch. But when the problem is upstream of your authority, you will just carry weight that doesn’t belong to you.

Here’s the other thing to remember. The person isn’t the problem either. There’s simply a missing piece of the process. Once you see it that way, the question changes. Instead of “Why won’t they just do it my way?” you start asking: “What would it take to make this easy for them to move forward?”

Why You’re Really Here

That question is the job, and it’s the reason you’re here. I had to learn it the hard way.

I wasn’t always an operator by title. I didn’t even know what the role meant. I've always been the person who liked building systems, making workflows run better, and finding the fix that gives the team some sort of relief.

When I create a solution to a problem or remove friction from a process that was causing delay, I am not just taking care of the organization’s mission. I am taking care of the people on my team. I am supporting my leadership, and everything within me wants to help make things better for them. That’s extremely fulfilling to me. I fix things. It’s how I’m built, and it’s what I like to do.

That perspective is the thing all founders really need. They don’t just need someone completing tasks or signing up for random software. They need someone who sees where the work keeps getting stuck and builds the system that fixes it, so the founder can do the things only they can do.

This means a bottleneck isn’t an interruption to your real work. Most of the time, the bottleneck is your real work, showing you exactly where the next process upgrade needs to be.

Recognize the Pattern.

The first time something stalls, that’s normal. You help it along, it moves, you’re done.

But when the same process gets stuck in the same place, over and over, that’s not a one-off anymore. Now it’s a pattern. And recognizing this is worth more than the frustration it causes you, because it’s showing you where the real work is.

Sometimes what’s stalling is a decision that keeps landing on one person’s desk. Sometimes it’s an old way of doing things that used to work and doesn’t anymore. Sometimes it’s a process nobody has ever looked at through systems thinking.

This all happens easily when you’re building and running hard—“done” becomes more valuable than “well-thought-out.” But eventually a process may have to change to get a better result.

This is the part you’re built for. You see what’s underneath the delay, and you know it can be built better.

Chasing vs. Helping.

So a decision is stuck with the founder. Here’s where most operators can go wrong, and it’s subtle, because it looks like you’re just doing your job.

You go back, and you flag it. “Hey, still need your call on this.” “Following up on the thing from last week.” “Did you decide on this yet?” All true, all appropriate, but all you’ve really done is hand the problem back exactly as it was before.

You’ve reminded them there’s a decision to make, but you haven’t made the making any easier. You’ve reminded them there’s a task to complete, but you haven’t made it any easier to complete the task.

That’s the difference between chasing and helping.

In the past, I’ve caught myself feeling like my full-time job was just sending reminders. I felt like I was just nagging all the time, and nagging is annoying to anyone. So when nothing changed after I sent multiple reminders, I would just go silent. Essentially, I would give up, and nothing was fixed despite the effort. I had to change my perspective.

Think about what a decision actually costs the person responsible for it. They have to stop what they’re doing, rebuild the full context you already have in your head, weigh all of the options they haven’t had time to think through, and worry about the ones they can’t see. This is real work, which is why it keeps sliding to the back of their list.

We made a rule on our team: we don't bring up problems. We bring solutions. Bringing up a problem sounds the same as complaining. But bringing up a problem alongside three different solutions you’ve been thinking about is an entirely different approach. You come to them with most of the thinking already done.

“We’re stuck on X. I see three different ways we could go. Option A will do this, with this tradeoff. Option B is much faster but will cost us here. Option C is what I think is best for us, and here’s why. What do you think?”

That’s a thirty-second yes instead of a project. You’ve carried the weight up to the last inch and left them the part that’s actually theirs: the call. You didn’t have to nag. You didn’t overstep and make the decision for them. You made the decision small enough to make.

That difference is everything. You no longer go to your leader with a problem. You’re going with a recommendation and room for them to decide. A problem lands on their desk as more work, but a recommendation lands as relief.

The Test of Honor.

Ok. So you’ve done the work. You brought them different solutions, you made the recommendation, and you handed them a thirty-second yes or no. And… maybe they still take three weeks. Or they pick the option you pointed to as the weakest. Or they change their mind after you’d already started. Real life. Real office.

This is the moment your own heart will be tested. Because the thought comes fast: I did everything right. I made this easy. Why can’t they just move? Why isn’t this project done yet?

A founder carries a different weight than the operator who is trying to help them.

You see your part of the organization clearly. But the founder is holding things you never see. The financial details. Commitments they made that they can’t talk about yet. A relationship that would perhaps be damaged by moving too fast on the very thing you’re pushing. The weight of being the one whose name is on all of it. You’re looking at just one decision. They’re looking at how that decision touches nine others you don’t have visibility into.

That doesn’t mean they’re always right. Sometimes the delay really is just a delay, and you’ll be frustrated, and that’s fair. But your view is real and partial at the same time. You can be completely right about your part and still not be seeing the whole board.

The operators who last, the ones founders trust with what really matters, are the ones who bring everything they’ve got and still stay under the authority of the person who has to answer for the whole thing. They push hard with ideas and hold loosely to control. You can own the vision and not be in charge of it.

It takes far more strength to bring your best thinking and then genuinely release the decision than it does to stew about being overruled. Anyone can resent. Staying in a place of honor while you feel blocked is the much harder thing.

That’s the operator every founder is looking for, and few ever find. Not because the skills are rare, but because the character is.

The question isn’t whether you have what it takes. You already showed that when you couldn’t sleep over something that wasn’t even your fault.

The question is whether you’ll let that same care make you better or bitter.

Which one are you becoming?

I’m Tiffany, and I help overloaded founders and leaders gain operational clarity by identifying bottlenecks, eliminating busywork, and implementing systems for growth. If you found this article helpful, the next one will be too.