THE QUESTION
Why do our lorries never leave on time?
The root causes, deepest first. Disagreements stay on the map.
closed · back to Actions
Viewing as guest. Enter a handle to join and take part.
This room’s map
Root causes on the left, outlined in green. Tap a claim to see its chain.
a link the room certified contested: the room could not settle it
Every claim on this map, with its own address (17)
Each page says what the room certified around the claim, with the counts, and can be cited, embedded, or read as JSON.
The merged map
Folded from 2 rooms (all demos).
why
Every room on this question built its own map; these are folded into one. The same claim raised in two rooms is one item, and each link shows how many rooms found it. Where rooms found opposite things, each finding stands, with how many of the rooms that judged the link found it.
The rooms certified 35 links between them, but no link was found by more than one independent source (rooms that share a source, or vote as one, count once), so there is no shared map yet. No wording was close enough in meaning to another room’s to be treated as one claim. Each room’s own map stands alone: Why do our lorries never leave on time? (15), Why are deliveries late? (20). A shared map appears when two rooms certify the same link; a card that travels between rooms during Generate is what makes that possible.
THE ROOMS IN THIS MAP
Why do our lorries never leave on time?
⚠ demo · 7 cards word for word the same as in “Why are deliveries late?”
counts its verdicts weigh on this map — steward trusted by this instance
Why are deliveries late?
demo · stands 1 vouch from its source, trusted steward admin
⚠ demo · 7 cards word for word the same as in “Why do our lorries never leave on time?”
counts its verdicts weigh on this map — vouched for by the steward of “Why do our lorries never leave on time?”
A room counts once someone accountable stands behind it. ● settled before any map was public; ○ after.
RAISED IN MORE THAN ONE ROOM · 12
| Peak-hour load exceeds planned capacity | 2 rooms | on the map |
| Schedules change too late to adapt | 2 rooms | not on the map: no link to it was certified |
| Targets reward speed over accuracy | 2 rooms | on the map |
| Handovers between shifts lose key details | 2 rooms | on the map |
| The site was designed for half the volume it now handles | 2 rooms | not on the map: no link to it was certified |
| New staff copy bad habits from old hands | 2 rooms | on the map |
| We have never once asked a customer what an error costs them | 2 rooms | not on the map: no link to it was certified |
| Data lives in three systems that disagree | 2 rooms | on the map |
| Supervisors are measured on dispatch time and nothing else | 2 rooms | on the map |
| Small errors are hidden to avoid blame | 2 rooms | on the map |
| Agency staff are on site for three days and never see the layout twice | 2 rooms | not on the map: no link to it was certified |
| Replenishment runs when it suits the forklift, not the pickers | 2 rooms | not on the map: no link to it was certified |
WHAT THE ROOMS WOULD DO
Each room judged its own actions against its own root causes, at three quarters of its own votes. Nothing here is a vote across rooms: it counts, cause by cause, what each room found. A room appears once its Actions stage has closed. Each number on the map marks a root cause that action reduces.
Reduced in 1 of 1 room:
New staff copy bad habits from old hands
① Rotate a planner onto the floor each week · Why are deliveries late?
② One owner per recurring failure, named publicly · Why are deliveries late?
Nobody has ever been thanked for catching an error
③ Publish the four worst locations and fix the racking · Why do our lorries never leave on time?
Peak-hour load exceeds planned capacity
① Rotate a planner onto the floor each week · Why are deliveries late?
④ Refresh training every quarter, not once · Why are deliveries late?
The forecast is made by people who never see a peak
① Rotate a planner onto the floor each week · Why are deliveries late?
② One owner per recurring failure, named publicly · Why are deliveries late?
The handheld takes four seconds to confirm, so people batch their scans
④ Refresh training every quarter, not once · Why are deliveries late?
The induction is a video nobody watches to the end
⑤ Pay the ten minutes for a proper handover · Why do our lorries never leave on time?
We measure errors per order, so a bigger order hides more mistakes
① Rotate a planner onto the floor each week · Why are deliveries late?
④ Refresh training every quarter, not once · Why are deliveries late?
No room found an action that reduces these:
- Handovers between shifts lose key details · judged in 1 room
- Nobody has costed what an error actually costs us · judged in 1 room
- Targets reward speed over accuracy · judged in 1 room
- The best pickers are moved to whatever is late, so nobody learns a zone · judged in 1 room
- The trolleys are too small for the orders we now get · judged in 1 room
FOUND BY 1 ROOM · 35
| Nobody has costed what an error actually costs us | → | An error is only an error if the customer notices |
| → | Targets reward speed over accuracy | |
| → | Pickers are ranked against each other on a screen by the door | |
| Nobody has ever been thanked for catching an error | → | Returns are put back on the shelf without being checked |
| → | Small errors are hidden to avoid blame | |
| Peak-hour load exceeds planned capacity | → | Overtime is the normal way we finish a week, not the exception |
| → | Picks are wrong often enough that customers now check every pallet | |
| The induction is a video nobody watches to the end | → | Handovers between shifts lose key details |
| → | The scanner and the label printer disagree about leading zeros | |
| The trolleys are too small for the orders we now get | → | New product codes arrive without anyone being told what changed |
| → | Targets reward speed over accuracy | |
| A picker who slows down to check is beaten by one who does not | → | Small errors are hidden to avoid blame |
| New staff copy bad habits from old hands | → | Picks are wrong often enough that customers now check every pallet |
| Nobody is paid for the ten minutes it takes to do a handover properly | → | New product codes arrive without anyone being told what changed |
| Supervisors are measured on dispatch time and nothing else | → | A short pick is recorded as complete so the line keeps moving |
| The best pickers are moved to whatever is late, so nobody learns a zon | → | Fixes are patched locally and never shared |
| The forecast is made by people who never see a peak | → | Targets reward speed over accuracy |
| The handheld takes four seconds to confirm, so people batch their scan | → | Targets reward speed over accuracy |
| The system says a location is empty when a pallet is sitting in it | → | Data lives in three systems that disagree |
| We measure errors per order, so a bigger order hides more mistakes | → | Two products with almost the same code sit on the same rack |
| Targets reward speed over accuracy | ⇄ | Fixes are patched locally and never shared |
| → | Nobody checks a pallet before it is wrapped | |
| → | Pickers are ranked against each other on a screen by the door | |
| A short pick is recorded as complete so the line keeps moving | ⇄ | Picks are wrong often enough that customers now check every pallet |
| ⇄ | Small errors are hidden to avoid blame | |
| Fixes are patched locally and never shared | ⇄ | Targets reward speed over accuracy |
| → | We spend more time fixing errors than we would preventing them | |
| Handovers between shifts lose key details | → | Nobody reconciles what left the building with what was ordered |
| → | The scanner and the label printer disagree about leading zeros | |
| Picks are wrong often enough that customers now check every pallet | ⇄ | A short pick is recorded as complete so the line keeps moving |
| → | Overtime is the normal way we finish a week, not the exception | |
| Small errors are hidden to avoid blame | ⇄ | A short pick is recorded as complete so the line keeps moving |
| → | Two products with almost the same code sit on the same rack | |
| Overtime is the normal way we finish a week, not the exception | → | A short pick is recorded as complete so the line keeps moving |
| Two products with almost the same code sit on the same rack | → | Picks are wrong often enough that customers now check every pallet |