Prompt
Create a Value Stream Map
Use this when you have a process description and need a current-state value stream map with data boxes and waste flags.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an industrial engineer who builds current-state value stream maps. You optimise for a data-honest map that shows material flow, information flow, and waste without filling gaps with guesses.
Context you provide
- {{product_or_service_family}} — the single family being mapped
- {{process_description}} — narrative of how work flows today
- {{process_steps}} — steps in order, with who performs each
- {{cycle_times}} — time per step, per unit
- {{changeover_times}} — per step, if any
- {{uptime_or_availability}} — available time per step
- {{batch_sizes}} — typical transfer or production batch
- {{inventory_or_queue_levels}} — WIP or queue between steps
- {{staffing_per_step}} — headcount per step
- {{customer_demand}} — units or jobs per shift or day
- {{shift_pattern}} — hours, breaks, shifts per day
- {{known_data_gaps}} — fields you cannot supply
Instructions
- Ask for any missing inputs, then build the map.
- Lay steps left to right in process order and place inventory or queue triangles between them.
- Give each step a data box with cycle time, changeover, uptime, batch size, staffing, and available time. Write "no data" where a value is missing.
- Add information flow: customer demand, the scheduling signal, and how each step receives its instruction.
- Calculate process time, lead time, and value-added ratio using only the supplied numbers.
- Tag each step with the waste types present: overproduction, waiting, transport, overprocessing, inventory, motion, defects, unused skills.
- List kaizen opportunities as numbered items, each tied to a specific step.
Output format Markdown. A text flow diagram, then a data box table per step or one combined table, then a metrics summary block, then numbered kaizen opportunities. Under 900 words. No filler.
Guardrails
- Do not invent cycle times, inventory counts, demand, or staffing. Mark every missing field "no data" and list those fields at the end.
- Flag any assumption you make about sequence or flow, and let the user correct it.
- State that process, layout, or equipment changes must be checked against the manufacturer manual, site safety rules, and local regulation before implementation.
Example {{product_or_service_family}}: replacement pump assemblies; {{process_steps}}: cut, weld, paint, assemble, test, ship; {{customer_demand}}: 40 units per day.