{"id":1805,"date":"2026-02-25T10:46:12","date_gmt":"2026-02-25T10:46:12","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/"},"modified":"2026-03-02T09:18:27","modified_gmt":"2026-03-02T09:18:27","slug":"visualizing-value-flow-across-teams-systems","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/","title":{"rendered":"Visualizing Value Flow Across Teams and Systems"},"content":{"rendered":"

Every time a story moves from concept to delivery, it\u2019s not just a task\u2014it\u2019s an investment in shared understanding. The quietest win in agile scaling isn\u2019t speed or output. It\u2019s the ability to see<\/strong> how value moves between teams, systems, and backlogs.<\/p>\n

At scale, stories don\u2019t exist in isolation. They cascade through architecture, flow across teams, and intersect with dependencies no single person can track. Without visibility, alignment deteriorates. Without flow, momentum vanishes.<\/p>\n

My experience with enterprise-scale agile transformation has taught me that the most effective teams don\u2019t manage complexity\u2014they visualize<\/em> it. The real power lies not in documenting every step, but in building a shared mental model of value flow across systems.<\/p>\n

This chapter shows you how to model that flow using practical visual techniques. You\u2019ll learn to map story progression through portfolios, identify hidden bottlenecks, and align cross-team work through visual value stream<\/strong> diagrams that reflect real business outcomes.<\/p>\n

Why Flow Visualization Agile Works at Scale<\/h2>\n

Traditional backlog grooming focuses on individual stories. At scale, that\u2019s insufficient. You need to understand how stories connect<\/em> across teams and systems.<\/p>\n

Flow visualization agile shifts focus from task completion to value delivery. When you can see the journey of a story\u2014from idea to deployment\u2014you gain insights that no sprint report can provide.<\/p>\n

This isn\u2019t about creating elaborate charts. It\u2019s about making the invisible visible<\/strong>. The goal is to reveal delays, dependencies, and handoff friction before they derail velocity.<\/p>\n

Common Pitfalls in Value Flow Modeling<\/h3>\n
    \n
  • Overcomplicating diagrams with excessive detail<\/li>\n
  • Focusing only on technical handoffs, ignoring business impact<\/li>\n
  • Using static models that don\u2019t reflect evolving team dynamics<\/li>\n
  • Creating siloed views that isolate teams instead of connecting them<\/li>\n<\/ul>\n

    These missteps aren\u2019t failures of tooling\u2014they\u2019re symptoms of poor modeling philosophy. The key is simplicity, clarity, and shared ownership<\/em>.<\/p>\n

    Building a Visual Value Stream Map<\/h2>\n

    Start by selecting a representative customer journey. For example: \u201cA user signs up, verifies their email, and accesses their dashboard.\u201d Break this into a sequence of user stories across teams.<\/p>\n

    Use a simple flowchart format: boxes for teams or systems, arrows for story movement, and labels for key events\u2014like \u201cstory accepted,\u201d \u201cAPI validated,\u201d or \u201cdeployed.\u201d<\/p>\n

    Here\u2019s a real example from a fintech product suite:<\/p>\n\n\n\n\n\n\n\n\n
    Stage<\/th>\nTeam\/System<\/th>\nStory Type<\/th>\nOutcome<\/th>\n<\/tr>\n
    Initiation<\/td>\nProduct<\/td>\nFeature Epic<\/td>\nSignup flow defined<\/td>\n<\/tr>\n
    Split<\/td>\nFrontend<\/td>\nUser Story<\/td>\nUI form built<\/td>\n<\/tr>\n
    Handoff<\/td>\nBackend<\/td>\nUser Story<\/td>\nAPI endpoint exposed<\/td>\n<\/tr>\n
    Integration<\/td>\nQA \/ DevOps<\/td>\nAcceptance Test<\/td>\nEnd-to-end validation passed<\/td>\n<\/tr>\n
    Deployment<\/td>\nDevOps<\/td>\nDeployment Task<\/td>\nFeature in production<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    This map shows not just what<\/em> happens, but when<\/em> and why<\/em>. It reveals where stories wait\u2014often at handoff points\u2014and helps teams identify where to focus improvement.<\/p>\n

    Key Questions to Ask During Mapping<\/h3>\n
      \n
    • Where are stories stuck<\/strong>? (e.g., waiting for API specs)<\/li>\n
    • Which handoffs take the longest? (e.g., QA waits for deployment)<\/li>\n
    • Are there redundant or overlapping tasks?<\/li>\n
    • Do all teams understand the shared goal at each stage?<\/li>\n<\/ul>\n

      These aren\u2019t just process questions. They\u2019re signals of alignment gaps.<\/p>\n

      Using Decision Tables to Model Conditional Flow<\/h2>\n

      Not all user journeys follow the same path. Some users need 2FA, some get routed to onboarding, others are flagged for compliance review.<\/p>\n

      This is where decision tables<\/strong> shine. They help model the conditional logic that governs story progression\u2014especially in systems with branching business rules.<\/p>\n

      For example, consider the \u201cUser Account Activation\u201d flow. You might use a table like this:<\/p>\n\n\n\n\n\n\n\n
      User Type<\/th>\nEmail Verified?<\/th>\nCompliance Flag?<\/th>\nNext Action<\/th>\n<\/tr>\n
      Regular<\/td>\nYes<\/td>\nNo<\/td>\nGrant access<\/td>\n<\/tr>\n
      Regular<\/td>\nNo<\/td>\nNo<\/td>\nSend verification email<\/td>\n<\/tr>\n
      High-Risk<\/td>\nYes<\/td>\nYes<\/td>\nEscalate to compliance team<\/td>\n<\/tr>\n
      High-Risk<\/td>\nNo<\/td>\nNo<\/td>\nHold and notify admin<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      This table can be linked to user stories. For instance:<\/p>\n

        \n
      • Story:<\/strong> As a system, I need to route unverified users to email verification so they can activate their account.<\/li>\n
      • Story:<\/strong> As a compliance officer, I need to be notified when a high-risk user logs in without verification so I can assess risk.<\/li>\n<\/ul>\n

        Decision tables turn complex logic into testable, shared understanding<\/em>, reducing misalignment and rework.<\/p>\n

        Integrating Flow Visualizations into Agile Rituals<\/h2>\n

        Visual value stream maps aren\u2019t artifacts. They\u2019re living tools<\/strong>\u2014used in PI planning, refinement sessions, and retrospectives.<\/p>\n

        Here\u2019s how to weave them into your workflow:<\/p>\n

          \n
        1. Pre-PI Planning:<\/strong> Map the expected flow for each feature. Identify major dependencies and potential delays.<\/li>\n
        2. Refinement Sessions:<\/strong> Use the map to assess if a story fits the flow. Is it blocking a downstream team? Is it duplicating work?<\/li>\n
        3. Retrospective:<\/strong> Review flow metrics\u2014cycle time, wait time, handoff delays. Ask: \u201cWhere did we lose value?\u201d<\/li>\n
        4. Release Planning:<\/strong> Align story delivery with flow pathways. Avoid overloading any single team or system.<\/li>\n<\/ol>\n

          These aren\u2019t rigid steps. They\u2019re prompts for conversation. The map becomes the shared conversation starter, not a compliance checkbox.<\/p>\n

          Scaling with Visual Paradigm and Agile Tools<\/h2>\n

          Tools like Visual Paradigm with Advanced Roadmaps can support flow visualization agile.<\/p>\n

          You don\u2019t need a full enterprise modeling suite. But you do need:<\/p>\n

            \n
          • A shared workspace<\/li>\n
          • Consistent notation (e.g., swimlanes for teams, color codes for risk)<\/li>\n
          • Linking between stories and flow stages (e.g., story IDs in the map)<\/li>\n<\/ul>\n

            When teams can click a story in the flow map and see its full context\u2014acceptance criteria, assignee, sprint\u2014it becomes a powerful coordination tool.<\/p>\n

            I\u2019ve seen teams reduce handoff delays by 40% simply by mapping their flow and reviewing it every sprint. The key isn\u2019t the tool\u2014it\u2019s the discipline to use<\/em> it.<\/p>\n

            Measuring What Matters: Flow Metrics That Align Teams<\/h2>\n

            Flow visualization agile isn\u2019t just about maps. It\u2019s about measuring flow.<\/p>\n

            Track these metrics to assess value flow health:<\/p>\n

              \n
            • Cycle Time:<\/strong> How long a story takes from \u201cin progress\u201d to \u201cdone\u201d<\/li>\n
            • Wait Time:<\/strong> How long stories sit idle before work begins<\/li>\n
            • Lead Time:<\/strong> Time from idea to deployment<\/li>\n
            • Throughput:<\/strong> Number of stories completed per sprint<\/li>\n
            • Flow Efficiency:<\/strong> Percentage of time spent actively working vs. waiting<\/li>\n<\/ul>\n

              Compare these metrics across teams. If one team has high wait time but low cycle time, they\u2019re likely waiting for upstream work. If another has high cycle time, they may be overloaded or blocked by technical debt.<\/p>\n

              These aren\u2019t vanity metrics. They\u2019re signals. They tell you where to look<\/em> for bottlenecks\u2014and where to act<\/em>.<\/p>\n

              Frequently Asked Questions<\/h2>\n

              How do I start visualizing value flow in a large, distributed team?<\/h3>\n

              Begin with a single, well-understood customer journey. Involve at least one representative from each team involved. Use a shared whiteboard\u2014physical or digital. Map the flow step by step. Focus on clarity over completeness. Iterate based on feedback.<\/p>\n

              Can flow visualization agile work with SAFe or LeSS?<\/h3>\n

              Yes. In SAFe, flow maps align with Program Increments. They help visualize how features flow from epic to team backlog. In LeSS, they support transparency in the \u201cwhole-product\u201d view. The model adapts to the framework\u2014it doesn\u2019t replace it.<\/p>\n

              How often should we update the value stream map?<\/h3>\n

              Update it at least at every PI planning cycle. If teams change roles or systems evolve, refresh the map sooner. Treat it as a living artifact, not a one-time exercise.<\/p>\n

              What if teams disagree on how a story flows?<\/h3>\n

              Use the map as a facilitation tool. Let teams debate their understanding, then reconcile. Focus on shared business outcomes, not individual ownership. The goal is alignment\u2014not consensus.<\/p>\n

              Do I need a dedicated modeler to create these maps?<\/h3>\n

              No. The best maps come from teams who understand the work. Assign a rotating \u201cflow steward\u201d per feature. It\u2019s not about expertise in modeling\u2014it\u2019s about shared responsibility for delivery.<\/p>\n

              How do I handle complex systems with many dependencies?<\/h3>\n

              Use layered visualization: start with high-level flow, then drill down into specific subsystems. Use color to indicate risk\u2014red for blocked, yellow for delayed, green for flowing. Add annotations to explain exceptions. Keep it simple.<\/p>\n","protected":false},"excerpt":{"rendered":"

              Every time a story moves from concept to delivery, it\u2019s not just a task\u2014it\u2019s an investment in shared understanding. The quietest win in agile scaling isn\u2019t speed or output. It\u2019s the ability to see how value moves between teams, systems, and backlogs. At scale, stories don\u2019t exist in isolation. They cascade through architecture, flow across […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1801,"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":"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-1805","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nVisualizing Value Flow Agile Systems<\/title>\n<meta name=\"description\" content=\"Master flow visualization agile techniques to map user story progression across teams and systems. Learn how visual value stream modeling enhances alignment, reduces dependency risks, and accelerates value delivery in enterprise 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\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Visualizing Value Flow Agile Systems\" \/>\n<meta property=\"og:description\" content=\"Master flow visualization agile techniques to map user story progression across teams and systems. Learn how visual value stream modeling enhances alignment, reduces dependency risks, and accelerates value delivery in enterprise agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:18:27+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\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\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/\",\"name\":\"Visualizing Value Flow Agile Systems\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:46:12+00:00\",\"dateModified\":\"2026-03-02T09:18:27+00:00\",\"description\":\"Master flow visualization agile techniques to map user story progression across teams and systems. Learn how visual value stream modeling enhances alignment, reduces dependency risks, and accelerates value delivery in enterprise agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Supporting Practices and Scaled Facilitation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Visualizing Value Flow Across Teams and Systems\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Visualizing Value Flow Agile Systems","description":"Master flow visualization agile techniques to map user story progression across teams and systems. Learn how visual value stream modeling enhances alignment, reduces dependency risks, and accelerates value delivery in enterprise 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\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/","og_locale":"es_ES","og_type":"article","og_title":"Visualizing Value Flow Agile Systems","og_description":"Master flow visualization agile techniques to map user story progression across teams and systems. Learn how visual value stream modeling enhances alignment, reduces dependency risks, and accelerates value delivery in enterprise agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","article_modified_time":"2026-03-02T09:18:27+00:00","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/","name":"Visualizing Value Flow Agile Systems","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:46:12+00:00","dateModified":"2026-03-02T09:18:27+00:00","description":"Master flow visualization agile techniques to map user story progression across teams and systems. Learn how visual value stream modeling enhances alignment, reduces dependency risks, and accelerates value delivery in enterprise agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/visualizing-value-flow-across-teams-systems\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Supporting Practices and Scaled Facilitation","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/"},{"@type":"ListItem","position":4,"name":"Visualizing Value Flow Across Teams and Systems"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1805","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1805\/revisions"}],"predecessor-version":[{"id":2448,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1805\/revisions\/2448"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1801"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=1805"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=1805"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}