{"id":1767,"date":"2026-02-25T10:45:58","date_gmt":"2026-02-25T10:45:58","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/"},"modified":"2026-02-25T10:45:58","modified_gmt":"2026-02-25T10:45:58","slug":"strategic-alignment-agile","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/","title":{"rendered":"How User Stories Enable Strategic Alignment"},"content":{"rendered":"<p>Most teams default to writing stories in isolation\u2014focused on tasks, technical specs, or feature checklists. But that approach severs the link between execution and strategy. I\u2019ve seen this happen repeatedly: teams deliver perfectly written stories, only to realize months later that the work didn\u2019t advance the business goal. The real power of user stories lies not just in clarity, but in their ability to reflect organizational intent.<\/p>\n<p>Agile strategy connection isn\u2019t about forcing alignment through mandates. It\u2019s about designing stories so that every increment reflects a strategic objective. When done well, the narrative of a user story becomes a proxy for value\u2014visible, measurable, and traceable.<\/p>\n<p>What you\u2019ll learn here is how to write stories that don\u2019t just describe what to build, but why it matters. You\u2019ll learn to anchor your backlog to OKRs, ensure each story maps to measurable outcomes, and maintain flow across teams without losing sight of the bigger picture.<\/p>\n<h2>Why Stories Are the Bridge Between Strategy and Execution<\/h2>\n<p>Too many organizations treat strategy as a top-down document and execution as a bottom-up process. The gap between them is filled with assumptions, misalignment, and wasted effort.<\/p>\n<p>User stories, when designed intentionally, become the bridge. They translate abstract goals\u2014like \u201cimprove customer retention\u201d or \u201creduce onboarding time\u201d\u2014into tangible, testable, and valuable work.<\/p>\n<p>The key isn\u2019t the format. It\u2019s the intent behind the format. A well-written story doesn\u2019t just say \u201cas a user, I want to\u2026\u201d\u2014it reflects a deliberate choice to serve a specific business outcome.<\/p>\n<h3>From OKR to Story: A Direct Mapping<\/h3>\n<p>Every story should answer: How does this support a measurable objective? When I worked with a financial services firm, their team struggled to align sprint goals with their OKR to \u201creduce customer friction in digital onboarding.\u201d<\/p>\n<p>We started by asking: What does \u201creducing friction\u201d actually mean? They identified three pain points: form abandonment, unclear error messages, and missing progress tracking.<\/p>\n<p>We then turned each pain point into a story:<\/p>\n<ul>\n<li><strong>As a new customer, I want to see a progress bar during onboarding so I know how far I\u2019ve come.<\/strong><\/li>\n<li><strong>As a user, I want clear error messages when I enter invalid data so I can correct mistakes quickly.<\/strong><\/li>\n<li><strong>As a user, I want to be redirected to my previous step after fixing an error so I don\u2019t lose time.<\/strong><\/li>\n<\/ul>\n<p>These stories weren\u2019t just tasks\u2014they were direct contributions to a strategic goal. Each was evaluated against the same success criteria: reduced abandonment rate by 15% within two sprints.<\/p>\n<p>When stories are built this way, they become more than work items. They become indicators of strategic progress.<\/p>\n<h2>Techniques to Ensure User Story Alignment<\/h2>\n<p>Alignment isn\u2019t automatic. It requires intentional design and consistent practices across teams.<\/p>\n<h3>1. Use the \u201cWhy\u201d Question in Story Refinement<\/h3>\n<p>At every refinement session, ask: Why is this story needed? If the answer isn\u2019t tied to a business outcome, consider reprioritizing or rephrasing.<\/p>\n<p>For example: \u201cAs a user, I want to log in with my email\u201d is too generic. \u201cAs a user, I want to log in with my email so I can access my profile faster\u201d is better\u2014but still weak.<\/p>\n<p>Ask again: Why does faster access matter? Maybe \u201cso I can update my address before a delivery.\u201d Now it links to a real business impact: higher delivery success rate.<\/p>\n<p>Keep asking \u201cwhy\u201d until you reach a strategic reason.<\/p>\n<h3>2. Tag Stories with Strategic Themes<\/h3>\n<p>Use lightweight tagging systems to link stories to initiatives, OKRs, or strategic themes.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>Theme:<\/strong> Customer Onboarding<\/li>\n<li><strong>OKR:<\/strong> Q3 OKR 1 \u2013 Reduce onboarding drop-off by 20%<\/li>\n<li><strong>Product Area:<\/strong> Digital Experience<\/li>\n<\/ul>\n<p>These tags are not bureaucratic overhead. They enable traceability during PI planning, retrospectives, and governance reviews.<\/p>\n<p>When someone asks, \u201cWhy did we build this?\u201d the answer is clear: Because it supports a strategic goal, and the data proves it.<\/p>\n<h3>3. Create a Strategic Backlog Layer<\/h3>\n<p>At the enterprise level, don\u2019t just aggregate stories. Create a strategic backlog that lives above the product backlogs.<\/p>\n<p>This layer contains:<\/p>\n<ul>\n<li>High-level initiatives tied to OKRs<\/li>\n<li>Features that deliver measurable outcomes<\/li>\n<li>Dependencies that span multiple teams<\/li>\n<\/ul>\n<p>Each item in this layer is a statement of intent. A feature like \u201cImproved Onboarding Flow\u201d isn\u2019t a story\u2014it\u2019s a goal. It\u2019s the umbrella under which all related stories are grouped.<\/p>\n<p>When teams refine stories, they must confirm: How does this support the strategic feature? If the connection isn\u2019t clear, the story is either misaligned or needs rework.<\/p>\n<p>Over time, this layer becomes your strategic compass.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intentions, alignment can break down.<\/p>\n<h3>1. Writing Stories That Serve Internal Processes, Not Customers<\/h3>\n<p>Example: \u201cAs a developer, I want to add a logger to the API\u201d is a technical task, not a user story. It doesn\u2019t serve a user or deliver value.<\/p>\n<p>Instead, ask: What does the user get from this? Perhaps: \u201cAs a support agent, I want to trace failed API calls so I can resolve customer issues faster.\u201d<\/p>\n<p>Reframing the story around actual user impact ensures it\u2019s relevant to organizational goals.<\/p>\n<h3>2. Letting Story Quantity Replace Story Quality<\/h3>\n<p>More stories don\u2019t equal more strategy. I\u2019ve seen teams with 500+ stories in a sprint, none of which clearly tied to a goal.<\/p>\n<p>Focus on quality over quantity. A single well-written story that advances a strategic objective is worth ten vague tasks.<\/p>\n<h3>3. Losing the Line of Sight During PI Planning<\/h3>\n<p>PI planning often drifts into task planning. Teams focus on \u201cwhat\u201d to build, not \u201cwhy\u201d it matters.<\/p>\n<p>Solution: Start PI planning with a strategy review. Every team must present: \u201cWhat strategic goal does this feature serve?\u201d<\/p>\n<p>If a team can\u2019t answer, the feature may need rework or reconsideration.<\/p>\n<h2>Measuring Alignment: Key Metrics to Track<\/h2>\n<p>Alignment isn\u2019t just qualitative. It must be measurable.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Measure<\/th>\n<th>How to Track<\/th>\n<th>Target<\/th>\n<\/tr>\n<tr>\n<td>Strategic Story Ratio<\/td>\n<td>Percentage of stories linked to OKRs or initiatives<\/td>\n<td>\u2265 80%<\/td>\n<\/tr>\n<tr>\n<td>Story-to-OKR Coverage<\/td>\n<td>Number of OKRs with at least one story linked<\/td>\n<td>100% of active OKRs<\/td>\n<\/tr>\n<tr>\n<td>Refinement Feedback Rate<\/td>\n<td>Stories rejected during refinement for misalignment<\/td>\n<td>\u2264 5% of backlog<\/td>\n<\/tr>\n<tr>\n<td>Value Delivery Accuracy<\/td>\n<td>Post-release impact vs. predicted value<\/td>\n<td>\u2265 75% alignment<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These metrics aren\u2019t for reporting\u2014they\u2019re for improvement.<\/p>\n<p>If your strategic story ratio is under 60%, it\u2019s a signal that refinement practices aren\u2019t aligned with strategy. Investigate: Are teams trained to ask \u201cwhy\u201d? Are managers reinforcing goal-oriented work?<\/p>\n<h2>Practical Takeaways<\/h2>\n<p>Strategic alignment agile isn\u2019t about documents. It\u2019s about habits.<\/p>\n<ul>\n<li>Always ask \u201cWhy?\u201d when writing or refining a story. The answer should link to a real business outcome.<\/li>\n<li>Use tagging systems that reflect strategic themes, not just technical components.<\/li>\n<li>Build a strategic backlog layer to maintain visibility across teams.<\/li>\n<li>Measure alignment\u2014not just delivery. Track how many stories actually serve a strategic purpose.<\/li>\n<li>Make alignment part of the definition of \u201cdone.\u201d If it doesn\u2019t connect to a goal, it\u2019s not truly complete.<\/li>\n<\/ul>\n<p>When stories are built with purpose, teams aren\u2019t just working\u2014they\u2019re advancing the organization\u2019s mission.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if my story is aligned with strategy?<\/h3>\n<p>A story is aligned if it can be traced to a specific objective\u2014like an OKR or strategic initiative. Ask: \u201cIf this story is delivered, what measurable outcome does it enable?\u201d If the answer is unclear, the story may not be aligned.<\/p>\n<h3>What if a story serves both a user and an internal need?<\/h3>\n<p>Focus on the user impact. For example: \u201cAs a support agent, I want to see error logs so I can resolve customer issues faster.\u201d This still serves a user (by improving resolution time). The technical detail is secondary.<\/p>\n<h3>How do I ensure alignment across multiple teams?<\/h3>\n<p>Use shared definitions of \u201cdone,\u201d common OKRs, and synchronized refinement. Hold joint planning sessions where teams co-create stories that support cross-team objectives.<\/p>\n<h3>Can technical stories ever be strategically aligned?<\/h3>\n<p>Yes, but only when tied to user value. A story like \u201cAs a system, I want to reduce latency to under 200ms\u201d is technical. Reframe it: \u201cAs a user, I want the application to respond in under 200ms so I don\u2019t lose context.\u201d Now it\u2019s aligned.<\/p>\n<h3>What\u2019s the difference between strategic alignment and backlog prioritization?<\/h3>\n<p>Backlog prioritization is about sequencing. Strategic alignment is about purpose. A story can be prioritized high but still misaligned. Prioritization without alignment leads to wasted effort.<\/p>\n<h3>How often should I review strategic alignment?<\/h3>\n<p>At every sprint review, ask: \u201cDid our work move us toward strategic goals?\u201d Conduct a quarterly alignment audit to evaluate which stories contributed to OKRs and which didn\u2019t. Use the findings to improve future story writing.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams default to writing stories in isolation\u2014focused on tasks, technical specs, or feature checklists. But that approach severs the link between execution and strategy. I\u2019ve seen this happen repeatedly: teams deliver perfectly written stories, only to realize months later that the work didn\u2019t advance the business goal. The real power of user stories lies [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1762,"menu_order":4,"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-1767","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>Strategic Alignment Agile<\/title>\n<meta name=\"description\" content=\"Discover how user stories maintain line of sight from daily work to enterprise objectives. Learn the real-world techniques for agile strategy connection and user story alignment at scale.\" \/>\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\/scaling-agile-storytelling\/strategic-alignment-agile\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Strategic Alignment Agile\" \/>\n<meta property=\"og:description\" content=\"Discover how user stories maintain line of sight from daily work to enterprise objectives. Learn the real-world techniques for agile strategy connection and user story alignment at scale.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/\" \/>\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=\"7 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\/scaling-agile-storytelling\/strategic-alignment-agile\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/\",\"name\":\"Strategic Alignment Agile\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:45:58+00:00\",\"description\":\"Discover how user stories maintain line of sight from daily work to enterprise objectives. Learn the real-world techniques for agile strategy connection and user story alignment at scale.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/#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\":\"Scaling Agile Storytelling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"How User Stories Enable Strategic Alignment\"}]},{\"@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":"Strategic Alignment Agile","description":"Discover how user stories maintain line of sight from daily work to enterprise objectives. Learn the real-world techniques for agile strategy connection and user story alignment at scale.","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\/scaling-agile-storytelling\/strategic-alignment-agile\/","og_locale":"pt_PT","og_type":"article","og_title":"Strategic Alignment Agile","og_description":"Discover how user stories maintain line of sight from daily work to enterprise objectives. Learn the real-world techniques for agile strategy connection and user story alignment at scale.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/","name":"Strategic Alignment Agile","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:45:58+00:00","description":"Discover how user stories maintain line of sight from daily work to enterprise objectives. Learn the real-world techniques for agile strategy connection and user story alignment at scale.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/strategic-alignment-agile\/#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":"Scaling Agile Storytelling","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/"},{"@type":"ListItem","position":4,"name":"How User Stories Enable Strategic Alignment"}]},{"@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\/1767","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\/1767\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1762"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1767"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}