{"id":7086,"date":"2026-01-22T08:03:00","date_gmt":"2026-01-22T08:03:00","guid":{"rendered":"https:\/\/www.jollydeck.com\/academy\/?p=7086"},"modified":"2026-02-09T22:09:49","modified_gmt":"2026-02-09T22:09:49","slug":"first-time-lms-implementation","status":"publish","type":"post","link":"https:\/\/www.jollydeck.com\/academy\/first-time-lms-implementation\/","title":{"rendered":"First-time LMS implementation"},"content":{"rendered":"\n<p>How first-time LMS implementations actually succeed<\/p>\n\n\n\n<p>This playbook describes how first-time LMS implementation is run at JollyDeck.<\/p>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Uncomfortable truth: Most first-time LMS implementations fail quietly, without a clear point of failure.<\/p>\n<\/div><\/div>\n\n\n\n<p>It is written for HR ops teams in organisations of 50\u2013250 employees, where SSO is already in place and learning must operate as a system, not a side project.<\/p>\n\n\n\n<p>The focus is execution. Ownership is explicit, sequencing is enforced, and failure modes are addressed directly. This is not a buying guide, a feature overview, or a culture manifesto. It is an operational reference designed to be followed.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">Executive summary<\/h1>\n\n\n\n<p>This playbook documents the operational model used to implement an LMS for the first time at JollyDeck.<br>It is designed for organisations of <strong>50\u2013250 employees<\/strong> where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SSO is already in place and mandatory<\/li>\n\n\n\n<li>HR operations owns people data and process cadence<\/li>\n\n\n\n<li>managers control time, prioritisation, and enforcement<\/li>\n\n\n\n<li>compliance training exists and cannot fail<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The core premise<\/strong><\/h3>\n\n\n\n<p>First-time LMS implementations do not fail because of technology.<br>They fail because <strong>ownership, identity, and manager accountability are weak or implicit<\/strong>.<\/p>\n\n\n\n<p>This playbook solves for that by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>assigning <strong>single-point ownership<\/strong> to HR ops<\/li>\n\n\n\n<li>treating <strong>SSO and identity<\/strong> as foundational, not optional<\/li>\n\n\n\n<li>using <strong>compliance training as the early anchor<\/strong> to force real behaviour<\/li>\n\n\n\n<li>engineering managers into the process via reporting and escalation<\/li>\n\n\n\n<li>defining <strong>hard stop conditions<\/strong> that prevent silent failure<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What success looks like<\/strong><\/h3>\n\n\n\n<p>Within 90 days:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>all users authenticate via SSO<\/li>\n\n\n\n<li>mandatory learning completion is predictable and visible<\/li>\n\n\n\n<li>managers act on overdue learning without manual chasing<\/li>\n\n\n\n<li>HR ops workload decreases rather than increases<\/li>\n\n\n\n<li>learning becomes an operational system, not a project<\/li>\n<\/ul>\n\n\n\n<p>This is <strong>not a culture manifesto<\/strong>.<br>It is an <strong>execution manual<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>An internal playbook for HR ops teams (the JollyDeck way)<\/strong><\/h3>\n\n\n\n<p>This guide is written for organisations implementing an LMS for the <strong>first time<\/strong>.<br>It assumes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>50\u2013250 employees<\/li>\n\n\n\n<li>an existing identity provider (Microsoft Entra ID \/ Google Workspace)<\/li>\n\n\n\n<li>SSO is mandatory<\/li>\n\n\n\n<li>HR operations owns people data and operational cadence<\/li>\n<\/ul>\n\n\n\n<p>This is <strong>not<\/strong> a buying guide.<br>This is <strong>not<\/strong> a feature overview.<\/p>\n\n\n\n<p>This is a practical implementation playbook designed to prevent the most common LMS failure modes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Who this guide is for (and who it\u2019s not)<\/strong><\/h2>\n\n\n\n<p><strong>This guide is for:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>HR ops teams<\/strong> responsible for onboarding, compliance, and people data<\/li>\n\n\n\n<li><strong>L&amp;D teams<\/strong> working inside HR ops constraints<\/li>\n\n\n\n<li><strong>internal implementation leads<\/strong> coordinating HR, IT, and managers<\/li>\n<\/ul>\n\n\n\n<p><strong>This guide is not for:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>organisations experimenting with \u201clearning culture\u201d without operational backing<\/li>\n\n\n\n<li>teams without a clear HR ops owner<\/li>\n\n\n\n<li>implementations where managers are not expected to act<\/li>\n<\/ul>\n\n\n\n<p>If those exclusions feel uncomfortable, pause the implementation. The LMS will not save you.<\/p>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>This playbook helps teams navigate inevitable internal constraints deliberately, not implicitly.<\/p>\n<\/div><\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The uncomfortable truth about first-time LMS implementations<\/strong><\/h2>\n\n\n\n<p>Most first-time LMS projects do not fail technically.<br>They fail operationally.<\/p>\n\n\n\n<p>The most common failure modes are:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>The LMS launches without real ownership<\/strong><strong><br><\/strong>HR, IT, and L&amp;D all \u201csupport\u201d it. No one runs it.<\/li>\n\n\n\n<li><strong>Managers are informed, but not operationally bound<\/strong><strong><br><\/strong>They agree it\u2019s important, then do nothing when deadlines collide.<\/li>\n\n\n\n<li><strong>Identity and user data are treated as a setup step<\/strong><strong><br><\/strong>Instead of as the backbone of automation, reporting, and trust.<\/li>\n\n\n\n<li><strong>Content perfection blocks launch<\/strong><strong><br><\/strong>Teams wait for a \u201ccomplete catalogue\u201d and ship nothing.<\/li>\n\n\n\n<li><strong>Adoption is measured too late<\/strong><strong><br><\/strong>By the time learning performance data is reviewed, behaviour is already set.<\/li>\n<\/ol>\n\n\n\n<p>This playbook exists to design these failures out.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The implementation model<\/strong><\/h2>\n\n\n\n<p>The JollyDeck implementation model is <strong>phase-based<\/strong>, with <strong>hard gates<\/strong>.<\/p>\n\n\n\n<p>Each phase has:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a single operational owner<\/li>\n\n\n\n<li>a concrete output<\/li>\n\n\n\n<li>a go \/ no-go decision<\/li>\n<\/ul>\n\n\n\n<p>You do not \u201cmove on\u201d because the calendar says so.<br>You move on because the system is ready.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The phases<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Charter and ownership<\/li>\n\n\n\n<li>Identity, SSO, and user model<\/li>\n\n\n\n<li>Minimum viable learning catalogue<\/li>\n\n\n\n<li>Manager-led pilot<\/li>\n\n\n\n<li>Launch and adoption operations<br><\/li>\n<\/ol>\n\n\n\n<p>Each phase links directly to the <strong>JollyDeck LMS implementation checklist<\/strong>, written as executable tasks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why SSO matters (and why JollyDeck treats it as foundational)<\/strong><\/h2>\n\n\n\n<p>In organisations of this size, SSO is not about convenience.<br>It is about <strong>legitimacy and adoption<\/strong>.<\/p>\n\n\n\n<p>When SSO is enforced:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>users appear automatically and correctly<\/li>\n\n\n\n<li>organisational structure is inherited, not re-created<\/li>\n\n\n\n<li>managers see their teams without manual mapping<\/li>\n\n\n\n<li>learning assignment and reporting become reliable<\/li>\n\n\n\n<li>the LMS feels like part of the company, not a tool<\/li>\n<\/ul>\n\n\n\n<p>When SSO is absent or optional:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>users trust the system far less<\/li>\n\n\n\n<li>login issues consume HR ops time<\/li>\n\n\n\n<li>managers disengage<\/li>\n\n\n\n<li>reporting becomes suspect<\/li>\n\n\n\n<li>automation breaks<\/li>\n<\/ul>\n\n\n\n<p>At JollyDeck, SSO is treated as a <strong>first-order requirement<\/strong>, not an add-on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>one identity source<\/li>\n\n\n\n<li>no parallel user databases<\/li>\n\n\n\n<li>no manual reconciliation loops<\/li>\n<\/ul>\n\n\n\n<p>If SSO is not ready, the implementation should not proceed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Ownership model (non-negotiable)<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>HR ops owns the LMS<\/strong><\/li>\n\n\n\n<li><strong>IT supports identity and security<\/strong><\/li>\n\n\n\n<li><strong>managers own completion<\/strong><\/li>\n\n\n\n<li><strong>L&amp;D supports content quality<\/strong><\/li>\n<\/ul>\n\n\n\n<p>This is not a shared responsibility model.<br>Shared responsibility is how LMSes quietly die.<\/p>\n\n\n\n<p>HR ops is the only function positioned to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>maintain people data integrity<\/li>\n\n\n\n<li>run recurring operational cycles<\/li>\n\n\n\n<li>enforce deadlines<\/li>\n\n\n\n<li>escalate when required<\/li>\n<\/ul>\n\n\n\n<p>Managers are not \u201cengaged\u201d.<br>They are <strong>instrumented<\/strong>.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><strong>JollyDeck LMS implementation checklist<\/strong><\/h1>\n\n\n\n<p>This checklist describes how LMS implementation is run at JollyDeck under normal operating conditions.<\/p>\n\n\n\n<p>In practice, not all constraints can always be satisfied at once. HR ops teams often operate within structural, political, and technical limits they do not fully control.<\/p>\n\n\n\n<p>The purpose of this checklist is not to ignore those realities, but to make trade-offs explicit. Where a task cannot be completed as written, that constraint should be recognised, recorded, and consciously accepted. Silent compromises are what cause LMS implementations to fail.<\/p>\n\n\n\n<p>If a step is skipped, it should be skipped deliberately \u2014 with a clear understanding of the risk introduced and the work deferred.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>First-time rollout (HR ops\u2013led)<\/strong><\/h2>\n\n\n\n<p>This checklist defines <strong>how LMS implementation is done at JollyDeck<\/strong>.<br>Tasks are written to be executed, not interpreted.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Phase 0: Charter and ownership<\/strong><\/h2>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>This playbook helps teams navigate inevitable internal constraints deliberately, not implicitly.<\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Owner:<\/strong> HR ops<br><strong>Timing:<\/strong> before any system setup<\/p>\n\n\n\n<p><strong>Top priority<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>define LMS scope (who is included now; who is explicitly excluded)<\/li>\n\n\n\n<li>confirm compliance training as the initial anchor use case<\/li>\n\n\n\n<li>confirm SSO as mandatory (no local credentials)<\/li>\n\n\n\n<li>assign HR ops as LMS system owner<\/li>\n\n\n\n<li>assign escalation authority to HR ops<\/li>\n<\/ul>\n\n\n\n<p><strong>Then consider<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>document manager accountability for learning completion, not promotion of the LMS<\/li>\n\n\n\n<li>secure executive sponsor backing for enforcement<\/li>\n<\/ul>\n\n\n\n<p><strong>Do not proceed if:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ownership is shared or unclear<\/li>\n\n\n\n<li>compliance is deferred<\/li>\n\n\n\n<li>managers are exempt from accountability<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Phase 1: Identity, SSO, and user model<\/strong><\/h2>\n\n\n\n<p><strong>Owner:<\/strong> HR ops (with IT support)<br><strong>Timing:<\/strong> before any content work<\/p>\n\n\n\n<p><strong>Top priority<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>designate the identity provider as the single source of truth<\/li>\n\n\n\n<li>enable SSO in JollyDeck<\/li>\n\n\n\n<li>disable password-based login<\/li>\n\n\n\n<li>import users automatically via SSO<\/li>\n\n\n\n<li>define user roles (learner, manager, admin)<\/li>\n\n\n\n<li>validate manager-to-direct-report visibility<\/li>\n<\/ul>\n\n\n\n<p><strong>Then consider<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>map departments and teams from the identity provider<\/li>\n\n\n\n<li>validate learner visibility of assigned learning<\/li>\n\n\n\n<li>test joiner flow (new user appears automatically)<\/li>\n\n\n\n<li>test mover flow (department or role change is reflected)<\/li>\n\n\n\n<li>test leaver flow (access is revoked correctly)<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Optional SSO almost always becomes permanent manual work.<\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Do not proceed if:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>users require manual creation or correction<\/li>\n\n\n\n<li>SSO can be bypassed<\/li>\n\n\n\n<li>managers cannot reliably see their teams<\/li>\n\n\n\n<li>joiners or leavers require manual intervention<\/li>\n\n\n\n<li>identity data is being fixed inside the LMS<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Phase 2: Minimum viable learning catalogue (compliance-led)<\/strong><\/h2>\n\n\n\n<p><strong>Owner:<\/strong> HR ops + L&amp;D<br><strong>Timing:<\/strong> after identity is stable<\/p>\n\n\n\n<p><strong>Top priority<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>define the mandatory compliance learning set<\/li>\n\n\n\n<li>define which roles require which compliance training<\/li>\n\n\n\n<li>create or import compliance courses into JollyDeck<\/li>\n\n\n\n<li>define completion deadlines for mandatory learning<\/li>\n\n\n\n<li>assign compliance learning by default<\/li>\n\n\n\n<li>validate completion tracking<\/li>\n\n\n\n<li>validate overdue status visibility<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Waiting for a complete catalogue is one of the most common causes of delayed launches.<\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Then consider<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>create a short \u201chow learning works here\u201d course<\/li>\n\n\n\n<li>assign onboarding learning paths (if applicable)<\/li>\n\n\n\n<li>validate learner access to assigned learning<\/li>\n\n\n\n<li>validate reporting accuracy for HR ops<\/li>\n<\/ul>\n\n\n\n<p><strong>Do not proceed if:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>mandatory learning is missing<\/li>\n\n\n\n<li>compliance roles are undefined<\/li>\n\n\n\n<li>completion cannot be reliably tracked<\/li>\n\n\n\n<li>overdue learners are not immediately visible<\/li>\n\n\n\n<li>HR ops cannot extract accurate reports without manual work<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Phase 3: Manager-led pilot<\/strong><\/h2>\n\n\n\n<p><strong>Owner:<\/strong> HR ops<br><strong>Timing:<\/strong> before organisation-wide launch<\/p>\n\n\n\n<p><strong>Top priority<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>select pilot group that includes real managers<\/li>\n\n\n\n<li>assign real compliance learning to pilot group<\/li>\n\n\n\n<li>require managers to view team progress<\/li>\n\n\n\n<li>require managers to act on at least one overdue learner<\/li>\n<\/ul>\n\n\n\n<p><strong>Then consider<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>collect friction points (login, reporting, clarity, timing)<\/li>\n\n\n\n<li>resolve blocking issues<\/li>\n\n\n\n<li>retest reporting after fixes<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Pilots that exclude managers rarely reflect real launch conditions.<\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Do not proceed if:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>managers ignore reports<\/li>\n\n\n\n<li>HR ops cannot trigger action<\/li>\n\n\n\n<li>completion stalls without manual chasing<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Phase 4: Launch and activation<\/strong><\/h2>\n\n\n\n<p><strong>Owner:<\/strong> HR ops<br><strong>Timing:<\/strong> once pilot passes<\/p>\n\n\n\n<p><strong>Top priority<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>send manager briefing (expectations and mechanics)<\/li>\n\n\n\n<li>assign organisation-wide mandatory learning<\/li>\n\n\n\n<li>activate automated reminders in JollyDeck<\/li>\n\n\n\n<li>monitor adoption daily for first 7 days<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Early monitoring has more impact than perfect launch messaging.<\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Then consider<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>send learner launch communication<\/li>\n\n\n\n<li>resolve issues immediately<\/li>\n\n\n\n<li>confirm reporting stability<\/li>\n<\/ul>\n\n\n\n<p><strong>Do not proceed if:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>reminders are disabled<\/li>\n\n\n\n<li>managers lack clarity on expectations<\/li>\n\n\n\n<li>HR ops cannot intervene decisively<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Phase 5: Adoption operations (30-60-90 days)<\/strong><\/h2>\n\n\n\n<div class=\"wp-block-group highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Adoption stabilises through routine, not one-off interventions.<\/p>\n<\/div><\/div>\n\n\n\n<p><strong>Owner:<\/strong> HR ops<br><strong>Timing:<\/strong> post-launch<\/p>\n\n\n\n<p><strong>Top priority<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>establish weekly HR ops review cadence<\/li>\n\n\n\n<li>send weekly manager progress digests<\/li>\n\n\n\n<li>escalate overdue mandatory learning<\/li>\n<\/ul>\n\n\n\n<p><strong>Then consider<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>review content usage<\/li>\n\n\n\n<li>retire unused or ineffective content<\/li>\n\n\n\n<li>adjust learning paths<\/li>\n\n\n\n<li>review reporting accuracy<\/li>\n\n\n\n<li>document operational improvements<\/li>\n<\/ul>\n\n\n\n<p><strong>Do not proceed if:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>compliance completion is unpredictable<\/li>\n\n\n\n<li>manager intervention does not occur<\/li>\n\n\n\n<li>HR ops workload increases over time<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Explicit stop conditions (pause immediately if\u2026)<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>HR ops loses control over user data<\/li>\n\n\n\n<li>SSO is bypassed<\/li>\n\n\n\n<li>managers are not held accountable<\/li>\n\n\n\n<li>compliance reporting becomes unclear<\/li>\n\n\n\n<li>manual work increases after launch<br><\/li>\n<\/ul>\n\n\n\n<p>Stopping early preserves trust.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What this checklist intentionally avoids<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>feature comparisons<\/li>\n\n\n\n<li>motivational theory<\/li>\n\n\n\n<li>culture narratives<\/li>\n<\/ul>\n\n\n\n<p>Those do not prevent failure.<br>Operational clarity does.<\/p>\n\n\n\n<div class=\"wp-block-group  highlight-special\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>Most implementation effort happens after launch, not before it.<\/p>\n<\/div><\/div>\n\n\n\n<p>Last update: January 2026<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How first-time LMS implementations actually succeed This playbook describes how first-time LMS implementation is run at JollyDeck. Uncomfortable truth: Most first-time LMS implementations fail quietly, without a clear point of failure. It is written for HR ops teams in organisations &hellip; <a href=\"https:\/\/www.jollydeck.com\/academy\/first-time-lms-implementation\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":4,"featured_media":7089,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[9,1,4],"tags":[],"class_list":["post-7086","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-uncategorized","category-whitepapers"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/posts\/7086","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/comments?post=7086"}],"version-history":[{"count":3,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/posts\/7086\/revisions"}],"predecessor-version":[{"id":7103,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/posts\/7086\/revisions\/7103"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/media\/7089"}],"wp:attachment":[{"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/media?parent=7086"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/categories?post=7086"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jollydeck.com\/academy\/wp-json\/wp\/v2\/tags?post=7086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}