Setting Vision vs. Managing Execution
Founders get told they are too in-the-weeds, so they pull up to vision, and then get told they have become disconnected and are not helping anybody. So they drop back into detail, and are told they are micromanaging. The oscillation is exhausting, it is common, and it is usually diagnosed as a balance problem — spend forty percent up here and sixty percent down there. That framing is wrong. The problem is almost never the ratio. It is that the switching is unannounced, so nobody around you can tell which mode they are dealing with.
What’s inside
The binary is false
What each actually requires
The oscillation problem
Allocating deliberately
Signalling altitude
The two failure archetypes
Where Blomma fits
The binary is false
Vision and execution are not two ends of a dial you set. They are two different kinds of contribution, and a CEO needs to make both, in different moments, on different things.
The reason the binary persists is that each failure mode is highly visible. A founder in the detail is obviously in the detail — everyone can see them reviewing the copy. A founder who has withdrawn to abstraction is obviously absent — everyone can see the strategy deck and the unanswered decisions. So the feedback you receive tends to describe whichever failure you are currently exhibiting, and the natural correction is to swing.
What resolves it is not finding the midpoint. It is choosing, deliberately, which things you engage with at which altitude — and being explicit about it so the people around you can work with it.
One useful reframe: your job at the vision level is to make the destination unmistakable. Your job at the execution level is to notice, early and honestly, when something is drifting. Those are compatible activities, and neither requires you to take over the work.
What each actually requires
Worth being concrete, because both terms are used loosely.
Vision, done properly, is not inspiration.It is a small number of clear answers — where we are going, who this is for, what we are not doing — plus far more repetition than feels reasonable. The work is specificity and consistency, not eloquence. A vision that produces no clear answer to a novel question is decoration, however well it is delivered.
Execution, done properly at your level, is not doing the work.It is knowing whether the work is on track, and having enough contact with reality that a comfortable explanation does not pass unchallenged. That means reading the actual numbers, talking to actual customers, and occasionally looking at the actual output — without taking over the decisions.
The distinction that makes both possible: beingin contact withthe work versus beinginthe work. Contact keeps your judgment calibrated and costs your team nothing. Being in it removes their ownership.
Most founders who think they have a balance problem actually have a contact-versus-control problem. They are either fully out of touch or making the decisions, with nothing in between.
The oscillation problem
The real cost is not the time allocation. It is unpredictability.
When you switch altitude without signalling, your team cannot tell whether a given question is a genuine inquiry or the beginning of an intervention. So they hedge: they present rather than discuss, they pre-solve before bringing you anything, and they stop raising problems early because they cannot predict whether raising one will result in support or in you taking it over.
That is a large hidden cost, and it is worse than either consistent extreme. A team can work with a founder who is always in the detail — they adapt, badly but predictably. They can work with a founder who is always at altitude. What they cannot work with is a founder whose mode changes without warning, because it makes every interaction a risk assessment.
Which means the fix is mostly about legibility rather than about the ratio. If your team knows which mode you are in and why, most of the cost disappears — even if the allocation is imperfect.
Allocating deliberately
A workable approach, and it is a calendar exercise rather than a philosophical one.
Pick two or three things where you will go deep this quarter, and name them. Genuinely deep — in the detail, in the reviews, close to the work. These should be the things that are existential, or where your specific judgment is irreplaceable, or where something is going wrong that needs your attention.
Everything else, you operate at altitude: outcomes, standards, and the occasional contact to stay calibrated. You do not review it, you do not attend its meetings as the decision-maker, and you do not make its calls.
Then tell people which is which. “I’m going to be close to the enterprise motion this quarter because it is new and I have the most pattern-matching on it. I am not going to be in the mobile work at all — that is yours, come to me if X.” That single communication removes most of the confusion your switching causes.
And revisit quarterly. The deep list should change as the constraint moves. A founder deep in the same thing for four consecutive quarters has probably not chosen it deliberately — it is the thing they like.
Signalling altitude
The cheapest high-value habit in this whole subject: say which mode you are in when you engage.
“I’m asking out of curiosity, not because I think something is wrong.” “This is your call — I’m just thinking out loud.” “This one I am going to decide, and here is why.” Three sentences, and each removes an ambiguity your team would otherwise have to guess at.
This matters most for speculative comments. At scale, “I wonder if we should” gets heard as “we are going to,” and a passing remark can redirect a team’s quarter. Naming a thought as a thought is not hedging; it is preventing an unintended instruction.
Four questions that tell you which altitude a situation genuinely needs: Is this reversible? Does it require information only I have? Would being wrong here be existential? Is the person who owns it able to make this call? Three yeses at the vision level means stay out; a no on the last one means the answer is support, not takeover.
The two failure archetypes
The founder who never leaves the detail.Symptoms: a calendar full of reviews, decisions queuing on their desk, a team that waits, and a strategy that exists as a deck and not as a decision aid. Usually caused by the detail being where they feel competent — which is understandable, and it caps the company at their bandwidth.
The founder who has disappeared upward.Symptoms: eloquent strategy nobody can operationalise, decisions that need them going unmade, and a growing gap between the numbers they cite and the reality on the ground. Usually caused by taking “stop being in the weeds” too literally, and it produces a leader whose judgment slowly degrades because they have no contact with anything real.
The second is less commented on and at least as damaging, partly because it looks like the correct answer. A founder who cannot tell you what is actually hard about their product right now has lost the thing that made them better than a hired operator.
Where Blomma fits
The difficulty here is self-perception. Almost nobody can accurately say which altitude they are operating at, and the feedback you get describes your current failure rather than the pattern. Your executives will not tell you plainly that your unannounced switching is expensive, because it is a criticism of how you operate rather than a business problem.
Blomma is an always-on AI career coach with no stake in your company. Use it to audit where you actually spent the last month, which usually settles the question faster than reflection. Use it to choose the two or three things that genuinely warrant depth this quarter, as opposed to the ones you enjoy. Use it to draft the communication that tells your team which mode applies where. And use it in the moment before you drop into something — the four questions take a minute and prevent most unintended interventions.
The second application: your executives experience your altitude changes most directly, and several of them are managing the resulting ambiguity rather than telling you about it. Coaching gives them somewhere to work out how to raise it..
Vision and execution are not competing claims on your time. They are two things your company needs from you, and the whole problem is that you switch between them without saying so.