In my last post I wrote about how I figured out I was an operator. This post is about what being an operator looks like in the day to day.
In my career I have been most inspired by two famous operators. The first is David Sacks, whose essay The Cadence I have read maybe a dozen times. I keep a printed copy of it in my desk drawer. The other is Sheryl Sandberg, whose approach to scaling one of the behemoths of the modern tech world is the stuff of legend.
But Sacks, Sandberg, and most others who have written about running and scaling companies wrote from a seat of real authority. Most of us operating in the real world are operating without founder authority. The mandate is real, but the power is borrowed. We create order, momentum, and follow-through not by decree but by judgment, credibility, and persuasion.
So over my career I have collected a set of principles for operating under exactly that condition. Most of them sound like common sense. All of them are lessons from the real world. In the weeks ahead I will dig into each one with its own post.
1. Get it over the finish line.
Finishing is the only work that matters. Founding teams generate good ideas constantly. We should integrate with this new software. We should build this capability. We should stand up a proper CRM. We should set up profitability models. Yet none of these ideas returns any benefit until it is completed, implemented, and operationalized.
Teams have their own version of the problem: everyone loves starting projects, and far fewer love shipping them. Many organizations have a graveyard of dusty projects that made it to eighty percent and no further.
The operator is the one who puts in the effort to get something from eighty percent to done. The operator also understands two uncomfortable truths: something eighty percent done can be as useless as something never started, and the last ten percent can take more effort than the first ninety.
2. Understand the problem before reacting to it.
People tend to react to problems instead of understanding them. It feels good to fire off an email or make a quick decision the moment a problem lands. Founding teams face a flood of random problems daily, and over time the overwhelm builds until clearing the plate becomes more attractive than sitting with what is actually on it.
The trouble is that a problem reacted to is a problem passed on at full size, or larger, because the reaction adds alarm on top of substance. Every problem that moves through a person comes out one of two sizes: smaller, because they took the time to understand it and handed on the manageable version, or bigger, because they added their own urgency to it and passed the weight downstream.
The operator’s role is to create the process, and enforce the discipline, of taking a beat to fully understand a problem before reacting to it. The mechanism varies, but the simplest version is often just to keep asking what we are actually trying to solve for until the answer makes sense. Done consistently, this is what it means to lighten the load: absorb the noise, pass on the signal, and make sure problems shrink as they move through you rather than grow.
3. Act on signals while stakes are still low.
Every serious problem announces itself early, quietly, while it is still cheap to address. Acting on those early signals is thankless work, and the operator who insists on it risks looking like a pedant.
Early action costs real time and effort on a problem that might never materialize, which can make the operator seem paranoid, or worse, a waster of everyone’s time. And when prevention works, the disaster never arrives, so nobody thanks you for a fire that did not happen. The counterfactual is invisible. You pay the cost in full view and never collect the credit.
But this is the role. Anticipate the pitfalls and sound the alarm, because once a crisis actually arrives, it is almost always worse and lasts longer than anyone expected.
4. Make a move when the cost of waiting exceeds the cost of being wrong.
Standing still is as much a decision as making a move. The discipline is to weigh the worst case of holding the status quo against the worst case of acting. Some problems compound while you deliberate, and for those, hesitation is not prudence. It is the most expensive option on the table.
Ask two questions of every stalled decision: what does waiting cost, and what does being wrong cost? When the first number clearly exceeds the second, move. You will sometimes be wrong, and being wrong will cost less than the waiting would have. This is not recklessness. It is taking the asymmetry seriously instead of treating all caution as free.
5. Fix the system instead of firefighting.
Many leaders are secretly addicted to firefighting, because being needed feels like being valuable. It is a trap. If a problem shows up repeatedly, the part of the system generating the problem is what needs fixing. That fix can be as complex as upgrading a key piece of infrastructure or as simple as giving customers better training so the problem stops arriving at your door.
6. Lead with clarity, not pressure.
When someone is stuck or a team is underperforming, the tendency is to apply pressure: more urgency, higher stakes, a tighter grip. It can work briefly, and it costs permanently, usually by burning out the team. The better lever is almost always clarity: help the team understand what good looks like, and who owns what. Most underperformance is not a motivation problem. It is an ambiguity problem.
7. Let the data shape the narrative, not the other way around.
Organizations run on stories, and stories can trick us into believing things are how we wish they were versus how they actually are. Sometimes activity gets reported as progress, or a forecast gets built backward from the number someone hoped to hit, or strategies assume everything will always go right.
The operator’s job is to hold the line between what is verifiable and what is merely the stories we tell ourselves and each other. Ask for the primary source. Pull the real numbers. Let them overturn the preferred story when they do. Because decisions built on evidence fail differently, and more rarely, than decisions built on narrative.
All seven principles, taken together, are about creating order, maintaining momentum, and keeping the team productive and calm from a seat that earns its influence rather than inherits it. Over the coming weeks I will take each principle, discuss in detail what it looks like in practice and how you can incorporate it into your day to day to build your operator muscle.







