About
I study how work actually gets done, then design the smallest change that improves it.
This isn't a timeline of roles. It's how I approach a problem: start on the floor, stay in the specifics, structure what I find, and hand back something a team can scope, fund, and pilot on Monday.
I spent a decade on the front line — retail, food service, logistics, and public safety — before I started writing any of it down. That's still where I start. I've found that the interesting problems are almost never where the org chart says they are, and that the people closest to the friction usually already know the fix.
01 · Systems Thinking
A bad customer moment is rarely a bad person.
Most friction is the predictable output of how a system is designed to allocate attention, inventory and time. I map the loop before proposing the fix, because a change made at the wrong point in the system just moves the pain somewhere less visible.
02 · Customer Curiosity
The interesting question is always “why did they do that?”
I'd rather watch fifteen people navigate an aisle than read a summary of what they said they'd do. Behavior is specific, situated, and repeatable. Curiosity is the discipline of staying in the observation long enough to see the pattern.
03 · Continuous Improvement
Small, measured changes compound faster than large ones.
I frame work as pilots with an explicit hypothesis and a measure attached. Shipping something learnable in four weeks beats a perfect program that arrives in a year and can't be evaluated.
04 · Operational Leadership
If it doesn't survive a Saturday, it isn't a solution.
Operations is the constraint every good idea eventually meets. I design with staffing, task load, peak volume and training reality in the room from the start, so proposals stay credible with the people who have to run them.
05 · Cross-functional Collaboration
Insight only matters if it travels.
The synthesis has to be legible to merchandising, store operations, technology and finance at once. I invest in how findings are communicated — the map, the framing, the one-page case — because that's what makes the work actionable.
Systems view
The loop I keep finding in retail operations.
Every case study on this site is, at bottom, an attempt to interrupt this loop at the earliest point where interruption is cheap.
Frontline signal
A customer question or an associate workaround happens, repeatedly.
No capture mechanism
The signal stays in the aisle; nothing collects it as structured data.
Decisions lose context
Planning works from transactions, so the cause of friction stays invisible.
Friction persists
The same workaround is reinvented, and the frontline absorbs the cost again.
Reinforcing loop · each state feeds the next
The method behind all of this is written down and repeatable.
Read the methodology