Frontline One-Thing Loop
Ask frontline workers for one fix, act, and repeat until leaders learn directly
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
Go regularly to the place where employees meet customers or make the product. Ask a specific counterfactual: if you had the leader's job and all the keys to the company, what one thing would you do today? The constraint of one action turns diffuse complaints into priorities. Aggregate the answers; McNeill says he typically received only five to ten recurring themes, not hundreds. Select a few fixes, send them to the responsible teams, and repeat the field visit on a steady cadence. The mechanism combines direct customer-adjacent information with visible follow-through. Over time, internal teams begin seeking and resolving frontline problems before the leader's visit, creating a broader habit of field awareness.
Origin
McNeill borrowed the practice from Sam Walton's accounts of speaking with warehouse workers during store visits, then used Friday frontline visits and a standard one-thing question with his teams.
Core principles
- 01The people closest to customers see failures first
- 02A single concrete question produces actionable priorities
- 03Leaders should close the loop by acting on recurring answers
- 04Repeated field contact changes what the wider team notices
How to run it
- 1
Go to the work
Visit the store, factory, service desk, or other frontline instead of relying only on reports.
Pro tip Make the visits frequent enough to reveal patterns rather than one-off impressions.
- 2
Ask the one-thing question
Give the frontline employee the leader's authority hypothetically and ask for the single change they would make today.
Pro tip Ask the same question across locations so answers can be compared.
- 3
Find recurring answers
Group the responses and identify the few issues repeated across people or sites.
Watch out Do not mistake one vivid complaint for a universal pattern.
- 4
Assign a small fix set
Turn the highest-value recurring themes into a short list of owned actions.
Pro tip McNeill sent teams roughly three things to work on after visits.
- 5
Close and repeat
Tell frontline contributors what changed, then revisit to test whether the issue improved and surface the next constraint.
Watch out Repeatedly asking without acting destroys trust in the loop.
In the wild
Walton visited the back of a store first and spoke with the warehouse worker, who knew what sold, what stalled, and who actually contributed. He then approached the store manager already informed about the operation.
→ He gained a direct operational picture before receiving the management account.
McNeill typically visited frontline operations on Fridays, asked what one thing should change, and sent his teams a short email naming roughly three issues to address.
→ Teams began looking for frontline issues themselves so they could stay ahead of his visits.
Common mistakes
Touring without listening
A ceremonial visit filtered through managers does not expose the knowledge held by people doing the work.
Collecting an unbounded wish list
The one-thing constraint helps reveal priorities; asking for everything produces noise and weak ownership.
Is it for you?
Best for
Leaders with customer-facing stores, service teams, factories, or field operations.
Not ideal for
Organizations that solicit frontline input but lack authority or intent to act on it.
From the transcript
“the first thing he does when he visits one of his stores he goes in the back and he talks to the warehouse guy because…”
“you have my job. You have all the keys to the company. What's one thing you do today?”
“I wouldn't get 500 answers, I'd get like 5 to 10.”
From the episode
Episode 541: Jon McNeill: Why "Less" and "Simple" are the Smartest Growth Strategies
Jon McNeill