When I Thought Strategy Could Be Separated From Operations
As someone who's spent the last 18 years moving between strategic roles and operational leadership, I used to believe these were two distinct worlds. Strategy happened in boardrooms with whiteboards and projections. Operations happened on factory floors and in customer service centers. I was wrong about that separation, and the lesson still shapes how I approach every decision today.
Back in my earlier days at Unitronics, I fell into the trap that catches many rising leaders. I thought my job was to craft brilliant strategies and then hand them off to operations teams to execute. The strategy was the vision. Operations was the mechanics. Clean lines, clear responsibilities. It sounds logical until you watch it fail in real time.
The wake-up call came during a product rollout where our strategic timeline looked perfect on paper. We had market research, competitive analysis, and financial projections that made complete sense. But we hadn't deeply integrated the operational realities of our manufacturing capabilities and supply chain constraints. The strategy assumed operations could bend to accommodate our timeline. Operations assumed strategy would adjust when reality hit.
Neither happened smoothly. We launched late, over budget, and with compromises that satisfied no one. The strategy wasn't wrong, and operations wasn't incompetent. The problem was treating them as separate functions instead of integrated parts of the same system.
That experience changed how I think about leadership entirely. When I moved into COO roles and eventually into consulting, I started approaching every challenge through what I call operational strategy. You can't design a go-to-market plan without understanding fulfillment capacity. You can't set growth targets without knowing your systems can scale. You can't promise customer experience improvements without operational changes to support them.
This integration became even more important as I worked with companies implementing new technologies. A digital transformation strategy that ignores how people actually work will create expensive software that nobody uses. An automation initiative that doesn't account for workforce transition will generate resistance that kills adoption. The most elegant strategic vision fails if the operational foundation can't support it.
Now when I work with leadership teams, I watch for this same disconnect. The telltale sign is when strategy discussions happen without operational leaders in the room, or when operational challenges get dismissed as implementation details to figure out later. Strategy and operations aren't sequential steps. They're parallel considerations that have to inform each other from the beginning.
Looking ahead, I see this integration becoming even more critical as business cycles accelerate and market conditions shift faster than ever. Companies that can think strategically and operationally at the same time will adapt quicker than those that treat them as separate disciplines. That's the kind of leadership I'm committed to developing, both in myself and in the teams I work with.