A strong intake separates the visible symptom from the suspected cause and captures enough context to design a focused review.

Describe the Symptom
Record what happens, where, how often, under which production conditions, and who sees the effect. Avoid turning an early theory into a confirmed root cause.
Describe the System
Include upstream inputs, downstream requirements, part families, machines, tools, people, schedules, inspection, outside processing, and recent changes that may influence the condition.
Describe What Has Been Tried
List prior adjustments, temporary workarounds, capital requests, training, maintenance, and process changes. Note which result was measured and which remained an impression.
A Useful Intake Packet
Missing items do not prevent a conversation; they reveal what discovery may need to establish.
- A one-sentence description of the production problem and its business effect.
- The product family, route, machine group, shift, or handoff in scope.
- Two or three recent examples, including when normal work resumed.
- Available measures with their definitions and time periods.
- Known constraints on access, safety, confidentiality, timing, or trials.
- The decision or deliverable your team expects from the engagement.