Operational Work Teaches You Nothing About Strategy
I recently sat through a mandatory training session on a workflow-orchestration platform. Most of the other participants seemed engaged. I wasn’t. And the session crystallized something I’d been circling for a while about the difference between operational, tactical, and strategic work.
Watch how people learn in these settings. In the demos, most participants copy-pasted working code without understanding what lay underneath it. The tool itself — and this is no criticism of it — is fundamentally transactional rather than analytical. It’s operational: you define steps, retries, schedules. It makes processes reliable. But reliability is not understanding, and execution is not judgment.
That distinction matters because of where each kind of work sits on the ladder of leverage. As someone trained in Information Systems, the classic framing applies to careers too: operational work optimizes today’s process, tactical work wins this quarter, strategic work decides what the game even is. The higher you go, the less of your day is spent executing — and the more of it is spent deciding, which is exactly the part operational experience never teaches. You can run flawless operations for a decade and remain unable to answer “should we be doing this at all?”
I’ll admit my own position honestly: I dislike managing people, and my social skills are mediocre, so a classical strategic role — all politics and persuasion — is probably not my natural home. Tactical work suits me better: concrete problems, systems to design, decisions with visible consequences. But the training reminded me that tactical skill is only worth as much as the strategy it serves. Being excellent at executing the wrong plan is just efficient waste.
There’s a quieter lesson in the copy-paste demos, too. Watching people complete exercises without absorbing them is watching operational learning at its limit: input, output, done. The understanding — why this design, what fails under load, when the whole approach should be discarded — lives one level up, in the analytical layer. Tools teach you their buttons. Only questions teach you judgment.
So the takeaway from a day I mostly didn’t enjoy: treat operational competence as table stakes, never as the goal. Automate the operational so you can afford the analytical. Choose tactics deliberately, in service of a strategy you’ve actually thought about — because otherwise someone else’s strategy is quietly using you as its executor.
Drafted with AI assistance from my personal journal (2025-06-18), then edited by me. See On AI Assistance.