{"id":1321,"date":"2026-02-25T10:39:43","date_gmt":"2026-02-25T10:39:43","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/"},"modified":"2026-03-02T09:22:30","modified_gmt":"2026-03-02T09:22:30","slug":"pmbok-project-closure-complete-guide","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/","title":{"rendered":"Project Closure and Lessons Learned"},"content":{"rendered":"<p>When a project\u2019s final deliverable has been accepted and all work is verified, the real work of leadership begins. That\u2019s when you step into the role of a steward \u2014 not just of the project, but of the organization\u2019s learning. I\u2019ve seen teams rush through closure only to repeat the same issues in the next project. The difference? A structured approach to closure that captures real insight.<\/p>\n<p>Project closure isn\u2019t just about signing off. It\u2019s the final checkpoint where processes, deliverables, and stakeholder alignment are formally validated. In PMBOK, this phase ensures that every piece of work meets its acceptance criteria, risks are closed, and documentation is archived for future reference.<\/p>\n<p>Through years of leading cross-functional projects, I\u2019ve found one truth: the most successful teams don\u2019t just finish \u2014 they reflect. This chapter walks you through the PMBOK project closure process, with tools, templates, and hard-earned wisdom to help you close with confidence and integrity.<\/p>\n<h2>Why PMBOK Project Closure Matters<\/h2>\n<p>Closing a project formally isn\u2019t administrative busywork. It\u2019s a strategic practice that preserves organizational memory and strengthens future delivery.<\/p>\n<p>When you skip closure, you lose the opportunity to document what went right \u2014 and what didn\u2019t. That\u2019s how teams repeat the same mistakes, even with better tools and smarter people.<\/p>\n<p>PMI\u2019s PMBOK Guide emphasizes closure as a formal process group. It\u2019s not optional. It ensures accountability, transparency, and continuity across project lifecycles.<\/p>\n<h3>The Core Objectives of PMBOK Project Closure<\/h3>\n<ul>\n<li>Verify that all deliverables meet acceptance criteria<\/li>\n<li>Obtain formal sign-off from stakeholders<\/li>\n<li>Release project resources and close contracts<\/li>\n<li>Archive project documentation for future reference<\/li>\n<li>Capture lessons learned for organizational improvement<\/li>\n<\/ul>\n<h2>Key Components of PMBOK Project Closure<\/h2>\n<h3>1. Final Deliverable Acceptance<\/h3>\n<p>Before anything else, ensure every project deliverable has been tested, approved, and accepted by the sponsor and key stakeholders.<\/p>\n<p>Use the <strong>closure report PMBOK<\/strong> to summarize acceptance status. Include any deviations from the original plan and how they were resolved.<\/p>\n<h3>2. Stakeholder Sign-Off<\/h3>\n<p>Formal sign-off is not a formality. It confirms that stakeholders acknowledge the project\u2019s completion and accept its outcomes.<\/p>\n<p>Document this with a signed acceptance form. If a stakeholder refuses sign-off, investigate the reason. It may reveal an unresolved risk or unmet expectation.<\/p>\n<h3>3. Resource Release and Contract Closure<\/h3>\n<p>Reassign team members. Close procurement contracts. Return borrowed equipment. Archive financial records.<\/p>\n<p>Failure to release resources can create bottlenecks in future projects. I once managed a program where a single team member was stuck on a closed project \u2014 delaying a new initiative by two weeks.<\/p>\n<h3>4. Documentation Archiving<\/h3>\n<p>Store all project artifacts in a centralized, searchable repository. Include:<\/p>\n<ul>\n<li>Project charter<\/li>\n<li>Work breakdown structure (WBS)<\/li>\n<li>Risk register<\/li>\n<li>Change logs<\/li>\n<li>Communication logs<\/li>\n<li>Lessons learned log<\/li>\n<\/ul>\n<p>These documents become the foundation for future project planning.<\/p>\n<h2>Lessons Learned: The Heart of PMBOK Project Closure<\/h2>\n<p>Lessons learned are not just a formality. They are the most valuable output of any project.<\/p>\n<p>When done well, they turn mistakes into mechanisms for improvement. When ignored, they become recurring obstacles.<\/p>\n<p>Every project, regardless of outcome, has lessons. The key is to capture them early, honestly, and systematically.<\/p>\n<h3>How to Conduct a Lessons Learned Session<\/h3>\n<ol>\n<li><strong>Invite the right people:<\/strong> Include core team members, sponsors, and key stakeholders who contributed to the project.<\/li>\n<li><strong>Use a structured format:<\/strong> Ask: What went well? What didn\u2019t? What would we do differently?<\/li>\n<li><strong>Focus on processes, not people:<\/strong> Avoid blame. Focus on how decisions were made and what could be improved.<\/li>\n<li><strong>Document in real time:<\/strong> Use a shared digital whiteboard or template to record insights immediately.<\/li>\n<li><strong>Follow up:<\/strong> Assign owners to implement improvements in future projects.<\/li>\n<\/ol>\n<p>One of my teams documented 17 lessons from a software delivery. In the next project, we reduced delivery delays by 30% \u2014 not because we were smarter, but because we acted on past insights.<\/p>\n<h3>Common Mistakes in Lessons Learned<\/h3>\n<ul>\n<li>Conducting the session too late \u2014 after team members have moved on<\/li>\n<li>Focusing only on problems, not successes<\/li>\n<li>Allowing the session to become a blame game<\/li>\n<li>Failing to archive or share findings<\/li>\n<\/ul>\n<p>Instead, treat it as a continuous improvement ritual \u2014 not a post-mortem.<\/p>\n<h2>Creating a Closure Report PMBOK<\/h2>\n<p>The closure report PMBOK is your project\u2019s final summary. It should be concise, data-driven, and accessible to stakeholders at all levels.<\/p>\n<p>Here\u2019s a simple template to follow:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Section<\/th>\n<th>Content<\/th>\n<\/tr>\n<tr>\n<td>Project Overview<\/td>\n<td>Name, objectives, start\/end dates, budget, team size<\/td>\n<\/tr>\n<tr>\n<td>Deliverable Status<\/td>\n<td>Completed, partially completed, or rejected \u2014 with reasons<\/td>\n<\/tr>\n<tr>\n<td>Performance Metrics<\/td>\n<td>Planned vs. actual cost, schedule, scope<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder Feedback<\/td>\n<td>Summary of acceptance and approval<\/td>\n<\/tr>\n<tr>\n<td>Lessons Learned<\/td>\n<td>Key insights from the team (include 3\u20135 bullet points)<\/td>\n<\/tr>\n<tr>\n<td>Recommendations<\/td>\n<td>For future projects, process improvements, or policy changes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use real data. Avoid vague statements like \u201cwe learned teamwork matters.\u201d Instead, say: \u201cDaily stand-ups reduced miscommunication by 40% \u2014 recommend for all future projects.\u201d<\/p>\n<h2>Integrating Lessons Learned into Organizational Practice<\/h2>\n<p>Capturing lessons is only half the battle. The real value comes when you integrate them into your organization\u2019s project culture.<\/p>\n<p>I once worked with a company that collected lessons but never reviewed them. After two years, they\u2019d lost 120 lessons \u2014 all forgotten.<\/p>\n<p>To avoid this:<\/p>\n<ul>\n<li><strong>Store lessons in a searchable database<\/strong> \u2014 accessible to all project managers<\/li>\n<li><strong>Review lessons at the start of new projects<\/strong> \u2014 include them in the initiation phase<\/li>\n<li><strong>Share them during onboarding<\/strong> \u2014 new project managers should read lessons from recent projects<\/li>\n<li><strong>Link to templates and tools<\/strong> \u2014 make improvements actionable<\/li>\n<\/ul>\n<p>When lessons are routinely referenced, you stop repeating mistakes.<\/p>\n<h2>PMBOK Project Closure Checklist<\/h2>\n<p>Use this checklist to ensure you don\u2019t miss any critical steps.<\/p>\n<ul>\n<li>\u2705 Final deliverables accepted by stakeholders<\/li>\n<li>\u2705 All change requests closed and documented<\/li>\n<li>\u2705 Contracts and procurement agreements closed<\/li>\n<li>\u2705 Team members formally released<\/li>\n<li>\u2705 All project documentation archived<\/li>\n<li>\u2705 Lessons learned session held and recorded<\/li>\n<li>\u2705 Closure report PMBOK shared with stakeholders<\/li>\n<li>\u2705 Project closed in the project management system<\/li>\n<\/ul>\n<h2>Conclusion<\/h2>\n<p>Project closure is not an ending. It\u2019s a transition \u2014 from execution to reflection, from delivery to improvement.<\/p>\n<p>By applying PMBOK project closure with discipline, you ensure that every project contributes to the organization\u2019s long-term success. The lessons learned PMBOK captures are not just records \u2014 they are investments in future performance.<\/p>\n<p>Close your project with care. Archive it with purpose. Learn from it with courage.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>When should a lessons learned session be conducted?<\/h3>\n<p>Conduct it as soon as the final deliverables are accepted \u2014 preferably within one week of project completion. Delaying weakens memory recall and reduces engagement.<\/p>\n<h3>What should be included in a PMBOK closure report?<\/h3>\n<p>Include project overview, deliverable status, performance metrics, stakeholder feedback, lessons learned, and recommendations. Keep it concise \u2014 no more than 5 pages.<\/p>\n<h3>How do I handle stakeholder resistance to sign-off?<\/h3>\n<p>Address concerns directly. If a stakeholder refuses sign-off, document the reason and escalate to a sponsor or governance board. Never assume acceptance.<\/p>\n<h3>Can a project be closed without a lessons learned session?<\/h3>\n<p>Technically yes, but it\u2019s a violation of PMBOK best practices. Lessons learned are part of the closure process. Skipping them undermines organizational learning.<\/p>\n<h3>Who should lead a lessons learned session?<\/h3>\n<p>Any experienced team member or project manager can lead it. The key is to remain neutral, facilitate open dialogue, and focus on processes, not people.<\/p>\n<h3>How often should lessons learned be reviewed in an organization?<\/h3>\n<p>Review them at the start of every new project. Also, conduct an annual audit of all captured lessons to identify recurring themes and update templates or guidelines.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a project\u2019s final deliverable has been accepted and all work is verified, the real work of leadership begins. That\u2019s when you step into the role of a steward \u2014 not just of the project, but of the organization\u2019s learning. I\u2019ve seen teams rush through closure only to repeat the same issues in the next [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1313,"menu_order":7,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-1321","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>PMBOK Project Closure: Complete Guide<\/title>\n<meta name=\"description\" content=\"Master PMBOK project closure with expert insights on lessons learned, closure reports, and process validation. Learn how to close projects formally and improve future performance.\" \/>\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\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PMBOK Project Closure: Complete Guide\" \/>\n<meta property=\"og:description\" content=\"Master PMBOK project closure with expert insights on lessons learned, closure reports, and process validation. Learn how to close projects formally and improve future performance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:22:30+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/\",\"name\":\"PMBOK Project Closure: Complete Guide\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:39:43+00:00\",\"dateModified\":\"2026-03-02T09:22:30+00:00\",\"description\":\"Master PMBOK project closure with expert insights on lessons learned, closure reports, and process validation. Learn how to close projects formally and improve future performance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PMBOK Essentials for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Core PMBOK Practices Explained\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Project Closure and Lessons Learned\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"PMBOK Project Closure: Complete Guide","description":"Master PMBOK project closure with expert insights on lessons learned, closure reports, and process validation. Learn how to close projects formally and improve future performance.","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\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/","og_locale":"es_ES","og_type":"article","og_title":"PMBOK Project Closure: Complete Guide","og_description":"Master PMBOK project closure with expert insights on lessons learned, closure reports, and process validation. Learn how to close projects formally and improve future performance.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","article_modified_time":"2026-03-02T09:22:30+00:00","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/","name":"PMBOK Project Closure: Complete Guide","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:39:43+00:00","dateModified":"2026-03-02T09:22:30+00:00","description":"Master PMBOK project closure with expert insights on lessons learned, closure reports, and process validation. Learn how to close projects formally and improve future performance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/pmbok-project-closure-complete-guide\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"PMBOK Essentials for Beginners","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Core PMBOK Practices Explained","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/pmbok-essentials-for-beginners\/pmbok-practices-explained\/"},{"@type":"ListItem","position":4,"name":"Project Closure and Lessons Learned"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1321","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1321\/revisions"}],"predecessor-version":[{"id":2471,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1321\/revisions\/2471"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1313"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=1321"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=1321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}