{"id":681,"date":"2026-02-25T10:22:45","date_gmt":"2026-02-25T10:22:45","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/"},"modified":"2026-02-25T10:22:45","modified_gmt":"2026-02-25T10:22:45","slug":"writing-stories-without-examples-or-models","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/","title":{"rendered":"Writing Stories Without Examples or Models"},"content":{"rendered":"

One of the most persistent gaps I\u2019ve seen in product backlogs is the absence of tangible references. A story like \u201cThe system should process orders quickly\u201d may sound plausible until you ask: what does \u201cquickly\u201d mean in context? How fast is fast enough? Without a shared model or example, the team defaults to assumptions\u2014often wrong ones.<\/p>\n

When I first led a product discovery session in a legacy system, I noticed the team kept describing flows without anchoring them to concrete examples. They\u2019d say, \u201cThe user gets an email when the order is ready,\u201d but no one could define what \u201cready\u201d meant. That\u2019s when I introduced a simple scenario: \u201cWhen the order status changes to \u2018shipped\u2019 and the tracking number is generated, send the confirmation email.\u201d Suddenly, the conversation shifted from vague intent to clear conditions.<\/p>\n

Stories without examples or models don\u2019t fail because they\u2019re poorly written\u2014they fail because they\u2019re abstract. They don\u2019t invite collaboration. They don\u2019t become conversation starters. Instead, they turn into guesswork wrapped in Agile jargon.<\/p>\n

This chapter shows how to fix that. You\u2019ll learn to use story model visualization and story mapping tools not as optional extras, but as foundational practices. These aren\u2019t just diagrams\u2014they\u2019re conversation catalysts that reveal hidden complexity, clarify behavior, and prevent rework.<\/p>\n

The Hidden Cost of Abstract Stories<\/h2>\n

Abstract stories are invisible to the team. They can\u2019t be tested. They can\u2019t be discussed. They\u2019re just promises with no proof.<\/p>\n

Take this example: \u201cAs a customer, I want to see my order history so I can track past purchases.\u201d The goal is clear, but how do we know when it\u2019s done? What counts as \u201csee\u201d? Is it a list? A calendar view? A search filter?<\/p>\n

Without a concrete example, acceptance conditions are guessed at. The developer builds a table. The tester finds no test coverage. The product owner says it\u2019s not what they meant. Rework begins. All because the story lacked a model or example.<\/p>\n

The truth is: if you can\u2019t show it, you can\u2019t be sure it exists. That\u2019s why story model visualization is not a luxury. It\u2019s essential.<\/p>\n

Why Models Matter<\/h3>\n

Models\u2014whether decision tables, state diagrams, or flowcharts\u2014turn abstract behavior into observable, testable logic. They help the team see the full range of possible outcomes, not just the happy path.<\/p>\n

Consider a story about refunds:<\/p>\n

As a customer, I want to request a refund so I can get my money back if I\u2019m not satisfied.<\/em><\/p>\n

That\u2019s insufficient. But with a decision table, you can map the rules:<\/p>\n\n\n\n\n\n\n\n
Order Status<\/th>\nReturn Window<\/th>\nRefund Eligible?<\/th>\n<\/tr>\n
Shipped<\/td>\nWithin 30 days<\/td>\nYes<\/td>\n<\/tr>\n
Shipped<\/td>\nAfter 30 days<\/td>\nNo<\/td>\n<\/tr>\n
Delivered<\/td>\nWithin 90 days<\/td>\nYes<\/td>\n<\/tr>\n
Canceled<\/td>\nAny time<\/td>\nNo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Now the story has boundaries. The team knows what to build\u2014and what not to. This is story model visualization in action.<\/p>\n

How to Use Story Mapping Tools Effectively<\/h2>\n

Story mapping tools\u2014 like Visual Paradigm \u2014turn conversations into visual artifacts. They help you sequence stories by user workflow, spot gaps, and identify technical debt.<\/p>\n

I\u2019ve seen teams use story maps to uncover a hidden dependency: a \u201cuser login\u201d story was missing, but the map revealed that all other user actions required authentication. That wasn\u2019t in the original backlog. With a map, it became obvious.<\/p>\n

Here\u2019s how to use story mapping tools to avoid writing stories without examples or models:<\/p>\n

    \n
  1. Start with the user journey.<\/strong> List every step a user takes from start to finish.<\/li>\n
  2. Group related stories.<\/strong> Cluster them by phase\u2014login, browse, order, pay, track.<\/li>\n
  3. Insert examples for each story.<\/strong> For \u201cEnter payment details,\u201d show a sample form with valid\/invalid inputs.<\/li>\n
  4. Use color coding.<\/strong> Mark stories with unclear acceptance criteria in yellow, high risk in red, and ready in green.<\/li>\n
  5. Update the map after every sprint.<\/strong> This keeps the backlog aligned with reality.<\/li>\n<\/ol>\n

    These tools aren\u2019t about perfection. They\u2019re about visibility. They force the team to confront ambiguity early.<\/p>\n

    Common Pitfalls in Story Mapping<\/h3>\n

    Even with story mapping tools, teams fall into traps:<\/p>\n

      \n
    • Building maps only at planning time.<\/strong> Maps should evolve. A static map is worse than no map.<\/li>\n
    • Using them only for estimation.<\/strong> They\u2019re far more powerful as discovery tools.<\/li>\n
    • Letting one person own the map.<\/strong> It\u2019s a team artifact. If only the product owner draws it, the team isn\u2019t engaged.<\/li>\n
    • Overcomplicating the model.<\/strong> A simple flowchart beats a 10-page UML diagram. Clarity over completeness.<\/li>\n<\/ul>\n

      The goal isn\u2019t to create a masterpiece. It\u2019s to make the invisible visible.<\/p>\n

      Examples Are More than Acceptance Criteria<\/h2>\n

      Acceptance criteria are often written as a checklist: \u201cGiven X, when Y, then Z.\u201d That\u2019s useful\u2014but it\u2019s still text. It doesn\u2019t show the full behavior.<\/p>\n

      Examples are different. They\u2019re specific, concrete scenarios that represent a class of behavior. They\u2019re not just tests\u2014they\u2019re conversations.<\/p>\n

      For instance:<\/p>\n

      As a user,<\/strong><\/p>\n

      I want to reset my password<\/strong><\/p>\n

      so I can regain access to my account.<\/strong><\/p>\n

      Now, instead of just listing criteria, show two examples:<\/p>\n

        \n
      • Example 1: Valid email input<\/strong>\n

        Given I\u2019m on the password reset page,<\/p>\n

        When I enter my registered email and click \u201cSend Reset Link\u201d,<\/p>\n

        Then I should see a confirmation: \u201cA reset link has been sent to your email.\u201d<\/p>\n<\/li>\n

      • Example 2: Invalid email input<\/strong>\n

        Given I\u2019m on the password reset page,<\/p>\n

        When I enter an unregistered email and click \u201cSend Reset Link\u201d,<\/p>\n

        Then I should see an error: \u201cNo account found with that email.\u201d<\/p>\n<\/li>\n<\/ul>\n

        These aren\u2019t just test scripts. They\u2019re part of the story. They\u2019re what make it real.<\/p>\n

        This is story model visualization at work. The example isn\u2019t a supplement\u2014it\u2019s the story\u2019s skeleton.<\/p>\n

        When to Use Which Tool<\/h2>\n

        Not every story needs a full diagram. The key is matching the model to the complexity.<\/p>\n\n\n\n\n\n\n
        Complexity Level<\/th>\nRecommended Tool<\/th>\nUse Case<\/th>\n<\/tr>\n
        Simple<\/td>\nSimple decision table<\/td>\nRefund eligibility based on date and status<\/td>\n<\/tr>\n
        Medium<\/td>\nFlowchart or sequence diagram<\/td>\nUser login with two-factor authentication<\/td>\n<\/tr>\n
        High<\/td>\nState machine or story map<\/td>\nOrder lifecycle with multiple transitions and roles<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Don\u2019t over-invest. Don\u2019t under-invest. Match the model to the risk.<\/p>\n

        Final Insight: A Story Without an Example Is a Promise<\/h2>\n

        I\u2019ve worked with teams who said, \u201cWe don\u2019t need examples. We\u2019ll figure it out in dev.\u201d That\u2019s not how it works. You don\u2019t figure out requirements in code\u2014you figure them out in conversation.<\/p>\n

        A story without examples or models is a promise to deliver value without a plan to deliver it. It\u2019s not a story. It\u2019s a placeholder for confusion.<\/p>\n

        Use story model visualization. Use story mapping tools. Let them turn vague abstractions into shared understanding. Let them turn silence into dialogue.<\/p>\n

        When your team can point to a diagram and say, \u201cThat\u2019s what we\u2019re building,\u201d you\u2019ve won. The story is no longer just written\u2014it\u2019s lived.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        Why should I use story model visualization instead of just writing acceptance criteria?<\/h3>\n

        Acceptance criteria are good for testability, but they don\u2019t show the full behavior. A decision table or flowchart reveals edge cases and dependencies that text alone can\u2019t. It\u2019s about seeing patterns, not just testing conditions. Story model visualization makes complex logic tangible.<\/p>\n

        Do story mapping tools slow down backlog refinement?<\/h3>\n

        No\u2014on the contrary, they accelerate it. A story map reveals gaps, duplicates, and dependencies early. It prevents the team from building a feature only to discover it doesn\u2019t fit the user journey. The time saved in rework far outweighs the time spent creating the map.<\/p>\n

        What if the team resists using models?<\/h3>\n

        Start small. Pick one high-risk story. Show the team the difference between a story with and without a model. Let them see how the model prevents rework. Over time, they\u2019ll see it\u2019s not overhead\u2014it\u2019s insurance.<\/p>\n

        Is there a standard format for story maps?<\/h3>\n

        No one-size-fits-all. The structure should reflect your user journey. The key is horizontal alignment (steps) and vertical organization (features). Use colors, labels, and symbols to clarify risk, effort, and dependencies. The goal is clarity, not aesthetics.<\/p>\n

        How do I know when a story needs a model?<\/h3>\n

        If the story involves conditions, transitions, or multiple outcomes, it likely needs a model. If you find yourself asking, \u201cWhat if this happens?\u201d or \u201cWhat should the system do next?\u201d\u2014it\u2019s time for a diagram. When the behavior isn\u2019t obvious, model it.<\/p>\n","protected":false},"excerpt":{"rendered":"

        One of the most persistent gaps I\u2019ve seen in product backlogs is the absence of tangible references. A story like \u201cThe system should process orders quickly\u201d may sound plausible until you ask: what does \u201cquickly\u201d mean in context? How fast is fast enough? Without a shared model or example, the team defaults to assumptions\u2014often wrong […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":676,"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-681","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nWriting Stories Without Examples or Models<\/title>\n<meta name=\"description\" content=\"Learn how to avoid writing user stories without examples or models. Use story model visualization and story mapping tools to clarify requirements and improve team alignment.\" \/>\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\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Writing Stories Without Examples or Models\" \/>\n<meta property=\"og:description\" content=\"Learn how to avoid writing user stories without examples or models. Use story model visualization and story mapping tools to clarify requirements and improve team alignment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/\",\"name\":\"Writing Stories Without Examples or Models\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:22:45+00:00\",\"description\":\"Learn how to avoid writing user stories without examples or models. Use story model visualization and story mapping tools to clarify requirements and improve team alignment.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Process and Collaboration Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Writing Stories Without Examples or Models\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Writing Stories Without Examples or Models","description":"Learn how to avoid writing user stories without examples or models. Use story model visualization and story mapping tools to clarify requirements and improve team alignment.","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\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/","og_locale":"pl_PL","og_type":"article","og_title":"Writing Stories Without Examples or Models","og_description":"Learn how to avoid writing user stories without examples or models. Use story model visualization and story mapping tools to clarify requirements and improve team alignment.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"7 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/","name":"Writing Stories Without Examples or Models","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:22:45+00:00","description":"Learn how to avoid writing user stories without examples or models. Use story model visualization and story mapping tools to clarify requirements and improve team alignment.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/writing-stories-without-examples-or-models\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Process and Collaboration Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/collaboration-issues-in-user-stories\/"},{"@type":"ListItem","position":4,"name":"Writing Stories Without Examples or Models"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/681","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/681\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/676"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=681"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=681"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}