{"id":667,"date":"2026-02-25T10:22:38","date_gmt":"2026-02-25T10:22:38","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/"},"modified":"2026-02-25T10:22:38","modified_gmt":"2026-02-25T10:22:38","slug":"cost-of-poor-user-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/","title":{"rendered":"The Hidden Cost of Poor User Stories"},"content":{"rendered":"

Most teams don\u2019t fail because they lack tools or talent. They fail because their stories don\u2019t hold up under scrutiny. A story that sounds fine on paper often unravels in implementation. The real cost isn\u2019t just wasted time\u2014it\u2019s broken trust, missed deadlines, and a backlog that no longer reflects reality.<\/p>\n

When stories are vague, misaligned, or untestable, developers guess. Designers interpret. Product owners react. This isn\u2019t just inefficient\u2014it\u2019s systemic. The cost of poor user stories compounds with every sprint, turning small missteps into large technical debt.<\/p>\n

Over 20 years of working with teams across startups, enterprises, and government systems, I\u2019ve seen the same pattern: stories written too fast, too alone, too far from the user. The fix isn\u2019t more process. It\u2019s clarity. It\u2019s conversation. It\u2019s knowing what a story is meant to be\u2014a placeholder for dialogue, not a contract.<\/p>\n

Here, I\u2019ll break down the hidden impacts that erode delivery quality, using real examples from teams I\u2019ve coached. You\u2019ll learn how to identify the root causes of failure, spot the signs before they spiral, and build a backlog where every story is a reliable step forward.<\/p>\n

The Three Pillars of Agile Waste Caused by Poor Stories<\/h2>\n

1. Rework from Ambiguous Goals<\/h3>\n

When a story lacks a clear “so that” clause, the team builds for a purpose they don\u2019t understand. This leads to rework. I\u2019ve seen stories like:<\/p>\n

As a user, I want to see the dashboard.<\/code><\/pre>\n
What does “see” mean? Display? Interact? Update in real time? The answer isn\u2019t in the story. It\u2019s in the conversation.<\/p>\n
Teams often implement the first interpretation they can, only to find out weeks later it doesn\u2019t match the user\u2019s actual need.<\/p>\n
Impact of weak stories: teams spend 30\u201350% of sprint capacity rebuilding work that was never properly scoped. This isn\u2019t a bug. It\u2019s a symptom of story failure.<\/p>\n
2. Misalignment Between Stakeholders<\/h3>\n
Stories that rely on assumptions\u2014especially around roles or context\u2014create misalignment. A story like:<\/p>\n
As a customer, I want to log in.<\/code><\/pre>\n
seems simple. But who is the customer? A returning user? A guest? A third-party API client? Without clear role definition, the implementation varies wildly across teams.<\/p>\n
One team built a full account creation flow for a story meant to be a simple login. The product owner hadn\u2019t clarified that the user already had an account. This led to a deployment delay and a costly rollback.<\/p>\n
agile waste causes: lack of shared understanding, duplicate effort, and post-mortems that blame the wrong people.<\/p>\n
3. Unplanned Re-Work and Scope Creep<\/h3>\n
Stories that aren\u2019t testable from the start become battlegrounds. When acceptance criteria are missing or vague, the team can\u2019t know when they\u2019re done. This invites scope creep.<\/p>\n
Example:<\/p>\n
As a user, I want to search for products.<\/code><\/pre>\n
No mention of filters, sorting, results per page, or performance. The team delivers a basic search. But the user wanted a real-time autocomplete with category suggestions.<\/p>\n
Post-implementation, the team is asked to rework the feature. Not because it\u2019s broken\u2014but because it wasn\u2019t aligned with the user\u2019s expectations.<\/p>\n
Every time this happens, the cost of poor user stories hits the budget. Fixing it later costs 5\u201310x more than clarifying it early.<\/p>\n
How Poor Stories Drain Team Velocity<\/h2>\n
Velocity isn\u2019t just a metric. It\u2019s a reflection of story quality. Teams that consistently deliver incomplete or incorrect stories don\u2019t just fall behind\u2014they lose momentum.<\/p>\n
Here\u2019s a real-world case from a financial SaaS product:<\/p>\n\n\n\n\n\n\n
Sprint<\/th>\nPlanned Story Points<\/th>\nCompleted Points<\/th>\nStories Re-worked<\/th>\nRework Rate<\/th>\n<\/tr>\n
Sprint 1<\/td>\n24<\/td>\n21<\/td>\n2<\/td>\n8%<\/td>\n<\/tr>\n
Sprint 2<\/td>\n24<\/td>\n17<\/td>\n4<\/td>\n17%<\/td>\n<\/tr>\n
Sprint 3<\/td>\n24<\/td>\n13<\/td>\n6<\/td>\n25%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
The team\u2019s velocity dipped. But the real problem wasn\u2019t their speed\u2014it was their story health. The stories were too big, unclear, and lacked acceptance criteria. The rework wasn\u2019t from bugs. It was from misalignment.<\/p>\n
When stories are poorly written, teams don\u2019t fail on a technical level. They fail on a purpose level. The work is done, but not the right work.<\/p>\n
Why Teams Keep Making the Same Mistake<\/h2>\n
Myth: “We\u2019ll fix it in refinement.”<\/h3>\n
Refinement is not a magic eraser. If a story is inherently ambiguous, no amount of refinement will fix it. The moment a story is added to a sprint, it\u2019s too late.<\/p>\n
Refinement is meant to clarify, not create. If you\u2019re still debating the goal during sprint planning, the story was never ready. This is where the real impact of weak stories begins.<\/p>\n
Myth: “The dev team should figure it out.”<\/h3>\n
That\u2019s not Agile. That\u2019s delegation. A user story is not a technical task. It\u2019s a conversation starter between a user and a deliverable. If the development team isn\u2019t involved in the conversation, they\u2019ll interpret the story through their own lens.<\/p>\n
That\u2019s how you get a story like:<\/p>\n
As a user, I want the app to be fast.<\/code><\/pre>\n
Which gets interpreted as \u201creduce load time under 2 seconds.\u201d But the user meant \u201cI want to find my order in less than 3 seconds.\u201d The actual goal was missed.<\/p>\n
How to Measure the Real Cost of Poor User Stories<\/h2>\n
Start by tracking these three indicators:<\/p>\n
    \n
  1. Story Rejection Rate:<\/strong> How many stories are rejected in refinement due to missing clarity or acceptance criteria?<\/li>\n
  2. Post-Sprint Re-work:<\/strong> How many newly delivered stories require changes in the next sprint?<\/li>\n
  3. Time-to-Clarify:<\/strong> How long does it take for a story to be clear enough to estimate?<\/li>\n<\/ol>\n
    If your rejection rate is above 15%, your backlog is unhealthy. If rework exceeds 20% of sprint output, you\u2019re in crisis mode.<\/p>\n
    These metrics reveal the true cost of poor user stories\u2014not in hours, but in missed value, delayed releases, and team fatigue.<\/p>\n
    Three Fixes That Actually Work<\/h2>\n
    1. Start with the Why, Not the What<\/h3>\n
    Before writing a story, ask: “Why does the user need this?” If you can\u2019t answer in one sentence, the story isn\u2019t valuable.<\/p>\n
    Replace:<\/p>\n
    As a user, I want to export data.<\/code><\/pre>\n
    With:<\/p>\n
    As a sales manager, I want to export monthly reports so that I can submit them to corporate by the 5th of each month.<\/code><\/pre>\n
    Now the goal is clear. The success condition is measurable. The purpose is tied to business outcome.<\/p>\n
    2. Use Acceptance Criteria That Are Testable<\/h3>\n
    Every story must have at least three acceptance criteria that are specific, measurable, and verifiable. Avoid:<\/p>\n
      \n
    • \u201cThe system should be fast.\u201d \u2192 Too vague.<\/li>\n
    • \u201cThe user should be able to navigate.\u201d \u2192 Not testable.<\/li>\n<\/ul>\n
      Instead, write:<\/p>\n
        \n
      • Given I\u2019m on the dashboard, when I click \u201cExport\u201d, the file downloads within 3 seconds.<\/li>\n
      • Given I have 1,000+ records, when I filter by date range, the first 50 results load in under 2 seconds.<\/li>\n
      • Given I\u2019ve selected a file format, when I export, the file includes the user\u2019s name and timestamp.<\/li>\n<\/ul>\n
        These are not just acceptance criteria. They are contracts.<\/p>\n
        3. Build the Story Map First<\/h3>\n
        Before writing individual stories, create a story map. This forces the team to think about the user journey\u2014and where each story fits.<\/p>\n
        A story map reveals gaps, duplicates, and misaligned priorities. It shows which stories deliver value early, which are dependencies, and which are just technical chores.<\/p>\n
        It\u2019s not just planning. It\u2019s strategy.<\/p>\n
        Frequently Asked Questions<\/h2>\n
        What does the impact of weak stories look like in practice?<\/h3>\n
        It shows up as missed deadlines, features that don\u2019t meet user needs, and team frustration. A story like \u201cAs a user, I want to save\u201d might take two weeks to implement\u2014only for the user to say, \u201cI don\u2019t need that. I just want to keep the draft.\u201d The cost: wasted effort, delayed value, and erosion of trust.<\/p>\n
        How can I tell if my team is suffering from agile waste causes?<\/h3>\n
        Look for patterns: recurring rework, frequent story changes mid-sprint, lack of clarity in sprint planning, and stories rejected in refinement. These aren\u2019t process failures\u2014these are symptoms of poor story quality.<\/p>\n
        Why do teams keep writing untestable user stories?<\/h3>\n
        Because they treat stories as documentation, not conversation. They write them alone, then present them to the team. The moment a story is written without discussion, it becomes a liability.<\/p>\n
        Can I fix a story after it\u2019s in the sprint?<\/h3>\n
        Yes\u2014but only if it\u2019s not too late. If the team is still in planning, you can rework the story. But if it\u2019s already in progress, changing the scope triggers risk. The fix is not in changing the story\u2014it\u2019s in the process. Fix the story *before* sprint planning.<\/p>\n
        Should I use templates for user stories?<\/h3>\n
        Yes\u2014but only as a scaffold, not a crutch. A template like \u201cAs a [role], I want to [action] so that [outcome]\u201d helps focus. But if the team uses it mechanically, without thinking, it creates robotic, valueless stories. Use the template to ask better questions, not to fill boxes.<\/p>\n
        How often should we review and improve our user stories?<\/h3>\n
        Not just in refinement. Review every story against a checklist: clarity, testability, business value, and user focus. Make this part of your Definition of Ready. The best stories aren\u2019t written\u2014they\u2019re evolved through conversation, feedback, and shared ownership.<\/p>\n","protected":false},"excerpt":{"rendered":"
        Most teams don\u2019t fail because they lack tools or talent. They fail because their stories don\u2019t hold up under scrutiny. A story that sounds fine on paper often unravels in implementation. The real cost isn\u2019t just wasted time\u2014it\u2019s broken trust, missed deadlines, and a backlog that no longer reflects reality. When stories are vague, misaligned, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":665,"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-667","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nCost of Poor User Stories<\/title>\n<meta name=\"description\" content=\"Understand the real cost of poor user stories: rework, misalignment, and delivery delays. Learn how agile waste causes and impact of weak stories cripple team velocity and product quality.\" \/>\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\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cost of Poor User Stories\" \/>\n<meta property=\"og:description\" content=\"Understand the real cost of poor user stories: rework, misalignment, and delivery delays. Learn how agile waste causes and impact of weak stories cripple team velocity and product quality.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 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\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/\",\"name\":\"Cost of Poor User Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:22:38+00:00\",\"description\":\"Understand the real cost of poor user stories: rework, misalignment, and delivery delays. Learn how agile waste causes and impact of weak stories cripple team velocity and product quality.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Why User Stories Go Wrong\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Hidden Cost of Poor User Stories\"}]},{\"@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":"Cost of Poor User Stories","description":"Understand the real cost of poor user stories: rework, misalignment, and delivery delays. Learn how agile waste causes and impact of weak stories cripple team velocity and product quality.","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\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/","og_locale":"pt_PT","og_type":"article","og_title":"Cost of Poor User Stories","og_description":"Understand the real cost of poor user stories: rework, misalignment, and delivery delays. Learn how agile waste causes and impact of weak stories cripple team velocity and product quality.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"8 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/","name":"Cost of Poor User Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:22:38+00:00","description":"Understand the real cost of poor user stories: rework, misalignment, and delivery delays. Learn how agile waste causes and impact of weak stories cripple team velocity and product quality.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/cost-of-poor-user-stories\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Why User Stories Go Wrong","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/why-user-stories-go-wrong\/"},{"@type":"ListItem","position":4,"name":"The Hidden Cost of Poor User Stories"}]},{"@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\/667","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\/667\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/665"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=667"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=667"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}