SORU
Why do our lorries never leave on time?
Kök nedenler, en derindekinden başlayarak. Anlaşmazlıklar haritada kalır.
kapandı · geri dön: Eylemler
Misafir olarak görüntülüyorsunuz. Katılmak için bir kullanıcı adı girin.
Bu odanın haritası
Kök nedenler solda, yeşil çerçeveli. Zincirini görmek için bir iddiaya dokunun.
odanın onayladığı bir bağ tartışmalı: oda karara bağlayamadı
Bu haritadaki her iddia, kendi adresiyle (17)
Her sayfa, odanın iddia çevresinde neyi onayladığını sayılarla birlikte gösterir; alıntılanabilir, gömülebilir ya da JSON olarak okunabilir.
Birleştirilmiş harita
2 odadan birleştirildi (tümü gösterim).
neden
Bu soru üzerindeki her oda kendi haritasını kurdu; burada tek haritada birleştirilir. İki odada dile getirilen aynı iddia tek bir öğedir ve her bağ onu kaç odanın bulduğunu gösterir. Odaların zıt sonuçlara vardığı yerlerde her bulgu geçerli kalır ve bağı değerlendiren odalardan kaçının bulduğu gösterilir.
Odalar aralarında 35 bağ onayladı, ama hiçbir bağ birden fazla bağımsız kaynak tarafından bulunmadı (bir kaynağı paylaşan ya da tek bir taraf gibi oy veren odalar bir kez sayılır), bu yüzden henüz ortak harita yok. Hiçbir ifade, tek bir iddia sayılacak kadar başka bir odanınkine anlamca yakın değildi. Her odanın kendi haritası tek başına duruyor: Why do our lorries never leave on time? (15), Why are deliveries late? (20). İki oda aynı bağı onayladığında ortak bir harita ortaya çıkar; bunu mümkün kılan, Üretme sırasında odalar arasında dolaşan bir karttır.
BU HARİTADAKİ ODALAR
Why do our lorries never leave on time?
⚠ demo · 7 cards word for word the same as in “Why are deliveries late?”
sayılır kararları bu haritada ağırlık taşır — 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?”
sayılır kararları bu haritada ağırlık taşır — vouched for by the steward of “Why do our lorries never leave on time?”
Bir oda, arkasında hesap verebilir biri durduğunda sayılır. ● herhangi bir harita kamuya açılmadan önce karara bağlandı; ○ sonra.
BİRDEN FAZLA ODADA DİLE GETİRİLENLER · 12
| Targets reward speed over accuracy | 2 oda | haritada |
| Small errors are hidden to avoid blame | 2 oda | haritada |
| Agency staff are on site for three days and never see the layout twice | 2 oda | haritada yok: ona giden hiçbir bağ onaylanmadı |
| The site was designed for half the volume it now handles | 2 oda | haritada yok: ona giden hiçbir bağ onaylanmadı |
| Data lives in three systems that disagree | 2 oda | haritada |
| We have never once asked a customer what an error costs them | 2 oda | haritada yok: ona giden hiçbir bağ onaylanmadı |
| Replenishment runs when it suits the forklift, not the pickers | 2 oda | haritada yok: ona giden hiçbir bağ onaylanmadı |
| Handovers between shifts lose key details | 2 oda | haritada |
| Schedules change too late to adapt | 2 oda | haritada yok: ona giden hiçbir bağ onaylanmadı |
| Peak-hour load exceeds planned capacity | 2 oda | haritada |
| Supervisors are measured on dispatch time and nothing else | 2 oda | haritada |
| New staff copy bad habits from old hands | 2 oda | haritada |
ODALAR NE YAPARDI
Her oda kendi eylemlerini kendi kök nedenlerine göre, kendi oylarının dörtte üçüyle değerlendirdi. Buradaki hiçbir şey odalar arası bir oylama değildir: neden neden, her odanın ne bulduğunu sayar. Bir oda, Eylemler aşaması kapandığında burada görünür. Haritadaki her numara, o eylemin azalttığı bir kök nedeni gösterir.
1 odanın 1 tanesinde azaltılıyor:
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?
Hiçbir oda bunları azaltan bir eylem bulmadı:
- Handovers between shifts lose key details · 1 odada değerlendirildi
- Nobody has costed what an error actually costs us · 1 odada değerlendirildi
- Targets reward speed over accuracy · 1 odada değerlendirildi
- The best pickers are moved to whatever is late, so nobody learns a zone · 1 odada değerlendirildi
- The trolleys are too small for the orders we now get · 1 odada değerlendirildi
1 ODA BULDU · 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 |