How to review one retail workflow with the people who use it
Updated: 1 day ago
I often compare three versions of a process: the one leadership expects, the one associates describe, and the one that happens on the floor. The differences are where a useful review begins. A procedure can be clear on paper and difficult to follow during a busy shift.
Choose one recurring workflow—a pickup handoff, replenishment request, or return review—and follow it with the people who use it. The aim is to understand a manageable piece of work well enough to improve it.
1. Choose a workflow with a clear boundary
Define where the workflow starts and ends. “Review replenishment” is broad; “follow a request from the selling floor until the item reaches the associate” gives the team a clearer boundary.
Write down what a successful handoff should achieve and who depends on it. Include the effect on the client, even when most of the work happens out of sight.
2. Gather the written and described versions
Read the procedure, then ask a leader how the process should work. Separately, ask the associates doing it to describe their steps. Avoid giving either group the other’s answer first.
Record the steps, decisions, systems, and exceptions in plain language. I leave differences unresolved at this stage. Correcting the account too early can prevent us from understanding why the work changed.
3. Observe the work with the team
Follow the process during a real shift. Look for waiting, repeated entry, extra searches, and workarounds. Ask what makes those steps necessary and what happens when the usual person is unavailable.
Keep observations separate from explanations. “The associate checked two screens” is something we saw. “The system caused the delay” is a possible explanation that still needs checking.
4. Review risk, capacity, and performance
Use the following questions to decide which gap deserves attention first. Then identify an owner and bring in the function that can help address it:
Where does uncertainty create risk or inconsistent decisions?
Where does the workflow consume time or repeat work?
How does it affect availability, service, or another commercial priority?
5. Test one change and update the standard
Describe one change, who needs to understand it, and what would count as an improvement. Test it in the work. I want to know whether it helps the next person in the process as well as the person carrying out the new step.
If the team adopts the change, update the procedure and assign responsibility for maintaining it. The review should leave people with a clearer way to work and an agreed follow-up—not simply another document.


Comments