Résolveur de problèmes A3

Exemple chargéAfficher

Révisez votre histoire A3. Passez en Modifier pour mettre à jour une section.

Aperçu ↗
Owner

Value stream lead (example)

Date

April 2026

Proposed countermeasures
#Countermeasure (what will we change / test?)OwnerDueStatus / result
1Pilot a 30-minute flex window on Tue–Thu with cross-trained backup from kitting.Pack supervisorWeek 2Planned
2Cap WIP in front of pack at 12 orders; overflow triggers a planner review same day.Planner + pack leadWeek 2In progress
3Weekly 20-minute pack-plan sync using last week’s cutoff misses as the agenda.Value stream leadWeek 1Started
Theme / title

Stabilise on-time delivery from final pack through carrier pickup

Background

Customer promise dates are set in the ERP, but our OTIF metric has been red for three weeks. Leadership asked for a single A3 to align pack, planning, and logistics on facts and experiments — not opinions.

Current condition

Pack-and-label runs a fixed headcount with no buffer. Mid-week spikes hit on Tuesday–Wednesday. Carriers collect at 16:00; after 15:45 we miss the slot and the shipment rolls to the next day. WIP in front of pack is not capped; planners push “hot” orders that disrupt sequence.

Target condition

OTIF ≥ 98% within 8 weeks, with no increase in pack headcount. Cutoff misses ≤ 1 per week. Visual standard in pack shows max queue and sequence rules; planners level promise dates within demonstrated pack capacity.

Root cause analysis

5 Whys + data: the bottleneck is not “people working slower” — it is that demand variation hits pack before planning adjusts, and we have no time buffer or leveling rule tied to carrier cutoff. S&OP output is not translated into a daily pack TAKT / WIP limit.

Plan & results

Week 1–2: baseline cutoff misses, train backup, install WIP limit marker. Week 3–4: run pilot; track OTIF, queue time, and misses. Early result (example): misses dropped from 9 → 4 in two weeks; need 2 more weeks to confirm.

Follow-up / standardisation

If pilot holds: update standard work, train night shift, add KPI to tier-2 board. Yokoten to second site after 30 stable days. If not: stop and revisit root cause with scheduling data.

Transformer l'analyse en action

Cet A3 est un instantané de session unique. Kanrix suit les contre-mesures, la responsabilisation des propriétaires et les progrès des KPI dans toute l'équipe.

Book an Execution Gap Review →