{"id":1092,"date":"2026-05-15T23:09:17","date_gmt":"2026-05-16T06:09:17","guid":{"rendered":"https:\/\/www.eckmandesign.com\/blog\/?p=1092"},"modified":"2026-05-04T09:56:23","modified_gmt":"2026-05-04T16:56:23","slug":"technical-debt-operations-problem","status":"publish","type":"post","link":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/","title":{"rendered":"Technical Debt Is Often an Operations Problem in Disguise."},"content":{"rendered":"\n

Technical debt is usually discussed as a software problem.<\/p>\n\n\n\n

Messy code. Old plugins. Fragile integrations. Slow pages. Unmaintained systems. Workarounds that became permanent.<\/p>\n\n\n\n

Those things matter. However, technical debt is often an operations problem in disguise.<\/p>\n\n\n\n

It grows when no one owns the system, when short-term fixes never get revisited, and when business processes are not clearly designed.<\/p>\n\n\n\n

Technical Debt Usually Has a History.<\/h2>\n\n\n\n

Technical debt rarely appears all at once.<\/p>\n\n\n\n

It builds through small decisions. A plugin is added to solve one urgent issue. A spreadsheet becomes the source of truth. A manual export becomes part of the weekly workflow. A temporary page becomes permanent. A developer patches around an unclear process. A team keeps using a tool because changing it feels harder than living with it.<\/p>\n\n\n\n

Over time, the business becomes dependent on fragile systems. The debt is no longer only technical. It becomes part of how the organization operates.<\/p>\n\n\n\n

Atlassian\u2019s guide to technical debt<\/a> describes how quick delivery choices can create future rework and maintenance cost. That framing is useful, but the operational side matters too: someone has to decide when the shortcut gets cleaned up, who owns the system, and what tradeoff the business accepted.<\/p>\n\n\n\n

The Code Is Not Always the Root Problem.<\/h2>\n\n\n\n

Sometimes the technical implementation is messy because the business process behind it is messy.<\/p>\n\n\n\n

No one knows who approves the content. No one knows which data source is correct. No one knows what happens when a request is incomplete. No one knows whether a feature is still needed.<\/p>\n\n\n\n

The software reflects that uncertainty. Cleaning up the code helps, but it may not solve the deeper issue.<\/p>\n\n\n\n

The business also needs clearer ownership, rules, and workflows. Otherwise, the same confusion will return in a cleaner codebase.<\/p>\n\n\n\n

Maintenance Is a Business Decision.<\/h2>\n\n\n\n

Every digital system needs maintenance.<\/p>\n\n\n\n

Websites need updates. Integrations need monitoring. Forms need testing. Analytics need review. Accessibility needs attention. Content needs structure. Automations need adjustment.<\/p>\n\n\n\n

When maintenance is not planned, it becomes reactive. That is when small issues turn into larger problems.<\/p>\n\n\n\n

A privacy script breaks. A form stops sending. A plugin conflicts with the theme. A page slows down. An automation produces the wrong output. No one notices until it affects the business.<\/p>\n\n\n\n

Operational Clarity Reduces Technical Debt.<\/h2>\n\n\n\n

The best way to reduce technical debt is not just to rewrite everything.<\/p>\n\n\n\n

It is to clarify how the system should work.<\/p>\n\n\n\n

That means defining what the system is responsible for, who owns it, what data it depends on, what workflows it supports, what needs regular review, what can be removed, what should be documented, and what should happen when something fails.<\/p>\n\n\n\n

Clear operations make better technical decisions possible. They give developers and decision-makers a shared understanding of what the system is supposed to do.<\/p>\n\n\n

Ownership is especially important. If no one owns the system, no one has the authority to remove an old dependency, retire a plugin, simplify a form, clean up content, or decide that a workaround has outlived its purpose.<\/p>\n\n\n\n

Without that ownership, technical debt keeps accumulating because every decision feels temporary and nobody has a clear mandate to improve the system.<\/p>\n\n\n\n

AI Can Create New Technical Debt.<\/h2>\n\n\n\n

AI automation adds another layer to this problem.<\/p>\n\n\n\n

A quick AI workflow may be useful at first. However, if it is not documented, monitored, reviewed, or connected to a clear business process, it can become another fragile dependency.<\/p>\n\n\n\n

Who maintains the prompt? Who reviews the output? What data does it use? What happens when the model changes? What should the system do when confidence is low?<\/p>\n\n\n\n

AI systems need ownership too. Without it, they become technical debt with a smarter interface.<\/p>\n\n\n\n

The Goal Is a System the Business Can Live With.<\/h2>\n\n\n\n

Good software is not just about what works today.<\/p>\n\n\n\n

It is about what the business can operate, maintain, and improve over time. That requires clean implementation, but it also requires clear decisions.<\/p>\n\n\n\n

A system should have a purpose. It should have an owner. It should be documented enough that another person can understand it. It should be reviewed before it becomes a liability.<\/p>\n\n\n\n

This is where Eckman Design\u2019s work on software systems and digital operations<\/a> connects strategy to implementation. The goal is not just to build something that launches. The goal is to build something the business can keep using without creating avoidable drag.<\/p>\n\n\n\n

Fix the Process While Fixing the System.<\/h2>\n\n\n\n

When technical debt appears, do not only ask what needs to be rebuilt.<\/p>\n\n\n\n

Ask why it became debt in the first place. Was the process unclear? Was ownership missing? Was the tool chosen too quickly? Was maintenance ignored? Did a temporary workaround become permanent?<\/p>\n\n\n\n

Those answers matter because they help the business avoid rebuilding the same problem in a newer tool.<\/p>\n\n\n\n

Eckman Design helps businesses clean up digital systems, clarify workflows, and build software that is easier to maintain.<\/p>\n","protected":false},"excerpt":{"rendered":"

Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.<\/p>\n","protected":false},"author":2,"featured_media":1091,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_focuskw":"","_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","footnotes":""},"categories":[71],"tags":[67,62,73,74,72],"class_list":["post-1092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-systems","tag-digital-operations","tag-operational-design","tag-software-maintenance","tag-software-systems","tag-technical-debt"],"yoast_head":"\nTechnical Debt Is Often an Operations Problem in Disguise. - Eckman Design<\/title>\n<meta name=\"description\" content=\"Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Technical Debt Is Often an Operations Problem in Disguise. - Eckman Design\" \/>\n<meta property=\"og:description\" content=\"Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/\" \/>\n<meta property=\"og:site_name\" content=\"Eckman Design\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-16T06:09:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/technical-debt-operations-problem-featured.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1536\" \/>\n\t<meta property=\"og:image:height\" content=\"864\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Chris Eckman\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@eckmandesign\" \/>\n<meta name=\"twitter:site\" content=\"@eckmandesign\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Chris Eckman\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/\"},\"author\":{\"name\":\"Chris Eckman\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/57dccfe49e17142828d059d468e60510\"},\"headline\":\"Technical Debt Is Often an Operations Problem in Disguise.\",\"datePublished\":\"2026-05-16T06:09:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/\"},\"wordCount\":820,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/technical-debt-operations-problem-featured.jpg\",\"keywords\":[\"Digital Operations\",\"Operational Design\",\"Software Maintenance\",\"Software Systems\",\"Technical Debt\"],\"articleSection\":[\"Software Systems\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/\",\"name\":\"Technical Debt Is Often an Operations Problem in Disguise. - Eckman Design\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/technical-debt-operations-problem-featured.jpg\",\"datePublished\":\"2026-05-16T06:09:17+00:00\",\"description\":\"Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/technical-debt-operations-problem-featured.jpg\",\"contentUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/technical-debt-operations-problem-featured.jpg\",\"width\":1536,\"height\":864,\"caption\":\"Abstract digital system showing tangled technical debt being reorganized into clearer workflows and architecture.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/technical-debt-operations-problem\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Technical Debt Is Often an Operations Problem in Disguise.\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\",\"name\":\"Eckman Design\",\"description\":\"AI Automation Software & Workflow Systems\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\",\"name\":\"Eckman Design, LLC.\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/04\\\/eckman_design_twitter_card.png\",\"contentUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/04\\\/eckman_design_twitter_card.png\",\"width\":1200,\"height\":630,\"caption\":\"Eckman Design, LLC.\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/Eckman-Design-913317988788314\\\/\",\"https:\\\/\\\/x.com\\\/eckmandesign\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/57dccfe49e17142828d059d468e60510\",\"name\":\"Chris Eckman\",\"sameAs\":[\"https:\\\/\\\/www.eckmandesign.com\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Technical Debt Is Often an Operations Problem in Disguise. - Eckman Design","description":"Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.","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:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/","og_locale":"en_US","og_type":"article","og_title":"Technical Debt Is Often an Operations Problem in Disguise. - Eckman Design","og_description":"Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.","og_url":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/","og_site_name":"Eckman Design","article_publisher":"https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/","article_published_time":"2026-05-16T06:09:17+00:00","og_image":[{"width":1536,"height":864,"url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/technical-debt-operations-problem-featured.jpg","type":"image\/jpeg"}],"author":"Chris Eckman","twitter_card":"summary_large_image","twitter_creator":"@eckmandesign","twitter_site":"@eckmandesign","twitter_misc":{"Written by":"Chris Eckman","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#article","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/"},"author":{"name":"Chris Eckman","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/person\/57dccfe49e17142828d059d468e60510"},"headline":"Technical Debt Is Often an Operations Problem in Disguise.","datePublished":"2026-05-16T06:09:17+00:00","mainEntityOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/"},"wordCount":820,"commentCount":0,"publisher":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/technical-debt-operations-problem-featured.jpg","keywords":["Digital Operations","Operational Design","Software Maintenance","Software Systems","Technical Debt"],"articleSection":["Software Systems"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/","url":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/","name":"Technical Debt Is Often an Operations Problem in Disguise. - Eckman Design","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#primaryimage"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/technical-debt-operations-problem-featured.jpg","datePublished":"2026-05-16T06:09:17+00:00","description":"Technical debt is not always caused by bad code. It often grows from unclear operations, rushed decisions, and neglected systems.","breadcrumb":{"@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#primaryimage","url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/technical-debt-operations-problem-featured.jpg","contentUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/technical-debt-operations-problem-featured.jpg","width":1536,"height":864,"caption":"Abstract digital system showing tangled technical debt being reorganized into clearer workflows and architecture."},{"@type":"BreadcrumbList","@id":"https:\/\/www.eckmandesign.com\/blog\/technical-debt-operations-problem\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.eckmandesign.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Technical Debt Is Often an Operations Problem in Disguise."}]},{"@type":"WebSite","@id":"https:\/\/www.eckmandesign.com\/blog\/#website","url":"https:\/\/www.eckmandesign.com\/blog\/","name":"Eckman Design","description":"AI Automation Software & Workflow Systems","publisher":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.eckmandesign.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.eckmandesign.com\/blog\/#organization","name":"Eckman Design, LLC.","url":"https:\/\/www.eckmandesign.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2016\/04\/eckman_design_twitter_card.png","contentUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2016\/04\/eckman_design_twitter_card.png","width":1200,"height":630,"caption":"Eckman Design, LLC."},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/","https:\/\/x.com\/eckmandesign"]},{"@type":"Person","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/person\/57dccfe49e17142828d059d468e60510","name":"Chris Eckman","sameAs":["https:\/\/www.eckmandesign.com\/"]}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1092","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/comments?post=1092"}],"version-history":[{"count":0,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1092\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media\/1091"}],"wp:attachment":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media?parent=1092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/categories?post=1092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/tags?post=1092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}