{"id":237323,"date":"2026-02-25T11:29:19","date_gmt":"2026-02-25T11:29:19","guid":{"rendered":"https:\/\/osmosys.co\/ca\/?p=237323"},"modified":"2026-02-25T11:29:22","modified_gmt":"2026-02-25T11:29:22","slug":"people-centric-modernization-change-management","status":"publish","type":"post","link":"https:\/\/osmosys.co\/ca\/people-centric-modernization-change-management\/","title":{"rendered":"People-Centric Modernization: Driving Change and Adoption Successfully"},"content":{"rendered":"<div id=\"bsf_rt_marker\"><\/div>\n<p>The best tech rollout means nothing if no one uses it.<\/p>\n\n\n\n<p>You\u2019ve probably seen both versions of the same story:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A CRM goes live. Users keep working in spreadsheets. Leadership calls it \u201cresistance.\u201d The product team calls it \u201ctraining gaps.\u201d Nobody calls it \u201cour delivery plan.\u201d<\/li>\n\n\n\n<li>Another rollout goes live. People actually switch. Managers reinforce it. Support requests drop. The new way of working becomes normal.<\/li>\n<\/ul>\n\n\n\n<p>The difference usually isn\u2019t the platform. It\u2019s change management, the work of helping people understand, adopt, and sustain the change.<\/p>\n\n\n\n<p>Prosci\u2019s research is blunt: <strong>88%<\/strong> of initiatives with excellent change management meet or exceed objectives, compared to <strong>13%<\/strong> with poor change management.<\/p>\n\n\n\n<p>This post is a practical guide to making <a href=\"https:\/\/osmosys.co\/blog\/legacy-to-cloud-application-modernization-azure\/\">modernization stick<\/a>, across Dynamics 365, Power Platform, Fabric\/data, and cloud programs, without treating adoption as an afterthought.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1) Modernization is more than technology<\/h2>\n\n\n\n<p>A common misconception: once the solution is \u201cbuilt correctly,\u201d adoption should happen automatically.<\/p>\n\n\n\n<p>In reality, even well-designed transformations struggle. McKinsey\u2019s transformation practice has repeatedly highlighted that a large share of transformations fail, with common causes including insufficient engagement and capability-building.<\/p>\n\n\n\n<p>In enterprise programs, the \u201chard\u201d work isn\u2019t only data migration, integrations, or security. It\u2019s also:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Role changes:<\/strong> new handoffs, new responsibilities, new approvals<\/li>\n\n\n\n<li><strong>Identity changes:<\/strong> \u201cthis is how I\u2019ve always done it\u201d<\/li>\n\n\n\n<li><strong>Incentive conflicts:<\/strong> teams measured on speed, not quality; output, not adoption<\/li>\n\n\n\n<li><strong>Unspoken fears:<\/strong> loss of control, visibility, or autonomy<\/li>\n<\/ul>\n\n\n\n<p>A people-centric plan treats those as delivery requirements, not as \u201csoft\u201d concerns to handle later.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2) What \u201cpeople-centric\u201d actually looks like<\/h2>\n\n\n\n<p>People-centric modernization doesn\u2019t mean making everything optional.<\/p>\n\n\n\n<p>It means you design the rollout around human behavior:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Clarity:<\/strong> what changes, for whom, and why<\/li>\n\n\n\n<li><strong>Confidence:<\/strong> \u201cI know how to do my job in the new system\u201d<\/li>\n\n\n\n<li><strong>Commitment:<\/strong> leaders reinforce the change consistently<\/li>\n\n\n\n<li><strong>Control:<\/strong> users can give feedback and see it acted on<\/li>\n<\/ul>\n\n\n\n<p>If you\u2019re implementing Dynamics 365, Power Platform, or a new data platform, user trust and habits matter as much as configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3) A practical change management framework (that teams will follow)<\/h2>\n\n\n\n<p>Here\u2019s the model we recommend for modernization programs (simple enough to run, structured enough to scale):<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Define the \u201cwhy\u201d in business language<\/h3>\n\n\n\n<p>Avoid generic messaging like \u201cdigital transformation.\u201d<\/p>\n\n\n\n<p>Use a sentence that connects to daily work:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cWe\u2019re reducing duplicate data entry between Sales and Finance.\u201d<\/li>\n\n\n\n<li>\u201cWe\u2019re cutting time to answer customer queries by keeping context in one place.\u201d<\/li>\n\n\n\n<li>\u201cWe\u2019re moving reporting from manual reconciliation to governed, reusable datasets.\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Map the impact by role (not by department)<\/h3>\n\n\n\n<p>Create a one-page <strong>role impact map<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What they do today<\/li>\n\n\n\n<li>What changes in the new world<\/li>\n\n\n\n<li>What stays the same<\/li>\n\n\n\n<li>What support they\u2019ll get<\/li>\n\n\n\n<li>What success looks like<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Choose adoption moments (not just training dates)<\/h3>\n\n\n\n<p>Most adoption plans fail because they confuse <strong>training completion<\/strong> with <strong>behavior change<\/strong>.<\/p>\n\n\n\n<p>Define the real moments that matter:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>First time a sales rep logs an opportunity end-to-end<\/li>\n\n\n\n<li>First time a supervisor approves a workflow inside Teams<\/li>\n\n\n\n<li>First time a nurse manager pulls a dashboard without asking an analyst<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Enable managers, not just end users<\/h3>\n\n\n\n<p>Managers are the enforcement layer.<\/p>\n\n\n\n<p>Equip them with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Talk track (what to reinforce and why)<\/li>\n\n\n\n<li>\u201cWhat good looks like\u201d checklist<\/li>\n\n\n\n<li>A small dashboard of adoption indicators (more on this later)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Build feedback loops into the rollout<\/h3>\n\n\n\n<p>Adoption improves when people feel heard.<\/p>\n\n\n\n<p>Set up:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Office hours<\/li>\n\n\n\n<li>A single intake channel for friction points<\/li>\n\n\n\n<li>A cadence for changes (weekly\/bi-weekly)<\/li>\n\n\n\n<li>A \u201cwhat we fixed\u201d changelog<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Reinforce and sustain<\/h3>\n\n\n\n<p>Your go-live isn\u2019t the end. It\u2019s the start of habit formation.<\/p>\n\n\n\n<p>Plan for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>30\/60\/90-day reinforcement nudges<\/li>\n\n\n\n<li>Refresher sessions<\/li>\n\n\n\n<li>Peer-sharing sessions (\u201chow I use this in real life\u201d)<\/li>\n\n\n\n<li>Recognition for teams who adopt well<\/li>\n<\/ul>\n\n\n\n<p>Prosci\u2019s research consistently shows better outcomes when the people side is managed intentionally, including being <strong>approximately seven times more likely<\/strong> to meet objectives versus poor change management.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/02\/2-3.png\" alt=\"Adoption dashboard snapshot highlighting weekly active users, workflow completion rate, feature usage, training-to-usage gap, helpdesk themes, and user satisfaction pulse.\" class=\"wp-image-239706 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">4) The champion model: your adoption multiplier<\/h2>\n\n\n\n<p>Champions are not \u201cpower users.\u201d They\u2019re translators.<\/p>\n\n\n\n<p>They help turn a system into a working habit by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>demonstrating real scenarios<\/li>\n\n\n\n<li>collecting friction points<\/li>\n\n\n\n<li>encouraging peers who hesitate<\/li>\n\n\n\n<li>preventing workaround culture<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What a strong champion network looks like<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>One champion per function or site (for multi-location orgs)<\/li>\n\n\n\n<li>Weekly 20-minute sync during rollout<\/li>\n\n\n\n<li>A clear escalation path to the product\/team<\/li>\n\n\n\n<li>Recognition from leadership (small, consistent)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Healthcare example (industry illustration, 30%)<\/h3>\n\n\n\n<p>Imagine a Canadian healthcare provider implementing a new data platform for clinical ops reporting.<\/p>\n\n\n\n<p>They appointed \u201cdata champions\u201d in each department:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Patient operations<\/li>\n\n\n\n<li>Nursing leadership<\/li>\n\n\n\n<li>Finance<\/li>\n\n\n\n<li>Compliance<\/li>\n<\/ul>\n\n\n\n<p>Instead of one massive training, they:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ran scenario-based workshops (\u201chow to answer these 5 questions faster\u201d)<\/li>\n\n\n\n<li>piloted with two departments first<\/li>\n\n\n\n<li>published a simple \u201creport glossary\u201d (shared definitions)<\/li>\n\n\n\n<li>opened weekly office hours for the first 8 weeks<\/li>\n<\/ul>\n\n\n\n<p>Result: adoption didn\u2019t rely on one analytics team. It became distributed, so new habits actually formed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5) How a Center of Excellence supports adoption (without creating bureaucracy)<\/h2>\n\n\n\n<p>A Center of Excellence (CoE) can help adoption, especially for Power Platform, Copilot Studio, and citizen development, when it focuses on enablement plus guardrails.<\/p>\n\n\n\n<p>Microsoft\u2019s <strong>Power Platform CoE Starter Kit<\/strong> is specifically designed to help organizations build governance, monitoring, and adoption capabilities using Power Platform\u2019s native tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What the CoE should do (adoption-first)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>publish \u201chow we build here\u201d standards (naming, environments, approvals)<\/li>\n\n\n\n<li>offer templates (apps, flows, dashboards)<\/li>\n\n\n\n<li>run office hours and clinics<\/li>\n\n\n\n<li>monitor adoption and risk indicators<\/li>\n\n\n\n<li>keep leadership informed with clear reporting<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What the CoE should avoid<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>turning into a gatekeeper for every small request<\/li>\n\n\n\n<li>creating policy documents nobody reads<\/li>\n\n\n\n<li>measuring success only by number of apps built<\/li>\n<\/ul>\n\n\n\n<p>If your CoE is helping people ship useful solutions safely, it\u2019s working. If it\u2019s slowing everyone down, it needs redesign.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6) Adoption metrics that actually tell you the truth<\/h2>\n\n\n\n<p>If you can\u2019t measure adoption, you can\u2019t manage it.<\/p>\n\n\n\n<p>Here are metrics that typically correlate with real usage (choose 6\u20138 that fit your environment):<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Behavior metrics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Active users (weekly), by role<\/li>\n\n\n\n<li>Core workflow completion rate (e.g., lead \u2192 opportunity \u2192 quote)<\/li>\n\n\n\n<li>Feature usage (top 5 critical features)<\/li>\n\n\n\n<li>Workarounds count (how often people export to Excel or use shadow tools)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Confidence metrics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Training-to-usage gap (trained users vs active users)<\/li>\n\n\n\n<li>\u201cTime-to-first-value\u201d (how quickly new users complete a real task)<\/li>\n\n\n\n<li>Helpdesk themes (volume + type; are they \u201chow do I\u201d or \u201cit\u2019s broken\u201d?)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Sentiment metrics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>User satisfaction pulse (3-question survey)<\/li>\n\n\n\n<li>Manager confidence score (\u201cmy team can operate in the new process\u201d)<\/li>\n<\/ul>\n\n\n\n<p>Keep metrics role-specific. A finance user\u2019s adoption signal isn\u2019t the same as a sales user\u2019s.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7) Course-correction tactics when adoption stalls<\/h2>\n\n\n\n<p>When adoption dips, don\u2019t assume people are lazy.<\/p>\n\n\n\n<p>Assume the rollout has friction.<\/p>\n\n\n\n<p>Try these fixes in order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Remove the top 3 points of friction<\/strong><br>Identify the most common blockers and fix them quickly (navigation, missing fields, slow load, unclear permissions).<\/li>\n\n\n\n<li><strong>Switch training from \u201cfeatures\u201d to \u201cscenarios\u201d<\/strong><br>People adopt tasks, not menus.<\/li>\n\n\n\n<li><strong>Use manager reinforcement<\/strong><br>Ask managers to review one workflow artifact weekly (e.g., opportunity notes, case closure quality).<\/li>\n\n\n\n<li><strong>Publish \u201chow we do this now\u201d one-pagers<\/strong><br>Short, role-based guides beat long documentation.<\/li>\n\n\n\n<li><strong>Run a 2-week adoption sprint<\/strong><br>Treat adoption like product work: backlog, prioritization, weekly release of fixes, and clear reporting.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">8) Region lens: ANZ, US, and Canada<\/h2>\n\n\n\n<p>The human question is the same everywhere:<br>\u201cWhat\u2019s in it for me?\u201d<\/p>\n\n\n\n<p>But the context changes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ANZ:<\/strong> distributed operations and site-based work often need local champions and clear manager reinforcement.<\/li>\n\n\n\n<li><strong>Canada:<\/strong> bilingual teams or regionally distributed orgs benefit from consistent definitions, repeatable training, and role-based documentation.<\/li>\n\n\n\n<li><strong>US:<\/strong> scale and change fatigue are common; adoption plans must be practical, time-bound, and measurable.<\/li>\n<\/ul>\n\n\n\n<p>If your program spans regions, \u201cone message\u201d isn\u2019t enough. Keep the core narrative consistent, but localize examples, champions, and enablement.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9) Downloadable asset: Change Management Playbook (one-page template)<\/h2>\n\n\n\n<p>Use this as a copy\/paste one-pager (turn into a PDF for your rollout pack).<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/02\/3-7.png\" alt=\"Checklist-style change management worksheet showing rollout steps, training plan, manager reinforcement actions, and a 30\/60\/90-day adoption cadence.\" class=\"wp-image-239713 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/02\/4-3.png\" alt=\"\" class=\"wp-image-239714 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p>If you want modernization to pay off, treat <strong>change management<\/strong> as part of delivery, not as a rollout email and a training calendar.<\/p>\n\n\n\n<p>The organizations that win don\u2019t just \u201cimplement Microsoft.\u201d They help people adopt it, role by role, habit by habit, using champions, clear reinforcement, and measurable feedback loops.<\/p>\n\n\n\n<p><strong>Want help mapping adoption for your next rollout?<\/strong><br>Osmosys offers a <strong>Free Change Management Workshop<\/strong> where we\u2019ll help you build a role-based adoption plan (champions, enablement, metrics, and a 30\/60\/90-day reinforcement rhythm).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQs<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1771911722171\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is change management in a modernization project?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Change management is the structured approach to helping people adopt new ways of working, through communication, training, reinforcement, and feedback loops, so the new system is actually used.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1771911731739\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Why do good systems fail to get adopted?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Common reasons include unclear \u201cwhy,\u201d insufficient role-based enablement, lack of manager reinforcement, and friction in the workflow that pushes people back to old tools.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1771911742368\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What metrics should I track for user adoption?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Start with weekly active users, core workflow completion, feature usage for critical tasks, training-to-usage gap, helpdesk themes, and a simple user sentiment pulse.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1771911750549\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Do I need a Center of Excellence for Power Platform adoption?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Not always, but a CoE can help when citizen development grows. Microsoft\u2019s CoE Starter Kit is built to support governance, monitoring, and adoption at scale.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1771911765578\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What\u2019s a realistic timeline to see adoption improve?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Most teams see meaningful movement in 4\u20138 weeks when they combine scenario-based training, manager reinforcement, and weekly fixes to remove friction.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/osmosys.co\/book-a-demo-2\/\"><img decoding=\"async\" data-src=\"https:\/\/osmosys.co\/wp-content\/uploads\/2026\/02\/4-1.png\" alt=\"Change management with Osmosys\" class=\"wp-image-239708 lazyload\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" \/><\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>The best tech rollout means nothing if no one uses it. You\u2019ve probably seen both versions of the same story: The difference usually isn\u2019t the platform. It\u2019s change management, the work of helping people understand, adopt, and sustain the change. Prosci\u2019s research is blunt: 88% of initiatives with excellent change management meet or exceed objectives, [&hellip;]<\/p>\n","protected":false},"author":44,"featured_media":237329,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","_lmt_disableupdate":"","_lmt_disable":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[32],"tags":[22],"class_list":["post-237323","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-crm","tag-crm"],"modified_by":"mounika","jetpack_featured_media_url":"https:\/\/osmosys.co\/ca\/wp-content\/uploads\/sites\/5\/2026\/02\/1-3.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/237323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/comments?post=237323"}],"version-history":[{"count":2,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/237323\/revisions"}],"predecessor-version":[{"id":237330,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/237323\/revisions\/237330"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/media\/237329"}],"wp:attachment":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/media?parent=237323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/categories?post=237323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/tags?post=237323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}