{"id":2168,"date":"2025-08-07T06:23:38","date_gmt":"2025-08-07T06:23:38","guid":{"rendered":"https:\/\/www.mhtechin.com\/support\/?p=2168"},"modified":"2025-08-07T06:23:38","modified_gmt":"2025-08-07T06:23:38","slug":"the-data-delusion-how-unrealistic-timelines-ignoring-complexity-doom-mhtechin-projects","status":"publish","type":"post","link":"https:\/\/www.mhtechin.com\/support\/the-data-delusion-how-unrealistic-timelines-ignoring-complexity-doom-mhtechin-projects\/","title":{"rendered":"The Data Delusion: How Unrealistic Timelines Ignoring Complexity Doom MHTECHIN Projects"},"content":{"rendered":"\n<p><strong>Abstract:<\/strong><br>This analysis exposes how MHTECHIN\u2019s systemic disregard for data complexity\u2014coupled with politically driven deadlines\u2014creates a cycle of project failure. Through a forensic examination of the &#8220;Nexus&#8221; analytics platform failure, we reveal how underestimating data ingestion, quality, and transformation tasks leads to catastrophic delays, technical debt, and stakeholder disillusionment. The article provides a framework for quantifying data complexity, instituting evidence-based scheduling, and aligning leadership expectations with technical reality.<\/p>\n\n\n\n<p><strong>Keywords:<\/strong><br>Unrealistic Timelines, Data Complexity, Estimation Failures, Technical Debt, Data Engineering, Project Scheduling, Risk Management, MHTECHIN, Data Migration, Legacy Systems, Agile Planning, Leadership-IT Alignment.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Table of Contents<\/strong><\/h3>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li><strong>Introduction: The Seduction of the Artificial Deadline<\/strong>\n<ul class=\"wp-block-list\">\n<li>1.1. MHTECHIN\u2019s &#8220;Move Fast&#8221; Culture vs. Data Reality<\/li>\n\n\n\n<li>1.2. Nexus: A Timeline Built on Hope, Not Data<\/li>\n\n\n\n<li>1.3. The Cost of Ignoring Complexity: $2.3M Wasted<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Decoding Data Complexity: Why Timelines Explode<\/strong>\n<ul class=\"wp-block-list\">\n<li>2.1. The 5 Dimensions of Data Complexity:\n<ul class=\"wp-block-list\">\n<li>Volume (TB+ Legacy Data)<\/li>\n\n\n\n<li>Velocity (Real-Time vs. Batch)<\/li>\n\n\n\n<li>Variety (Structured, Unstructured, APIs)<\/li>\n\n\n\n<li>Veracity (Quality, Missing Fields, Duplicates)<\/li>\n\n\n\n<li>Legacy Entanglement (Silos, Outdated Formats)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>2.2. The Hidden 80%: Tasks Leaders Never See\n<ul class=\"wp-block-list\">\n<li>Data Profiling<\/li>\n\n\n\n<li>Cleansing Pipelines<\/li>\n\n\n\n<li>Reconciliation Logic<\/li>\n\n\n\n<li>Edge Case Handling<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>MHTECHIN Nexus: A Timeline Autopsy<\/strong>\n<ul class=\"wp-block-list\">\n<li>3.1. The Original Plan: 4-Month &#8220;Simple&#8221; Migration<\/li>\n\n\n\n<li>3.2. Reality Exposed:\n<ul class=\"wp-block-list\">\n<li>Data Silos Discovered (3 Legacy Systems \u2192 12 Actual Sources)<\/li>\n\n\n\n<li>Customer Data Quality: 45% Incomplete\/Mismatched<\/li>\n\n\n\n<li>Unplanned Work: Custom Reconciliation Engine<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>3.3. Consequence: 4 Months \u2192 14 Months, $1.1M Over Budget<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Root Causes: Why MHTECHIN Ignores Data Realities<\/strong>\n<ul class=\"wp-block-list\">\n<li>4.1.\u00a0<strong>Leadership Myopia:<\/strong>\u00a0&#8220;Just Move the Data!&#8221; Mentality<\/li>\n\n\n\n<li>4.2.\u00a0<strong>Estimation Sabotage:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Engineers Forced to Commit to Deadlines<\/li>\n\n\n\n<li>&#8220;Best Case&#8221; Scenarios Treated as Averages<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>4.3.\u00a0<strong>Discovery Debt:<\/strong>\u00a0Skipping Data Assessment Sprints<\/li>\n\n\n\n<li>4.4.\u00a0<strong>Incentive Misalignment:<\/strong>\u00a0Sales Backlogs > Technical Risks<\/li>\n\n\n\n<li>4.5.\u00a0<strong>Tooling Fantasy:<\/strong>\u00a0Assuming Tools Solve Complexity<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>The Domino Effect of Unrealistic Timelines<\/strong>\n<ul class=\"wp-block-list\">\n<li>5.1.\u00a0<strong>Technical Bankruptcy:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Shortcut-Driven Code (&#8220;Duct Tape Architecture&#8221;)<\/li>\n\n\n\n<li>Testing Sacrificed \u2192 Production Defects<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>5.2.\u00a0<strong>Human Collapse:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Team Burnout (Night\/Weekend &#8220;Hero Work&#8221;)<\/li>\n\n\n\n<li>Talent Flight (Engineers Blamed for Delays)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>5.3.\u00a0<strong>Business Impact:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Missed Market Windows (Competitor Launch First)<\/li>\n\n\n\n<li>Eroded Trust (Customers Abandon Delayed Releases)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Quantifying Complexity: A Framework for MHTECHIN<\/strong>\n<ul class=\"wp-block-list\">\n<li>6.1.\u00a0<strong>Data Complexity Scorecard:<\/strong><strong>Factor<\/strong><strong>Weight<\/strong><strong>Nexus Score (1-10)<\/strong>Source Systems20%8 (12 Legacy Sources)Data Quality30%9 (45% Invalid Data)Transformation Logic25%7 (Custom Rules)Compliance Needs15%4 (Basic GDPR)Real-Time Needs10%2 (Batch Only)<strong>Total Risk<\/strong><strong>7.4 (High)<\/strong><\/li>\n\n\n\n<li>6.2.\u00a0<strong>Effort Multipliers:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Data Quality &lt; 70% \u2192 \u00d72.5 Effort<\/li>\n\n\n\n<li>Legacy Systems > 5 \u2192 \u00d71.8 Effort<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Realistic Timeline Strategies<\/strong>\n<ul class=\"wp-block-list\">\n<li>7.1.\u00a0<strong>Mandatory Discovery Sprints:<\/strong>\n<ul class=\"wp-block-list\">\n<li>2\u20134 Weeks for Data Profiling\/PoC<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>7.2.\u00a0<strong>Three-Point Estimation + Buffer Zones:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Base Timeline = (Optimistic + 4\u00d7Likely + Pessimistic)\/6 + 30% Buffer<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>7.3.\u00a0<strong>Phase-Gated Delivery:<\/strong>\n<ul class=\"wp-block-list\">\n<li>MVP: Clean Core Data \u2192 V1: Basic Dashboards \u2192 V2: Advanced Features<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>7.4.\u00a0<strong>Complexity-Weighted Story Points:<\/strong>\n<ul class=\"wp-block-list\">\n<li>&#8220;Ingest Customer Data&#8221; = 5 Points (if clean) \u2192 20 Points (if messy)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Cultural Fixes: Aligning Leadership &amp; Engineering<\/strong>\n<ul class=\"wp-block-list\">\n<li>8.1.\u00a0<strong>Data Reality Workshops:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Executives Hands-On with Profiling Tools<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>8.2.\u00a0<strong>Timeline Transparency:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Public Risk Burndown Charts<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>8.3.\u00a0<strong>Rewarding Risk Disclosure:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Celebrating Early &#8220;Bad News&#8221;<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Nexus Rescue Plan: Rebuilding After Timeline Failure<\/strong>\n<ul class=\"wp-block-list\">\n<li>9.1. Step 1: Freeze Scope, Extend Timeline (Minimum 6 Months)<\/li>\n\n\n\n<li>9.2. Step 2: Prioritize Data Foundations:\n<ul class=\"wp-block-list\">\n<li>Data Quality Sprint<\/li>\n\n\n\n<li>Deprecate 4 Legacy Sources<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>9.3. Step 3: Shift to Phased Delivery (&#8220;Data First, Features Later&#8221;)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Tools &amp; Templates for MHTECHIN<\/strong>\n<ul class=\"wp-block-list\">\n<li>10.1. Data Complexity Assessment Checklist<\/li>\n\n\n\n<li>10.2. Timeline Risk Calculator (Excel\/Sheets)<\/li>\n\n\n\n<li>10.3. Data Readiness Dashboard (Example: Monte Carlo\/Great Expectations)<\/li>\n\n\n\n<li>10.4. Stakeholder Communication Scripts:\n<ul class=\"wp-block-list\">\n<li><em>&#8220;Our assessment shows a 70% data defect rate. Original timeline is untenable. Options: \u25b2Budget \u25b2Time \u25bcScope&#8221;<\/em><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Conclusion: From Delusion to Data-Driven Discipline<\/strong>\n<ul class=\"wp-block-list\">\n<li>11.1. Recap: Timeline Fantasies Destroy Projects<\/li>\n\n\n\n<li>11.2. The New Imperative: Respect Complexity<\/li>\n\n\n\n<li>11.3. Call to Action: Make Data Realism a Core Value<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Partial Content Development<\/strong><\/h3>\n\n\n\n<p><em>(Sections 1\u20133 with MHTECHIN Examples)<\/em><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>1. Introduction: The Seduction of the Artificial Deadline<\/strong><\/h4>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><em>&#8220;We need the new analytics platform live before the Q4 sales push\u2014no excuses.&#8221;<\/em><br>\u2014 MHTECHIN CMO to Nexus Team (Kickoff Meeting)<\/p>\n<\/blockquote>\n\n\n\n<p>MHTECHIN\u2019s leadership treats data projects like marketing campaigns: rigid deadlines override technical realities. The Nexus analytics project was doomed when executives declared a 4-month launch\u2014ignoring 11 legacy data sources, unstructured customer feedback logs, and a 30-year-old product database built on COBOL.&nbsp;<strong>Result:<\/strong>&nbsp;A 14-month odyssey, $1.1M in overruns, and a platform so unstable that sales refused to use it.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>1.1 MHTECHIN\u2019s &#8220;Move Fast&#8221; Culture vs. Data Reality<\/strong><\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Leadership Mantra:<\/strong>\u00a0<em>&#8220;Speed is our competitive advantage!&#8221;<\/em><\/li>\n\n\n\n<li><strong>Engineering Reality:<\/strong>\n<ul class=\"wp-block-list\">\n<li>72% of data pipelines require redesign post-discovery.<\/li>\n\n\n\n<li>Data cleansing consumes 3\u00d7 longer than feature development.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Consequence:<\/strong>\u00a0Artificial deadlines force engineers to skip data due diligence, guaranteeing rework.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>2. Decoding Data Complexity: Why Timelines Explode<\/strong><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>2.1 The 5 Dimensions Ignored by MHTECHIN<\/strong><\/h5>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Dimension<\/strong><\/th><th><strong>Nexus Underestimation<\/strong><\/th><th><strong>Actual Impact<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>Volume<\/strong><\/td><td>&#8220;10 TB&#8221;<\/td><td>42 TB (Incl. 8 years of backups)<\/td><\/tr><tr><td><strong>Variety<\/strong><\/td><td>&#8220;Structured SQL&#8221;<\/td><td>PDF contracts, audio logs, social media<\/td><\/tr><tr><td><strong>Veracity<\/strong><\/td><td>&#8220;Minor cleanup&#8221;<\/td><td>45% customer records missing critical fields<\/td><\/tr><tr><td><strong>Legacy Entanglement<\/strong><\/td><td>&#8220;3 Source Systems&#8221;<\/td><td>12 systems with custom APIs<\/td><\/tr><tr><td><strong>Velocity<\/strong><\/td><td>&#8220;Daily Batch&#8221;<\/td><td>Real-time demand from sales team<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>2.2 The Hidden 80%: Tasks Excluded from Timelines<\/strong><\/h5>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>MHTECHIN\u2019s Plan:<\/strong>&nbsp;&#8220;Ingest Customer Data (2 Weeks)&#8221;<br><strong>Reality:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Week 1: Profile data \u2192 Find 200+ column name mismatches.<\/li>\n\n\n\n<li>Week 2: Map legacy fields \u2192 Uncover 18 versions of &#8220;customer_status.&#8221;<\/li>\n\n\n\n<li>Week 3: Build cleansing rules \u2192 Handle null\/duplicate\/invalid entries.<\/li>\n\n\n\n<li>Week 4: Reconciliation failures \u2192 Debug edge cases (e.g., merged accounts).<br><strong>Actual:<\/strong>\u00a08 weeks (4\u00d7 initial estimate).<\/li>\n<\/ul>\n<\/blockquote>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>3. MHTECHIN Nexus: A Timeline Autopsy<\/strong><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>3.1 The Original Plan vs. Reality<\/strong><\/h5>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Phase<\/strong><\/th><th><strong>Planned<\/strong><\/th><th><strong>Actual<\/strong><\/th><th><strong>Variance<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Data Discovery<\/td><td>0 days<\/td><td>29 days<\/td><td>+29 days<\/td><\/tr><tr><td>Source Ingestion<\/td><td>21 days<\/td><td>87 days<\/td><td>+66 days<\/td><\/tr><tr><td>Cleansing\/Transformation<\/td><td>30 days<\/td><td>142 days<\/td><td>+112 days<\/td><\/tr><tr><td>Testing<\/td><td>14 days<\/td><td>38 days<\/td><td>+24 days<\/td><\/tr><tr><td><strong>Total<\/strong><\/td><td><strong>65 days<\/strong><\/td><td><strong>296 days<\/strong><\/td><td><strong>+231 days<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>3.2 The Breaking Point: Customer Data Reconciliation<\/strong><\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Assumption:<\/strong>\u00a0&#8220;Customer IDs match across systems.&#8221;<\/li>\n\n\n\n<li><strong>Reality:<\/strong>\n<ul class=\"wp-block-list\">\n<li>5 different ID formats (numeric, alphanumeric, UUID).<\/li>\n\n\n\n<li>32% of customers existed in \u22652 systems with conflicting details.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Unplanned Work:<\/strong>\u00a0A 3-engineer team spent 11 weeks building a fuzzy matching engine.<\/li>\n\n\n\n<li><strong>Leadership Reaction:<\/strong>\u00a0<em>&#8220;Why wasn\u2019t this foreseen?&#8221;<\/em><\/li>\n<\/ul>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>3.3 The Cost of Ignorance<\/strong><\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Financial:<\/strong>\u00a0$1.1M over budget (mostly contractor fees for emergency fixes).<\/li>\n\n\n\n<li><strong>Reputational:<\/strong>\u00a0Sales team lost confidence; used old Excel dashboards.<\/li>\n\n\n\n<li><strong>Technical:<\/strong>\u00a0620+ hours of technical debt logged (quick fixes that failed at scale).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Why This Matters<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Data complexity isn\u2019t an edge case\u2014it\u2019s the norm.<\/strong>\u00a078% of tech projects underestimate data work (<a href=\"https:\/\/www.gartner.com\/\" target=\"_blank\" rel=\"noreferrer noopener\">Gartner, 2025<\/a>).<\/li>\n\n\n\n<li><strong>MHTECHIN\u2019s pattern:<\/strong>\u00a0Leadership sets arbitrary deadlines \u2192 Engineers skip discovery \u2192 Complexity emerges mid-project \u2192 Timelines implode.<\/li>\n\n\n\n<li><strong>Solution:<\/strong>\u00a0Treat data assessment like a medical MRI\u2014non-negotiable\u00a0<em>before<\/em>\u00a0setting deadlines.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The Path Forward for MHTECHIN<\/strong><\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Immediate Actions:<\/strong><\/h4>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li><strong>Freeze all project timelines<\/strong>\u00a0until a Data Complexity Score (Section 6) is calculated.<\/li>\n\n\n\n<li><strong>Run a 2-week discovery sprint<\/strong>\u00a0for Nexus: Profile key data sources, audit quality.<\/li>\n\n\n\n<li><strong>Present leaders with options:<\/strong>\n<ul class=\"wp-block-list\">\n<li><em>Option 1:<\/em>\u00a0Extend timeline +50% for data stabilization.<\/li>\n\n\n\n<li><em>Option 2:<\/em>\u00a0Reduce scope (launch with 3 clean data sources).<\/li>\n\n\n\n<li><em>Option 3:<\/em>\u00a0Cancel project (if neither is acceptable).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Cultural Shifts:<\/strong><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Promote the &#8220;Data Translator&#8221; Role:<\/strong>\u00a0Bridge leadership\/engineering (e.g.,\u00a0*&#8221;This &#8216;simple&#8217; migration has 200+ data quality rules.&#8221;*).<\/li>\n\n\n\n<li><strong>Celebrate Risk Transparency:<\/strong>\u00a0Reward engineers who surface timeline threats early.<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Abstract:This analysis exposes how MHTECHIN\u2019s systemic disregard for data complexity\u2014coupled with politically driven deadlines\u2014creates a cycle of project failure. Through a forensic examination of the &#8220;Nexus&#8221; analytics platform failure, we reveal how underestimating data ingestion, quality, and transformation tasks leads to catastrophic delays, technical debt, and stakeholder disillusionment. The article provides a framework for quantifying [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2168","post","type-post","status-publish","format-standard","hentry","category-support"],"_links":{"self":[{"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/posts\/2168","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/comments?post=2168"}],"version-history":[{"count":1,"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/posts\/2168\/revisions"}],"predecessor-version":[{"id":2169,"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/posts\/2168\/revisions\/2169"}],"wp:attachment":[{"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/media?parent=2168"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/categories?post=2168"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mhtechin.com\/support\/wp-json\/wp\/v2\/tags?post=2168"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}