{"id":592,"date":"2026-02-25T10:20:44","date_gmt":"2026-02-25T10:20:44","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/"},"modified":"2026-02-25T10:20:44","modified_gmt":"2026-02-25T10:20:44","slug":"bpmn-level-of-detail-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/","title":{"rendered":"Wrong Level of Detail: Too High, Too Low, or Mixed"},"content":{"rendered":"<p>Too many modelers start with a blank canvas and assume they must capture every click, every field, every state change. That\u2019s the trap. I\u2019ve seen diagrams so overloaded with technical steps that even the business analyst can\u2019t find the actual decision points. On the other end, I\u2019ve reviewed models so abstract\u2014\u201cProcess starts\u201d \u2192 \u201cProcess ends\u201d\u2014that no one can tell what\u2019s really happening.<\/p>\n<p>These are not just aesthetic issues. They\u2019re communication failures. The wrong level of detail breaks trust. A diagram that\u2019s too deep confuses stakeholders; one that\u2019s too shallow hides critical logic. The result? Misunderstandings, rework, and automation failures.<\/p>\n<p>This chapter cuts through the noise. You\u2019ll learn how to choose the right BPMN detail level based on context and audience. We\u2019ll show how to fix mixed-level diagrams, simplify overly complex models, and rebuild abstract ones for clarity. You\u2019ll walk away with a structured approach that turns vague or messy diagrams into trustworthy, executable models.<\/p>\n<h2>Why Level of Detail Matters in BPMN<\/h2>\n<p>Every BPMN diagram serves a purpose. That purpose determines its level of detail.<\/p>\n<p>Modeling a customer onboarding process for executives? Focus on key milestones: application submission, eligibility check, document upload, approval. No need to show every button click or error validation.<\/p>\n<p>But if you&#8217;re handing this to developers to implement, you need to break down the &#8220;eligibility check&#8221; into conditions: \u201ccredit score &gt; 650\u201d, \u201cresidency status verified\u201d, \u201cno fraud flags\u201d. That\u2019s where detail becomes essential.<\/p>\n<p>Here\u2019s the truth: <strong>no single level fits all<\/strong>. A model meant for stakeholder review cannot function as a technical blueprint. Confusing the two leads to wasted time, rework, and frustration.<\/p>\n<h3>Common Patterns of Misjudged Detail<\/h3>\n<p><strong>Too abstract BPMN models<\/strong> often use generic labels like &#8220;Process data&#8221;, &#8220;Handle request&#8221;, or &#8220;Complete task&#8221;. They may skip decision points or merge multiple steps into one. This makes it impossible to verify whether all scenarios are covered.<\/p>\n<p><strong>Over detailed BPMN diagrams<\/strong> include system-level actions: &#8220;Click &#8216;Submit&#8217; button&#8221;, &#8220;Validate field X against regex&#8221;, &#8220;Call API \/v1\/verify&#8221;. These are not business events\u2014they\u2019re implementation artifacts. They don\u2019t belong in a BPMN model intended to represent business intent.<\/p>\n<p>When both extremes appear in one diagram, you have a mixed-level mess. A step like &#8220;Approve Application&#8221; might be split into &#8220;Click Approve button&#8221;, &#8220;Submit form&#8221;, &#8220;Wait for confirmation&#8221; \u2014 but the next step is &#8220;Review applicant\u2019s background&#8221;, which is high-level. This inconsistency breaks flow and confuses everyone.<\/p>\n<h2>Choosing the Right BPMN Detail Level<\/h2>\n<p>There\u2019s no universal rule. But there\u2019s a framework. Use this decision tree to guide your modeling choices.<\/p>\n<ol>\n<li><strong>Who is the audience?<\/strong> Executives? IT teams? Audit teams? End users?<\/li>\n<li><strong>What\u2019s the goal?<\/strong> Communicate scope? Enable automation? Document compliance?<\/li>\n<li><strong>What\u2019s the process stage?<\/strong> Strategy? Design? Implementation? Audit?<\/li>\n<\/ol>\n<p>Let\u2019s break it down.<\/p>\n<h3>For Executive or Strategic Review<\/h3>\n<p>Use high-level models with 5\u20137 key activities. Focus on value streams, handoffs, and outcomes.<\/p>\n<p>Example: A customer onboarding process might be summarized as:<\/p>\n<ul>\n<li>Application Received<\/li>\n<li>Eligibility Check<\/li>\n<li>Document Verification<\/li>\n<li>Approval \/ Rejection<\/li>\n<li>Onboarding Completion<\/li>\n<\/ul>\n<p>Use call activities to represent complex subprocesses. No internal detail needed.<\/p>\n<h3>For Technical or Implementation Use<\/h3>\n<p>Decompose high-level steps into granular, executable tasks. Include decision points, exception flows, and system interactions.<\/p>\n<p>Example: \u201cEligibility Check\u201d becomes:<\/p>\n<ul>\n<li>Verify credit score (&gt; 650?)<\/li>\n<li>Check employment history (\u22652 years?)<\/li>\n<li>Validate ID and address match<\/li>\n<li>Run fraud risk assessment<\/li>\n<li>Make eligibility decision<\/li>\n<\/ul>\n<p>Use gateways to model decision logic. Show alternate paths for rejection, fraud flags, or incomplete data.<\/p>\n<h3>For Collaboration or Cross-Functional Alignment<\/h3>\n<p>Use detailed models to align departments. Show ownership, handoffs, and communication flows.<\/p>\n<p>Example: The \u201cDocument Verification\u201d step might involve:<\/p>\n<ul>\n<li>Bank sends documents via secure portal<\/li>\n<li>Compliance team reviews documents<\/li>\n<li>Requests missing items via message flow<\/li>\n<li>Updates status when complete<\/li>\n<\/ul>\n<p>Use message flows to show communication between departments. Keep the focus on responsibility and timing.<\/p>\n<h2>How to Re-Level a Diagram<\/h2>\n<p>When you inherit a model that\u2019s either too abstract or too detailed, don\u2019t start over. Re-level it systematically.<\/p>\n<h3>Step 1: Audit the Audience and Purpose<\/h3>\n<p>Ask: Who will use this? What are they trying to do? Is the goal to explain, implement, or audit?<\/p>\n<p>If the model is for a compliance audit, you need full traceability. If it\u2019s for a sprint planning meeting, focus on user stories and outcomes.<\/p>\n<h3>Step 2: Identify Mixed Levels<\/h3>\n<p>Scan the diagram. Look for:<\/p>\n<ul>\n<li>One step labeled \u201cSubmit form\u201d followed by \u201cClick Submit button\u201d<\/li>\n<li>\u201cApprove\u201d next to \u201cVerify identity via ID check\u201d<\/li>\n<li>A step labeled \u201cProcess\u201d that includes technical verbs like \u201ccall\u201d, \u201cvalidate\u201d, \u201cretrieve\u201d<\/li>\n<\/ul>\n<p>These are red flags. They signal a mix of business and technical levels.<\/p>\n<h3>Step 3: Group and Refactor<\/h3>\n<p>Group related activities into subprocesses. Use <strong>call activities<\/strong> to reference reusable logic.<\/p>\n<p>Example:<\/p>\n<pre><code>Subprocess: Verify Identity\n- Check government ID\n- Match photo to applicant\n- Confirm expiration date\n<\/code><\/pre>\n<p>Replace \u201cVerify identity via ID check\u201d with a call activity pointing to this subprocess.<\/p>\n<h3>Step 4: Apply the 80\/20 Rule<\/h3>\n<p>Focus on the 20% of steps that drive 80% of the outcome. Remove low-impact steps that don\u2019t affect decision-making or handoffs.<\/p>\n<p>Ask: \u201cWould removing this step change the process outcome?\u201d If no, it may be unnecessary detail.<\/p>\n<h2>Decision Matrix: What Level to Use<\/h2>\n<p>Here\u2019s a quick reference for choosing detail based on context.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Purpose<\/th>\n<th>Audience<\/th>\n<th>Recommended Detail Level<\/th>\n<\/tr>\n<tr>\n<td>Strategic planning<\/td>\n<td>Executives, board<\/td>\n<td>High-level, 5\u20137 steps<\/td>\n<\/tr>\n<tr>\n<td>Process improvement<\/td>\n<td>Business analysts, process owners<\/td>\n<td>Medium, includes decisions, exceptions<\/td>\n<\/tr>\n<tr>\n<td>System implementation<\/td>\n<td>Developers, testers<\/td>\n<td>Low-level, includes system actions, logic<\/td>\n<\/tr>\n<tr>\n<td>Compliance or audit<\/td>\n<td>Internal audit, regulators<\/td>\n<td>Medium to low, with traceability<\/td>\n<\/tr>\n<tr>\n<td>Training or onboarding<\/td>\n<td>New hires, cross-functional teams<\/td>\n<td>Medium, with clear labels and flows<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Best Practices for Consistent Detail<\/h2>\n<p>Here\u2019s how to maintain consistency across your models.<\/p>\n<ul>\n<li><strong>Use call activities for reusable logic<\/strong>: Never repeat a subprocess in multiple diagrams. Use a call activity to reference it.<\/li>\n<li><strong>Label steps with verb-object structure<\/strong>: \u201cReview application\u201d not \u201cProcess review\u201d.<\/li>\n<li><strong>Keep gateways simple<\/strong>: Use clear, business-friendly conditions. Avoid technical logic like \u201cif field X is not null\u201d.<\/li>\n<li><strong>Document assumptions<\/strong>: Add annotations for edge cases or rules not captured in the diagram.<\/li>\n<li><strong>Use consistent terminology<\/strong>: If you call it \u201capproval\u201d in one diagram, don\u2019t call it \u201csign-off\u201d in another.<\/li>\n<\/ul>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between too abstract BPMN models and over detailed BPMN diagrams?<\/h3>\n<p>Too abstract models hide decision points and miss critical logic. They use vague labels like \u201chandle request\u201d or \u201cprocess data\u201d, making them useless for implementation. Over detailed diagrams include technical steps like \u201cclick submit button\u201d or \u201ccall API endpoint\u201d, which are not business events and break the model\u2019s intent.<\/p>\n<h3>How do I know if my BPMN model is at the right level of detail?<\/h3>\n<p>Ask: \u201cWould someone unfamiliar with the process understand this from the diagram alone?\u201d If not, adjust. Test with your target audience. If stakeholders ask \u201cwhat happens next?\u201d too often, it\u2019s too abstract. If they say \u201cthat\u2019s not how it works\u201d, it\u2019s likely too detailed.<\/p>\n<h3>Can I have multiple levels of detail in one BPMN diagram?<\/h3>\n<p>Not in a single view. Mixing levels confuses readers and breaks the model\u2019s integrity. Instead, use <strong>subprocesses<\/strong> to represent detailed logic. Reference them with call activities. This preserves the high-level flow while allowing drill-down when needed.<\/p>\n<h3>How should I model a process that\u2019s both business and technical?<\/h3>\n<p>Model the business process first. Then, create a separate technical view if needed. Use DMN to model logic, and link it to BPMN. Never embed technical steps like \u201ccall API\u201d in a business process diagram. That\u2019s a modeling error that undermines credibility.<\/p>\n<h3>What\u2019s the best way to re-level an existing BPMN diagram?<\/h3>\n<p>Start by identifying the audience and purpose. Then, audit for mixed levels. Group activities, use call activities for repeated logic, simplify labels, and remove system-level actions. Keep the core flow clear and aligned with business intent.<\/p>\n<h3>Should I use the same level of detail for every process in my company?<\/h3>\n<p>No. Different processes serve different purposes. Use high-level models for strategy, medium for operations, and low for systems. The key is consistency in <strong>how<\/strong> you apply level of detail, not the level itself.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many modelers start with a blank canvas and assume they must capture every click, every field, every state [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":591,"menu_order":0,"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-592","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>BPMN Level of Detail Mistakes: Fix Your Models<\/title>\n<meta name=\"description\" content=\"Fix over detailed BPMN diagrams and too abstract BPMN models. Learn how to choose the right BPMN detail level for your audience and purpose with practical guidance and real examples.\" \/>\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\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Level of Detail Mistakes: Fix Your Models\" \/>\n<meta property=\"og:description\" content=\"Fix over detailed BPMN diagrams and too abstract BPMN models. Learn how to choose the right BPMN detail level for your audience and purpose with practical guidance and real examples.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/\",\"name\":\"BPMN Level of Detail Mistakes: Fix Your Models\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:20:44+00:00\",\"description\":\"Fix over detailed BPMN diagrams and too abstract BPMN models. Learn how to choose the right BPMN detail level for your audience and purpose with practical guidance and real examples.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scope, Levels, and Process Boundaries\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Wrong Level of Detail: Too High, Too Low, or Mixed\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Level of Detail Mistakes: Fix Your Models","description":"Fix over detailed BPMN diagrams and too abstract BPMN models. Learn how to choose the right BPMN detail level for your audience and purpose with practical guidance and real examples.","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\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/","og_locale":"ja_JP","og_type":"article","og_title":"BPMN Level of Detail Mistakes: Fix Your Models","og_description":"Fix over detailed BPMN diagrams and too abstract BPMN models. Learn how to choose the right BPMN detail level for your audience and purpose with practical guidance and real examples.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"7\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/","name":"BPMN Level of Detail Mistakes: Fix Your Models","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:20:44+00:00","description":"Fix over detailed BPMN diagrams and too abstract BPMN models. Learn how to choose the right BPMN detail level for your audience and purpose with practical guidance and real examples.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/bpmn-level-of-detail-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Scope, Levels, and Process Boundaries","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-scope-mistakes\/"},{"@type":"ListItem","position":4,"name":"Wrong Level of Detail: Too High, Too Low, or Mixed"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/592\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/591"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=592"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}