{"id":1798,"date":"2026-02-25T10:46:09","date_gmt":"2026-02-25T10:46:09","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/"},"modified":"2026-02-25T10:46:09","modified_gmt":"2026-02-25T10:46:09","slug":"reusable-user-story-patterns-product-families","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/","title":{"rendered":"Reusable Story Patterns for Product Families"},"content":{"rendered":"<p>Here\u2019s the truth that changes everything: the most efficient way to scale agile isn\u2019t by duplicating work across teams\u2014it\u2019s by creating reusable story patterns that evolve with your product line. I\u2019ve seen teams waste months rewriting the same story logic across similar products. The breakthrough came when we stopped treating stories as isolated units and started treating them as components in a shared library.<\/p>\n<p>By defining reusable user story patterns, you\u2019re not just saving time\u2014you\u2019re building a common language across product lines, reducing ambiguity, and accelerating delivery. This chapter shows how to identify, structure, and apply reusable story fragments so your teams can deliver consistent value across multiple products without reinventing the wheel.<\/p>\n<h2>Why Reusable Story Patterns Are Essential in Product Line Agile<\/h2>\n<p>When you manage a portfolio of related products, shared functionality is inevitable. Think authentication, reporting, data export, or compliance logging. These features appear across multiple products but with slight variations.<\/p>\n<p>Without reuse, each team rewrites the same acceptance criteria, defines similar user roles, and creates redundant tests. This leads to inconsistency, higher maintenance cost, and delayed feedback.<\/p>\n<p>Reusable user story patterns solve this by capturing proven, validated story structures that apply across your product family. They act like templates with context-specific variables\u2014delivering agility without chaos.<\/p>\n<h3>When to Use Reusable Story Patterns<\/h3>\n<ul>\n<li>When multiple products share core functionality (e.g., multi-tenancy, audit trails).<\/li>\n<li>When teams are working in parallel but must maintain aligned behavior.<\/li>\n<li>When compliance, security, or UX standards must be consistent.<\/li>\n<li>When you want to reduce onboarding time for new teams or new products.<\/li>\n<\/ul>\n<h2>How to Build a Reusable Story Pattern<\/h2>\n<p>Creating a reusable story pattern isn\u2019t about copying and pasting. It\u2019s about abstraction with intent.<\/p>\n<p>Start by observing recurring story types across product teams. Look for patterns in structure, acceptance criteria, and user roles.<\/p>\n<h3>Step 1: Identify Shared Story Types<\/h3>\n<p>Collect user stories from different products that serve the same purpose. For example:<\/p>\n<ul>\n<li><em>As a user, I want to log in securely so that I can access my account.<\/em><\/li>\n<li><em>As a customer, I want to authenticate via SSO so that I can access the portal without a password.<\/em><\/li>\n<li><em>As a system, I need to validate credentials through the identity provider so that only authorized users can proceed.<\/em><\/li>\n<\/ul>\n<p>These may all stem from the same underlying requirement: secure authentication. They share structure, context, and acceptance logic.<\/p>\n<h3>Step 2: Abstract the Core Elements<\/h3>\n<p>Extract the common components and replace specific details with placeholders:<\/p>\n<pre><code>As a [user role], I want to [authenticate using method] so that I can [access system] securely.\n\nAcceptance Criteria:\n- When [user role] attempts to [authentication method], the system must [validate credentials via X].\n- If authentication fails, the system must [display error message Y] and prevent access.\n- The system must log authentication attempts in [audit log location].\n<\/code><\/pre>\n<p>This abstract form becomes your reusable story pattern. It\u2019s not a template\u2014it\u2019s a validated, reusable unit of work.<\/p>\n<h3>Step 3: Document for Clarity and Reuse<\/h3>\n<p>Store your pattern in a shared repository with:<\/p>\n<ul>\n<li>A clear name (e.g., \u00ab\u00a0Secure Authentication via SSO or Password\u00a0\u00bb)<\/li>\n<li>Description of intended use<\/li>\n<li>Context: which product lines it applies to<\/li>\n<li>Examples of actual stories derived from the pattern<\/li>\n<li>Acceptance criteria variants<\/li>\n<li>Link to related architectural or compliance standards<\/li>\n<\/ul>\n<h2>Examples of Reusable Story Patterns in Practice<\/h2>\n<p>Here are real patterns we\u2019ve used across product families in financial and healthcare tech:<\/p>\n<h3>Pattern 1: Secure Authentication (Multi-Product)<\/h3>\n<p><strong>Use Case<\/strong>: Used in 5+ products with varying authentication methods (password, SSO, MFA).<\/p>\n<p><strong>Abstract Story<\/strong>:<\/p>\n<pre><code>As a [user type], I want to authenticate using [method: password, SSO, MFA] so that I can access [product name] securely.\n\nAcceptance Criteria:\n- The system must verify [method] via [identity provider].\n- If [method] fails, display error: \"[error message]\".\n- All authentication attempts must be logged in [audit log system].\n- Session timeout must be [X] minutes after inactivity.\n<\/code><\/pre>\n<p><strong>Usage<\/strong>: Reused in CRM, billing, compliance, and analytics platforms with only method and product name changed.<\/p>\n<h3>Pattern 2: Data Export with Compliance Controls<\/h3>\n<p><strong>Use Case<\/strong>: Required in regulatory products to export data with audit controls.<\/p>\n<p><strong>Abstract Story<\/strong>:<\/p>\n<pre><code>As a [user role], I want to export [data type] so that I can [purpose: e.g., analyze, report].\n\nAcceptance Criteria:\n- The export must include a timestamp of creation and user identity.\n- The file must be encrypted at rest and in transit.\n- The system must log export actions in [compliance log].\n- Exports are restricted to [X] per day per user.\n<\/code><\/pre>\n<p><strong>Usage<\/strong>: Applied across HR, finance, and audit systems with minor adjustments for data sensitivity levels.<\/p>\n<h2>How to Scale Multi-Product Reuse<\/h2>\n<p>Reusability doesn\u2019t happen by accident. You need a system to support it.<\/p>\n<h3>Key Enablers for Multi-Product Reuse<\/h3>\n<ul>\n<li><strong>Shared Story Repository<\/strong>: A central source of truth (e.g., Confluence, product wiki, or integrated tool) where patterns are stored and versioned.<\/li>\n<li><strong>Pattern Catalog with Metadata<\/strong>: Tag each pattern with areas like \u00ab\u00a0security,\u00a0\u00bb \u00ab\u00a0compliance,\u00a0\u00bb \u00ab\u00a0UI,\u00a0\u00bb \u00ab\u00a0admin,\u00a0\u00bb and \u00ab\u00a0multi-tenant.\u00a0\u00bb<\/li>\n<li><strong>Story Refinement with Reuse in Mind<\/strong>: During backlog refinement, teams should ask: \u201cCan this story be derived from a known pattern?\u201d<\/li>\n<li><strong>Team Training and Onboarding<\/strong>: New team members learn not just how to write stories but how to find and use existing patterns.<\/li>\n<li><strong>Feedback Loop for Improvement<\/strong>: If a pattern is used in multiple products and fails, it\u2019s updated across the board.<\/li>\n<\/ul>\n<h3>Trade-offs to Consider<\/h3>\n<ul>\n<li><strong>Over-Abstraction Risk<\/strong>: Don\u2019t create patterns that are too generic. They become hard to customize and lose value.<\/li>\n<li><strong>Stagnation<\/strong>: Patterns must be reviewed regularly. A pattern used for 5 years without updates becomes outdated.<\/li>\n<li><strong>Overhead vs. Benefit<\/strong>: Not every story needs to be a pattern. Focus on high-frequency, high-impact ones.<\/li>\n<\/ul>\n<h2>Comparison: Reusable Patterns vs. Manual Copy-Paste<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Factor<\/th>\n<th>Copy-Paste<\/th>\n<th>Reusable Pattern<\/th>\n<\/tr>\n<tr>\n<td>Time to implement<\/td>\n<td>High (duplicate work)<\/td>\n<td>Low (reuse with customization)<\/td>\n<\/tr>\n<tr>\n<td>Consistency<\/td>\n<td>Low (varies per team)<\/td>\n<td>High (enforced by standard)<\/td>\n<\/tr>\n<tr>\n<td>Maintenance cost<\/td>\n<td>High (fix in multiple places)<\/td>\n<td>Low (fix in one place)<\/td>\n<\/tr>\n<tr>\n<td>Onboarding speed<\/td>\n<td>Slow<\/td>\n<td>Fast<\/td>\n<\/tr>\n<tr>\n<td>Scalability<\/td>\n<td>Poor<\/td>\n<td>Excellent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Integrating Reusable Patterns into Product Line Agile<\/h2>\n<p>At scale, reusable story patterns are not optional\u2014they\u2019re foundational.<\/p>\n<p>They support:<\/p>\n<ul>\n<li><strong>Product line agility<\/strong>: Rapid feature delivery across product lines without sacrificing quality.<\/li>\n<li><strong>Compliance consistency<\/strong>: Enforced across multiple products, reducing audit risk.<\/li>\n<li><strong>Team alignment<\/strong>: Reduces communication overhead and misunderstandings.<\/li>\n<li><strong>Enterprise-level standards<\/strong>: Makes it possible to define and enforce story quality at scale.<\/li>\n<\/ul>\n<p>Most importantly, they embody the principle: <em>Don\u2019t write stories from scratch\u2014reuse what already works.<\/em><\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know when a story pattern is ready to be shared?<\/h3>\n<p>Only share patterns that have been used successfully across at least two products or teams. They should have passed acceptance testing and demonstrated stability during deployment. A formal review by a story quality board or architecture committee helps ensure maturity.<\/p>\n<h3>Can reusable user story patterns be modified per product?<\/h3>\n<p>Yes\u2014but with a rule: modifications must be documented and approved. The core pattern remains intact. For example, changing the authentication method or audit log location is acceptable. Replacing the entire acceptance logic is not.<\/p>\n<h3>What if teams in different product lines have different standards?<\/h3>\n<p>Start with a shared baseline. Use the pattern as a common starting point, then allow local customization through configurable variables. The goal is alignment, not uniformity. The pattern ensures you\u2019re all speaking the same language.<\/p>\n<h3>How do I avoid creating too many patterns?<\/h3>\n<p>Apply the \u201c12-week rule.\u201d A pattern must be used at least 3 times within 12 weeks before it\u2019s formally added to the library. This filters noise and focuses on real reuse.<\/p>\n<h3>How does this integrate with SAFe or LeSS?<\/h3>\n<p>Reusable patterns fit naturally into SAFe\u2019s \u201cProgram Increment\u201d planning, where features are broken into stories. The pattern becomes a pre-validated story component. In LeSS, they align with the \u201cshared product backlog\u201d and \u201cfeature-driven development\u201d model.<\/p>\n<h3>Are reusable patterns a form of automation?<\/h3>\n<p>No, but they\u2019re a foundation for automation. Once a pattern is stable, you can automate acceptance tests based on its criteria. This ensures every reuse of the pattern maintains quality.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Here\u2019s the truth that changes everything: the most efficient way to scale agile isn\u2019t by duplicating work across teams\u2014it\u2019s by creating reusable story patterns that evolve with your product line. I\u2019ve seen teams waste months rewriting the same story logic across similar products. The breakthrough came when we stopped treating stories as isolated units and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1792,"menu_order":5,"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-1798","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>Reusable User Story Patterns for Product Families<\/title>\n<meta name=\"description\" content=\"Discover how to create reusable user story patterns for product families to enable multi-product reuse, streamline development, and maintain consistency at scale in enterprise agile environments.\" \/>\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\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Reusable User Story Patterns for Product Families\" \/>\n<meta property=\"og:description\" content=\"Discover how to create reusable user story patterns for product families to enable multi-product reuse, streamline development, and maintain consistency at scale in enterprise agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/\",\"name\":\"Reusable User Story Patterns for Product Families\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:46:09+00:00\",\"description\":\"Discover how to create reusable user story patterns for product families to enable multi-product reuse, streamline development, and maintain consistency at scale in enterprise agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Advanced Story Patterns for Enterprises\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Reusable Story Patterns for Product Families\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Reusable User Story Patterns for Product Families","description":"Discover how to create reusable user story patterns for product families to enable multi-product reuse, streamline development, and maintain consistency at scale in enterprise agile environments.","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\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/","og_locale":"fr_FR","og_type":"article","og_title":"Reusable User Story Patterns for Product Families","og_description":"Discover how to create reusable user story patterns for product families to enable multi-product reuse, streamline development, and maintain consistency at scale in enterprise agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/","name":"Reusable User Story Patterns for Product Families","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:46:09+00:00","description":"Discover how to create reusable user story patterns for product families to enable multi-product reuse, streamline development, and maintain consistency at scale in enterprise agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/reusable-user-story-patterns-product-families\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Advanced Story Patterns for Enterprises","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/"},{"@type":"ListItem","position":4,"name":"Reusable Story Patterns for Product Families"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1798","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1798\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1792"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=1798"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=1798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}