Why I Believed So Strongly in Supply Chain Strategy
For most of my career, I have written and spoken about how to design, align, and execute supply chain strategy. I strongly believe that the supply chain cannot be reduced to operational excellence alone. It needs direction, ambition, and explicit strategic intent. It must be aligned with the company’s strategy, manufacturing priorities, commercial realities, and long-term value creation. That belief has shaped much of my work.
What I write about far less often are the moments when that belief – applied with full conviction and good intentions – led me straight into a wall.
This is one of those moments.
Several years ago, I was working as a Logistics Director in a manufacturing environment. I had a clear mandate to run and improve my function, and I took that mandate very seriously – perhaps too literally. Driven by ambition and a genuine desire to do the right thing, I developed a comprehensive logistics strategy for the entire site. It was not a superficial deck or a set of generic slogans. It was a structured, multi-year roadmap, broken down into several strategic pillars, each with defined ambition levels, milestones, and concrete initiatives.
I was deeply invested in this work. The strategy reflected my experience, my understanding of the plant’s constraints, and my vision of what logistics needed to become to support future growth. Importantly, I was not acting in isolation. I discussed the concept with my direct manager and with the Plant Director. I received initial buy-in. There were no warning signs. Everything suggested that I was on the right track.
The Moment Alignment Quietly Disappeared
The moment of truth was meant to be a presentation to the Vice President of Supply Chain. I prepared thoroughly. The slides were solid, the narrative coherent, the logic clear. Yet by the second or third slide, I already began to sense that something was wrong. The questions were not about execution or feasibility. They challenged the very foundations of the strategy – the underlying why.
It quickly became apparent that the Vice President had a fundamentally different view of what supply chain strategy should look like at the site level. More importantly, he already had his own vision—one he was rolling out consistently across all plants. I did not know this. No one had communicated it to me. And in that moment, it stopped mattering whether my strategy was good, well-thought-out, or locally relevant. It simply did not fit into a larger, unspoken picture.
What made the situation truly difficult was not the disagreement itself. Disagreement is normal and often healthy. What hurt was what followed. The same leaders who had previously supported my work – who had encouraged me to think boldly – became silent. Or they subtly withdrew their support, behaving as if the strategy had never really been needed in the first place. In that room, the narrative shifted from “this is a strong initiative” to “this might not be appropriate.”
In practice, the strategy died before it had a chance to evolve. On a personal level, it cut much deeper. I had not just lost a project; I had lost momentum and trust in the system. Rebuilding motivation took time, and even when it returned, it came back in a different form. From that point on, it was clear that putting down deep roots in that organization would be difficult. Eventually, the story ended.
Looking back, the most uncomfortable insight is this: no one was acting in bad faith. The Vice President was not wrong to have a vision. My managers were not deliberately misleading me. And I was not wrong to want to professionalize and elevate logistics. The failure lived in the space between ambition and context.
Where My Assumptions Broke Down
I had assumed that managing a function meant owning its strategic direction. I had assumed that local excellence and strong logic would be enough. I had assumed that alignment would naturally emerge if the work was solid. All of those assumptions turned out to be wrong.
What I failed to do was understand the organization’s real decision architecture. I did not invest enough time in understanding whose vision truly mattered, where strategy was actually defined, and what role site-level leaders were expected to play. In hindsight, my role was less about creating strategy and more about translating and executing a strategy that already existed – one that I simply did not know.
5 Things You Can Do to Avoid My Mistakes
- Clarify where strategy is truly owned.
Do not assume that functional ownership equals strategic ownership. Explicitly ask where the supply chain strategy is defined, who shapes it, and how much freedom exists at the site or regional level. - Understand senior leaders’ agendas before building anything comprehensive.
Before investing months in a detailed roadmap, invest weeks in understanding the vision, priorities, and mental models of the most senior stakeholders – especially those you rarely interact with. - Test the “why” early, not just the “what.”
Early validation should focus on strategic intent, not on structure or execution. If the fundamental purpose is misaligned, no level of detail will save the initiative later. - Read silence and hesitation as data.
Lack of resistance is not the same as commitment. If support is vague or non-committal, treat it as a signal to probe deeper rather than as implicit approval. - Design for translation before transformation.
In many organizations, the real value of functional leaders lies not in inventing new strategies but in translating a global vision into a local reality. Make sure you know which role you are expected to play.
This experience fundamentally reshaped how I approach transformation work today. It taught me that ambition, expertise, and even visible support from direct superiors are not always enough. Strategy does not live in decks or roadmaps; it lives in power structures, expectations, and often unspoken rules.
Before designing anything ambitious, the first task is not analysis or planning. It is sense-making. Understanding whose game you are playing, and by which rules.
If there is one lesson worth passing on, it is this: never confuse responsibility for results with authority over direction. Otherwise, you may deliver a very good answer to a question that was never asked.
And sometimes, that is the most expensive mistake of all.