The problem with traditional mapping workshops
Mapping a process typically takes weeks. You schedule workshops, gather people from different areas, draw post-its, discuss each step, redo the design, schedule another meeting because someone was absent. In the end, the map becomes outdated before it's even approved.
An alternative exists: record a conversation with whoever executes the process and transform that into validated BPMN in a fraction of the time. The secret lies in three points: asking the right questions during the conversation, structuring the answers into process elements, and validating only what matters with the team afterward.
What to ask in the initial conversation
The recording needs to capture the real process, not the ideal one described in some old manual. Start with the basic question: what triggers this process? It could be a customer request, a date on the calendar, a detected error, any event that initiates the sequence of activities.
Then, follow the flow: what happens first? Who does it? How long does it take on average? What does this person need to have on hand to execute? Where do they get the information? Who do they pass it to next?
Decisions are critical. Whenever someone says "then I check if" or "it depends on," ask: depends on what exactly? What are the possible paths? Who decides? Based on what criteria? Hypothetical example: "if the amount is above $10,000, it goes to the manager; below that, the analyst approves directly."
Ask about exceptions. What happens when something goes wrong? What if the system crashes? What if the customer doesn't respond? Real processes have alternative paths that nobody documents but everyone executes.
How to transform the conversation into BPMN elements
BPMN has a clear structure: events, activities, gateways (decisions), actors (swimlanes), and flows. The meeting transcript contains all these elements, they just need to be identified and organized.
Start events are phrases like "when the order arrives," "every 5th of the month," "as soon as the system notifies." End events appear as "then it ends," "process closed," "customer receives and done."
Activities are verbs: analyze, approve, send, calculate, verify, register. Each verb becomes a box in the diagram. The actor (who does it) defines the horizontal swimlane where the box goes.
Gateways appear in conditions: "if/then," "depends on," "could be A or B." An exclusive gateway (diamond with X) splits the flow into paths that don't happen simultaneously. A parallel gateway (diamond with +) shows simultaneous tasks.
Average times become annotations on activities. Systems used become annotations or attributes. Required documents become data objects connected to activities.
What to validate with the team afterward
Don't validate everything. Validate what generates decisions or changes. Show the BPMN diagram to the people who execute and ask: does this flow represent what you do? Are the decisions correct? Do the times make sense?
Focus on the forks. Confirm the criteria for each decision and who has authority. Hypothetical example: does the analyst really approve up to $10,000 alone, or do they need informal approval from the coordinator?
Validate the exceptions. Is the alternative path when the system crashes correct? What about when the supplier is late? Processes break at edge cases, not in the happy path.
Confirm the times. If you noted "2 hours" for credit analysis, ask: is this the real average time or a goal that never happens? Wrong times generate wrong estimates and frustration.
Ignore details that don't affect the flow. The form color, the exact email text, the field layout on the screen: this doesn't matter for the process map. What matters is the sequence, the decision, the responsible party, the time.
How IN transforms meetings into validated BPMN
IN · Business Intelligence receives the meeting recording (or a written description of the process) and generates the complete BPMN 2.0 diagram: events, activities, gateways, swimlanes, times. It also identifies pain points, estimates gains in hours and dollars, suggests to-be redesign, and creates AI agents to execute operational steps. The exported BPMN opens directly in Camunda or bpmn.io. You validate, adjust if necessary, and have the process mapped in a fraction of traditional time, ready for analysis and automation.
Informational content. Numerical examples are hypothetical.