Operations vs Governance (same team)
Every new director gets the same advice: govern, don’t manage or noses in, fingers out. Set the strategy, hold management to account, and leave the running of the company to the people you hired to run it. It’s sound advice but it’s also the source of one of the more expensive blind spots on small-company boards.
The advice exists for good reason. A director who can’t stop operating is a real problem. They second-guess the CEO in front of staff, relitigate decisions that were already made, and turn every board meeting into a status update. The instinct to pull people back from that is correct.
But the correction gets over-applied. “Stop managing” quietly becomes “stop understanding,” and a director talks themselves into treating operational detail as beneath the role. Strategy up here, the messy stuff down there. The board reads the dashboard and trusts that the dashboard is true.
The difference between operations and governance
Operations is the running of the company. The actual work: hiring, building, shipping, billing, paying suppliers, keeping customers. It happens every day and it belongs to management.
Governance is the work of overseeing that, on behalf of the people who own the company. Setting the direction, choosing the chief executive (and holding them to account), approving the calls too big for management to make alone, and checking the company is solvent, lawful, and not carrying risks it can’t survive. It happens periodically and it belongs to the board.
The short version: management runs the company, the board makes sure the company is being run properly.
Think of a football club. The players are on the field doing the work, and the coach picks the lineup, runs training, and decides how they play on the day. That’s operations, and the coach is closer to a chief executive than a director. The board sits where the owners sit. They hire the coach, set the budget, judge the season, and move the coach on if the results don’t come. What they don’t do is pick the team or call plays from the stands.
But an owner who doesn’t understand the game can’t tell whether a losing season is bad luck, a thin squad, or a coach who’s lost the room. They have to take the coach’s word for it. That’s the problem with distance, in a nutshell.
Distance doesn’t make you objective. It changes what you can see.
There’s a comforting story that distance from the operation makes a director more objective. It does, but only narrowly. Standing back strips out some genuine biases: the sunk-cost loyalty to a process because you built it, the defensiveness about a decision you personally made, the attachment that stops you asking why you do something at all. A director who never touched the ops can ask the naive question without ego riding on the answer. That’s worth something.
What distance doesn’t do is hand you the truth. It trades resolution for vantage. You see the horizon clearly and the near field goes soft. The thing that fills that soft near field is management’s version of reality, because they’re the only ones standing close enough to describe it to you. The mechanism meant to make directors independent is the same one that makes them dependent on the people they’re supposed to be scrutinising.
The far-sighted director
Far-sighted is a flattering term. We use it to mean wise, prudent, able to see what’s coming, and most directors are happy to be described that way. It’s worth remembering what the term actually describes: an eye that focuses on distant objects and can’t bring close ones into view. Hyperopia: a defect.
That’s the trap. The director who wants to be seen as far-sighted in the figurative sense is often far-sighted in the literal one and doesn’t notice. They can talk fluently about the market in three years and can’t tell you whether this quarter’s cash forecast is plausible. The near field is where a company actually lives or dies, and it’s exactly the part they’ve trained themselves not to look at.
Governing means testing, and testing needs a model
The board’s real job is to test what it’s told. Is the company solvent? Are these forecasts real or hopeful? Is this risk being managed or just described in a slide? None of those questions can be answered by someone with no working model of how the company runs.
If you can’t tell a plausible number from an implausible one, you’re not governing. You’re a spectator with a vote.
It scales up too and can even apply to countries. A finance minister who can’t make sense of the economy they’re handed, and so takes Treasury’s word for what the numbers mean, is the same failure in a bigger chair. The title doesn’t confer the understanding. Someone still has to tell a real number from a hopeful one.
Good directors decide through a lens that includes operations, not because they want to run the place, but because operational literacy is what enables them to push back. The point isn’t to operate the company. It’s to understand the operation well enough to know when the story you’re being told doesn’t add up.
That’s the challenge. You’re told to stop thinking operationally, and you should stop operating. But you should never stop understanding operations.
The executive director’s problem is the opposite one
The whole piece has been about distance. The executive director has the reverse problem: they can’t get any. They are the operation, and they sit on the body that judges it.
The mindset shift is hard enough. You spend the morning pushing your function’s agenda and the afternoon weighing it dispassionately against everyone else’s. But the sharper issue is interest, not mindset. Some board decisions don’t just affect your team, they affect you: your budget, your headcount, sometimes your job. A restructure that’s right for the company might dismantle the division you built. The textbook answer is to declare the interest and leave the room, and sometimes that’s exactly what happens.
It just isn’t always practical. In a small company you may be the only person in the room who understands what’s being decided. Recuse yourself from everything that touches your position and the board loses the operational literacy it recruited you for. Recuse from nothing and you’re voting on your own interests. And there’s a thornier version still: as a director you’re responsible for assessing the chief executive, which means appraising the performance of the person you report to the rest of the week. The same closeness that makes an executive director useful is what makes them conflicted, and there’s no clean way to have one without the other.
Balance is the point
This is why board composition matters more than any individual director. The executive director brings the near field, the detail, the knowledge of how the thing actually runs. The non-executive brings the far field, the horizon, the questions no one inside the building thinks to ask. Neither sees the whole picture alone. A board stacked with one type governs with a known blind spot.
That mix only works on trust, the kind that lets people speak plainly and disagree without it turning personal. But trust on a board isn’t the same as comfort. Trust that’s never tested isn’t trust, it’s deference, and deference is where this article started: the board that reads the dashboard and assumes the dashboard is true. The strongest boards trust each other enough to keep testing each other (you’re on the same team after all). The day the questions stop is the day the distance creeps back in.
Lessons learned
I’ve walked that dual role line, and switching modes doesn’t come naturally when like me, you’re an operator first. It’s a muscle, and you have to keep exercising it or you slip back into running things by reflex. The most useful tool I can recommend, if you have one available, is a senior non-executive on the board willing to mentor. They catch you when you drop back into ops mode, and in return you help them build and stress-test their model of how the company actually works. It’s the near and far field correcting each other, one conversation at a time.
The advice to “stop managing” is right. The version that becomes “stop understanding” is how boards end up surprised by things that were visible for months. I’ve seen the gap between what a board believed and what the operation was actually doing, and the distance between those two pictures was the whole problem. Distance had given the board a clean, confident, far-sighted view of a company that no longer existed.
Key takeaways - for directors and NEDs:
Keep your fingers out of operations and your eyes wide open. Build enough of a model of how the company runs that you can test what you’re told rather than just receive it. Treat “I don’t get into the detail” as a risk you’re carrying, not a principle you’re upholding.
Key takeaways - for COOs and operators:
The board can only test what it can see. If management controls the whole picture, the board is governing on trust. Give directors the operational visibility that lets them do their job, even when an unfiltered view is less flattering than the dashboard.
I’m John Chung, I’ve spent over 15 years building and running startups and scale-ups as a founder, operator, and non-executive director (GAICD). I write about the gap between how companies are supposed to operate and how they actually operate.
All content is produced by me, reflecting my own experience and judgement. Generative AI tools were used for editorial support, in this case Claude specifically.