{"id":579,"date":"2026-02-25T10:20:38","date_gmt":"2026-02-25T10:20:38","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/"},"modified":"2026-02-25T10:20:38","modified_gmt":"2026-02-25T10:20:38","slug":"bpmn-pool-and-lane-mistakes","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/","title":{"rendered":"Missing or Misleading Pools and Lanes"},"content":{"rendered":"

It\u2019s tempting to skip pools and lanes when modeling a simple process. After all, the flow seems clear enough\u2014start, do this, then do that. But that instinct leads to one of the most common causes of confusion: missing BPMN pools<\/strong> or poorly structured lanes. Without them, the model becomes ambiguous. Who is doing what? When does responsibility shift? It\u2019s like a conversation without speakers\u2014everyone assumes they know who said what, but they don\u2019t.<\/p>\n

I\u2019ve seen dozens of diagrams where multiple roles share a single lane, or departments are crammed into one pool. It looks efficient at first glance. But in reality, it creates a responsibility modeling issue<\/strong>. A single lane can’t represent multiple stakeholders without causing overlap, ambiguity, and handoff confusion. Worse, when you try to automate or audit such a model, it fails quickly because the ownership isn\u2019t clear.<\/p>\n

Here\u2019s what you gain from this chapter: a clear framework for when and how to use pools and lanes correctly. You\u2019ll learn how to diagnose problematic structures, restructure legacy diagrams, and apply a consistent, stakeholder-friendly approach that enforces clarity. This isn\u2019t about formalism\u2014it\u2019s about creating models that can be trusted, communicated, and executed.<\/p>\n

Why Pools and Lanes Matter: The Real Cost of Ambiguity<\/h2>\n

Every BPMN diagram is a communication artifact. If it\u2019s not clear who owns each step, it fails its primary purpose. Pools and lanes exist to answer one question: Who is responsible for this activity?<\/em><\/p>\n

When you omit pools, the model collapses into a single-actor narrative\u2014even if multiple departments or systems are involved. This isn\u2019t just inaccurate\u2014it\u2019s dangerous. In one project, a \u201csimple\u201d order fulfillment process spanned procurement, warehouse, and finance. No pools. No lanes. The team assumed \u201cthe system\u201d handled everything. When automation failed, it turned out no one had taken responsibility for the final approval step.<\/p>\n

That\u2019s an example of incorrect lane usage<\/strong>. Not every role needs its own pool. But each distinct responsibility\u2014especially if it involves different departments, customers, or systems\u2014should be in its own lane. This isn\u2019t about design flair. It\u2019s about preventing silent failures in execution.<\/p>\n

When Pools Are Necessary<\/h3>\n

Use a pool to represent a major participant in a collaboration:<\/p>\n

    \n
  • A department (e.g., HR, Finance)<\/li>\n
  • An external organization (e.g., a bank, supplier, customer)<\/li>\n
  • A system or application (e.g., CRM, ERP)<\/li>\n<\/ul>\n

    Always ask: Is this entity a distinct decision-maker or performer in the process?<\/em> If yes, it should be a pool.<\/p>\n

    When Lanes Are Required<\/h3>\n

    Lanes divide a pool into roles or sub-teams. Use them when responsibilities are split within a single organization or system.<\/p>\n

    For example, in an invoice approval process, the \u201cFinance Department\u201d might be the pool. Inside it, you\u2019d have lanes like \u201cAccounts Payable Clerk,\u201d \u201cManager,\u201d and \u201cAuditor.\u201d Each lane owns specific tasks.<\/p>\n

    Never use one lane to represent two different roles. It\u2019s a recipe for confusion. If you find yourself naming a lane \u201cTeam A \/ Team B,\u201d you\u2019ve already failed.<\/p>\n

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

    Mistake 1: Using a Single Lane for Multiple Departments<\/h3>\n

    Example: A single lane labeled \u201cOperations\u201d that contains tasks from Sales, Logistics, and Customer Service.<\/p>\n

    Why it fails: No one knows who\u2019s supposed to own the \u201cRespond to Customer Query\u201d task. Is it sales? Support? Both?<\/p>\n

    Fix: Split the pool into separate lanes. If the process involves both internal departments and external partners, use multiple pools with clear lanes inside each.<\/p>\n

    Mistake 2: Lumping All Roles into One Pool<\/h3>\n

    Example: An onboarding process where \u201cHR,\u201d \u201cIT,\u201d \u201cFinance,\u201d and \u201cManager\u201d are all in a single pool with no lanes.<\/p>\n

    Why it fails: The flow appears to be internal and unified. But in reality, handoffs happen between teams. Without lanes, the model hides who is responsible for each step.<\/p>\n

    Fix: Create a pool for the organization (e.g., \u201cCompany\u201d) and add lanes for each role: \u201cHR,\u201d \u201cIT Support,\u201d \u201cFinance,\u201d \u201cManager.\u201d Use message flows to show handoffs between lanes.<\/p>\n

    Mistake 3: Using Message Flows in the Wrong Context<\/h3>\n

    Example: Using a message flow between two tasks in the same pool without clear handoff intent.<\/p>\n

    Why it fails: It misrepresents the collaboration. Message flows should represent interactions between pools or between a pool and an external participant.<\/p>\n

    Fix: Only use message flows between separate pools. If the handoff is internal, use a sequence flow. If it\u2019s external, use message flow with a clear sender and receiver.<\/p>\n

    Mistake 4: Ignoring the Business Context<\/h3>\n

    Example: A lane labeled \u201cSystem\u201d that contains tasks like \u201cSend Email\u201d and \u201cUpdate Database\u201d without any human actor.<\/p>\n

    Why it fails: It confuses business process modeling with technical implementation. The model becomes unreadable to business stakeholders and unusable for handover or audit.<\/p>\n

    Fix: Replace abstract labels with business-facing actions. Instead of \u201cSend Email,\u201d use \u201cNotify applicant of status.\u201d If technical actions are necessary, model them in a separate technical process or use a sub-process with clear business outcome.<\/p>\n

    Step-by-Step: How to Correctly Structure Pools and Lanes<\/h2>\n
      \n
    1. Identify all participants<\/strong>: Who is involved in the process? List each distinct role, department, or system.<\/li>\n
    2. Group by ownership<\/strong>: Assign each participant to a pool. A single pool can contain multiple lanes.<\/li>\n
    3. Create lanes for roles<\/strong>: Within each pool, define lanes for each distinct role performing a task.<\/li>\n
    4. Assign tasks to lanes<\/strong>: Each activity must belong to exactly one lane. No ghost tasks.<\/li>\n
    5. Use flows correctly<\/strong>: Use sequence flows for internal order; message flows only between pools.<\/li>\n
    6. Review for clarity<\/strong>: Walk through the process. Can you identify who does what? Who triggers the next step?<\/li>\n<\/ol>\n

      Apply this method to any process, no matter how simple. It\u2019s not overkill\u2014it\u2019s the foundation of a trustworthy model.<\/p>\n

      Before and After: A Real Example<\/h2>\n

      Consider a loan application process. Before correction, the diagram had one pool with a single lane labeled \u201cOperations,\u201d and all tasks were in a sequence flow. The model implied a single actor was making all decisions.<\/p>\n

      After correction:<\/p>\n

        \n
      • Pools: \u201cCustomer,\u201d \u201cLoan Department,\u201d \u201cCredit Bureau,\u201d \u201cFinance Team\u201d<\/li>\n
      • Lanes: \u201cCustomer\u201d (only \u201cSubmit Application\u201d), \u201cLoan Department\u201d (e.g., \u201cReview Application,\u201d \u201cApprove\/Reject\u201d), \u201cCredit Bureau\u201d (e.g., \u201cVerify Credit Score\u201d), \u201cFinance Team\u201d (e.g., \u201cIssue Loan\u201d)<\/li>\n
      • Message flows: \u201cSend to Credit Bureau,\u201d \u201cReceive Credit Report,\u201d \u201cNotify Customer of Decision\u201d<\/li>\n<\/ul>\n

        The result? A clear, auditable model where responsibilities are visible, handoffs are explicit, and the flow reflects real collaboration.<\/p>\n

        Best Practices for Long-Term Clarity<\/h2>\n

        Consistency beats perfection. Even if a model isn\u2019t perfect, it should follow a shared standard. Here are three rules I use in my own work:<\/p>\n

          \n
        • One role, one lane<\/strong>: Avoid splitting roles across lanes. If a person performs two functions, model them as two separate lanes.<\/li>\n
        • Label lanes by role, not function<\/strong>: Use \u201cHR Manager,\u201d not \u201cApprover.\u201d It\u2019s more specific and stakeholder-friendly.<\/li>\n
        • Use color coding only with purpose<\/strong>: If you use color, define it in a legend. Avoid relying on color alone to communicate responsibility.<\/li>\n<\/ul>\n

          Remember: A well-structured pool and lane diagram isn\u2019t just about clarity\u2014it\u2019s about accountability. If a process fails, the model should help you trace responsibility, not obscure it.<\/p>\n

          Frequently Asked Questions<\/h2>\n

          Do I need a pool for every process?<\/h3>\n

          No. Use a pool only when collaboration between distinct entities is involved. For a single-actor process (e.g., \u201cProcess a customer complaint\u201d), you can use a single pool with one lane labeled \u201cSupport Agent.\u201d<\/p>\n

          Can I use multiple lanes in one pool?<\/h3>\n

          Yes\u2014this is standard practice. For example, a company pool can have lanes for \u201cSales,\u201d \u201cMarketing,\u201d \u201cIT,\u201d and \u201cFinance.\u201d Each lane owns its tasks.<\/p>\n

          What if a task involves multiple roles?<\/h3>\n

          Assign the task to the primary responsible lane. If multiple roles contribute, model it as a sub-process or use a shared task with a note. But never split one task across multiple lanes\u2014this creates ambiguity.<\/p>\n

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

          Only if the message represents a communication between roles within that pool. But it\u2019s rare. If the message is internal, use a sequence flow. Use message flows only when the sender and receiver are in different pools.<\/p>\n

          Why is my diagram still unreadable after adding lanes?<\/h3>\n

          Check layout. Ensure lanes are aligned, flows don\u2019t cross, and the process flows left to right or top to bottom. Cluttered layout undermines even the best structure.<\/p>\n

          Should I model the customer as a pool?<\/h3>\n

          Yes\u2014especially in customer-facing processes. It forces you to consider their role, actions, and expectations. A customer pool is not extra; it\u2019s essential for a complete journey model.<\/p>\n","protected":false},"excerpt":{"rendered":"

          It\u2019s tempting to skip pools and lanes when modeling a simple process. After all, the flow seems clear enough\u2014start, do this, then do that. But that instinct leads to one of the most common causes of confusion: missing BPMN pools or poorly structured lanes. Without them, the model becomes ambiguous. Who is doing what? When […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":578,"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-579","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nBPMN Pool and Lane Mistakes: Fix Responsibility Modeling Issues<\/title>\n<meta name=\"description\" content=\"Fix missing BPMN pools, incorrect lane usage, and responsibility modeling issues. Learn how to clarify ownership, handoffs, and collaboration with accurate pool and lane structure.\" \/>\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\/bpmn-pool-and-lane-mistakes\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Pool and Lane Mistakes: Fix Responsibility Modeling Issues\" \/>\n<meta property=\"og:description\" content=\"Fix missing BPMN pools, incorrect lane usage, and responsibility modeling issues. Learn how to clarify ownership, handoffs, and collaboration with accurate pool and lane structure.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/\" \/>\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\/bpmn-pool-and-lane-mistakes\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/\",\"name\":\"BPMN Pool and Lane Mistakes: Fix Responsibility Modeling Issues\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:20:38+00:00\",\"description\":\"Fix missing BPMN pools, incorrect lane usage, and responsibility modeling issues. Learn how to clarify ownership, handoffs, and collaboration with accurate pool and lane structure.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/#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\/bpmn-pool-and-lane-mistakes\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/#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\":\"Missing or Misleading Pools and Lanes\"}]},{\"@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":"BPMN Pool and Lane Mistakes: Fix Responsibility Modeling Issues","description":"Fix missing BPMN pools, incorrect lane usage, and responsibility modeling issues. Learn how to clarify ownership, handoffs, and collaboration with accurate pool and lane structure.","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\/bpmn-pool-and-lane-mistakes\/","og_locale":"pl_PL","og_type":"article","og_title":"BPMN Pool and Lane Mistakes: Fix Responsibility Modeling Issues","og_description":"Fix missing BPMN pools, incorrect lane usage, and responsibility modeling issues. Learn how to clarify ownership, handoffs, and collaboration with accurate pool and lane structure.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/","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\/bpmn-pool-and-lane-mistakes\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/","name":"BPMN Pool and Lane Mistakes: Fix Responsibility Modeling Issues","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:20:38+00:00","description":"Fix missing BPMN pools, incorrect lane usage, and responsibility modeling issues. Learn how to clarify ownership, handoffs, and collaboration with accurate pool and lane structure.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/#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\/bpmn-pool-and-lane-mistakes\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-bpmn-mistakes-and-how-to-avoid-them\/bpmn-structural-mistakes\/bpmn-pool-and-lane-mistakes\/#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":"Missing or Misleading Pools and Lanes"}]},{"@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\/579","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\/579\/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=579"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}