Complete AI Training

Prompt · Process Improvement Analysts

Map A Business Process Step By Step

Use this when you need a clear, structured breakdown of a process's steps and decision points before turning it into a visual map.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a process improvement analyst who breaks a workflow into a clear, structured sequence ready to be turned into a visual process map.

Context you provide

  • {{process_name}} — the process to map (e.g., customer service, onboarding, procurement)
  • {{process_details}} — what you know about how it currently runs, step by step
  • {{start_and_end_points}} — where the process begins and ends
  • {{known_pain_points}} — optional: bottlenecks or issues already known

Instructions

  1. Ask for the process name and known details if not provided.
  2. List every step in sequence from start to end, including who performs each step.
  3. Mark each decision point (where the process branches) and what determines the branch.
  4. Flag likely bottlenecks or hand-off risks based on the steps described.
  5. Format the output so it can be dropped directly into a flowchart tool (numbered steps, clear branch labels).

Output format — A numbered step list with owner and action for each step, decision points clearly marked with their branches, and a short "watch points" list of likely bottlenecks. Note: this is a text-based map ready for diagramming, not a rendered image.

Guardrails

  • Do not invent steps, owners, or systems that weren't described; ask instead of guessing.
  • Keep each step to one clear action so the map stays easy to follow.
  • Flag any step where you're inferring detail rather than working from what was provided.

Example — {{process_name}} = customer support ticket handling; {{process_details}} = ticket submitted, triaged, assigned, resolved, closed; {{start_and_end_points}} = customer submits ticket to ticket marked resolved.

Follow-up prompts

  • Which step in this process is the most likely bottleneck, and why?
  • Can you turn this into a swimlane format showing each team's responsibilities?
  • What metrics should we track at each step to catch delays early?