-
- lead time (order → delivery)
-
- touch time (real work)
-
- queue time (waiting).
-
- you measure tidiness, not queues and wip.
-
- you ask for habits, but don’t change rules.
-
- improvement depends on a lean “hero.”
-
- one area improves while the system worsens.
-
- you talk tools (5s/kanban) without talking flow and constraints.
-
- how many projects are open at once (total wip)?
-
- how much does a project change after launch?
-
- how often do you replan the same order?
-
- what share of work arrives as “urgent”?
-
- how big are the queues before key steps?
-
- how much time is lost searching for material/info?
-
- do installation kits ship complete with evidence—or by feel?
-
- are defects recorded as a system or fixed silently?
-
- is variability customer-driven or self-inflicted?
-
- is the constraint stable or moving weekly?
-
- are prioritization rules clear—or pressure-driven?
-
- does the team trust the plan—or treat it as “approximate”?
-
- impact on lead time and promises
-
- repeatability (families of comparable work)
-
- urgency pain (structural, not a one-off spike)
-
- measurability (queues/wip/defects)
-
- reputation risk (second visits, claims).
-
- lead time
-
- total wip
-
- first pass yield
-
- otif-style (on time, in full—especially kits)
-
- replans per order.
-
- local productivity
-
- utilization (busy ≠ flowing)
-
- pieces/day without context
-
- plan adherence when the plan isn’t credible.










