The Retail Operating Pyramid

Retail organizations rarely fail from a lack of strategy. They fail because strategy erodes as it passes downward through the organization, and no one is measuring where the erosion happens. The Retail Operating Pyramid gives that erosion a shape you can inspect.

The five layers

Vision → Strategy → Operations → Processes → Execution

• Vision — the multi-year statement of what the retailer is trying to become.
• Strategy — the resource-allocation choices made to pursue that vision.
• Operations — the standing structures (staffing models, store formats, systems) that carry out the strategy.
• Processes — the repeatable procedures within operations (replenishment cadence, scheduling rules, service scripts).
• Execution — what actually happens on the floor, on a given shift, in front of a given customer.

Diagnosing a broken pyramid

Most operational problems presented as "execution issues" are actually strategy or operations problems wearing an execution costume. The pyramid is used to test that assumption before prescribing a fix:

Symptom at execution layer	Likely true origin
Associates skip a step under load	Process layer: the process assumes headcount that operations didn't staff
Inconsistent customer experience across stores	Operations layer: store format or staffing model varies without a stated reason
Store teams optimize for the wrong metric	Strategy layer: incentive design doesn't match the stated resource-allocation priority
Strategy sounds right but nothing changes	Vision layer: the vision was never translated into a resourcing decision

Applying the framework

1. Start at the execution symptom and walk upward, one layer at a time.
2. At each layer, ask: does this layer's design logically produce the layer below it? If not, that is the break.
3. Fix at the layer where the break occurs — not at the layer where the symptom is visible.

Execution is the layer everyone can see. It is almost never the layer where the problem originates.