{"id":598,"date":"2026-02-25T10:20:47","date_gmt":"2026-02-25T10:20:47","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/"},"modified":"2026-02-25T10:20:47","modified_gmt":"2026-02-25T10:20:47","slug":"cross-department-bpmn-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/","title":{"rendered":"Misrepresenting Cross-Department Collaboration"},"content":{"rendered":"

When departments share a lane in a BPMN diagram, ownership dissolves into ambiguity. That\u2019s not collaboration \u2014 it\u2019s confusion disguised as teamwork. The core principle? Each department must have its own lane or pool<\/strong>. No exceptions. This rule prevents shared responsibility from becoming shared blame.<\/p>\n

Too many models use a single lane labeled \u201cFinance & HR\u201d or \u201cOperations Team.\u201d This may look efficient, but it erases accountability. When a task like \u201cApprove Expense\u201d appears in a shared lane, who owns it? Is it the Finance team? HR? A shared duty? That uncertainty ruins auditability and blocks automation.<\/p>\n

My advice? Start with the business reality: if two departments act independently, they need separate lanes. You\u2019ll save hours of rework, reduce miscommunication, and create models that actually reflect reality. You don\u2019t need complex diagrams to be clear \u2014 just honest structure.<\/p>\n

Why Misusing Lanes for Departments Is a Critical Error<\/h2>\n

Using a single lane for multiple departments violates BPMN\u2019s fundamental purpose: to make roles and handoffs explicit. When teams are crammed together, the model becomes a black box where actions are performed but ownership is invisible.<\/p>\n

Consider this real-world example: a loan approval process where \u201cCredit Analyst\u201d and \u201cRisk Manager\u201d both belong to the same lane. The handoff between them looks seamless \u2014 but in reality, the risk team often operates with different priorities, timelines, and escalation paths. Blending them creates a model that\u2019s accurate in form but useless in practice.<\/p>\n

Here\u2019s the trade-off: separating lanes adds visual complexity, but it delivers clarity. A well-structured collaboration diagram should be easy to follow by someone unfamiliar with the process.<\/p>\n

Red Flags of Misused Lanes<\/h3>\n
    \n
  • A single lane contains multiple roles from different departments.<\/li>\n\n \n
  • Labels like \u201cTeam A & B\u201d or \u201cShared Tasks\u201d appear instead of specific roles.<\/li>\n<\/limessage><\/liactivities><\/ul>\n

    Correcting Collaboration: Lanes, Pools, and Message Flows<\/h2>\n

    The fix is straightforward: assign each department its own pool or lane. Use pools for external partners (e.g., Customer, Vendor) and lanes within a pool for internal departments.<\/p>\n

    Every handoff must be either a sequence flow (within a pool) or a message flow (between pools). Message flows are mandatory for cross-department communication<\/strong>. They visually signal that one department sends information to another \u2014 and that message triggers the next step.<\/p>\n

    Let\u2019s say Finance needs to approve an invoice before HR processes payroll. In a corrected model:<\/p>\n

      \n
    1. Finance has its own lane.<\/li>\n
    2. \u201cReview Invoice\u201d is in the Finance lane.<\/li>\n
    3. A message flow labeled \u201cApproved Invoice\u201d goes to HR.<\/li>\n
    4. HR\u2019s \u201cProcess Payroll\u201d starts only after receiving that message.<\/li>\n<\/ol>\n

      This makes the dependency clear, the trigger visible, and the responsibility unambiguous.<\/p>\n

      Best Practices for Modeling Departmental Collaboration<\/h3>\n

      Use this checklist when modeling cross-department collaboration:<\/p>\n

        \n
      • Assign every department its own lane or pool.<\/li>\n
      • Never use a single lane for multiple business units.<\/li>\n
      • Use message flows to show communication between departments.<\/li>\n
      • Label message flows with clear, business-friendly descriptions (e.g., \u201cSend Approval Request\u201d).<\/li>\n
      • Ensure every message flow has a corresponding receiving task.<\/li>\n<\/ul>\n

        Common Pitfalls and How to Fix Them<\/h2>\n

        Even when you separate lanes, mistakes creep in. Here are the most frequent ones and how to avoid them.<\/p>\n

        Pitfall 1: Overusing Sequence Flows Between Pools<\/h3>\n

        Sequence flows are for internal process steps. Using them between pools implies a direct control flow \u2014 but departments don\u2019t control each other\u2019s actions. They communicate via messages.<\/p>\n

        Fix:<\/strong> Replace sequence flows with message flows. This enforces the correct model: one department sends a message, the other responds.<\/p>\n

        Pitfall 2: Invisible Handoffs<\/h3>\n

        Some models show a task in one department ending and a task in another starting \u2014 but no flow connects them. This creates a \u201cghost\u201d handoff, where the workflow seems to continue, but no mechanism triggers the next step.<\/p>\n

        Fix:<\/strong> Always use a message flow to link the end of one task to the start of another. Even if it\u2019s a simple \u201cnext step\u201d message, it must be visible.<\/p>\n

        Pitfall 3: Ambiguous Message Content<\/h3>\n

        Labeling a message flow as \u201cSend Data\u201d or \u201cPass Info\u201d is worse than no label at all. It tells no one what\u2019s being sent or why.<\/p>\n

        Fix:<\/strong> Use specific, outcome-based language. Examples:<\/p>\n

          \n
        • \u201cSend Approved Budget Proposal\u201d<\/li>\n
        • \u201cNotify Finance: Payment Request Ready\u201d<\/li>\n
        • \u201cForward HR Onboarding Form to Payroll\u201d<\/li>\n<\/ul>\n

          Real-World Example: Rebuilding a Broken Process<\/h2>\n

          Here\u2019s a before-and-after look at a real case I audited.<\/p>\n

          Before: Shared Lane, Confused Handoff<\/h3>\n
            \n
          • Lane: \u201cFinance & HR\u201d<\/li>\n
          • Tasks: \u201cReview Expense,\u201d \u201cApprove,\u201d \u201cProcess Payroll\u201d<\/li>\n
          • Sequence flows connect all tasks.<\/li>\n
          • No message flows.<\/li>\n<\/ul>\n

            Result: When asked who approves payroll, no one could say. The model implied HR did \u2014 but Finance had to approve first.<\/p>\n

            After: Clear Pools with Message Flows<\/h3>\n
              \n
            • Pools: \u201cFinance\u201d and \u201cHR\u201d<\/li>\n
            • Finance lane: \u201cReview Expense,\u201d \u201cSend Approval to HR\u201d<\/li>\n
            • Message flow: \u201cApproval Received\u201d from Finance to HR<\/li>\n
            • HR lane: \u201cProcess Payroll\u201d \u2014 starts after message.<\/li>\n<\/ul>\n

              Result: The model now reflects reality. The handoff is explicit. Auditors can trace the chain. Automation teams can build the correct triggers.<\/p>\n

              Key Takeaways<\/h2>\n

              Clear collaboration begins with structure. Never merge departments in one lane<\/strong>. Always use separate pools or lanes, and always use message flows to represent handoffs.<\/p>\n

              cross department BPMN mistakes<\/strong> aren\u2019t just about bad layout \u2014 they\u2019re about eroding accountability. A good model shows who does what, when, and how they\u2019re connected.<\/p>\n

              When you model collaboration correctly, you\u2019re not just creating a diagram. You\u2019re creating a contract between teams.<\/p>\n

              Frequently Asked Questions<\/h2>\n

              Should I always use separate pools for every department?<\/h3>\n

              No \u2014 if a department is a single team with a unified role (e.g., \u201cCustomer Support\u201d), one lane suffices. But if multiple departments (e.g., Sales, Marketing, IT) are involved in a process, each must have its own lane or pool.<\/p>\n

              Can I use message flows inside a single pool?<\/h3>\n

              Yes, but only when modeling communication between different roles within the same organization. For example, \u201cSend Report to Manager\u201d in the \u201cFinance\u201d lane uses a message flow because it\u2019s a handoff between roles.<\/p>\n

              What\u2019s the difference between message flow and sequence flow?<\/h3>\n

              Sequence flow shows control flow within a process. Message flow shows communication between separate processes or pools. Use sequence flow for internal steps. Use message flow for external or inter-role handoffs.<\/p>\n

              How do I handle a department that doesn\u2019t have a dedicated lane?<\/h3>\n

              If a team is small and only contributes minimally, you can include them in a larger lane. But if they make decisions or perform actions that affect the process, separate them into their own lane.<\/p>\n

              Can I reuse a message flow across multiple scenarios?<\/h3>\n

              Yes, but define it once in a message flow catalog or documentation. Avoid repeating the same message in multiple places unless it\u2019s a standard, widely accepted pattern.<\/p>\n

              Why is BPMN handoff clarity so important for automation?<\/h3>\n

              Automation tools rely on clear triggers. A message flow is a trigger. If handoffs are unclear, the system can\u2019t know when to execute the next step \u2014 leading to delays, errors, or failed workflows.<\/p>\n","protected":false},"excerpt":{"rendered":"

              When departments share a lane in a BPMN diagram, ownership dissolves into ambiguity. That\u2019s not collaboration \u2014 it\u2019s confusion disguised as teamwork. The core principle? Each department must have its own lane or pool. No exceptions. This rule prevents shared responsibility from becoming shared blame. Too many models use a single lane labeled \u201cFinance & […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":597,"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-598","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nCross-Department BPMN Mistakes to Avoid<\/title>\n<meta name=\"description\" content=\"Fix common BPMN mistakes in cross-department collaboration. Learn how to model clear ownership, proper lanes, and message flows to ensure auditable, executable processes.\" \/>\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\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cross-Department BPMN Mistakes to Avoid\" \/>\n<meta property=\"og:description\" content=\"Fix common BPMN mistakes in cross-department collaboration. Learn how to model clear ownership, proper lanes, and message flows to ensure auditable, executable processes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"1 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/\",\"name\":\"Cross-Department BPMN Mistakes to Avoid\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:20:47+00:00\",\"description\":\"Fix common BPMN mistakes in cross-department collaboration. Learn how to model clear ownership, proper lanes, and message flows to ensure auditable, executable processes.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common BPMN Mistakes and How to Avoid Them\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Collaboration and Interaction Mistakes\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Misrepresenting Cross-Department Collaboration\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Cross-Department BPMN Mistakes to Avoid","description":"Fix common BPMN mistakes in cross-department collaboration. Learn how to model clear ownership, proper lanes, and message flows to ensure auditable, executable processes.","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\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/","og_locale":"id_ID","og_type":"article","og_title":"Cross-Department BPMN Mistakes to Avoid","og_description":"Fix common BPMN mistakes in cross-department collaboration. Learn how to model clear ownership, proper lanes, and message flows to ensure auditable, executable processes.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"1 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/","name":"Cross-Department BPMN Mistakes to Avoid","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:20:47+00:00","description":"Fix common BPMN mistakes in cross-department collaboration. Learn how to model clear ownership, proper lanes, and message flows to ensure auditable, executable processes.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/cross-department-bpmn-mistakes\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Common BPMN Mistakes and How to Avoid Them","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/"},{"@type":"ListItem","position":3,"name":"Collaboration and Interaction Mistakes","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-collaboration-mistakes\/"},{"@type":"ListItem","position":4,"name":"Misrepresenting Cross-Department Collaboration"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/598","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/598\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/597"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=598"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=598"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}