$24M in annual technology investment had no strategic direction. Three years. Two failed attempts. One precise organizational diagnosis — and a process engineered to succeed where the others hadn't.

Before designing the strategy process, I assessed the organizational conditions that had defeated every previous attempt. The resistance wasn't interpersonal — it was systemic. A conflict-avoidant operating culture had made ambiguity structurally preferable to the vulnerability of commitment. Once I understood the system producing the resistance, I could design around it precisely rather than reacting to it repeatedly. The process I designed gave every stakeholder contribution and co-ownership from the start — building participation into the architecture so that by the time the strategy was complete, no one had grounds to reject work they had helped build. This is organizational change management applied upstream, before the change is asked for.

Different parts of this work required different capabilities. I brought my own: strategy architecture, analytical rigor, the methodological discipline to hold a sequential process steady under organizational pressure. But I also assessed what else the work needed — and deliberately brought in a collaborator whose strengths addressed the gap. In service design, everything is intentional because everything is impactful. Choosing who does what work, and why, is not a staffing decision — it's a design decision. The pairing was a precision instrument: I held the synthesis and strategy scaffolding while my collaborator ran parallel stakeholder validation, keeping people tethered to a process they'd have otherwise found ways to exit.

When I arrived, the product and business teams weren't misaligned — they were at war. No shared language, no shared direction, no functional relationship between the people building the technology and the people whose operations depended on it. Rather than addressing the conflict directly, I built the bridge through shared artifacts and shared accountability. I brought the Supply Chain Strategy into the room — authored by a key business partner the team actively resisted — and framed that partnership as alignment to something larger, not capitulation. The transportation team shifted from a siloed function to a contributor to a wider supply chain strategy. That reframe was the precondition for the TMS/WMS modernization that followed.

Good strategy doesn't begin with people declaring what it should be. It begins with rigorous inquiry — allowing the strategy to reveal itself from the evidence. The four strategic pillars weren't chosen by leadership preference. They emerged from structured workshops with seven cross-functional groups, secondary research, user feedback, and six months of iterative synthesis. Themes that kept reappearing — regardless of who was in the room or what role they held — became the pillars. The same process surfaced the vision: Frictionless flow from farm to fork. That distinction matters because it's the difference between a strategy people defend and a strategy people trust.