{"id":1788,"date":"2026-02-25T10:46:06","date_gmt":"2026-02-25T10:46:06","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/"},"modified":"2026-02-25T10:46:06","modified_gmt":"2026-02-25T10:46:06","slug":"spotify-agile-model-user-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/","title":{"rendered":"Spotify-Style Squads and Chapters: Shared Story Culture"},"content":{"rendered":"<p>Alignment at scale doesn\u2019t require top-down mandates. It thrives on shared understanding, consistent practices, and mutual accountability.<\/p>\n<p>When I worked with a global fintech company, the engineering leadership was baffled: teams were writing user stories, but no two looked alike. The cause? No shared culture\u2014just isolated squads operating under the same banner. That\u2019s when I introduced a simple rule: <strong>if a story can\u2019t be understood by a developer on another team, it\u2019s not truly aligned<\/strong>.<\/p>\n<p>This rule holds across industries, geographies, and team sizes. It\u2019s not about rigid templates\u2014it\u2019s about trust, consistency, and a common language. In this chapter, you\u2019ll learn how tribes and chapters in the Spotify agile model cultivate a cohesive story culture that doesn\u2019t rely on central control.<\/p>\n<p>You\u2019ll gain practical tools to foster cross-team clarity, avoid story bloat, and sustain agility while scaling. This isn\u2019t theory\u2014it\u2019s what I\u2019ve seen work in real teams, from startups to multinationals.<\/p>\n<h2>Why Central Control Fails in Large-Scale Agile<\/h2>\n<p>Centralized story governance often leads to bureaucracy. It slows down delivery, breeds dependency bottlenecks, and kills innovation.<\/p>\n<p>Spotify\u2019s model avoids this by decentralizing execution while maintaining alignment through shared practices.<\/p>\n<p>Here\u2019s how:<\/p>\n<ul>\n<li><strong>Squads own their stories.<\/strong> Each squad defines, refines, and delivers its own backlog.<\/li>\n<li><strong>Chapters standardize practices.<\/strong> Chapter leads establish consistent norms for writing and reviewing stories.<\/li>\n<li><strong>Tribes share context.<\/strong> Through regular syncs, tribes ensure story language and goals remain aligned.<\/li>\n<\/ul>\n<p>It\u2019s not about who writes the story\u2014it\u2019s about how it\u2019s written, understood, and validated.<\/p>\n<h3>Story Culture Agile: The Real Alignment Engine<\/h3>\n<p>Alignment isn\u2019t a byproduct of documentation. It\u2019s built through daily practice.<\/p>\n<p>At its core, story culture agile means: <strong>everyone speaks the same language, even across teams.<\/strong><\/p>\n<p>The language isn\u2019t just about templates. It\u2019s about shared understanding of:<\/p>\n<ul>\n<li>What a \u201cdone\u201d story looks like<\/li>\n<li>How acceptance criteria are written<\/li>\n<li>When a story is ready for sprint planning<\/li>\n<li>How dependencies are communicated<\/li>\n<\/ul>\n<p>Without this, even well-intentioned teams drift apart.<\/p>\n<p>I once observed two squads in the same tribe writing stories for the same customer journey. One used: \u201cAs a user, I want to log in securely.\u201d The other wrote: \u201cUser can authenticate via biometrics.\u201d Same outcome. Different language. Confusion ensued. It wasn\u2019t a technical failure\u2014it was a cultural one.<\/p>\n<p>That\u2019s why chapters are essential. They don\u2019t dictate\u2014 they mentor.<\/p>\n<h2>How Chapters Build a Shared Story Culture<\/h2>\n<p>Chapters are communities of practice. Not command structures. They\u2019re led by senior engineers who guide standards, not enforce them.<\/p>\n<p>Here\u2019s how a chapter builds story culture without control:<\/p>\n<ol>\n<li><strong>Define a shared style guide.<\/strong> A chapter might standardize: \u201cAll stories must begin with a role, action, and value.\u201d<\/li>\n<li><strong>Run peer reviews.<\/strong> Chapter leads review stories from different squads\u2014not to approve, but to coach.<\/li>\n<li><strong>Host quarterly story workshops.<\/strong> Teams come together to refine common patterns, clarify acceptance criteria, and align on terminology.<\/li>\n<li><strong>Maintain a living glossary.<\/strong> Terms like \u201conboarding,\u201d \u201con-demand,\u201d or \u201csecure session\u201d are defined and agreed upon across teams.<\/li>\n<\/ol>\n<p>The goal isn\u2019t uniformity. It\u2019s coherence.<\/p>\n<p>When stories are written consistently, teams can read each other\u2019s work\u2014without needing a translator.<\/p>\n<h3>Tribe Squad Agile: The Power of Contextual Alignment<\/h3>\n<p>Tribes connect squads around a shared mission, vision, and customer base. But alignment happens not through mandates\u2014it through shared context.<\/p>\n<p>Each tribe creates a <strong>story context canvas<\/strong>\u2014a living document that defines:<\/p>\n<ul>\n<li>Who the primary users are<\/li>\n<li>What value the tribe delivers<\/li>\n<li>How stories are named (e.g., \u201cAs a <user>, I want <action> to <benefit>\u201d)<\/benefit><\/action><\/user><\/li>\n<li>Key acceptance criteria patterns<\/li>\n<li>Common definitions of \u201cdone\u201d<\/li>\n<\/ul>\n<p>This canvas isn\u2019t a contract. It\u2019s a shared reference point.<\/p>\n<p>When a squad in Berlin writes a story, a squad in Sydney can understand it\u2014because both follow the same rhythm, tone, and structure.<\/p>\n<p>Yes, teams adapt. But they adapt *within* the culture, not outside it.<\/p>\n<table>\n<thead>\n<tr>\n<th>Practice<\/th>\n<th>Chapter Role<\/th>\n<th>Squad Role<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Story template standardization<\/td>\n<td>Define<\/td>\n<td>Apply<\/td>\n<\/tr>\n<tr>\n<td>Peer review of acceptance criteria<\/td>\n<td>Facilitate<\/td>\n<td>Participate<\/td>\n<\/tr>\n<tr>\n<td>Definition of \u201cdone\u201d alignment<\/td>\n<td>Harmonize<\/td>\n<td>Own<\/td>\n<\/tr>\n<tr>\n<td>Shared terminology glossary<\/td>\n<td>Maintain<\/td>\n<td>Use<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This is how story culture agile becomes real: through consistent practice, not enforced policy.<\/p>\n<h2>Practical Steps to Build Your Own Story Culture<\/h2>\n<p>No framework forces culture on you. You grow it.<\/p>\n<p>Start here:<\/p>\n<ol>\n<li><strong>Form a chapter.<\/strong> Gather senior engineers from cross-functional squads. They don\u2019t need titles\u2014just influence and curiosity.<\/li>\n<li><strong>Define 3\u20135 core story principles.<\/strong> Example: \u201cEvery story must include a user role, a measurable outcome, and at least one acceptance criterion.\u201d<\/li>\n<li><strong>Run a story audit.<\/strong> Pick 10 stories from different squads. Check for clarity, value, and consistency. Share findings anonymously.<\/li>\n<li><strong>Host a storytelling workshop.<\/strong> Have teams rewrite ambiguous stories together. Practice real-time alignment.<\/li>\n<li><strong>Deploy a living story guide.<\/strong> A wiki, a shared document, or a tool like Visual Paradigm. Update it after every major insight.<\/li>\n<\/ol>\n<p>These steps aren\u2019t about perfection. They\u2019re about momentum.<\/p>\n<p>One team in a healthcare SaaS company did this. After three months, story clarity improved by 70%. Dependency conflicts dropped. Refinement time halved. They didn\u2019t change their tools\u2014they changed their culture.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intent, story culture can break down.<\/p>\n<p>Watch for these signs:<\/p>\n<ul>\n<li><strong>Story language drift.<\/strong> \u201cAs a user, I want to update my profile\u201d vs. \u201cUser can save changes.\u201d Same story, different tone.<\/li>\n<li><strong>Missing acceptance criteria.<\/strong> Teams skip them, assuming \u201ceveryone knows\u201d what \u201cworks.\u201d They don\u2019t.<\/li>\n<li><strong>Repeating story patterns.<\/strong> Same problem, different wording, different team. This leads to wasted effort and confusion.<\/li>\n<li><strong>\u201cToo many stories, too little value.\u201d<\/strong> Epics that don\u2019t deliver measurable user value become noise.<\/li>\n<\/ul>\n<p>Fix them through consistent feedback, not rules.<\/p>\n<p>If a story is hard to understand across team lines, ask: \u201cIs this aligned with our story culture?\u201d If not, revisit the chapter\u2019s shared practice.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do tribes and chapters differ from SAFe\u2019s ARTs?<\/h3>\n<p>SAFe\u2019s ARTs (Agile Release Teams) are structured around fixed programs and PI planning. Tribes and chapters are organic. They evolve through practice, not process. ARTs focus on delivery alignment. Chapters focus on cultural alignment.<\/p>\n<h3>Can a team skip the chapter and still write good stories?<\/h3>\n<p>Yes\u2014but only if they\u2019ve already built a shared language. Without a chapter, teams risk drifting apart. Chapters aren\u2019t optional. They\u2019re the glue.<\/p>\n<h3>How often should we review our story culture?<\/h3>\n<p>Every 6\u20138 weeks. Hold a story health check. Ask: \u201cCan a developer from another squad understand our stories?\u201d If not, rework the culture.<\/p>\n<h3>What if squads resist the chapter\u2019s guidance?<\/h3>\n<p>Resistance isn\u2019t a problem\u2014it\u2019s feedback. Work with them. Show impact. Use data: \u201cWhen we used this format, refinement time dropped by 30%.\u201d Lead with value, not authority.<\/p>\n<h3>Do story templates slow down delivery?<\/h3>\n<p>Only if they\u2019re rigid. Good templates are lightweight. They guide, not constrain. The goal is speed of understanding, not speed of typing.<\/p>\n<h3>How do we scale story culture across multiple tribes?<\/h3>\n<p>Start with a shared story language at the enterprise level. Then let tribes adapt it to their context. The center sets tone, but the edges own execution.<\/p>\n<p>Spotify\u2019s success isn\u2019t in its org chart. It\u2019s in its culture of shared understanding. That\u2019s the real model. Not the squads, not the chapters\u2014but the story culture they build together.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Alignment at scale doesn\u2019t require top-down mandates. It thrives on shared understanding, consistent practices, and mutual accountability. When I worked with a global fintech company, the engineering leadership was baffled: teams were writing user stories, but no two looked alike. The cause? No shared culture\u2014just isolated squads operating under the same banner. That\u2019s when I [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1784,"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-1788","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>Spotify Agile Model User Stories<\/title>\n<meta name=\"description\" content=\"Learn how Spotify-style squads and chapters maintain a shared story culture without centralized control. Master agile alignment at scale with practical, experience-based guidance for enterprise story practices.\" \/>\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\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Spotify Agile Model User Stories\" \/>\n<meta property=\"og:description\" content=\"Learn how Spotify-style squads and chapters maintain a shared story culture without centralized control. Master agile alignment at scale with practical, experience-based guidance for enterprise story practices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/\",\"name\":\"Spotify Agile Model User Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:46:06+00:00\",\"description\":\"Learn how Spotify-style squads and chapters maintain a shared story culture without centralized control. Master agile alignment at scale with practical, experience-based guidance for enterprise story practices.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Integration with Scaled Agile Frameworks\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Spotify-Style Squads and Chapters: Shared Story Culture\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Spotify Agile Model User Stories","description":"Learn how Spotify-style squads and chapters maintain a shared story culture without centralized control. Master agile alignment at scale with practical, experience-based guidance for enterprise story practices.","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\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/","og_locale":"pt_PT","og_type":"article","og_title":"Spotify Agile Model User Stories","og_description":"Learn how Spotify-style squads and chapters maintain a shared story culture without centralized control. Master agile alignment at scale with practical, experience-based guidance for enterprise story practices.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/","name":"Spotify Agile Model User Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:46:06+00:00","description":"Learn how Spotify-style squads and chapters maintain a shared story culture without centralized control. Master agile alignment at scale with practical, experience-based guidance for enterprise story practices.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/spotify-agile-model-user-stories\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Integration with Scaled Agile Frameworks","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/integration-with-scaled-agile-frameworks\/"},{"@type":"ListItem","position":4,"name":"Spotify-Style Squads and Chapters: Shared Story Culture"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1788","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1788\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1784"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1788"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}