[{"data":1,"prerenderedAt":359},["ShallowReactive",2],{"\u002Fen\u002Fblog\u002Fmap-business-process-one-meeting":3,"\u002Fen\u002Fblog\u002Fmap-business-process-one-meeting-surround":342,"\u002Fen\u002Fblog\u002Fmap-business-process-one-meeting-alternates":353},{"id":4,"title":5,"authors":6,"badge":12,"body":14,"date":327,"description":328,"extension":329,"i18nKey":330,"image":331,"meta":334,"navigation":335,"path":336,"seo":337,"stem":339,"updated":340,"__hash__":341},"posts_en\u002Fen\u002Fblog\u002Fmap-business-process-one-meeting.md","How to Map a Business Process in One Meeting",[7],{"name":8,"to":9,"avatar":10},"Stef Kaptein","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fstef-kaptein\u002F",{"src":11,"alt":8},"\u002Fcompany\u002Fstef.png",{"label":13},"Process mapping",{"type":15,"value":16,"toc":310},"minimark",[17,21,24,29,32,35,52,55,69,72,76,79,82,99,102,106,109,112,116,119,122,126,129,132,146,149,153,156,182,185,189,192,196,199,203,206,210,213,217,293,296,300,303,307],[18,19,20],"p",{},"Mapping a business process often takes longer than it should. A workshop is scheduled. People explain how the process works. Someone takes notes. After the meeting, those notes still need to be translated into a process model. Questions appear, another meeting is scheduled, and several versions of the process start circulating.",[18,22,23],{},"It does not have to work that way. With the right people, the right questions and a clear structure, you can capture a surprisingly complete business process model in a single meeting. The key is to treat the meeting as a process-mapping session rather than a general discussion about the process.",[25,26,28],"h2",{"id":27},"before-the-meeting-define-the-process-boundary","Before the meeting: define the process boundary",[18,30,31],{},"Do not start with individual activities. First establish exactly which process you are mapping. A useful process has a clear beginning and end.",[18,33,34],{},"For example, instead of \"We are going to map our sales process,\" define the scope as:",[36,37,38,46],"ul",{},[39,40,41,45],"li",{},[42,43,44],"strong",{},"Start:"," a qualified customer requests a quotation.",[39,47,48,51],{},[42,49,50],{},"End:"," the customer accepts or rejects the quotation.",[18,53,54],{},"This prevents the workshop from expanding into every process connected to sales, finance, customer service and operations. Before the meeting, establish four things:",[36,56,57,60,63,66],{},[39,58,59],{},"What triggers the process?",[39,61,62],{},"What result marks the end of the process?",[39,64,65],{},"Who is involved?",[39,67,68],{},"What level of detail is actually needed?",[18,70,71],{},"The goal is not to document the entire organisation. The goal is to understand one process from start to finish.",[25,73,75],{"id":74},"invite-the-people-who-actually-know-the-process","Invite the people who actually know the process",[18,77,78],{},"One of the biggest process-modeling mistakes is only inviting managers. Managers often know how a process should work. The people performing it know how it actually works.",[18,80,81],{},"For a useful business process modeling session, try to include:",[36,83,84,87,90,93,96],{},[39,85,86],{},"the process owner;",[39,88,89],{},"one or more people who perform the process;",[39,91,92],{},"someone who receives the output of the process;",[39,94,95],{},"subject-matter experts where necessary;",[39,97,98],{},"the facilitator.",[18,100,101],{},"For more complicated processes, representatives from different teams may be required. You do not necessarily need ten people in the room. You need the right people.",[25,103,105],{"id":104},"start-with-the-happy-path","Start with the happy path",[18,107,108],{},"Once the boundaries are clear, resist the temptation to immediately discuss every possible exception. Start with the simplest question: \"What normally happens?\"",[18,110,111],{},"Imagine you are mapping a customer order process. The first version is usually a short, straight sequence of steps. That is your initial process flow. It probably isn't complete, and that is fine. You now have a structure that everyone can see and challenge.",[25,113,115],{"id":114},"ask-what-happens-next","Ask \"what happens next?\"",[18,117,118],{},"This is one of the most effective questions a process facilitator can ask. For every activity, ask: what happens next? Then: who does that? And: what needs to happen before they can do it?",[18,120,121],{},"This gradually turns a conversation into a structured business process model. Avoid spending too much time discussing wording. You can improve activity names later. At this stage, you are trying to discover the flow.",[25,123,125],{"id":124},"find-the-decisions","Find the decisions",[18,127,128],{},"A process is rarely a perfectly straight line. At certain points, something is evaluated and the path changes. These are the decisions that become gateways or branching logic in a BPMN diagram or other process model.",[18,130,131],{},"Ask questions such as:",[36,133,134,137,140,143],{},[39,135,136],{},"Can something different happen here?",[39,138,139],{},"What determines what happens next?",[39,141,142],{},"Is this always approved? What happens if the answer is no?",[39,144,145],{},"Can more than one path happen at the same time?",[18,147,148],{},"Every decision you surface is essential to understanding the actual process.",[25,150,152],{"id":151},"the-most-important-question-what-if-it-goes-wrong","The most important question: \"what if it goes wrong?\"",[18,154,155],{},"The happy path is usually easy to describe. The exceptions are where process knowledge becomes valuable. After establishing the normal process, go through it again and ask: what can go wrong here?",[36,157,158,161,164,167,170,173,176,179],{},[39,159,160],{},"incomplete customer information;",[39,162,163],{},"invalid payment details;",[39,165,166],{},"unavailable products;",[39,168,169],{},"rejected payments;",[39,171,172],{},"damaged inventory;",[39,174,175],{},"failed deliveries;",[39,177,178],{},"cancelled orders;",[39,180,181],{},"returned orders.",[18,183,184],{},"Then ask: what happens when that occurs? This is often where the real process emerges. A diagram containing only the happy path may look clean, but it can give a misleading representation of how work actually happens.",[25,186,188],{"id":187},"ask-about-waiting","Ask about waiting",[18,190,191],{},"Not every important process step is an activity. Processes frequently stop and wait for something. Ask whether you are waiting for someone, information or a deadline, what happens if nobody responds, and whether something automatically happens after a certain period. These situations can become events in BPMN and other process-modeling approaches.",[25,193,195],{"id":194},"identify-responsibility","Identify responsibility",[18,197,198],{},"Once the main flow is visible, determine who performs each activity. Ask who owns each step, which team performs it, whether responsibility moves between departments, and whether a step is performed by a person or automatically by a system. This becomes particularly important when using BPMN process modeling, where pools and lanes can communicate responsibility.",[25,200,202],{"id":201},"dont-turn-the-workshop-into-a-bpmn-lesson","Don't turn the workshop into a BPMN lesson",[18,204,205],{},"If participants don't know BPMN, don't spend half the meeting teaching BPMN notation. The facilitator should translate the conversation into the model. Participants need to understand the process; they do not necessarily need to understand every symbol in the process modeling software.",[25,207,209],{"id":208},"build-the-process-while-people-are-talking","Build the process while people are talking",[18,211,212],{},"If the facilitator only takes written notes, there is a second job after the meeting: turning those notes into the process diagram. A better approach is to create the process model during the workshop. Participants can immediately correct sequencing and missing paths. This creates an immediate feedback loop: discuss, model, review, correct.",[25,214,216],{"id":215},"a-practical-60-minute-agenda","A practical 60-minute agenda",[218,219,220,233],"table",{},[221,222,223],"thead",{},[224,225,226,230],"tr",{},[227,228,229],"th",{},"Time",[227,231,232],{},"Activity",[234,235,236,245,253,261,269,277,285],"tbody",{},[224,237,238,242],{},[239,240,241],"td",{},"0-5 min",[239,243,244],{},"Define purpose, start and end",[224,246,247,250],{},[239,248,249],{},"5-15 min",[239,251,252],{},"Capture the happy path",[224,254,255,258],{},[239,256,257],{},"15-30 min",[239,259,260],{},"Identify decisions and alternative paths",[224,262,263,266],{},[239,264,265],{},"30-40 min",[239,267,268],{},"Identify exceptions and failure scenarios",[224,270,271,274],{},[239,272,273],{},"40-50 min",[239,275,276],{},"Add responsibilities, systems and events",[224,278,279,282],{},[239,280,281],{},"50-57 min",[239,283,284],{},"Walk through the complete process",[224,286,287,290],{},[239,288,289],{},"57-60 min",[239,291,292],{},"Confirm open questions and ownership",[18,294,295],{},"For very complex processes, one meeting may not be enough. But the same structure still prevents the workshop from becoming an unstructured conversation.",[25,297,299],{"id":298},"finish-with-a-walkthrough","Finish with a walkthrough",[18,301,302],{},"Do not finish when the diagram looks complete. Read it from beginning to end and test the normal, rejected, exception and timeout scenarios. If the process model can answer those questions, you have created useful process documentation.",[25,304,306],{"id":305},"the-objective-isnt-a-beautiful-diagram","The objective isn't a beautiful diagram",[18,308,309],{},"A process-mapping meeting is successful when the people involved agree: \"Yes, this is how the process actually works.\" A visually perfect diagram that represents the wrong process has little value. A clear and accurate model gives you something you can analyse, communicate and improve.",{"title":311,"searchDepth":312,"depth":312,"links":313},"",2,[314,315,316,317,318,319,320,321,322,323,324,325,326],{"id":27,"depth":312,"text":28},{"id":74,"depth":312,"text":75},{"id":104,"depth":312,"text":105},{"id":114,"depth":312,"text":115},{"id":124,"depth":312,"text":125},{"id":151,"depth":312,"text":152},{"id":187,"depth":312,"text":188},{"id":194,"depth":312,"text":195},{"id":201,"depth":312,"text":202},{"id":208,"depth":312,"text":209},{"id":215,"depth":312,"text":216},{"id":298,"depth":312,"text":299},{"id":305,"depth":312,"text":306},"2026-08-13","A practical facilitator's guide to capturing a complete business process model in a single meeting, from the happy path to the exceptions that reveal how work really happens.","md","map-in-one-meeting",{"src":332,"alt":333},"\u002Fillustrations\u002Fworkflow.svg","A BPMN diagram of an order-intake process with a stock-check gateway",{},true,"\u002Fen\u002Fblog\u002Fmap-business-process-one-meeting",{"title":5,"description":338},"Learn how to map a business process in a single meeting. A facilitator's guide to process mapping, BPMN, exceptions and decisions.","en\u002Fblog\u002Fmap-business-process-one-meeting",null,"7-K6piUHY1089QM_cx1FZKLo-EYow7mH2FJejkUuUw8",[343,348],{"title":344,"path":345,"stem":346,"description":347,"children":-1},"As-Is vs. To-Be Process Mapping","\u002Fen\u002Fblog\u002Fas-is-vs-to-be-process-mapping","en\u002Fblog\u002Fas-is-vs-to-be-process-mapping","How to improve a business process diagram without modeling everything twice",{"title":349,"path":350,"stem":351,"description":352,"children":-1},"Text to BPMN","\u002Fen\u002Fblog\u002Ftext-to-bpmn","en\u002Fblog\u002Ftext-to-bpmn","How to Turn a Process Description Into a Clear BPMN Diagram",[354,356],{"code":355,"path":336},"en",{"code":357,"path":358},"nl","\u002Fnl\u002Fblog\u002Feen-bedrijfsproces-in-kaart-brengen-in-een-meeting",1787928890339]