A three-year stall ended when I put a dollar figure on the problem
(Blurred) The insight snapshot that changed the meeting — one page, clear financial framing, specific enough to print. The VP read it in the room and redirected the entire strategy conversation around it.
Estimated enterprise-wide loss per week across 34 DCs — calculated from $15M confirmed at a single site during one field visit.
$10.5M in quantified benefits against $4.6M total system cost — the financial case that got three VPs to sign the charter.
The initiative had been dormant for three years. Once the financial framing landed, it moved from stalled to enterprise deployment in four months.
Transportation, Supply Chain Strategy, and Distribution Strategy — alignment that had eluded the project for years, secured after one reframe.
Transportation was bleeding money visible on spreadsheets — but leadership couldn't pinpoint the reasons on the ground, because staff put on their best face and gave the right answers. One page, the right numbers, delivered at the right moment — that's what three years of inertia needed.
The Problem
A trailer tracking initiative had been stalled for three years. Staff spent three-quarters of their day hunting lost trailers. Nobody had quantified what that was actually costing — until someone went to the ground to look.
The Solution
I visited distribution centers, translated operational reality into financial language, and built the product requirements infrastructure that made a 220% ROI case impossible to ignore — and a three-year stall impossible to sustain.
A strategy meeting with the Supply Chain VP collapsed mid-presentation. He stopped the room: "I don't know what you're talking about." I sent a one-page insight snapshot — $15M lost per week at one DC, managers spending more than half their day hunting trailers, product never recovered. He printed it out and read it in the room. "This is what we're going to focus on." Meeting over.
VP alignment securedVisited 5 distribution centers to conduct observations and interviews with actual users, replacing the product team's untested assumptions with validated, on-the-ground evidence — the kind of truth staff don't volunteer in a meeting room.
Assumptions validatedReplaced a Mural visual tool with a custom multi-tab Excel sheet that mapped user research findings directly to product requirements — empowering the design team to move faster and with more confidence.
Velocity createdBuilt the Collaborative Thinking Dojo — a single Mural board joining the project charter, research, and requirements tools — so the entire team could collaborate, reference, and decide from one shared source of truth.
Single source of truthThe real problem is almost never the problem they present. This is a Clarity architecture — the kind where the most important work happens before any tool is designed, when someone finally goes to the ground and translates what they find into language leadership can act on.
How I Work →