{"id":582,"date":"2026-02-25T10:20:39","date_gmt":"2026-02-25T10:20:39","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/"},"modified":"2026-02-25T10:20:39","modified_gmt":"2026-02-25T10:20:39","slug":"overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/","title":{"rendered":"Overloaded Diagrams: Too Much on One Canvas"},"content":{"rendered":"<p>Too much detail in BPMN turns a clear business process into a visual maze. I\u2019ve seen diagrams that span multiple screens, where a single flow contains 50+ activities, decision points, and exceptions. The result? A model that no one can read, maintain, or trust. This isn\u2019t just clutter\u2014it\u2019s a source of misunderstanding, rework, and failed automation. The root issue? A single diagram trying to represent too many scenarios, responsibilities, or levels of detail.<\/p>\n<p>My experience has taught me that a well-structured BPMN model should be <strong>readable at a glance<\/strong>. If you need to zoom in to see what\u2019s happening, or if your eyes are jumping from one corner to another, the diagram is overloaded. The fix isn\u2019t adding more labels or better colors\u2014it\u2019s rethinking the structure.<\/p>\n<p>This chapter lays out practical, field-tested techniques for splitting large BPMN models without losing context. You\u2019ll learn how to use sub-processes, levels of detail, and linked diagrams to keep your processes focused, scalable, and executable. You\u2019ll also discover how <strong>BPMN diagram refactoring<\/strong> is not a one-time chore\u2014it\u2019s a continuous practice that pays off in clarity and consistency.<\/p>\n<h2>The Hidden Costs of Overloaded BPMN Diagrams<\/h2>\n<p>When a BPMN diagram tries to do too much, it fails in ways that aren\u2019t always obvious. The model might technically follow the notation rules, but that doesn\u2019t mean it\u2019s useful.<\/p>\n<ul>\n<li><strong>Loss of clarity<\/strong>: Readers can\u2019t follow the main path. Decision logic gets buried in a sea of activities.<\/li>\n<li><strong>Increased maintenance burden<\/strong>: A single change may ripple across dozens of steps, increasing the risk of breaking something else.<\/li>\n<li><strong>Unrealistic expectations<\/strong>: Stakeholders assume the diagram shows reality. When the truth is it\u2019s a mix of scenarios, exceptions, and technical details.<\/li>\n<li><strong>High risk of errors<\/strong>: The more elements, the more likely a gateway is misconnected, or a loop never terminates.<\/li>\n<\/ul>\n<p>These problems are especially common when a process is modeled from the ground up without a clear plan. The diagram starts as a simple flow, but over time, new conditions, roles, and exceptions are added\u2014until the canvas is full.<\/p>\n<h2>When You Should Split a BPMN Diagram<\/h2>\n<p>Not every large process needs to be split. But when you see these signs, it\u2019s time to act:<\/p>\n<ul>\n<li>You can\u2019t show the entire diagram on one screen without scrolling.<\/li>\n<li>There are more than 10 decision points in a single flow.<\/li>\n<li>Multiple business units or systems are involved, but they\u2019re all in one pool.<\/li>\n<li>You\u2019re modeling both normal flow and multiple exception scenarios in one diagram.<\/li>\n<\/ul>\n<p>These are red flags that your <strong>too much detail in BPMN<\/strong> has become a liability. The solution is not to shrink the font. It\u2019s to restructure.<\/p>\n<h3>Three Fundamental Strategies for Splitting BPMN Models<\/h3>\n<p>There\u2019s no one-size-fits-all approach. But three strategies have consistently worked in real-world projects:<\/p>\n<h4>1. Use Sub-Processes for Internal Detail<\/h4>\n<p>Group related activities under a <strong>collapsed sub-process<\/strong> when the internal logic is complex but not critical to the high-level view.<\/p>\n<p>For example, a \u201cCredit Check\u201d activity can be a sub-process that includes:<\/p>\n<ul>\n<li>Verify credit score<\/li>\n<li>Check payment history<\/li>\n<li>Review outstanding debt<\/li>\n<li>Apply risk rating<\/li>\n<\/ul>\n<p>Keep the main process focused on the business outcome: \u201cApprove or decline loan.\u201d This is <strong>BPMN diagram refactoring<\/strong> at its most practical.<\/p>\n<h4>2. Apply Levels of Detail (LoD) for Different Audiences<\/h4>\n<p>Not every stakeholder needs the same level of detail. A business analyst might need a high-level view. An IT developer needs step-by-step logic.<\/p>\n<p>Use a <strong>two-tier approach<\/strong>:<\/p>\n<ul>\n<li><strong>Level 1 (High-level):<\/strong> Shows only major phases, decision points, and handoffs.<\/li>\n<li><strong>Level 2 (Detailed):<\/strong> Expands key sub-processes into full diagrams.<\/li>\n<\/ul>\n<p>Label each with a version or LoD tag. This allows different teams to access the right view.<\/p>\n<h4>3. Use Linked Diagrams for Scenarios and Variants<\/h4>\n<p>When multiple paths exist\u2014such as credit approval, rejection, and escalation\u2014don\u2019t try to fit them into one flow.<\/p>\n<p>Create separate diagrams:<\/p>\n<ul>\n<li><strong>Main Process<\/strong>: Normal approval flow<\/li>\n<li><strong>Sub-Process: Credit Review<\/strong>: Full credit check logic<\/li>\n<li><strong>Exception Flow: Escalation<\/strong>: How to handle failed checks<\/li>\n<\/ul>\n<p>Connect them using a <strong>call activity<\/strong> or <strong>choreography link<\/strong>. This keeps the main process clean and reusable.<\/p>\n<h2>How to Refactor a Large BPMN Diagram: A Step-by-Step Guide<\/h2>\n<p>Refactoring isn\u2019t about rewriting from scratch. It\u2019s about organizing intelligence that already exists.<\/p>\n<ol>\n<li><strong>Map the current scope<\/strong>: Identify all primary activities, decision points, and exceptions.<\/li>\n<li><strong>Group by theme<\/strong>: Cluster activities that belong together\u2014e.g., \u201cUnderwriting,\u201d \u201cRisk Assessment,\u201d \u201cCustomer Onboarding.\u201d<\/li>\n<li><strong>Choose the right container<\/strong>: Use sub-processes for internal logic, call activities for reusable flows, or separate diagrams for distinct scenarios.<\/li>\n<li><strong>Define clear boundaries<\/strong>: Each new diagram should have a clear start (e.g., \u201cRisk Approval Request Received\u201d) and end (e.g., \u201cRisk Rating Finalized\u201d).<\/li>\n<li><strong>Link with context<\/strong>: Add a brief description and reference to the parent process.<\/li>\n<\/ol>\n<p>Example:<\/p>\n<p>Original: One diagram with 30+ activities, including credit checks, risk scoring, and escalation paths.<\/p>\n<p>Refactored: Three diagrams:<\/p>\n<ul>\n<li>Main Process: \u201cLoan Approval Flow\u201d (high-level)<\/li>\n<li>Sub-Process: \u201cCredit Risk Assessment\u201d (detail)<\/li>\n<li>Separate Diagram: \u201cEscalation to Senior Review\u201d<\/li>\n<\/ul>\n<p>The new structure is easier to validate, review, and automate.<\/p>\n<h2>Best Practices: What to Avoid<\/h2>\n<p>Here are common mistakes that undermine refactoring:<\/p>\n<ul>\n<li><strong>Creating too many nested sub-processes<\/strong>: Depth beyond two levels makes it hard to follow.<\/li>\n<li><strong>Overusing call activities<\/strong>: If every task is a call, you lose the operational context.<\/li>\n<li><strong>Forgetting to document the hierarchy<\/strong>: Without clear labels, readers don\u2019t know which diagram is the \u201ctop\u201d level.<\/li>\n<li><strong>Mixing levels in one diagram<\/strong>: Don\u2019t show a high-level process next to a detailed technical workflow.<\/li>\n<\/ul>\n<p>Keep it simple. If a diagram has more than 15\u201320 visible activities, consider splitting it.<\/p>\n<h2>Table: Choosing the Right Splitting Technique<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Use Case<\/th>\n<th>Best Practice<\/th>\n<th>Example<\/th>\n<\/tr>\n<tr>\n<td>Internal logic too complex<\/td>\n<td>Use collapsed sub-process<\/td>\n<td>Credit check step as a sub-process<\/td>\n<\/tr>\n<tr>\n<td>Multiple business scenarios<\/td>\n<td>Create linked diagrams<\/td>\n<td>Approve vs. Reject paths<\/td>\n<\/tr>\n<tr>\n<td>Reused process across multiple flows<\/td>\n<td>Use call activity<\/td>\n<td>\u201cCustomer Verification\u201d used in 3 flows<\/td>\n<\/tr>\n<tr>\n<td>High-level overview needed<\/td>\n<td>Apply Level of Detail (LoD)<\/td>\n<td>Diagram A: High-level; Diagram B: Detailed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if my BPMN diagram is too large?<\/h3>\n<p>If you need to scroll in multiple directions, use a zoom level below 50%, or can\u2019t explain the process in one sentence, it\u2019s likely overloaded. Aim for fewer than 15\u201320 visible activities on screen.<\/p>\n<h3>Can I split a process across multiple pools?<\/h3>\n<p>Yes, but only when there are clear handoffs between organizations or departments. Use message flows to connect them. Avoid spreading one business process across multiple pools without a valid boundary.<\/p>\n<h3>What happens to the original diagram after splitting?<\/h3>\n<p>Keep it as a \u201cmaster\u201d or \u201csummary\u201d diagram. Use it to reference the child diagrams. Document which sub-processes are expanded where, and maintain version control.<\/p>\n<h3>Is it okay to have multiple diagrams for the same process?<\/h3>\n<p>Yes\u2014when each serves a different audience or purpose. A business owner needs a high-level view. A developer needs the detailed flow. Just ensure they\u2019re linked and consistent.<\/p>\n<h3>How do I prevent my team from creating overloaded diagrams in the future?<\/h3>\n<p>Implement a <strong>modular modeling standard<\/strong>. Define rules like: \u201cNo diagram should have more than 20 activities.\u201d Use model reviews to check for LoD alignment. Train teams to use sub-processes and call activities early.<\/p>\n<h3>What if my tool doesn\u2019t support sub-processes or call activities?<\/h3>\n<p>Use a tool that does. Most modern BPMN tools (e.g., Visual Paradigm) support these features. If your tool doesn\u2019t, consider upgrading. A poorly supported tool creates more problems than it solves.<\/p>\n<h2>Key Takeaways<\/h2>\n<p>Overloaded BPMN diagrams are not just messy\u2014they\u2019re dangerous. They hide flaws, confuse stakeholders, and make automation nearly impossible. The real solution isn\u2019t more effort\u2014it\u2019s smarter structure.<\/p>\n<p>Use <strong>sub-processes<\/strong> for internal logic, <strong>levels of detail<\/strong> for different audiences, and <strong>linked diagrams<\/strong> for multiple scenarios. This is <strong>splitting large BPMN models<\/strong> done right.<\/p>\n<p>When in doubt, ask: \u201cCan someone unfamiliar with this process understand it in under 90 seconds?\u201d If not, it\u2019s time to split, simplify, and restructure. The diagram you create today will be the blueprint your team follows tomorrow.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too much detail in BPMN turns a clear business process into a visual maze. I\u2019ve seen diagrams that span multiple screens, where a single flow contains 50+ activities, decision points, and exceptions. The result? A model that no one can read, maintain, or trust. This isn\u2019t just clutter\u2014it\u2019s a source of misunderstanding, rework, and failed [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":578,"menu_order":3,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-582","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Overloaded BPMN Diagrams: Fixing Too Much on One Canvas<\/title>\n<meta name=\"description\" content=\"Fix overloaded BPMN diagrams by splitting large models, using sub-processes, and refactoring for clarity. Learn how to avoid too much detail in BPMN and improve maintainability with proven techniques.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Overloaded BPMN Diagrams: Fixing Too Much on One Canvas\" \/>\n<meta property=\"og:description\" content=\"Fix overloaded BPMN diagrams by splitting large models, using sub-processes, and refactoring for clarity. Learn how to avoid too much detail in BPMN and improve maintainability with proven techniques.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/\",\"name\":\"Overloaded BPMN Diagrams: Fixing Too Much on One Canvas\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:20:39+00:00\",\"description\":\"Fix overloaded BPMN diagrams by splitting large models, using sub-processes, and refactoring for clarity. Learn how to avoid too much detail in BPMN and improve maintainability with proven techniques.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structural, Flow, and Layout Problems\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Overloaded Diagrams: Too Much on One Canvas\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Overloaded BPMN Diagrams: Fixing Too Much on One Canvas","description":"Fix overloaded BPMN diagrams by splitting large models, using sub-processes, and refactoring for clarity. Learn how to avoid too much detail in BPMN and improve maintainability with proven techniques.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/","og_locale":"pl_PL","og_type":"article","og_title":"Overloaded BPMN Diagrams: Fixing Too Much on One Canvas","og_description":"Fix overloaded BPMN diagrams by splitting large models, using sub-processes, and refactoring for clarity. Learn how to avoid too much detail in BPMN and improve maintainability with proven techniques.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"7 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/","name":"Overloaded BPMN Diagrams: Fixing Too Much on One Canvas","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:20:39+00:00","description":"Fix overloaded BPMN diagrams by splitting large models, using sub-processes, and refactoring for clarity. Learn how to avoid too much detail in BPMN and improve maintainability with proven techniques.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/overloaded-bpmn-diagrams-fixing-too-much-on-one-canvas\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Structural, Flow, and Layout Problems","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/"},{"@type":"ListItem","position":4,"name":"Overloaded Diagrams: Too Much on One Canvas"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/582","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/582\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/578"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=582"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=582"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}