{"id":678,"date":"2026-02-25T10:22:44","date_gmt":"2026-02-25T10:22:44","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/"},"modified":"2026-02-25T10:22:44","modified_gmt":"2026-02-25T10:22:44","slug":"lack-of-communication-in-agile-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/","title":{"rendered":"Skipping Dialogue: Writing Without Conversation"},"content":{"rendered":"<p>One decision separates teams that deliver value from those that grind to a halt: whether they write user stories in isolation or as part of a shared conversation. I\u2019ve seen sprint after sprint derailed not by technical debt, but by stories where no one had ever spoken aloud to clarify what \u201cthe user\u201d actually needed. The moment a story appears in the backlog without a conversation, it becomes a liability, not a tool.<\/p>\n<p>Lack of communication in agile stories is not just a symptom\u2014it\u2019s the root cause of misalignment, rework, and team frustration. When a story is written by a single person and dropped into the backlog, it assumes the team will intuit the intent. That assumption fails every time. I\u2019ve worked with teams who spent two weeks building a feature that no one had actually discussed\u2014because the story was \u201cclear enough.\u201d It wasn\u2019t. It wasn\u2019t even testable. And it wasn\u2019t aligned with the real user.<\/p>\n<p>You\u2019ll gain a deeper understanding of how to turn stories from static text into dynamic conversation starters. This chapter walks you through the real cost of solo writing, how to design collaborative refinement sessions, and practical ways to embed team conversation agile at every level. You\u2019ll learn not just what to do, but why it works\u2014and how to fix it when it doesn\u2019t.<\/p>\n<h2>The Myth of the Self-Sufficient Story<\/h2>\n<p>Many teams think they\u2019re being efficient by writing stories independently. They\u2019re not. They\u2019re just delaying the inevitable misunderstanding.<\/p>\n<p>A story is not a document. It\u2019s a placeholder for a conversation. The moment you write it down without a discussion, you\u2019ve already broken the Agile contract.<\/p>\n<p>When you write a story in isolation, you\u2019re making assumptions about the user, the context, and the outcome\u2014assumptions that may not hold. The result? A story that passes &#8220;acceptance&#8221; but fails in delivery.<\/p>\n<p>Consider this: a product owner writes a story: \u201cAs a customer, I want to see my order history so I can re-purchase easily.\u201d It sounds fine. But without a conversation, no one has questioned: \u201cWhat does \u2018see\u2019 mean?\u201d \u201cIs it chronological? By date? By product?\u201d \u201cDo we filter by status?\u201d \u201cDo we include canceled orders?\u201d<\/p>\n<p>These are not edge cases. They are the difference between a usable feature and a rework nightmare.<\/p>\n<h3>Why Solo Writing Fails Every Time<\/h3>\n<p>Even experienced product owners fall into this trap. The pressure to \u201cmove fast\u201d leads to writing stories that feel complete but are fundamentally ambiguous. Here\u2019s what happens under the surface:<\/p>\n<ul>\n<li>Assumptions replace clarity.<\/li>\n<li>Acceptance criteria are guessed, not defined.<\/li>\n<li>Teams start coding based on interpretations, not shared understanding.<\/li>\n<li>Post-delivery, the product doesn\u2019t meet expectations.<\/li>\n<\/ul>\n<p>When I\u2019ve audited backlogs like this, the root cause is almost always the same: no conversation happened before the story was accepted.<\/p>\n<h2>Collaboration in Story Writing: The Real Work Begins<\/h2>\n<p>Writing a story is not the end of the work. It\u2019s the beginning of a team conversation agile must sustain. The real value isn\u2019t in the text\u2014it\u2019s in the thinking behind it.<\/p>\n<p>Every effective story starts with a conversation between the product owner, developers, QA, and sometimes UX. The goal isn\u2019t to draft a perfect sentence. It\u2019s to surface assumptions, challenge interpretations, and align on what \u201cdone\u201d means.<\/p>\n<p>Consider a story like: \u201cAs a user, I want to reset my password.\u201d It\u2019s simple. But without conversation, it could mean: a link sent by email, a self-service portal, or a phone number verification. The difference in tech effort, security design, and user impact is massive. Only team conversation agile can uncover that.<\/p>\n<h3>How to Structure a Real Story Refinement Session<\/h3>\n<p>Refinement isn\u2019t just a checklist\u2014it\u2019s a collaborative ritual. Here\u2019s how to run it effectively:<\/p>\n<ol>\n<li><strong>Start with the story aloud.<\/strong> Read it out loud. The simple act of hearing it exposes awkward phrasing and missing context.<\/li>\n<li><strong>Ask \u201cWho is the user?\u201d<\/strong> Define the role clearly. Is it a returning customer? A new user? A business admin?<\/li>\n<li><strong>Clarify the \u201cSo that\u2026\u201d purpose.<\/strong> Why does this matter? What outcome are we trying to achieve?<\/li>\n<li><strong>Define acceptance criteria together.<\/strong> Use examples: \u201cWhen I click \u2018Send Reset Link\u2019, I get a confirmation message.\u201d<\/li>\n<li><strong>Estimate only after alignment.<\/strong> No estimation should happen before the team understands the story.<\/li>\n<\/ol>\n<p>Do this consistently, and you\u2019ll find stories become more precise, acceptance tests become easier to write, and delivery confidence soars.<\/p>\n<h2>Practical Patterns for Embedding Team Conversation Agile<\/h2>\n<p>Here are three principles I\u2019ve used across dozens of teams to turn stories into conversation hubs:<\/p>\n<ul>\n<li><strong>Write stories in real-time with the team.<\/strong> Instead of drafting alone, co-write during refinement. One person types while others guide the wording.<\/li>\n<li><strong>Use visual aids.<\/strong> A simple sketch of the flow or a user journey map can clarify intent faster than 200 words of text.<\/li>\n<li><strong>Make acceptance criteria examples, not just conditions.<\/strong> Replace \u201cMust send email\u201d with \u201cWhen a user submits the reset form, they receive an email with a 15-minute expiring link.\u201d<\/li>\n<\/ul>\n<p>The goal isn\u2019t to document everything. It\u2019s to make the story a shared artifact that everyone can test and trust.<\/p>\n<h3>When the Conversation Is Missing: A Real Example<\/h3>\n<p>One team was building a \u201cdownload receipts\u201d feature. The story was: \u201cAs a customer, I want to download my receipt so I can file taxes.\u201d<\/p>\n<p>They moved forward without discussion. Developers assumed PDF. QA assumed it was just a link. The feature shipped\u2014only for the business to realize the receipts needed to include VAT, tax IDs, and legal disclaimers. And they were only available in HTML, not PDF.<\/p>\n<p>It cost two weeks of rework. The root cause? No conversation occurred. The story was written in isolation.<\/p>\n<p>If they had asked: \u201cWhat does the receipt need to include?\u201d and \u201cWho will use it?\u201d the problem would have surfaced in the refinement session.<\/p>\n<h2>Measuring the Impact of Conversation<\/h2>\n<p>You can\u2019t manage what you don\u2019t measure. But don\u2019t track story count. Track the quality of the conversation.<\/p>\n<p>Use this simple checklist to audit your refinement sessions:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Check<\/th>\n<th>Yes<\/th>\n<th>No<\/th>\n<\/tr>\n<tr>\n<td>Story was read aloud during refinement<\/td>\n<td>\u25a1<\/td>\n<td>\u25a1<\/td>\n<\/tr>\n<tr>\n<td>Team discussed the user role and context<\/td>\n<td>\u25a1<\/td>\n<td>\u25a1<\/td>\n<\/tr>\n<tr>\n<td>Acceptance criteria were built collaboratively<\/td>\n<td>\u25a1<\/td>\n<td>\u25a1<\/td>\n<\/tr>\n<tr>\n<td>Team agreed on the definition of \u201cdone\u201d<\/td>\n<td>\u25a1<\/td>\n<td>\u25a1<\/td>\n<\/tr>\n<tr>\n<td>Estimation happened only after alignment<\/td>\n<td>\u25a1<\/td>\n<td>\u25a1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>When you run a refinement session and check \u201cNo\u201d on more than one item, you\u2019ve got a problem with collaboration in story writing. That\u2019s not a backlog issue. It\u2019s a team process failure.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I write a story before the team meeting?<\/h3>\n<p>Yes, but only as a draft. The real work begins when the team discusses it. A story written in isolation isn\u2019t a story\u2014it\u2019s a placeholder. Until the team talks about it, it\u2019s not part of the backlog.<\/p>\n<h3>What if the team doesn\u2019t show up for refinement?<\/h3>\n<p>Stop calling it \u201crefinement.\u201d If no one attends, it\u2019s not a conversation\u2014it\u2019s a checklist. You need presence. If developers and QA aren\u2019t there, the story will fail. Prioritize team conversation agile over story volume.<\/p>\n<h3>How do I handle a product owner who insists on writing stories solo?<\/h3>\n<p>Ask them: \u201cWhat do you gain by writing it alone?\u201d The answer is almost never efficiency. The real gain is clarity, shared ownership, and reduced rework. Show them the cost of a single misinterpreted story. Then invite them to co-write with the team.<\/p>\n<h3>Is it okay to write acceptance criteria in advance?<\/h3>\n<p>Only if it\u2019s based on a conversation. Pre-written criteria without alignment are assumptions in disguise. The best acceptance criteria emerge during the conversation, not before.<\/p>\n<h3>How often should we run refinement sessions?<\/h3>\n<p>At least twice per sprint. One for new stories, one for refinement of existing ones. But always with the team present. The frequency matters less than the consistency of collaboration in story writing.<\/p>\n<h3>What\u2019s the difference between refinement and backlog grooming?<\/h3>\n<p>Nothing\u2014same thing, different name. But don\u2019t use the term without the conversation. Grooming that excludes the team is just sorting. Refinement that includes the team is dialogue.<\/p>\n<p>When you treat every story as a conversation starter, not a document, you build teams that deliver value, not just features. The lack of communication in agile stories is not a technical issue\u2014it\u2019s a cultural one. Fix the conversation, and you fix the backlog.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One decision separates teams that deliver value from those that grind to a halt: whether they write user stories in isolation or as part of a shared conversation. I\u2019ve seen sprint after sprint derailed not by technical debt, but by stories where no one had ever spoken aloud to clarify what \u201cthe user\u201d actually needed. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":676,"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-678","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>lack of communication in agile stories<\/title>\n<meta name=\"description\" content=\"Avoid the #1 Agile story failure: writing without conversation. Learn how collaboration in story writing drives clarity, prevents rework, and builds shared understanding.\" \/>\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\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"lack of communication in agile stories\" \/>\n<meta property=\"og:description\" content=\"Avoid the #1 Agile story failure: writing without conversation. Learn how collaboration in story writing drives clarity, prevents rework, and builds shared understanding.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-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=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/\",\"name\":\"lack of communication in agile stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:22:44+00:00\",\"description\":\"Avoid the #1 Agile story failure: writing without conversation. Learn how collaboration in story writing drives clarity, prevents rework, and builds shared understanding.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-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\":\"Process and Collaboration Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Skipping Dialogue: Writing Without Conversation\"}]},{\"@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":"lack of communication in agile stories","description":"Avoid the #1 Agile story failure: writing without conversation. Learn how collaboration in story writing drives clarity, prevents rework, and builds shared understanding.","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\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/","og_locale":"pt_PT","og_type":"article","og_title":"lack of communication in agile stories","og_description":"Avoid the #1 Agile story failure: writing without conversation. Learn how collaboration in story writing drives clarity, prevents rework, and builds shared understanding.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/","name":"lack of communication in agile stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:22:44+00:00","description":"Avoid the #1 Agile story failure: writing without conversation. Learn how collaboration in story writing drives clarity, prevents rework, and builds shared understanding.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/lack-of-communication-in-agile-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":"Process and Collaboration Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/"},{"@type":"ListItem","position":4,"name":"Skipping Dialogue: Writing Without Conversation"}]},{"@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\/678","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\/678\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/676"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=678"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=678"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}