THE QUESTION
Why are deliveries late?
Say what you meant. Two cards merge only if both authors agree.
closed · back to Actions
Viewing as guest. Enter a handle to join and take part.
Merge duplicates
Only for two cards making the same claim.
why
A merge happens only when both authors consent. Argue meaning in the card's side chat before folding anything.
merged "Key details get dropped at shi…" → "Handovers between shifts lose …"
The lighting in aisle 7 is bad enough that codes are read wrong
I mean this happens weekly, not once in a while.
cluster 5
Nothing said yet.
Picks are wrong often enough that customers now check every pallet
cluster 5discuss
People are afraid to say a target is impossible
To be precise: this is about the process, not any person.
Small errors are hidden to avoid blame
cluster 4discuss
Replenishment runs when it suits the forklift, not the pickers
Meaning the recurring case, not one-off incidents.
The lighting in aisle 7 is bad enough that codes are read wrong
I mean this happens weekly, not once in a while.
cluster 5in focus ↑ · close ✕
We spend more time fixing errors than we would preventing them
Meaning the recurring case, not one-off incidents.
Handovers between shifts lose key details
cluster 2discuss
Peak-hour load exceeds planned capacity
cluster 3discuss
Training is one-off, never refreshed
cluster 1discuss
There is no way to stop the line without explaining yourself to two managers
Suppliers change packaging without telling anyone here
Overtime is the normal way we finish a week, not the exception
New staff copy bad habits from old hands
cluster 1discuss
The best pickers are moved to whatever is late, so nobody learns a zone
To be precise: this is about the process, not any person.
The warehouse map in the system is a year out of date
Supervisors are measured on dispatch time and nothing else
The person who finds an error is the person who gets asked why
Scope: our site specifically, not the whole company.
The site was designed for half the volume it now handles
Agency staff are on site for three days and never see the layout twice
To be precise: this is about the process, not any person.
The handheld takes four seconds to confirm, so people batch their scans
Not blaming anyone — the incentive does this on its own.
Data lives in three systems that disagree
I mean this happens weekly, not once in a while.
cluster 2discuss
The error rate fell for six weeks after a visit, then went back
Scope: our site specifically, not the whole company.
The people who designed the process have never picked an order
Nobody checks a pallet before it is wrapped
The busiest picker is the one who never reports an error
Schedules change too late to adapt
cluster 3discuss
Targets reward speed over accuracy
We have never once asked a customer what an error costs them
Rent went up, so a third of the aisle width went to more racking
The pick list order does not match the aisle order
Sales promise delivery windows before the warehouse is asked
To be precise: this is about the process, not any person.
A short pick is recorded as complete so the line keeps moving
The scanner logs out every hour and people stop scanning
To be precise: this is about the process, not any person.
We measure errors per order, so a bigger order hides more mistakes
Stock counts are corrected in the system but not on the shelf
Everyone knows which customer complains, and their orders are checked twice
Two products with almost the same code sit on the same rack
Not blaming anyone — the incentive does this on its own.
The clock on the wall is four minutes fast, so every shift starts rushed
Equipment failures go unreported for days
cluster 4discuss
Fixes are patched locally and never shared
The forecast is made by people who never see a peak
To be precise: this is about the process, not any person.
No one owns the problem end to end