{"id":1783,"date":"2026-02-25T10:46:04","date_gmt":"2026-02-25T10:46:04","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/"},"modified":"2026-02-25T10:46:04","modified_gmt":"2026-02-25T10:46:04","slug":"story-ownership-agile-cross-functional-accountability","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/","title":{"rendered":"Aligning Story Ownership with Cross-Functional Accountability"},"content":{"rendered":"<p>Most teams default to assigning user stories to a single developer or a single team lead. This feels safe\u2014like a clear chain of command. But in large-scale Agile, that single point of ownership becomes a bottleneck, a single point of failure, and a silent killer of flow.<\/p>\n<p>I\u2019ve seen it too many times: a story sits in the queue because \u201cthe developer is busy,\u201d or a team delays delivery because \u201cthe backend person hasn\u2019t signed off.\u201d The real issue isn\u2019t resource shortage. It\u2019s misaligned ownership.<\/p>\n<p>Story ownership agile isn\u2019t about assigning a name to a task. It\u2019s about defining who is accountable for what\u2014and how that responsibility flows across team boundaries. This chapter shows how to structure ownership so that teams move forward together, not in parallel with friction.<\/p>\n<p>When done right, cross-functional accountability ensures every story has clarity, momentum, and a shared sense of purpose. You\u2019ll learn how to map ownership without over-assigning, how to define roles that support delivery, and how to prevent dependency rot from derailing your sprints.<\/p>\n<h2>Why Single-Owner Models Break at Scale<\/h2>\n<p>At the team level, assigning a single owner for a story is simple. But when multiple teams must collaborate on a single feature, that model collapses under complexity.<\/p>\n<p>Consider a user story: \u201cAs a customer, I want to update my profile so I can change my address.\u201d The front-end team owns the UI. The back-end team owns the API. The security team must review data access. The compliance team must validate privacy rules.<\/p>\n<p>Assigning one person to \u201cown\u201d this story isn\u2019t just inaccurate\u2014it\u2019s dangerous. It creates false ownership, silos, and a culture where \u201cI\u2019m not responsible\u201d becomes the default response.<\/p>\n<p>Instead, we must shift to a model where ownership is distributed, but accountability is clear. This is where cross functional accountability comes in\u2014not as a buzzword, but as a practical, repeatable way to align teams around outcomes.<\/p>\n<h3>Three Pillars of Sustainable Story Ownership<\/h3>\n<p>True story ownership agile rests on three pillars:<\/p>\n<ul>\n<li><strong>Clarity of Responsibility:<\/strong> Who decides when the story is done? Who ensures the acceptance criteria are met?<\/li>\n<li><strong>Shared Accountability:<\/strong> When something breaks, no one hides behind \u201cI wasn\u2019t responsible.\u201d Everyone is expected to contribute.<\/li>\n<li><strong>Flow Over Formality:<\/strong> The goal isn\u2019t to document ownership in a spreadsheet. It\u2019s to enable smooth, fast delivery across teams.<\/li>\n<\/ul>\n<p>These aren\u2019t abstract ideals. They\u2019re the foundation of how mature Agile teams actually work. The key is to define ownership in terms of outcomes, not roles.<\/p>\n<h2>Ownership Mapping Agile: A Practical Framework<\/h2>\n<p>Ownership mapping agile is the process of visually assigning roles and responsibilities across teams for each story. It\u2019s not a one-time activity. It\u2019s a living practice that evolves with the product and the team.<\/p>\n<p>Start by asking: Who must be involved for this story to be delivered? Then map each role to a specific responsibility\u2014not just \u201cwho will code,\u201d but \u201cwho ensures the data is encrypted?\u201d<\/p>\n<p>Here\u2019s a simple framework I use in enterprise settings:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Role<\/th>\n<th>Responsibility<\/th>\n<th>Expected Output<\/th>\n<\/tr>\n<tr>\n<td>Delivery Owner<\/td>\n<td>Ensures the story is ready, accepted, and delivered in the sprint<\/td>\n<td>Done-by-sprint delivery<\/td>\n<\/tr>\n<tr>\n<td>Integration Lead<\/td>\n<td>Manages API contracts, shared data models, and integration testing<\/td>\n<td>Validated integration with other teams<\/td>\n<\/tr>\n<tr>\n<td>Compliance Guardian<\/td>\n<td>Verifies data privacy, security, and audit requirements<\/td>\n<td>Compliance sign-off<\/td>\n<\/tr>\n<tr>\n<td>Customer Advocate<\/td>\n<td>Ensures the story delivers real business value<\/td>\n<td>Validation by real users or stakeholders<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This structure doesn\u2019t replace team-level ownership. It enhances it. Each team can appoint their own person to fulfill these roles\u2014no central control, no bureaucracy.<\/p>\n<p>When I worked with a financial services organization, their compliance team was constantly delayed because they weren\u2019t involved early enough. We implemented this ownership mapping model. Within two sprints, compliance sign-offs moved from \u201clast minute\u201d to \u201cearly in refinement.\u201d The outcome? Zero delivery delays due to compliance issues for the next six months.<\/p>\n<h3>When Teams Share Ownership: The \u201cYes, And\u201d Rule<\/h3>\n<p>One of the most effective practices I\u2019ve seen is the \u201cYes, and\u201d rule during story grooming. When two teams are working on a shared story, instead of saying \u201cWe can\u2019t do that until you finish,\u201d they say \u201cYes, and here\u2019s how we can help you deliver earlier.\u201d<\/p>\n<p>For example:<\/p>\n<p><em>Front-end team:<\/em> \u201cWe\u2019re blocked because the API contract isn\u2019t final.\u201d<\/p>\n<p><em>Back-end team:<\/em> \u201cYes, and we can ship a draft contract today that satisfies your needs. We\u2019ll update it after the compliance review.\u201d<\/p>\n<p>This isn\u2019t optimism. It\u2019s a commitment to cross-functional accountability.<\/p>\n<p>That\u2019s the shift: from \u201cI\u2019m not responsible\u201d to \u201cHow can I help?\u201d<\/p>\n<h2>How to Build Ownership Mapping into Your Workflow<\/h2>\n<p>Ownership mapping agile isn\u2019t an add-on. It\u2019s built into how you prepare and manage stories.<\/p>\n<p>Here\u2019s a five-step process I\u2019ve used across 12+ enterprise programs:<\/p>\n<ol>\n<li><strong>Identify High-Value Stories:<\/strong> Start with stories that impact multiple teams or require cross-functional integration.<\/li>\n<li><strong>Map Roles in Advance:<\/strong> Before refinement, define the roles (Integration Lead, Compliance Guardian, etc.) and assign them to team members.<\/li>\n<li><strong>Clarify Handoff Points:<\/strong> Define when and how information transfers between teams\u2014e.g., \u201cAPI contract must be shared 48 hours before sprint review.\u201d<\/li>\n<li><strong>Include in Refinement:<\/strong> Discuss ownership roles during backlog refinement. Ensure everyone agrees on responsibilities.<\/li>\n<li><strong>Review in Retrospective:<\/strong> After delivery, reflect: \u201cWhere did ownership break down? What can we improve?\u201d<\/li>\n<\/ol>\n<p>This process doesn\u2019t add time\u2014it removes delays caused by miscommunication, rework, and dependency confusion.<\/p>\n<h3>Common Pitfalls in Cross-Functional Accountability<\/h3>\n<p>Even with a solid model, teams fall into traps:<\/p>\n<ul>\n<li><strong>Over-Assigning Roles:<\/strong> Too many \u201cguardians\u201d slow down progress. Limit to essential roles.<\/li>\n<li><strong>Assigning Roles to Individuals, Not Teams:<\/strong> Ownership should be team-based. One person shouldn\u2019t carry all the weight.<\/li>\n<li><strong>Ignoring the \u201cHow\u201d of Handoffs:<\/strong> Defining roles is not enough. You must define how information flows.<\/li>\n<\/ul>\n<p>Remember: accountability is not about blame. It\u2019s about clarity and shared commitment.<\/p>\n<h2>Ownership at Scale: From Teams to Programs<\/h2>\n<p>At the program level, ownership mapping agile becomes a coordination mechanism. Instead of tracking individual tasks, you track responsibilities across teams.<\/p>\n<p>For example, in a SAFe environment, a Feature may involve multiple teams. The Product Owner of the Feature should not dictate who does what. Instead, they should facilitate a session where teams define who owns what\u2014based on expertise, capacity, and dependency needs.<\/p>\n<p>This isn\u2019t delegation. It\u2019s alignment. The Product Owner ensures the feature is viable. The teams ensure the work is done correctly.<\/p>\n<p>As a rule: if a story requires input from two or more teams, it must include cross-functional accountability from day one.<\/p>\n<h3>Ownership Isn\u2019t a Contract\u2014It\u2019s a Promise<\/h3>\n<p>Think of story ownership agile not as a legal document, but as a team agreement. It\u2019s a promise that \u201cI\u2019ll do my part, and you\u2019ll do yours.\u201d<\/p>\n<p>When that promise holds, delivery becomes predictable. When it breaks, delays follow.<\/p>\n<p>My advice? Start small. Pick one high-impact story. Apply ownership mapping agile. Measure the difference in delivery speed, rework, and team satisfaction. Then scale it.<\/p>\n<p>It doesn\u2019t require new tools. It requires a shift in mindset: from \u201cWho\u2019s responsible?\u201d to \u201cHow can we be responsible together?\u201d<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What does ownership mapping agile actually look like in practice?<\/h3>\n<p>It\u2019s a visual table or diagram where each story lists the roles involved\u2014like Integration Lead, Compliance Guardian, and Customer Advocate\u2014and who from which team holds each. This is reviewed during refinement and updated as needed.<\/p>\n<h3>How do you handle ownership when teams are in different time zones?<\/h3>\n<p>Use asynchronous communication. During refinement, assign roles in writing. Set clear handoff windows (e.g., \u201cAPI contract must be shared by 10 AM your time\u201d). Document all decisions in the story\u2019s metadata.<\/p>\n<h3>Can a story have multiple delivery owners?<\/h3>\n<p>Not in the same sense. There should be one primary delivery owner per story\u2014typically the team lead or tech lead from the team that owns the main delivery. But the responsibilities can be shared across teams. The key is clarity on who is accountable for completion.<\/p>\n<h3>What if a team refuses to assign an ownership role?<\/h3>\n<p>Address it early. Ownership mapping agile is not optional in cross-team work. If a team avoids it, the risk of delay increases. Facilitate a conversation: \u201cWhat\u2019s making it hard to assign a role? How can we help?\u201d<\/p>\n<h3>How often should we review ownership mapping agile?<\/h3>\n<p>At a minimum, during each PI planning and sprint retrospective. But if a story spans multiple sprints, review ownership during mid-sprint check-ins.<\/p>\n<h3>Does this contradict Agile\u2019s \u201cself-organizing teams\u201d principle?<\/h3>\n<p>No. It enhances it. Self-organizing teams choose who fulfills each role. The framework doesn\u2019t dictate who\u2014just what the roles are and what they\u2019re responsible for. This preserves autonomy while ensuring accountability.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams default to assigning user stories to a single developer or a single team lead. This feels safe\u2014like a clear chain of command. But in large-scale Agile, that single point of ownership becomes a bottleneck, a single point of failure, and a silent killer of flow. I\u2019ve seen it too many times: a story [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1776,"menu_order":6,"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-1783","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>Story Ownership Agile: Cross-Functional Accountability<\/title>\n<meta name=\"description\" content=\"Master story ownership agile with cross-functional accountability models that empower teams, reduce bottlenecks, and sustain flow in large-scale Agile environments.\" \/>\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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Story Ownership Agile: Cross-Functional Accountability\" \/>\n<meta property=\"og:description\" content=\"Master story ownership agile with cross-functional accountability models that empower teams, reduce bottlenecks, and sustain flow in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/\" \/>\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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/\",\"name\":\"Story Ownership Agile: Cross-Functional Accountability\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:46:04+00:00\",\"description\":\"Master story ownership agile with cross-functional accountability models that empower teams, reduce bottlenecks, and sustain flow in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Cross-Team Collaboration and Flow\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Aligning Story Ownership with Cross-Functional Accountability\"}]},{\"@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":"Story Ownership Agile: Cross-Functional Accountability","description":"Master story ownership agile with cross-functional accountability models that empower teams, reduce bottlenecks, and sustain flow in large-scale Agile environments.","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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/","og_locale":"pl_PL","og_type":"article","og_title":"Story Ownership Agile: Cross-Functional Accountability","og_description":"Master story ownership agile with cross-functional accountability models that empower teams, reduce bottlenecks, and sustain flow in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/","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\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/","name":"Story Ownership Agile: Cross-Functional Accountability","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:46:04+00:00","description":"Master story ownership agile with cross-functional accountability models that empower teams, reduce bottlenecks, and sustain flow in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/story-ownership-agile-cross-functional-accountability\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Cross-Team Collaboration and Flow","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/"},{"@type":"ListItem","position":4,"name":"Aligning Story Ownership with Cross-Functional Accountability"}]},{"@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\/1783","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\/1783\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1776"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1783"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}