{"id":570,"date":"2026-02-25T10:20:33","date_gmt":"2026-02-25T10:20:33","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/"},"modified":"2026-02-25T10:20:33","modified_gmt":"2026-02-25T10:20:33","slug":"bpmn-anti-patterns","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/","title":{"rendered":"Typical Anti-Patterns in BPMN Adoption"},"content":{"rendered":"

Too many teams treat BPMN like a fancy flowchart. That\u2019s the root of most adoption failures. A BPMN diagram isn\u2019t just a visual aid\u2014it\u2019s a living, executable specification. When you shortcut the method, you risk creating confusion, misalignment, and technical debt. I\u2019ve reviewed hundreds of BPMN diagrams over the past two decades, and the same patterns keep reappearing: jumping straight into tools, overloading diagrams, and modeling from the wrong perspective. These aren\u2019t minor oversights. They\u2019re BPMN adoption pitfalls<\/strong> that make models unusable for automation, audit, or training.<\/p>\n

Here\u2019s what you\u2019ll learn: the five most damaging bad BPMN habits<\/strong> that plague teams, why they happen, and how to correct them with real-world examples. This isn\u2019t theory\u2014it\u2019s what I\u2019ve seen break processes in live environments. By the end of this chapter, you\u2019ll know how to spot these common BPMN anti patterns<\/strong> before they cost you time, budget, and credibility.<\/p>\n

1. Treating BPMN as a Prettier Flowchart<\/h2>\n

Many modelers start by sketching a process flow on paper or in a tool, then apply BPMN symbols as if they were decorative. The result? A diagram that looks professional but lacks semantics.<\/p>\n

That\u2019s not BPMN. That\u2019s a flowchart with a badge.<\/p>\n

Every symbol in BPMN carries meaning. A start event isn\u2019t just a circle; it defines a trigger. A parallel gateway isn\u2019t just a cross\u2014it signals a split in control flow. Mistaking them for visual embellishments leads to ambiguity and misinterpretation.<\/p>\n

When you model without a method, you\u2019re not documenting a process\u2014you\u2019re documenting a guess.<\/p>\n

Why It Happens<\/h3>\n
    \n
  • Team members are used to simple flowcharts from school or past projects.<\/li>\n
  • Leaders expect „a diagram“ without clarifying the purpose.<\/li>\n
  • Tool vendors promote drag-and-drop ease, reinforcing the idea that design is incidental.<\/li>\n<\/ul>\n

    How to Fix It<\/h3>\n

    Start with a modeling purpose<\/strong>. Ask: Who is this for? What decision will it enable? Does it need to be executable?<\/em><\/p>\n

    Use the three-stage approach<\/strong>:<\/p>\n

      \n
    1. Define scope<\/strong>: What process are you modeling? Where does it start and end?<\/li>\n
    2. Define audience<\/strong>: Is this for IT, business, or external auditors?<\/li>\n
    3. Choose the right notation<\/strong>: Only then do you assign symbols based on semantics, not aesthetics.<\/li>\n<\/ol>\n

      When you treat BPMN as a language\u2014not a painting\u2014you build models that mean something.<\/p>\n

      2. Jumping Straight into a Tool Without a Method<\/h2>\n

      It\u2019s tempting. Open the tool, click \u201cNew Process,\u201d and start dragging shapes. You\u2019ll have a diagram in minutes. But you\u2019ll also have a mess.<\/p>\n

      Tools don\u2019t teach you BPMN\u2014they enable it. If you skip the method, you\u2019re not modeling; you\u2019re guessing.<\/p>\n

      I once reviewed a BPMN diagram generated from a spreadsheet. The modeler had no idea what a message flow was. The process had 37 activities, 12 gateways, and no clear ownership. It was a technical nightmare\u2014and completely unusable for automation.<\/p>\n

      The Hidden Cost of Tool-First Modeling<\/h3>\n
        \n
      • Design decisions are made on the fly, not through intention.<\/li>\n
      • Validation features are ignored because the modeler doesn\u2019t know they exist.<\/li>\n
      • Patterns from previous models aren\u2019t reused\u2014repetition creeps in.<\/li>\n<\/ul>\n

        Best Practice: Model on Paper First<\/h3>\n

        Before touching a tool, sketch the process on paper. Use sticky notes for activities, arrows for flow. This forces clarity.<\/p>\n

        Ask yourself:<\/p>\n

          \n
        • Does every activity have a clear owner?<\/li>\n
        • Is the flow unambiguous?<\/li>\n
        • Do gateways represent decisions, not just branches?<\/li>\n<\/ul>\n

          Once the logic is sound, only then bring it into the tool. That way, the tool becomes a precision instrument\u2014not a crutch.<\/p>\n

          3. Creating One Giant All-in-One Diagram<\/h2>\n

          \u201cWe need to see the whole customer journey.\u201d Sure. But \u201cwhole\u201d doesn\u2019t mean \u201call at once.\u201d<\/p>\n

          Overloading a single diagram with every possible path, exception, and role creates a visual labyrinth. It\u2019s not a model\u2014it\u2019s a memory test.<\/p>\n

          I once worked with a team that tried to model a loan approval process in one diagram. It included credit checks, underwriting, legal review, stakeholder sign-offs, and multiple retry paths. The flow crossed itself 14 times. No one could read it.<\/p>\n

          Why It\u2019s a Trap<\/h3>\n
            \n
          • Too many elements \u2192 too much visual noise.<\/li>\n
          • Too many decision points \u2192 hard to validate.<\/li>\n
          • Too many lanes \u2192 unclear ownership.<\/li>\n<\/ul>\n

            How to Break It Down<\/h3>\n

            Use the level-of-detail rule<\/strong>: One diagram should serve one purpose.<\/p>\n

            Split complex processes using:<\/p>\n

              \n
            • Sub-processes<\/strong>: Group related steps under a collapsible container.<\/li>\n
            • Call activities<\/strong>: Reference reusable templates (e.g., \u201cCredit Check\u201d).<\/li>\n
            • Linked diagrams<\/strong>: Use a diagram index or callout to reference other models.<\/li>\n<\/ul>\n

              For example:<\/p>\n

                \n
              • Diagram 1: High-level customer onboarding<\/li>\n
              • Diagram 2: Detailed credit check (as a sub-process)<\/li>\n
              • Diagram 3: Legal review (external process)<\/li>\n<\/ul>\n

                Now the model is readable, maintainable, and scalable.<\/p>\n

                4. Modeling from a Technical Perspective<\/h2>\n

                Too many models start with \u201cthe system\u201d instead of \u201cthe business.\u201d This leads to diagrams that look like technical workflows, not process blueprints.<\/p>\n

                Instead of \u201cUser submits form,\u201d you see \u201cPOST \/api\/submit.\u201d Instead of \u201cApprove application,\u201d you see \u201cCall ApprovalService.\u201d These aren\u2019t models\u2014they\u2019re API specs.<\/p>\n

                Don\u2019t confuse BPMN with system design. BPMN is a business process model. It\u2019s about what happens<\/em>, not how it\u2019s implemented<\/em>.<\/p>\n

                Red Flags of Technical Modeling<\/h3>\n
                  \n
                • Activity names include system IDs or URLs.<\/li>\n
                • Gateways depend on API response codes.<\/li>\n
                • Messages are named after headers or status codes.<\/li>\n<\/ul>\n

                  Fix: Shift to Business Language<\/h3>\n

                  Replace technical jargon with business verbs and objects:<\/p>\n\n\n\n\n\n\n
                  Technical<\/th>\nBusiness<\/th>\n<\/tr>\n
                  POST \/api\/submit<\/td>\nSubmit application form<\/td>\n<\/tr>\n
                  Call ApprovalService<\/td>\nInitiate approval workflow<\/td>\n<\/tr>\n
                  Handle error 401<\/td>\nRequest user re-authentication<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                  Now your model speaks to both business and IT.<\/p>\n

                  5. Ignoring Stakeholder Alignment<\/h2>\n

                  A model is only as good as the agreement behind it. When you build a process in isolation, you risk misrepresenting reality.<\/p>\n

                  I once saw a \u201cverified\u201d BPMN diagram where the business said \u201cwe review the contract,\u201d but the IT team said \u201cwe send it to legal.\u201d The model showed a single \u201cReview\u201d task\u2014but no one could say who did what.<\/p>\n

                  That\u2019s a classic case of unclear responsibility<\/strong>. It leads to handoff delays, rework, and frustration.<\/p>\n

                  How to Align Stakeholders<\/h3>\n

                  Use the stakeholder walkthrough<\/strong> technique:<\/p>\n

                    \n
                  1. Invite business, IT, and operations to a session.<\/li>\n
                  2. Walk through the process step by step.<\/li>\n
                  3. Ask: \u201cWho owns this step? What do they do?\u201d<\/li>\n
                  4. Use sticky notes to assign ownership in lanes.<\/li>\n
                  5. Document assumptions and edge cases.<\/li>\n<\/ol>\n

                    When everyone sees themselves in the model, trust builds\u2014and errors are caught early.<\/p>\n

                    Frequently Asked Questions<\/h2>\n

                    What\u2019s the biggest mistake in BPMN adoption?<\/h3>\n

                    Treating BPMN as a flowchart instead of a structured language. Without proper semantics, models become ambiguous, unexecutable, and unreliable.<\/p>\n

                    How do I avoid overload in a BPMN diagram?<\/h3>\n

                    Apply the one-model, one-purpose rule. Split complex processes into sub-processes, call activities, or separate diagrams. Use levels of detail to control complexity.<\/p>\n

                    Can I use BPMN for technical workflows?<\/h3>\n

                    BPMN is designed for business processes. Use it to model decision logic, handoffs, and responsibilities. For technical workflows, consider UML activity diagrams or sequence diagrams.<\/p>\n

                    How do I handle conflicting stakeholder views in BPMN?<\/h3>\n

                    Document differences. Use annotations or alternative paths. Prioritize clarity over consensus. If two stakeholders disagree, label both paths and note the uncertainty.<\/p>\n

                    Should I reuse BPMN elements across teams?<\/h3>\n

                    Yes. Build a small library of reusable components (e.g., \u201cApproval,\u201d \u201cError Handling\u201d). Use a shared repository to ensure consistency and reduce errors.<\/p>\n

                    What should I check in a peer review of a BPMN diagram?<\/h3>\n

                    Check for: valid start\/end events, correct gateway types, unbroken flow, clear ownership, consistent naming, and stakeholder alignment. Use a checklist to stay systematic.<\/p>\n","protected":false},"excerpt":{"rendered":"

                    Too many teams treat BPMN like a fancy flowchart. That\u2019s the root of most adoption failures. A BPMN diagram isn\u2019t just a visual aid\u2014it\u2019s a living, executable specification. When you shortcut the method, you risk creating confusion, misalignment, and technical debt. I\u2019ve reviewed hundreds of BPMN diagrams over the past two decades, and the same […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":566,"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-570","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nBPMN Anti-Patterns: Fix These Common Modeling Mistakes<\/title>\n<meta name=\"description\" content=\"Discover the most common BPMN adoption pitfalls and bad BPMN habits that sabotage process clarity. Learn how to avoid these anti-patterns and build professional, executable models.\" \/>\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\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Anti-Patterns: Fix These Common Modeling Mistakes\" \/>\n<meta property=\"og:description\" content=\"Discover the most common BPMN adoption pitfalls and bad BPMN habits that sabotage process clarity. Learn how to avoid these anti-patterns and build professional, executable models.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/\",\"name\":\"BPMN Anti-Patterns: Fix These Common Modeling Mistakes\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:20:33+00:00\",\"description\":\"Discover the most common BPMN adoption pitfalls and bad BPMN habits that sabotage process clarity. Learn how to avoid these anti-patterns and build professional, executable models.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Why BPMN Goes Wrong in Practice\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Typical Anti-Patterns in BPMN Adoption\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Anti-Patterns: Fix These Common Modeling Mistakes","description":"Discover the most common BPMN adoption pitfalls and bad BPMN habits that sabotage process clarity. Learn how to avoid these anti-patterns and build professional, executable models.","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\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/","og_locale":"de_DE","og_type":"article","og_title":"BPMN Anti-Patterns: Fix These Common Modeling Mistakes","og_description":"Discover the most common BPMN adoption pitfalls and bad BPMN habits that sabotage process clarity. Learn how to avoid these anti-patterns and build professional, executable models.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/","name":"BPMN Anti-Patterns: Fix These Common Modeling Mistakes","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:20:33+00:00","description":"Discover the most common BPMN adoption pitfalls and bad BPMN habits that sabotage process clarity. Learn how to avoid these anti-patterns and build professional, executable models.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/bpmn-anti-patterns\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Why BPMN Goes Wrong in Practice","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/why-bpmn-diagrams-go-wrong\/"},{"@type":"ListItem","position":4,"name":"Typical Anti-Patterns in BPMN Adoption"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/570\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/566"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=570"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}