{"id":672,"date":"2026-02-25T10:22:41","date_gmt":"2026-02-25T10:22:41","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/"},"modified":"2026-02-25T10:22:41","modified_gmt":"2026-02-25T10:22:41","slug":"vague-roles-in-user-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/","title":{"rendered":"Vague Roles: When &#8216;User&#8217; Isn\u2019t Specific Enough"},"content":{"rendered":"<p>One of the most persistent sources of confusion in Agile teams is a poorly defined actor. When a story begins with \u201cAs a user,\u201d without specifying who that user actually is, the entire foundation of clarity crumbles.<\/p>\n<p>I\u2019ve seen dozens of stories rejected during refinement simply because the role was generic. \u201cUser\u201d is not a role\u2014it\u2019s a placeholder. It doesn\u2019t tell the developer whether this is a customer, a support agent, a finance manager, or a system administrator.<\/p>\n<p>The real problem isn\u2019t just ambiguity\u2014it\u2019s the downstream effect. Without a clear actor, acceptance criteria become guesswork. Design decisions drift. Testing becomes inconsistent. The team builds something that may not actually serve anyone.<\/p>\n<p>After 20 years of refining backlogs, I\u2019ve learned this: a story is not a task. It\u2019s a conversation. And that conversation can\u2019t begin until someone knows who is asking for it.<\/p>\n<p>This chapter explores how to replace vague roles with precise actors, using real examples from product work. You\u2019ll learn how to apply user role clarity and actor definition in agile stories to improve precision, reduce rework, and align the team around real user value.<\/p>\n<h2>Why Generic Roles Break Stories<\/h2>\n<p>Let\u2019s be clear: \u201cuser\u201d is a verb. It describes an action. But in a user story, \u201cuser\u201d is meant to be a noun\u2014the person or system acting.<\/p>\n<p>When that noun is undefined, the story becomes a void. No context. No boundary. No ownership.<\/p>\n<p>Consider this example:<\/p>\n<p><code>As a user, I want to reset my password so I can log in again.<\/code><\/p>\n<p>Who is the user? A customer? An admin? A new user who forgot their password? The story doesn\u2019t say. So the team must ask questions. And every question delays delivery.<\/p>\n<p>More troubling: the lack of a specific actor often hides deeper issues. Is this story for a B2C customer? A B2B partner? A third-party API client? Without clarity, you can\u2019t design correctly\u2014or test.<\/p>\n<p>Even worse, vague roles encourage surface-level thinking. Teams focus on \u201cwhat\u201d needs to be built, not \u201cwho\u201d it\u2019s for. This erodes empathy and turns user stories into feature checklists.<\/p>\n<p>Here are four telltale signs your story has a vague role:<\/p>\n<ul>\n<li>The acceptance criteria depend on assumptions about the user\u2019s role.<\/li>\n<li>Multiple team members interpret the story differently.<\/li>\n<li>Designers or testers ask for clarification on the actor.<\/li>\n<li>The story is accepted but fails in production because it didn\u2019t meet actual user needs.<\/li>\n<\/ul>\n<p>If any of these ring true, your story is suffering from poor actor definition in agile stories.<\/p>\n<h2>How to Define the Right Actor<\/h2>\n<p>Clear actor definition isn\u2019t about complexity\u2014it\u2019s about specificity. You\u2019re not trying to name every possible role. You\u2019re trying to name the one that counts.<\/p>\n<p>Start by stepping back and asking: Who actually experiences this feature?<\/p>\n<p>Instead of \u201cuser,\u201d ask: Is this for a customer? A team lead? A data analyst? A new onboarding user? A system that processes data?<\/p>\n<p>Once you identify the correct actor, test it with three questions:<\/p>\n<ol>\n<li>Could someone else interpret this role differently?<\/li>\n<li>Is the role tied to a real job or person in the system?<\/li>\n<li>If I removed this role, would the story still make sense?<\/li>\n<\/ol>\n<p>If the answer to #3 is \u201cyes,\u201d then the role is still too generic.<\/p>\n<p>Let\u2019s revisit the password reset story with a sharper role:<\/p>\n<p><code>As a new customer, I want to reset my password so I can access my account after forgetting it.<\/code><\/p>\n<p>Now the story has context. The team knows this is for someone who just signed up. They can design a flow with email verification, a temporary token, and clear error messaging for password recovery.<\/p>\n<p>Notice how the revised story now implies the user journey. It\u2019s not just \u201creset password.\u201d It\u2019s \u201creset password after onboarding failure.\u201d That\u2019s a critical difference.<\/p>\n<p>Here\u2019s a quick reference for common actors in real products:<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Generic Role<\/th>\n<th>Specific Actor<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>User<\/td>\n<td>New customer<\/td>\n<td>Implies onboarding stage, needs email confirmation<\/td>\n<\/tr>\n<tr>\n<td>User<\/td>\n<td>Support agent<\/td>\n<td>Implies ticket system, case management flow<\/td>\n<\/tr>\n<tr>\n<td>User<\/td>\n<td>Finance manager<\/td>\n<td>Implies budget approval, reporting, audit trails<\/td>\n<\/tr>\n<tr>\n<td>User<\/td>\n<td>API client<\/td>\n<td>Implies rate limiting, authentication, response schema<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use these not as rigid templates, but as starting points. The goal is to **replace abstraction with identity**.<\/p>\n<h3>Strategies for Actor Clarity<\/h3>\n<p>Here are three practical techniques I\u2019ve used in dozens of product teams:<\/p>\n<ol>\n<li><strong>Role Mapping at Story Refinement<\/strong>: During backlog refinement, always ask: \u201cWho is this story for?\u201d Write the answer in bold. If it\u2019s \u201cuser,\u201d push back until it\u2019s specific.<\/li>\n<li><strong>Use Persona Anchors<\/strong>: Attach stories to real personas. If a story isn\u2019t tied to a named persona, it\u2019s too abstract.<\/li>\n<li><strong>Ask \u201cWho Would Be Disappointed?\u201d<\/strong>: If the story fails, who would care? That person is the actor.<\/li>\n<\/ol>\n<p>These are simple, but they force conversations that expose hidden assumptions.<\/p>\n<p>One of my favorite techniques: write the story first, then ask, \u201cWho is this story for?\u201d If the answer isn\u2019t immediate, the role is vague.<\/p>\n<h2>The Ripple Effect of Poor Actor Definition<\/h2>\n<p>When the actor is unclear, the entire development lifecycle suffers.<\/p>\n<p>Designers may create a UI that fits a customer but not a support agent. Developers may build a complex form when a simple email link would suffice. Testers may miss edge cases because they don\u2019t know the user\u2019s context.<\/p>\n<p>Even worse: if the actor is ambiguous, so is the acceptance criteria.<\/p>\n<p>Take this poorly defined story:<\/p>\n<p><code>As a user, I want to see my order history so I can track past purchases.<\/code><\/p>\n<p>What does \u201csee\u201d mean? A table? A list? A calendar view? What data? All orders? Only completed ones? What if the user is an admin\u2014should they see all orders?<\/p>\n<p>Now, with a clearer role:<\/p>\n<p><code>As a returning customer, I want to view my past 12 months of purchase history so I can review my spending and reorder frequently bought items.<\/code><\/p>\n<p>Suddenly, the acceptance criteria become clear: show only completed orders, include date, product name, and total cost. No refunds. No canceled orders.<\/p>\n<p>This is how user role clarity transforms stories from vague ideas into precise, testable deliverables.<\/p>\n<p>Remember: a story isn\u2019t a task. It\u2019s a commitment to a conversation. And that conversation can only happen when everyone agrees on who is speaking.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intentions, teams fall into traps:<\/p>\n<ul>\n<li><strong>Over-abstracting**: \u201cAs a user\u201d becomes the default. Break the habit by banning it in story writing unless absolutely necessary.<\/strong><\/li>\n<p><strong><\/p>\n<li><strong>Using job titles as roles**: \u201cAs a manager\u201d is still too broad. Instead, ask: What kind of manager? A sales manager? A project manager? A regional manager?<\/strong><\/li>\n<p><strong><\/p>\n<li><strong>Assuming roles are obvious**: Just because a role seems obvious to the product owner doesn\u2019t mean it is to developers or testers.<\/strong><\/li>\n<p><strong><\/p>\n<li><strong>Confusing system actors with human actors**: A system can be an actor, but only if it\u2019s a defined entity (e.g., \u201cAs a billing system, I need to send a reminder to the customer 48 hours before renewal\u201d).<\/strong><\/li>\n<p><strong><br \/>\n    <\/strong><\/strong><\/strong><\/strong><\/ul>\n<p><strong><strong><strong><\/p>\n<p>When in doubt, ask: \u201cWould a developer reading this story know exactly who to build for?\u201d If not, revise the role.<\/p>\n<h2>Final Checklist: Is Your Actor Clear?<\/h2>\n<p>Before you accept a story, run this quick audit:<\/p>\n<ul>\n<li>Is the actor named or described in detail (e.g., \u201cnew customer,\u201d \u201csupport agent\u201d)?<\/li>\n<li>Can you describe the person\u2019s job, goals, and context?<\/li>\n<li>Is the role tied to a real user journey or system process?<\/li>\n<li>Would the same story work for a different role? (If yes, it\u2019s still too generic.)<\/li>\n<li>Has the team discussed and agreed on this role during refinement?<\/li>\n<\/ul>\n<p>If you can answer yes to all five, your story has solid user role clarity.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What if the user is both a customer and an admin?<\/h3>\n<p>Split the story. If the same person has two roles, write two stories: one for the customer perspective, one for the admin. That way, each story captures a distinct value path.<\/p>\n<h3>How do I define the actor when it\u2019s a system or API?<\/h3>\n<p>Use clear naming: \u201cAs a payment processor, I need to validate the credit card before charging.\u201d This makes the role explicit and avoids confusion with human actors.<\/p>\n<h3>Can I use \u201ca customer\u201d instead of a specific role?<\/h3>\n<p>\u201cA customer\u201d is acceptable only if the context is clear. Avoid \u201ca user.\u201d Use \u201cthe customer\u201d or \u201ca returning customer\u201d for better precision.<\/p>\n<h3>What if the role changes during development?<\/h3>\n<p>That\u2019s fine. But the story must reflect the intended actor at the time of release. If the role shifts, revisit the story and update it. Don\u2019t leave it ambiguous.<\/p>\n<h3>How often should I review actor definition in agile stories?<\/h3>\n<p>Review it during every story refinement session. Make it part of your Definition of Ready. If the actor isn\u2019t clear, the story doesn\u2019t move forward.<\/p>\n<h3>Do I need to define the actor in every story?<\/h3>\n<p>Yes. Even if the role is repeated across multiple stories, name it each time. Consistency matters more than brevity.<\/p>\n<p>Clarity begins with the actor. When the role is vague, the story loses its purpose. When the role is clear, the story becomes a roadmap for value.<\/p>\n<p>Don\u2019t write stories. Write conversations with real people. Replace \u201cuser\u201d with identity. Replace guesswork with design. That\u2019s how you build products people actually want.<\/p>\n<p><\/strong><\/strong><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the most persistent sources of confusion in Agile teams is a poorly defined actor. When a story begins with \u201cAs a user,\u201d without specifying who that user actually is, the entire foundation of clarity crumbles. I\u2019ve seen dozens of stories rejected during refinement simply because the role was generic. \u201cUser\u201d is not a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":670,"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-672","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>Vague Roles in User Stories<\/title>\n<meta name=\"description\" content=\"Fix vague roles in user stories by improving user role clarity and actor definition in agile stories. Learn how to write testable, actionable stories that deliver real value.\" \/>\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\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Vague Roles in User Stories\" \/>\n<meta property=\"og:description\" content=\"Fix vague roles in user stories by improving user role clarity and actor definition in agile stories. Learn how to write testable, actionable stories that deliver real value.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/\",\"name\":\"Vague Roles in User Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:22:41+00:00\",\"description\":\"Fix vague roles in user stories by improving user role clarity and actor definition in agile stories. Learn how to write testable, actionable stories that deliver real value.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structural Mistakes That Undermine Clarity\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Vague Roles: When &#8216;User&#8217; Isn\u2019t Specific Enough\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Vague Roles in User Stories","description":"Fix vague roles in user stories by improving user role clarity and actor definition in agile stories. Learn how to write testable, actionable stories that deliver real value.","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\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/","og_locale":"ru_RU","og_type":"article","og_title":"Vague Roles in User Stories","og_description":"Fix vague roles in user stories by improving user role clarity and actor definition in agile stories. Learn how to write testable, actionable stories that deliver real value.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"8 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/","name":"Vague Roles in User Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:22:41+00:00","description":"Fix vague roles in user stories by improving user role clarity and actor definition in agile stories. Learn how to write testable, actionable stories that deliver real value.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/vague-roles-in-user-stories\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Structural Mistakes That Undermine Clarity","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/common-mistakes-in-writing-user-stories\/user-story-structure-mistakes\/"},{"@type":"ListItem","position":4,"name":"Vague Roles: When &#8216;User&#8217; Isn\u2019t Specific Enough"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/672","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/672\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/670"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=672"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}