{"id":1255,"date":"2026-05-23T10:21:02","date_gmt":"2026-05-23T17:21:02","guid":{"rendered":"https:\/\/www.eckmandesign.com\/blog\/?p=1255"},"modified":"2026-05-30T09:32:31","modified_gmt":"2026-05-30T16:32:31","slug":"data-quality-before-ai-automation","status":"publish","type":"post","link":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/","title":{"rendered":"Data Quality Before AI Is An Operations Problem"},"content":{"rendered":"\n

Data quality before AI decides whether automation can be trusted inside the workflow.<\/p>\n\n\n\n

AI automation does not fix unclear data ownership. It usually exposes it faster.<\/p>

Data quality before AI means agreeing on sources, definitions, required fields, review rules, and exception paths.<\/p>

A model can generate a useful output only when the workflow gives it reliable context and clear boundaries.<\/p>

The first data project is often operational, not technical: decide who owns the information and how it stays current.<\/p><\/blockquote>\n\n\n\n

Many AI automation plans start with the output. The team wants faster support replies, better lead summaries, cleaner reports, or a system that drafts the next action. Those outputs sound useful, but the system can only reason from the information it receives.<\/p>\n\n\n\n

If the CRM contains duplicate records, the knowledge base is stale, the project status means different things to different teams, and ownership fields are missing, AI will not make the workflow more reliable. The automation may simply move bad information faster.<\/p>\n\n\n\n

That is why data quality before AI<\/strong> is not a cleanup chore at the edge of the project. It is the operational foundation for any AI-assisted workflow that needs to make recommendations, draft responses, route work, or support decisions.<\/p>\n\n\n\n

Data quality before AI starts with ownership.<\/h2>\n\n\n\n

Data quality before AI starts with ownership because someone has to decide which source is trusted, which fields matter, and how the information stays current. Without ownership, cleanup becomes a one-time effort that decays as soon as the workflow gets busy.<\/p>\n\n\n\n

Ownership is not the same as access. Many people can edit a customer record, update a spreadsheet, tag a support issue, or add a note to a project. That does not mean anyone owns the definition of a qualified lead, a closed ticket, a blocked project, or a ready-for-review task.<\/p>\n\n\n\n

AI systems need those definitions because the model is often asked to interpret business context. If “priority” means urgency in one system and revenue impact in another, the automation may route the work incorrectly. If “complete” means submitted in one workflow and approved in another, a generated status summary may create false confidence.<\/p>\n\n\n\n

The International Monetary Fund’s Data Quality Assessment Framework<\/a> treats data quality as something that can be assessed across dimensions such as assurances of integrity, methodological soundness, accuracy, reliability, serviceability, and accessibility. A small business does not need a formal statistical framework to prepare for AI, but the principle applies: data quality has structure, not just cleanliness.<\/p>\n\n\n\n

The automation inherits the source system’s habits.<\/h2>\n\n\n\n

An AI-assisted workflow inherits the habits of the systems around it. If people use freeform notes as the real source of truth, the automation has to guess. If teams rely on side spreadsheets, the automation may miss the current state. If exceptions live in email, the model may never see the reason a normal rule should not apply.<\/p>\n\n\n\n

This problem often appears when businesses connect AI to a CRM, ticketing system, shared drive, or knowledge base. The technical connection may work. The retrieval may return documents. The prompt may be well written. However, the workflow still fails because the information is incomplete, contradictory, outdated, or owned by nobody.<\/p>\n\n\n\n

For example, a support automation can draft better answers when the knowledge base has current articles, clear product names, escalation rules, and review dates. The same automation becomes risky when source material includes old policies, duplicate article versions, and unresolved edge cases.<\/p>\n\n\n\n

The issue is not that AI cannot help. The issue is that the business has not decided which information the AI system should trust.<\/p>\n\n\n\n

Data quality is a workflow design issue.<\/h2>\n\n\n\n

Data quality is a workflow design issue because data becomes reliable through repeated behavior. A required field, naming rule, status definition, review cadence, or approval path only matters if the workflow makes the rule easy to follow and hard to ignore.<\/p>\n\n\n\n

Data Problem<\/th>Operational Cause<\/th>AI Automation Risk<\/th><\/tr><\/thead>
Duplicate customer records.<\/td>No clear system of record or merge process.<\/td>The model summarizes the wrong account history.<\/td><\/tr>
Missing required fields.<\/td>Intake allows work to move forward without context.<\/td>The automation asks the wrong follow-up or routes work poorly.<\/td><\/tr>
Inconsistent status values.<\/td>Teams use the same word for different workflow stages.<\/td>The system reports progress that is not real.<\/td><\/tr>
Stale source documents.<\/td>No owner or review cycle exists.<\/td>The model retrieves outdated policy or process guidance.<\/td><\/tr>
Untracked exceptions.<\/td>Edge cases live in messages and memory.<\/td>The automation treats unusual cases as routine.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The table shows why data cleanup should not be isolated from workflow design. A team can clean a spreadsheet, normalize a CRM, or rewrite a knowledge base once. However, the data will drift again unless the workflow explains how new information enters, changes, gets reviewed, and gets retired.<\/p>\n\n\n\n

That is the same reason an AI readiness audit should start with the workflow. Eckman Design covers that connection in An AI Automation Readiness Audit Should Start With the Workflow<\/a>.<\/p>\n\n\n\n

Clean data does not mean perfect data.<\/h2>\n\n\n\n

Clean data does not mean the business must stop everything until every record is perfect. A practical AI automation project needs enough data quality for the workflow’s risk level. A draft summary for human review can tolerate more uncertainty than an automation that updates a customer record, triggers billing, or sends a response without approval.<\/p>\n\n\n\n

The useful question is not “Is the data perfect?” The useful question is “What decision will the automation make or support, and what information must be reliable for that decision?” That framing turns data cleanup into a targeted readiness activity.<\/p>\n\n\n\n

A low-risk workflow might need clear labels, fresh documents, and a human approval step. A higher-risk workflow might need stricter permissions, audit trails, source ranking, field validation, and exception routing. The design should match the operational consequence of a wrong output.<\/p>\n\n\n\n

Prepare the data by preparing the operating model.<\/h2>\n\n\n\n

A practical data readiness pass should improve the operating model, not just the database. The business needs to decide which system owns each type of information, which fields are required, which records are stale, and how people will maintain the source over time.<\/p>\n\n\n\n

  1. Name the workflow the AI system will support.<\/li>
  2. Identify the source systems the workflow depends on.<\/li>
  3. Define the terms the system must interpret correctly.<\/li>
  4. List the required fields for safe routing, drafting, or decision support.<\/li>
  5. Assign owners for source quality, review cycles, and exceptions.<\/li>
  6. Decide when the AI system must ask for human review instead of proceeding.<\/li><\/ol>\n\n\n\n

    This checklist keeps the work business-focused. A team may still need technical help with integrations, cleanup scripts, validation rules, or retrieval boundaries. However, those technical steps should serve the operating model rather than replace it.<\/p>\n\n\n\n

    The same point applies when spreadsheets have quietly become the source of truth. If a spreadsheet runs the workflow, AI automation may inherit a fragile operating system. Eckman Design covers that pattern in Spreadsheets Break When They Become The Workflow<\/a>.<\/p>\n\n\n\n

    Better data makes AI less mysterious.<\/h2>\n\n\n\n

    Better data makes AI less mysterious because the workflow can explain why the system produced an output. The team can see which source was used, which fields mattered, which rules applied, and where human review entered the process. That visibility matters more than a bigger prompt.<\/p>\n\n\n\n

    When source information is owned, structured, and reviewed, AI becomes part of a working system. The model can summarize, draft, classify, or recommend, but the business still controls the boundaries. People know what the system is allowed to use, what it is allowed to change, and when it must escalate.<\/p>\n\n\n\n

    That is the practical value of data quality before AI. The work is not glamorous, but it makes automation useful, explainable, and safer to operate.<\/p>\n\n\n\n

    If your team is exploring AI automation, start by inspecting the data the workflow already depends on. Eckman Design helps teams turn messy operational data into systems that support practical AI-assisted work.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Data quality before AI is an operations problem. Clean inputs, owners, definitions, and review rules matter before any model can help the workflow safely.<\/p>\n","protected":false},"author":2,"featured_media":1263,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[58],"tags":[68,117,115,116,67,62],"class_list":["post-1255","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-automation","tag-ai-automation","tag-ai-readiness-assessment","tag-data-quality","tag-data-quality-before-ai","tag-digital-operations","tag-operational-design"],"yoast_head":"\nData Quality Before AI Automation Starts<\/title>\n<meta name=\"description\" content=\"Data quality before AI automation means fixing source systems, owners, definitions, review rules, and exception paths before models touch work.\" \/>\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\/data-quality-before-ai-automation\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Data Quality Before AI Automation Starts\" \/>\n<meta property=\"og:description\" content=\"Data quality before AI automation means fixing source systems, owners, definitions, review rules, and exception paths before models touch work.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/\" \/>\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-23T17:21:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-30T16:32:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/data-quality-before-ai-automation-featured.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t<meta property=\"og:image:height\" content=\"900\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\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=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/\"},\"author\":{\"name\":\"Chris Eckman\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cfa32ec7412d4f546a33e3a8f110ff1b\"},\"headline\":\"Data Quality Before AI Is An Operations Problem\",\"datePublished\":\"2026-05-23T17:21:02+00:00\",\"dateModified\":\"2026-05-30T16:32:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/\"},\"wordCount\":1310,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/data-quality-before-ai-automation-v2-featured.webp\",\"keywords\":[\"AI Automation\",\"AI Readiness Assessment\",\"Data Quality\",\"Data Quality Before AI\",\"Digital Operations\",\"Operational Design\"],\"articleSection\":[\"AI Automation\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/\",\"name\":\"Data Quality Before AI Automation Starts\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/data-quality-before-ai-automation-v2-featured.webp\",\"datePublished\":\"2026-05-23T17:21:02+00:00\",\"dateModified\":\"2026-05-30T16:32:31+00:00\",\"description\":\"Data quality before AI automation means fixing source systems, owners, definitions, review rules, and exception paths before models touch work.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/data-quality-before-ai-automation-v2-featured.webp\",\"contentUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/data-quality-before-ai-automation-v2-featured.webp\",\"width\":1600,\"height\":900,\"caption\":\"Data quality before AI shown as messy record cards passing through validation trays into clean workflow inputs\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/data-quality-before-ai-automation\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Quality Before AI Is An Operations Problem\"}]},{\"@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\\\/cfa32ec7412d4f546a33e3a8f110ff1b\",\"name\":\"Chris Eckman\",\"sameAs\":[\"https:\\\/\\\/www.eckmandesign.com\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Data Quality Before AI Automation Starts","description":"Data quality before AI automation means fixing source systems, owners, definitions, review rules, and exception paths before models touch work.","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\/data-quality-before-ai-automation\/","og_locale":"en_US","og_type":"article","og_title":"Data Quality Before AI Automation Starts","og_description":"Data quality before AI automation means fixing source systems, owners, definitions, review rules, and exception paths before models touch work.","og_url":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/","og_site_name":"Eckman Design","article_publisher":"https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/","article_published_time":"2026-05-23T17:21:02+00:00","article_modified_time":"2026-05-30T16:32:31+00:00","og_image":[{"width":1600,"height":900,"url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/data-quality-before-ai-automation-featured.webp","type":"image\/webp"}],"author":"Chris Eckman","twitter_card":"summary_large_image","twitter_creator":"@eckmandesign","twitter_site":"@eckmandesign","twitter_misc":{"Written by":"Chris Eckman","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#article","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/"},"author":{"name":"Chris Eckman","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/person\/cfa32ec7412d4f546a33e3a8f110ff1b"},"headline":"Data Quality Before AI Is An Operations Problem","datePublished":"2026-05-23T17:21:02+00:00","dateModified":"2026-05-30T16:32:31+00:00","mainEntityOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/"},"wordCount":1310,"commentCount":0,"publisher":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/data-quality-before-ai-automation-v2-featured.webp","keywords":["AI Automation","AI Readiness Assessment","Data Quality","Data Quality Before AI","Digital Operations","Operational Design"],"articleSection":["AI Automation"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/","url":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/","name":"Data Quality Before AI Automation Starts","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#primaryimage"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/data-quality-before-ai-automation-v2-featured.webp","datePublished":"2026-05-23T17:21:02+00:00","dateModified":"2026-05-30T16:32:31+00:00","description":"Data quality before AI automation means fixing source systems, owners, definitions, review rules, and exception paths before models touch work.","breadcrumb":{"@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#primaryimage","url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/data-quality-before-ai-automation-v2-featured.webp","contentUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/data-quality-before-ai-automation-v2-featured.webp","width":1600,"height":900,"caption":"Data quality before AI shown as messy record cards passing through validation trays into clean workflow inputs"},{"@type":"BreadcrumbList","@id":"https:\/\/www.eckmandesign.com\/blog\/data-quality-before-ai-automation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.eckmandesign.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Data Quality Before AI Is An Operations Problem"}]},{"@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\/cfa32ec7412d4f546a33e3a8f110ff1b","name":"Chris Eckman","sameAs":["https:\/\/www.eckmandesign.com\/"]}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1255","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=1255"}],"version-history":[{"count":0,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1255\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media\/1263"}],"wp:attachment":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media?parent=1255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/categories?post=1255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/tags?post=1255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}