{"id":703,"date":"2026-02-25T10:22:56","date_gmt":"2026-02-25T10:22:56","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/"},"modified":"2026-02-25T10:22:56","modified_gmt":"2026-02-25T10:22:56","slug":"post-mortem-user-stories-learning-from-failure","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/","title":{"rendered":"Post-Mortem Analysis: Learning from Failed Stories"},"content":{"rendered":"<p>Stories don\u2019t fail because of poor code. They fail because of poor thinking. The most painful truth? Most teams don\u2019t analyze failure\u2014because they don\u2019t believe the story was ever broken. I\u2019ve seen teams ship features that users never opened, only to realize weeks later that the core story was never about the user at all. That\u2019s not a bug\u2014it\u2019s a symptom of a missing process.<\/p>\n<p>Post-mortem user stories are not about blame. They\u2019re about clarity. They\u2019re about turning a broken story into a teachable moment. When you do this right, you don\u2019t just improve one story\u2014you improve the entire team\u2019s ability to write with intent. This is where trust is rebuilt, and quality becomes a shared habit.<\/p>\n<p>You\u2019ll learn how to run a real retrospective\u2014not a perfunctory check-in\u2014but a structured analysis that surfaces root causes. You\u2019ll extract patterns, not just observations. And you\u2019ll use those insights to build better stories, faster. This chapter is for teams tired of rework, misaligned sprints, and stories that feel like puzzles.<\/p>\n<h2>Why Most Retrospectives Fail to Surface Real Issues<\/h2>\n<p>Agile retrospectives often descend into \u201cwhat went well\u201d and \u201cwhat didn\u2019t.\u201d But that\u2019s not learning. That\u2019s noise.<\/p>\n<p>When stories fail, teams default to symptoms: \u201cWe missed the deadline.\u201d \u201cThe developer didn\u2019t understand the scope.\u201d \u201cThe user didn\u2019t like it.\u201d These are outcomes. They don\u2019t reveal the real problem.<\/p>\n<p>Post-mortem analysis forces you to dig deeper. You\u2019re not asking \u201cWhat went wrong?\u201d You\u2019re asking, \u201cWhat assumption led us to write this story in the first place?\u201d<\/p>\n<p>Consider this: a story like \u201cAs a customer, I want to view my order history so that I can track past purchases\u201d sounds fine. But if users never looked at it, or couldn\u2019t find it, the issue wasn\u2019t the story\u2019s wording\u2014it was the assumption that users cared about order history at all.<\/p>\n<p>That\u2019s where reflection begins.<\/p>\n<h3>Start with the Right Question<\/h3>\n<p>Don\u2019t ask: \u201cWhy wasn\u2019t this story completed?\u201d<\/p>\n<p>Ask: \u201cWhat did we think the user needed, and how did we know?\u201d<\/p>\n<p>Ask: \u201cWho validated that this story was valuable before we shipped?\u201d<\/p>\n<p>These questions expose blind spots. They turn a failure into a conversation starter.<\/p>\n<p>Use this checklist:<\/p>\n<ul>\n<li>Was the user role clearly defined?<\/li>\n<li>Did we test the story\u2019s value before coding?<\/li>\n<li>Was acceptance criteria defined with the team?<\/li>\n<li>Did the stakeholder confirm the outcome?<\/li>\n<li>Was the story sized correctly for the sprint?<\/li>\n<\/ul>\n<p>If even one item is \u201cno,\u201d the story was never fully validated. That\u2019s not a failure\u2014it\u2019s a signal to improve the process.<\/p>\n<h2>Running a Constructive Post-Mortem<\/h2>\n<p>Post-mortem user stories should not be a blame game. The goal is not to find fault, but to understand assumptions.<\/p>\n<p>Start by gathering the people involved: product owner, developers, QA, and ideally, a stakeholder. No one else. Keep it small, focused.<\/p>\n<p>Use a simple template:<\/p>\n<ol>\n<li><strong>What was the story?<\/strong> Re-state it clearly.<\/li>\n<li><strong>What did we expect?<\/strong> What outcome were we aiming for?<\/li>\n<li><strong>What actually happened?<\/strong> Did it ship? Was it used? Did users complain?<\/li>\n<li><strong>Why did it diverge?<\/strong> Identify the gap between intent and reality.<\/li>\n<li><strong>What assumption was wrong?<\/strong> This is the gold.<\/li>\n<li><strong>How do we fix it?<\/strong> Not just for this story\u2014but for the next 10.<\/li>\n<\/ol>\n<p>Example: <em>\u201cAs a user, I want to filter my dashboard so that I can see only high-priority tasks.\u201d<\/em><\/p>\n<p>Expected: Immediate usability improvement.<\/p>\n<p>Reality: 12% of users used it. 90% didn\u2019t know it existed. The filter was buried under tabs.<\/p>\n<p>Root cause: We assumed users would know how to use filters. We didn\u2019t validate visibility or discoverability.<\/p>\n<p>Fix: Add a guided tour or onboarding step. Create a design pattern for critical actions. Test discovery before shipping.<\/p>\n<p>This is how post-mortem turns insight into process change.<\/p>\n<h3>Use a Blameless Root Cause Framework<\/h3>\n<p>One of the most effective tools I\u2019ve used is the \u201c5 Whys\u201d technique. Drill down until you hit an assumption, not a failure.<\/p>\n<p>Problem: The story wasn\u2019t used.<\/p>\n<p>Why? Because users didn\u2019t see it.<\/p>\n<p>Why? Because it was on a hidden tab.<\/p>\n<p>Why? Because the design team thought it was \u201cobvious.\u201d<\/p>\n<p>Why? Because they assumed the user would know how to navigate.<\/p>\n<p>Why? Because no one asked users how they would expect to find it.<\/p>\n<p>Now you\u2019ve hit the real issue: no user validation. Not a bad UI, not a bug. A missing conversation.<\/p>\n<h2>Turning Lessons into Actionable Improvements<\/h2>\n<p>Learning from mistakes isn\u2019t about documenting issues. It\u2019s about changing behavior.<\/p>\n<p>After every post-mortem, update one practice. Not all of them. One.<\/p>\n<p>Here\u2019s how to prioritize:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Change<\/th>\n<th>Impact<\/th>\n<th>Effort<\/th>\n<\/tr>\n<tr>\n<td>Add user validation before story acceptance<\/td>\n<td>High<\/td>\n<td>Medium<\/td>\n<\/tr>\n<tr>\n<td>Introduce a story impact rating (1\u20135) in refinement<\/td>\n<td>Medium<\/td>\n<td>Low<\/td>\n<\/tr>\n<tr>\n<td>Require a prototype or mockup for stories with complex flows<\/td>\n<td>High<\/td>\n<td>Medium<\/td>\n<\/tr>\n<tr>\n<td>Link all stories to a user journey map<\/td>\n<td>High<\/td>\n<td>High<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Choose the one with the highest impact and lowest effort to implement. That\u2019s your next improvement.<\/p>\n<p>Don\u2019t try to fix everything. That\u2019s why post-mortems fail. You\u2019re not building a new process\u2014you\u2019re refining the old one.<\/p>\n<h3>Embedding Learning into the Backlog<\/h3>\n<p>Most teams forget to document the insights. That\u2019s a missed opportunity.<\/p>\n<p>Create a \u201cLessons Learned\u201d section in your backlog. Use it to tag stories with patterns:<\/p>\n<ul>\n<li><strong>Pattern:<\/strong> \u201cAssumed user knows how to filter\u201d<\/li>\n<li><strong>Trigger:<\/strong> When a story involves navigation or filtering<\/li>\n<li><strong>Check:<\/strong> Add a discovery step before development<\/li>\n<li><strong>Tool:<\/strong> Include a usability test with 3 users<\/li>\n<\/ul>\n<p>Now, when a similar story appears, the team can flag it and apply the fix automatically.<\/p>\n<p>This is how you scale learning. Not with training, but with shared memory.<\/p>\n<h2>Measuring Success Beyond Velocity<\/h2>\n<p>Agile retrospectives and learning from mistakes are useless if you don\u2019t measure what changes.<\/p>\n<p>Track two metrics:<\/p>\n<ol>\n<li><strong>Story Rejection Rate:<\/strong> How many stories were dropped or rewritten after sprint planning?<\/li>\n<li><strong>Post-Release Feedback:<\/strong> How many stories were used, and how?<\/li>\n<\/ol>\n<p>These are your signals. If the rejection rate is high, your refinement process is weak. If feedback is negative, your user validation is missing.<\/p>\n<p>Use this data to improve the Definition of Ready. Make it real, not ceremonial.<\/p>\n<p>Example: Stories must include either a user test, a prototype, or a stakeholder confirmation before being accepted into a sprint.<\/p>\n<p>That\u2019s not a rule. It\u2019s a guardrail.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How often should we run post-mortem analysis for user stories?<\/h3>\n<p>At least once per sprint. Not every story needs a deep dive, but every failed or misused story should be reviewed. Focus on stories that were not delivered, rejected during refinement, or had negative user feedback.<\/p>\n<h3>Can post-mortem user stories replace regular agile retrospectives?<\/h3>\n<p>No. Post-mortem analysis is a supplement to retrospectives. Retrospectives focus on team processes and morale. Post-mortems focus on individual story failures and improvements. Use both. One for culture, one for clarity.<\/p>\n<h3>What if no one wants to admit a story was wrong?<\/h3>\n<p>Start with empathy, not data. Ask, \u201cWhat did we learn?\u201d instead of \u201cWho failed?\u201d Use the \u201c5 Whys\u201d to expose assumptions, not people. When the goal is improvement, not punishment, honesty follows.<\/p>\n<h3>How do I convince my team to do post-mortems?<\/h3>\n<p>Show them the cost of rework. Show a side-by-side: a story written with validation vs one written without. Highlight how the second one is more likely to be scrapped. Data beats opinion.<\/p>\n<h3>Is post-mortem analysis only for failed stories?<\/h3>\n<p>Not at all. Even successful stories can benefit from reflection. Ask: \u201cWhat made this work?\u201d and \u201cHow can we replicate this?\u201d This builds a culture of continuous learning, not just reactive fixes.<\/p>\n<h3>What should I do with the lessons learned?<\/h3>\n<p>Turn them into checklists, templates, or backlog tags. Use them to train new team members. Reference them in story refinement. Make the learning visible and reusable. That\u2019s how habits are formed.<\/p>\n<p>Post-mortem user stories aren\u2019t about perfection. They\u2019re about progress. Every flawed story is a chance to improve\u2014not the process, but the team\u2019s understanding of what it means to write with purpose.<\/p>\n<p>When you stop fearing failure, you start building trust. When you stop blaming, you start learning. And when you document that learning, you build a backlog that evolves\u2014not just in size, but in quality.<\/p>\n<p>That\u2019s the real power of agile retrospectives and learning from mistakes.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Stories don\u2019t fail because of poor code. They fail because of poor thinking. The most painful truth? Most teams don\u2019t analyze failure\u2014because they don\u2019t believe the story was ever broken. I\u2019ve seen teams ship features that users never opened, only to realize weeks later that the core story was never about the user at all. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":701,"menu_order":1,"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-703","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>Post-Mortem User Stories: Learn from Failure<\/title>\n<meta name=\"description\" content=\"Conduct agile retrospectives that turn failed user stories into actionable improvements. Learn how post-mortem analysis drives continuous delivery excellence.\" \/>\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\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Post-Mortem User Stories: Learn from Failure\" \/>\n<meta property=\"og:description\" content=\"Conduct agile retrospectives that turn failed user stories into actionable improvements. Learn how post-mortem analysis drives continuous delivery excellence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\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=\"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\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/\",\"name\":\"Post-Mortem User Stories: Learn from Failure\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:22:56+00:00\",\"description\":\"Conduct agile retrospectives that turn failed user stories into actionable improvements. Learn how post-mortem analysis drives continuous delivery excellence.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Lessons Learned and Continuous Improvement\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Post-Mortem Analysis: Learning from Failed Stories\"}]},{\"@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":"Post-Mortem User Stories: Learn from Failure","description":"Conduct agile retrospectives that turn failed user stories into actionable improvements. Learn how post-mortem analysis drives continuous delivery excellence.","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\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/","og_locale":"es_ES","og_type":"article","og_title":"Post-Mortem User Stories: Learn from Failure","og_description":"Conduct agile retrospectives that turn failed user stories into actionable improvements. Learn how post-mortem analysis drives continuous delivery excellence.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/","name":"Post-Mortem User Stories: Learn from Failure","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:22:56+00:00","description":"Conduct agile retrospectives that turn failed user stories into actionable improvements. Learn how post-mortem analysis drives continuous delivery excellence.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/post-mortem-user-stories-learning-from-failure\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Lessons Learned and Continuous Improvement","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/"},{"@type":"ListItem","position":4,"name":"Post-Mortem Analysis: Learning from Failed Stories"}]},{"@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\/703","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":0,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/703\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/701"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=703"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=703"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}