I'm deep in the tactical right now.
Solving problems on the spot. Sitting close to operations. Feeling the pulse of the service every single day. I can see exactly what we need to build to make it better.
It feels great. And that's the problem.
Tactical work is not the enemy of strategy. It's a trap precisely because it works. It gives you an immediate result. It makes you feel productive. And it never runs out.
This isn't procrastination. Procrastination feels bad — you know you're avoiding something. Tactical work feels like the opposite. It feels like the most responsible thing you could possibly be doing right now. That's what makes it so hard to catch.
Part of the pull is external. The fires are infinite. Operations will never hand you a quiet week.
But part of it is internal, and that part is harder to admit. It's the builder mentality. You became a founder because you like building. Fixing. Shipping. Touching the product. Being in the tactical scratches that itch perfectly.
That instinct is an asset — it's the reason you can build anything at all. But left alone, it quietly makes the same choice for you every morning: tactical over strategic. You don't decide to skip strategy. You just never arrive at it.
And the cost is invisible until it's expensive. You optimize the service beautifully — but you might be optimizing your way up the wrong hill. A company that is all tactical is very busy going somewhere it never chose.
I don't think the answer is "do less tactical." Being close to operations is real signal. It's how I know what to build. The answer is to change my relationship with it.
Two things I'm starting to test.
The first: make the tactical an input, not just an output. Right now every problem I solve produces a fix and then disappears. So I've started keeping a log — what I put out today, and what it tells me. Done consistently, strategy time stops being a blank page. It becomes pattern-matching across everything the tactical already taught me. The tactical starts feeding the strategy instead of replacing it.
The second: delegate the tactical I've already learned from. I'm in the weeds partly to understand operations — and that's correct. But once I've extracted the signal from a category of problems, that category no longer needs me. The first ten times I handle something, I'm learning. After that, I'm just a bottleneck. Delegation isn't giving away all the tactical. It's giving away the part I've already mined.
So here's where I've landed, at least for now.
Keep the tactical. Stay close to the pulse. But make every piece of it earn its place. Either it's still teaching you something — or it has already taught you, and it belongs to someone else.
The builder mentality that pulls you in is worth keeping. It just can't be the one holding the steering wheel.
I'm testing this now. We'll see.
Relevant posts: