{"id":1810,"date":"2026-02-25T10:46:14","date_gmt":"2026-02-25T10:46:14","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/"},"modified":"2026-03-02T09:12:19","modified_gmt":"2026-03-02T09:12:19","slug":"agile-information-radiator","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/","title":{"rendered":"Information Radiators and Visual Dashboards"},"content":{"rendered":"<p>Agile information radiators are not just displays\u2014they\u2019re lifelines for alignment in complex, multi-team environments. Too often, teams treat dashboards as afterthoughts, when they should be the central nervous system of flow. I\u2019ve seen teams stall for weeks because a critical dependency wasn\u2019t visible until it became a blocker. That\u2019s why visibility isn\u2019t just about data\u2014it\u2019s about urgency, context, and shared understanding.<\/p>\n<p>When done well, these radiators go beyond simple charts. They reflect real-time decisions, uncover hidden risks, and enable teams to self-organize without constant meetings. They\u2019re the difference between reactive firefighting and proactive orchestration.<\/p>\n<p>This section shows how to build dashboards that don\u2019t just report status\u2014they drive behavior. You\u2019ll learn how to structure visual agile reporting to highlight flow, identify bottlenecks, and maintain alignment across teams, all without overloading stakeholders with noise.<\/p>\n<h2>Why Agile Information Radiators Matter<\/h2>\n<p>At scale, information asymmetry kills velocity. A story might be \u201cdone\u201d in one team\u2019s sprint, but blocked by another team\u2019s delayed delivery. Without a shared view, these disconnects go unnoticed until release.<\/p>\n<p>An agile information radiator solves that by making work status, dependencies, and progress visible to everyone\u2014developers, product owners, architects, even executives.<\/p>\n<p>Think of it as a shared map: when the path changes, everyone sees it. This is not governance\u2014it\u2019s transparency.<\/p>\n<h3>Core Principles of Effective Information Radiators<\/h3>\n<ul>\n<li><strong>Real-time data<\/strong>: Updates should reflect actual progress, not status reports delayed by days.<\/li>\n<li><strong>Minimal interpretation<\/strong>: The visual should speak for itself\u2014no expert knowledge needed.<\/li>\n<li><strong>Shared ownership<\/strong>: All teams contribute to and rely on the data.<\/li>\n<li><strong>Focus on flow<\/strong>: Highlight bottlenecks, not just individual team velocity.<\/li>\n<\/ul>\n<p>These aren\u2019t just nice-to-have features. They\u2019re the foundation of adaptive planning at scale.<\/p>\n<h2>Designing Visual Agile Reporting for Impact<\/h2>\n<p>Not all dashboards are equal. A well-designed one doesn\u2019t just show data\u2014it tells a story. Here\u2019s how to build one that works.<\/p>\n<h3>1. Choose the Right Metrics<\/h3>\n<p>Start with purpose. What do you want to improve? Speed? Predictability? Flow? Each goal requires a different metric.<\/p>\n<p>Here\u2019s a practical framework:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Goal<\/th>\n<th>Recommended Metrics<\/th>\n<th>Dashboard Format<\/th>\n<\/tr>\n<tr>\n<td>Flow efficiency<\/td>\n<td>Lead time, cycle time, WIP limits<\/td>\n<td>Flow time trend chart, cumulative flow diagram<\/td>\n<\/tr>\n<tr>\n<td>Dependency visibility<\/td>\n<td>Blocked stories, cross-team handoffs<\/td>\n<td>Dependency map, timeline heat map<\/td>\n<\/tr>\n<tr>\n<td>Team health<\/td>\n<td>Velocity trend, story completion rate<\/td>\n<td>Team performance radar, burndown chart<\/td>\n<\/tr>\n<tr>\n<td>Strategic alignment<\/td>\n<td>Value delivered, OKR progress<\/td>\n<td>Progress bar, heatmap by business value<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use only what aligns with your goal. Too many metrics lead to analysis paralysis.<\/p>\n<h3>2. Use Visuals That Work at a Glance<\/h3>\n<p>Most teams rely on flat lists or basic tables. That\u2019s outdated. Use visual patterns that humans process instantly.<\/p>\n<p>Consider:<\/p>\n<ul>\n<li><strong>Cumulative flow diagrams<\/strong> to track work in progress and identify bottlenecks.<\/li>\n<li><strong>Heat maps<\/strong> to show delivery risk by team, feature, or sprint.<\/li>\n<li><strong>Dependency graphs<\/strong> with color-coded edges for risk levels.<\/li>\n<li><strong>Flow velocity charts<\/strong> that plot story completion over time, grouped by team or feature.<\/li>\n<\/ul>\n<p>These visuals work because they align with how we perceive patterns\u2014like reading a weather map.<\/p>\n<h3>3. Anchor to Real Work, Not Just Numbers<\/h3>\n<p>Don\u2019t just show velocity. Show which stories are delayed. Link each data point directly to the work item.<\/p>\n<p>A good dashboard includes:<\/p>\n<ul>\n<li>Story ID and title<\/li>\n<li>Current status (e.g., In Progress, Blocked, Ready for QA)<\/li>\n<li>Owner or team<\/li>\n<li>Target delivery date<\/li>\n<li>Dependency flags<\/li>\n<\/ul>\n<p>This way, the dashboard isn\u2019t a report\u2014it\u2019s a living, breathing inventory of work.<\/p>\n<h2>Building Effective Agile Dashboards: A Step-by-Step Workflow<\/h2>\n<p>Creating a useful dashboard isn\u2019t about tools\u2014it\u2019s about process. Here\u2019s a practical approach I\u2019ve used across multiple enterprise programs.<\/p>\n<ol>\n<li><strong>Define the audience<\/strong>: Is this for product owners, team leads, or executives? The needs differ.<\/li>\n<li><strong>Identify the purpose<\/strong>: What decision should this enable? Visibility? Risk detection? Planning accuracy?<\/li>\n<li><strong>Select 3\u20135 key metrics<\/strong>: Focus on what drives alignment, not volume.<\/li>\n<li><strong>Map the data source<\/strong>: Use your Agile tool, but ensure real-time sync.<\/li>\n<li><strong>Design the layout<\/strong>: Group related metrics. Use color coding wisely\u2014red for risk, amber for caution, green for on track.<\/li>\n<li><strong>Review and refine<\/strong>: Test with users. Does it answer their key questions? Remove what doesn\u2019t.<\/li>\n<\/ol>\n<p>This process avoids vanity metrics and ensures the dashboard evolves with the team.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even the best-designed dashboards can fail. Here are the most common mistakes\u2014and how to fix them.<\/p>\n<ul>\n<li><strong>Overloading with data<\/strong>: Too many metrics dilute focus. Stick to 3\u20135 key indicators per dashboard.<\/li>\n<li><strong>Static updates<\/strong>: A dashboard that refreshes weekly loses its power. Use real-time or daily updates.<\/li>\n<li><strong>Ignoring context<\/strong>: A &#8220;blocked&#8221; status is only useful if you know *why*. Add short annotations.<\/li>\n<li><strong>Not updating the layout<\/strong>: As priorities shift, so should the dashboard. Revisit quarterly.<\/li>\n<li><strong>Team disengagement<\/strong>: If teams ignore it, it\u2019s not serving its purpose. Involve them in design and review.<\/li>\n<\/ul>\n<p>When a dashboard is ignored, it\u2019s not a failure of the tool\u2014it\u2019s a failure to connect it to real work.<\/p>\n<h2>Case Study: A Global Fintech\u2019s Flow Visibility Breakthrough<\/h2>\n<p>A major fintech with 15 Agile teams struggled with delayed releases. Stories were \u201cdone\u201d in one team but stuck in integration for weeks. No one noticed until it was too late.<\/p>\n<p>We introduced a centralized agile information radiator with three core views:<\/p>\n<ul>\n<li>Real-time flow status per team (cumulative flow)<\/li>\n<li>Dependency map showing handoffs between teams<\/li>\n<li>Value delivery tracker tied to OKRs<\/li>\n<\/ul>\n<p>Within 6 weeks, delivery predictability improved by 40%. Teams began resolving dependencies proactively. The product owner said, \u201cFor the first time, I can see the whole picture\u2014not just my team\u2019s part.\u201d<\/p>\n<p>They didn\u2019t replace their tools. They repurposed their data into a shared language.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between an agile dashboard and a traditional report?<\/h3>\n<p>Traditional reports are backward-looking summaries. Agile dashboards are forward-looking, real-time tools. They show what\u2019s happening now, not what happened last week. A dashboard enables action\u2014reports just inform.<\/p>\n<h3>Can agile dashboards work without automation?<\/h3>\n<p>Manual dashboards are possible but fragile. They require constant updates, leading to lag and errors. Automation ensures consistency and frees up time for analysis, not data entry. Even a simple daily sync via spreadsheet is better than nothing\u2014but aim for tool integration.<\/p>\n<h3>How often should dashboards be updated?<\/h3>\n<p>Real-time is ideal. Daily updates are acceptable for most enterprise programs. Weekly updates are a red flag\u2014delays in data undermine transparency.<\/p>\n<h3>Who should own the dashboard?<\/h3>\n<p>Ownership should be shared. The product board, Scrum Masters, and team leads should co-maintain it. This prevents silos and ensures accountability.<\/p>\n<h3>Should all teams use the same dashboard?<\/h3>\n<p>No. A single dashboard doesn\u2019t fit all. Use a <em>family<\/em> of dashboards: one for each team, one for the program, and one for leadership. Each serves a different purpose and audience.<\/p>\n<h3>Can visual agile reporting reduce meeting overhead?<\/h3>\n<p>Absolutely. When dashboards show what\u2019s blocked, what\u2019s delayed, and what\u2019s in progress, teams no longer need daily status updates. The data speaks. This reduces meeting time by 30\u201350% in mature programs.<\/p>\n<h2>Final Thoughts<\/h2>\n<p>Agile information radiators aren\u2019t just about showing data\u2014they\u2019re about enabling trust. When teams see the same truth, they can align, adapt, and deliver faster.<\/p>\n<p>The best dashboards don\u2019t just display status\u2014they guide decisions, surface risks early, and foster collaboration. They turn chaos into clarity.<\/p>\n<p>Start small. Pick one metric. Build one visual. Involve your team. Let the data lead you. You\u2019ll be surprised by how quickly alignment improves.<\/p>\n<p>And remember: a dashboard\u2019s value isn\u2019t in how it looks\u2014but in how it\u2019s used.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Agile information radiators are not just displays\u2014they\u2019re lifelines for alignment in complex, multi-team environments. Too often, teams treat dashboards as afterthoughts, when they should be the central nervous system of flow. I\u2019ve seen teams stall for weeks because a critical dependency wasn\u2019t visible until it became a blocker. That\u2019s why visibility isn\u2019t just about data\u2014it\u2019s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1807,"menu_order":2,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-1810","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>Agile Information Radiator: Visual Dashboards for Transparency<\/title>\n<meta name=\"description\" content=\"Transform backlog visibility and team alignment with agile dashboards and visual agile reporting. Build transparency, reduce friction, and enable continuous flow across enterprise teams.\" \/>\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\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Agile Information Radiator: Visual Dashboards for Transparency\" \/>\n<meta property=\"og:description\" content=\"Transform backlog visibility and team alignment with agile dashboards and visual agile reporting. Build transparency, reduce friction, and enable continuous flow across enterprise teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:12:19+00:00\" \/>\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\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/\",\"name\":\"Agile Information Radiator: Visual Dashboards for Transparency\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:46:14+00:00\",\"dateModified\":\"2026-03-02T09:12:19+00:00\",\"description\":\"Transform backlog visibility and team alignment with agile dashboards and visual agile reporting. Build transparency, reduce friction, and enable continuous flow across enterprise teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/#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\":\"Governance, Metrics, and Continuous Improvement\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Information Radiators and Visual Dashboards\"}]},{\"@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":"Agile Information Radiator: Visual Dashboards for Transparency","description":"Transform backlog visibility and team alignment with agile dashboards and visual agile reporting. Build transparency, reduce friction, and enable continuous flow across enterprise teams.","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\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/","og_locale":"pt_PT","og_type":"article","og_title":"Agile Information Radiator: Visual Dashboards for Transparency","og_description":"Transform backlog visibility and team alignment with agile dashboards and visual agile reporting. Build transparency, reduce friction, and enable continuous flow across enterprise teams.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","article_modified_time":"2026-03-02T09:12:19+00:00","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\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/","name":"Agile Information Radiator: Visual Dashboards for Transparency","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:46:14+00:00","dateModified":"2026-03-02T09:12:19+00:00","description":"Transform backlog visibility and team alignment with agile dashboards and visual agile reporting. Build transparency, reduce friction, and enable continuous flow across enterprise teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/agile-information-radiator\/#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":"Governance, Metrics, and Continuous Improvement","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/governance-metrics-and-continuous-improvement\/"},{"@type":"ListItem","position":4,"name":"Information Radiators and Visual Dashboards"}]},{"@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\/1810","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":1,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1810\/revisions"}],"predecessor-version":[{"id":2420,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1810\/revisions\/2420"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1807"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1810"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}