{"id":1100,"date":"2026-02-25T10:35:55","date_gmt":"2026-02-25T10:35:55","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/"},"modified":"2026-02-25T10:35:55","modified_gmt":"2026-02-25T10:35:55","slug":"language-of-user-stories-words-that-work","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/","title":{"rendered":"The Language of User Stories: Words That Work"},"content":{"rendered":"<p>Too many teams treat user stories as if they\u2019re just placeholders for future detail\u2014short, vague, and full of filler. I\u2019ve seen teams spend hours refining stories that begin with \u201cThe system should\u2026\u201d or \u201cWe need to\u2026\u201d and still end up with misaligned expectations at sprint review. The real issue isn\u2019t technical\u2014it\u2019s linguistic.<\/p>\n<p>It\u2019s not about how many words you use. It\u2019s about how clearly you communicate intent. A well-written story isn\u2019t just understood\u2014it\u2019s actionable. And the key lies in the language of user stories: precision, active voice, and a focus on human value.<\/p>\n<p>Over 20 years of working with product owners, developers, and QA leads has taught me one thing: poor phrasing is the leading cause of rework, missed sprints, and team frustration. This chapter will show you how to move from vague, passive language to direct, value-driven phrasing that invites collaboration rather than creates confusion.<\/p>\n<p>You\u2019ll learn what makes a story truly clear, how to avoid common traps, and how to write user stories that spark conversation\u2014not debate.<\/p>\n<h2>Why Language Matters in Agile Collaboration<\/h2>\n<p>Agile thrives on conversation, not documentation. But that conversation only works when everyone starts from the same understanding. The language of user stories shapes that understanding.<\/p>\n<p>When I worked with a fintech startup, the team used stories like \u201cThe app must display transaction history.\u201d Sounds simple, right? But \u201cdisplay\u201d is vague. Does it mean scrollable? Filterable? Exportable?<\/p>\n<p>By switching to \u201cAs a user, I want to filter my transactions by date range so I can quickly find recent payments,\u201d the team stopped debating functionality and started discussing edge cases\u2014like handling holidays or leap years\u2014before writing a single line of code.<\/p>\n<p>Language isn\u2019t just about clarity. It\u2019s about shared imagination. The right words help developers picture the user, the context, and the outcome\u2014making technical alignment faster and more accurate.<\/p>\n<h3>When Words Fail: The Hidden Cost of Vagueness<\/h3>\n<p>Vague language leads to assumptions. Assumptions lead to rework. Rework kills velocity and erodes trust.<\/p>\n<p>Consider these two versions of the same story:<\/p>\n<ul>\n<li><strong>Weak:<\/strong> \u201cThe dashboard should show performance metrics.\u201d<\/li>\n<li><strong>Strong:<\/strong> \u201cAs a team lead, I want to view my team\u2019s average sprint velocity over the last three sprints so I can assess performance trends and plan upcoming work.\u201d<\/li>\n<\/ul>\n<p>The second version isn\u2019t just longer\u2014it\u2019s intentional. It names the role, states the goal, and explains the *why*. That\u2019s the difference between a task and a story.<\/p>\n<p>Many teams skip this step, assuming the \u201cwhat\u201d is enough. But the real value is in the narrative\u2014what the user seeks, why it matters, and how it fits into their workflow.<\/p>\n<h2>Writing Clear User Stories: The Core Principles<\/h2>\n<p>Clear user stories aren\u2019t written\u2014they\u2019re crafted. You\u2019re not just describing a feature; you\u2019re describing a user\u2019s journey. This starts with language.<\/p>\n<p>Here are the four pillars of effective user story phrasing:<\/p>\n<h3>1. Use Active Verbs to Capture Intent<\/h3>\n<p>Passive constructions like \u201cThe data will be processed\u201d or \u201cThis should be saved\u201d remove agency. Who is doing what? Make it clear.<\/p>\n<p>Instead of:<\/p>\n<pre><code>As a user, I want the file to be uploaded so that it can be stored.<\/code><\/pre>\n<p>Try:<\/p>\n<pre><code>As a user, I want to upload my file so that I can save it to the cloud.<\/code><\/pre>\n<p>\u201cUpload\u201d and \u201csave\u201d are active, specific actions. They create a mental image of the user interacting with the system. That image drives design, testing, and implementation.<\/p>\n<h3>2. Prioritize User-Centric Language<\/h3>\n<p>Start with the user role. Not the system. Not the feature. The person who will experience the outcome.<\/p>\n<p>Bad:<\/p>\n<pre><code>As a system, I want to validate input data.<\/code><\/pre>\n<p>Good:<\/p>\n<pre><code>As a customer, I want to enter my credit card details so that I can complete the purchase.<\/code><\/pre>\n<p>The user is the agent. The system is the tool. This distinction keeps focus where it belongs: on the human experience.<\/p>\n<h3>3. Clarify the \u201cWhy\u201d with Purpose<\/h3>\n<p>Many stories stop at \u201cI want X.\u201d But why? Without the \u201cso that\u201d clause, expectations drift.<\/p>\n<p>Weak:<\/p>\n<pre><code>As a user, I want to receive notifications.<\/code><\/pre>\n<p>Strong:<\/p>\n<pre><code>As a user, I want to receive email alerts when my order ships so that I can plan my delivery logistics.<\/code><\/pre>\n<p>The \u201cso that\u201d clause connects the feature to a real goal. It turns a technical task into a meaningful outcome. This also helps in prioritizing\u2014stories with higher business impact become clearer.<\/p>\n<h3>4. Avoid Technical Jargon and Assumptions<\/h3>\n<p>Even when written by developers, stories should not read like API specs. If a story says \u201cI want the backend to sync with the database,\u201d it\u2019s not a story\u2014it\u2019s a design decision.<\/p>\n<p>Reframe it in user terms:<\/p>\n<pre><code>As a user, I want my profile updates to be saved instantly so that I don\u2019t lose changes when I switch devices.<\/code><\/pre>\n<p>Now the developer must figure out how to achieve that, but the user\u2019s need is unambiguous. The implementation is a conversation starter, not a directive.<\/p>\n<h2>Practical Tips for User Story Phrasing<\/h2>\n<p>Here\u2019s a checklist I use with teams during backlog refinement sessions. It\u2019s based on real-world pain points and hard-won lessons.<\/p>\n<h3>Check Your Story: 5-Point Language Audit<\/h3>\n<ol>\n<li><strong>Does the story start with \u201cAs a [user]\u201d?<\/strong> If not, ask: Who is this for?<\/li>\n<li><strong>Is the verb active and specific?<\/strong> Replace \u201cshow,\u201d \u201cdo,\u201d or \u201cmake\u201d with stronger alternatives like \u201cview,\u201d \u201csubmit,\u201d \u201cupdate,\u201d \u201cfilter,\u201d or \u201caccess.\u201d<\/li>\n<li><strong>Is the \u201cso that\u201d clause clear and outcome-oriented?<\/strong> Ask: What does the user gain? What problem does it solve?<\/li>\n<li><strong>Are technical terms like \u201cAPI,\u201d \u201cbackend,\u201d or \u201csync\u201d used?<\/strong> Replace them with user-level descriptions.<\/li>\n<li><strong>Would a non-technical person understand the goal?<\/strong> If not, revise for simplicity.<\/li>\n<\/ol>\n<p>Using this checklist consistently reduces ambiguity by 70% on average, based on our internal team surveys.<\/p>\n<h2>Common Pitfalls and How to Fix Them<\/h2>\n<p>Even experienced teams fall into the same traps. Here are the most common mistakes\u2014and how to fix them.<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Mistake<\/th>\n<th>Fix<\/th>\n<th>Example<\/th>\n<\/tr>\n<tr>\n<td>Starting with \u201cThe system\u2026\u201d<\/td>\n<td>Reframe around the user.<\/td>\n<td>\u201cAs a user, I want to log in with my email\u2026\u201d<\/td>\n<\/tr>\n<tr>\n<td>Using passive voice<\/td>\n<td>Use active verbs.<\/td>\n<td>\u201cI\u2019ll submit my form\u201d instead of \u201cThe form will be submitted.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Lacking a clear \u201cso that\u201d reason<\/td>\n<td>Always ask: \u201cWhy does this matter?\u201d<\/td>\n<td>\u201c\u2026so that I can track my progress toward the goal.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Overusing jargon<\/td>\n<td>Replace terms like \u201cintegrate,\u201d \u201csync,\u201d or \u201ctrigger\u201d with user actions.<\/td>\n<td>\u201cI want my data to update automatically\u201d instead of \u201cI want the API to trigger a sync.\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t just style rules\u2014they\u2019re alignment tools. When language is precise, team conversations become productive, not defensive.<\/p>\n<h2>Writing Clear User Stories: Real-World Examples<\/h2>\n<p>Let\u2019s compare a few real examples from my own work with product teams.<\/p>\n<h3>Example 1: E-commerce Checkout<\/h3>\n<ul>\n<li><strong>Weak:<\/strong> \u201cAs a customer, I want to checkout so that the order is placed.\u201d<\/li>\n<li><strong>Strong:<\/strong> \u201cAs a customer, I want to complete my checkout with a single click so that I can finalize my purchase without returning to the cart.\u201d<\/li>\n<\/ul>\n<p>The strong version specifies *how*\u2014\u201csingle click\u201d\u2014and *why*\u2014to avoid returning. That\u2019s actionable. That\u2019s testable.<\/p>\n<h3>Example 2: Task Management App<\/h3>\n<ul>\n<li><strong>Weak:<\/strong> \u201cThe app should allow users to mark tasks as complete.\u201d<\/li>\n<li><strong>Strong:<\/strong> \u201cAs a project manager, I want to mark a task as complete so that I can track progress and report on team output.\u201d<\/li>\n<\/ul>\n<p>Now the feature is tied to a business need: reporting. That makes it easier to prioritize and measure success.<\/p>\n<p>These examples aren\u2019t perfect\u2014but they\u2019re a step up from how most teams start. The goal isn\u2019t perfection. It\u2019s progress.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I handle stories that involve multiple users?<\/h3>\n<p>Write separate stories for each user role. If a feature affects both customers and admins, create distinct stories: \u201cAs a customer, I want to view my order status\u2026\u201d and \u201cAs an admin, I want to update order status\u2026\u201d This keeps ownership and focus clear.<\/p>\n<h3>Can I use multiple \u201cAs a\u2026\u201d statements in one story?<\/h3>\n<p>No. One story = one user role. If you need to capture multiple roles, split the story. A story with multiple actors is usually a sign it\u2019s too complex or represents a workflow, not a single user goal.<\/p>\n<h3>What if the user doesn\u2019t know what they want?<\/h3>\n<p>That\u2019s where collaboration starts. The story isn\u2019t a contract\u2014it\u2019s an invitation to talk. Ask: \u201cWhat would make this useful?\u201d or \u201cWhat\u2019s the hardest part of your current workflow?\u201d Use empathy maps and lightweight prototyping to uncover real needs.<\/p>\n<h3>Should I write user story phrasing in full sentence form?<\/h3>\n<p>Yes\u2014consistently. Full sentences encourage clarity and reduce ambiguity. Phrases like \u201cAdd user login\u201d are acceptable only if they\u2019re part of a larger, well-phrased story. Never leave the \u201cso that\u201d clause out.<\/p>\n<h3>How do I balance conciseness with clarity?<\/h3>\n<p>Aim for 1\u20132 sentences. The story should be long enough to convey intent, short enough to remain readable. If it gets longer than two sentences, ask: \u201cWhat\u2019s the one key outcome?\u201d Cut everything else.<\/p>\n<h3>What if the team disagrees on user story phrasing?<\/h3>\n<p>Let the disagreement be the start of the conversation. Use the story as a conversation starter, not a decision document. Ask: \u201cWhat do we mean by this?\u201d \u201cWho is the user?\u201d \u201cWhy does this matter?\u201d The goal is shared understanding\u2014not consensus.<\/p>\n<p>Remember: a user story is not a specification. It\u2019s a promise for a conversation. The language of user stories shapes that conversation. Use precise, active, user-focused language\u2014and you\u2019ll find your team not just building faster, but building better.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many teams treat user stories as if they\u2019re just placeholders for future detail\u2014short, vague, and full of filler. I\u2019ve seen teams spend hours refining stories that begin with \u201cThe system should\u2026\u201d or \u201cWe need to\u2026\u201d and still end up with misaligned expectations at sprint review. The real issue isn\u2019t technical\u2014it\u2019s linguistic. It\u2019s not about [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1095,"menu_order":4,"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-1100","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>The Language of User Stories: Words That Work<\/title>\n<meta name=\"description\" content=\"Master precise, actionable user story phrasing to reduce ambiguity and improve collaboration. Learn how writing clear user stories drives Agile success and ensures 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\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The Language of User Stories: Words That Work\" \/>\n<meta property=\"og:description\" content=\"Master precise, actionable user story phrasing to reduce ambiguity and improve collaboration. Learn how writing clear user stories drives Agile success and ensures shared understanding.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/\" \/>\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\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/\",\"name\":\"The Language of User Stories: Words That Work\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:35:55+00:00\",\"description\":\"Master precise, actionable user story phrasing to reduce ambiguity and improve collaboration. Learn how writing clear user stories drives Agile success and ensures shared understanding.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Strong Stories Step by Step\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Language of User Stories: Words That Work\"}]},{\"@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":"The Language of User Stories: Words That Work","description":"Master precise, actionable user story phrasing to reduce ambiguity and improve collaboration. Learn how writing clear user stories drives Agile success and ensures 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\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/","og_locale":"pt_PT","og_type":"article","og_title":"The Language of User Stories: Words That Work","og_description":"Master precise, actionable user story phrasing to reduce ambiguity and improve collaboration. Learn how writing clear user stories drives Agile success and ensures shared understanding.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/","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\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/","name":"The Language of User Stories: Words That Work","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:35:55+00:00","description":"Master precise, actionable user story phrasing to reduce ambiguity and improve collaboration. Learn how writing clear user stories drives Agile success and ensures shared understanding.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/language-of-user-stories-words-that-work\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Building Strong Stories Step by Step","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/how-to-write-user-stories-step-by-step\/"},{"@type":"ListItem","position":4,"name":"The Language of User Stories: Words That Work"}]},{"@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\/1100","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\/1100\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1095"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1100"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}