{"id":1208,"date":"2026-06-16T10:18:02","date_gmt":"2026-06-16T17:18:02","guid":{"rendered":"https:\/\/www.eckmandesign.com\/blog\/?p=1208"},"modified":"2026-06-16T10:18:02","modified_gmt":"2026-06-16T17:18:02","slug":"crm-data-quality-system-of-record","status":"publish","type":"post","link":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/","title":{"rendered":"Your CRM Is Not the System of Record If Nobody Trusts It"},"content":{"rendered":"\n

CRM data quality decides whether the CRM is actually the system of record or just another place where information gets copied after the real work happens somewhere else. A CRM can be expensive, well configured, and full of fields, but the business will route around it if people do not trust the data inside it.<\/p>\n\n\n\n

CRM data quality is an operating problem, not just an admin cleanup task.<\/p>

A CRM becomes the system of record only when teams trust the records enough to use them.<\/p>

Bad data creates bad handoffs, weak reporting, missed follow-up, and fragile automation.<\/p>

The fix starts with ownership, field discipline, lifecycle rules, and review habits.<\/p><\/blockquote>\n\n\n\n

Many companies say the CRM is the source of truth. Then sales keeps notes in personal documents. Operations asks for confirmation in Slack. Leadership exports spreadsheets before every forecast meeting. Customer success builds its own tracker because account records are incomplete.<\/p>\n\n\n\n

At that point, the CRM is not the system of record. The CRM is one more system people check, correct, and argue with.<\/p>\n\n\n\n

CRM Data Quality Is A Trust Problem<\/h2>\n\n\n\n

CRM data quality is a trust problem because people change behavior when they believe the record is unreliable. They stop entering details, stop checking fields, and stop treating reports as evidence. The system then gets worse because trust and usage decline together.<\/p>\n\n\n\n

This creates a cycle. The data is weak, so people work outside the CRM. Because people work outside the CRM, the data gets weaker. Eventually the business has a system that requires maintenance but does not guide the work.<\/p>\n\n\n\n

The UK Government Data Quality Framework<\/a> describes data quality through dimensions such as accuracy, completeness, uniqueness, consistency, timeliness, and validity. Those dimensions translate directly into CRM operations. A contact can be present but wrong, complete but duplicated, current but inconsistent, or valid but useless for the next handoff.<\/p>\n\n\n\n

The CRM Fails When Work Happens Around It<\/h2>\n\n\n\n

A CRM stops acting like a system of record when important work happens around it. The real customer state moves through inboxes, calls, spreadsheets, private notes, proposal tools, and project management systems while the CRM receives partial updates later.<\/p>\n\n\n\n

This is not always laziness. Often the CRM does not match the workflow. Fields are unclear. Required data is unavailable at the moment it is requested. Duplicate rules are weak. Pipeline stages do not reflect how deals actually move. Handoffs require context the CRM does not capture.<\/p>\n\n\n\n

The result is operational drag. Sales asks operations to verify details. Operations asks sales what was promised. Leadership asks why the forecast changed. Marketing asks which leads turned into real customers. Nobody has one reliable record.<\/p>\n\n\n\n

This is one reason internal tools can be better than another SaaS subscription<\/a>. Sometimes the problem is not the CRM vendor. The problem is the missing operating layer around the CRM.<\/p>\n\n\n\n

Bad Data Breaks Handoffs First<\/h2>\n\n\n\n

Bad CRM data usually breaks handoffs before it breaks dashboards. A team can tolerate weak reports for a while, but a bad handoff creates immediate friction. The wrong owner follows up. The wrong package gets quoted. The wrong implementation notes move downstream.<\/p>\n\n\n\n

The handoff from marketing to sales needs source, intent, qualification, and consent context. The handoff from sales to delivery needs scope, promises, timeline, decision makers, and known risks. The handoff from support to account management needs account history, urgency, and resolution status.<\/p>\n\n\n\n

When those fields are missing or unreliable, people create side channels. Those side channels may solve the immediate case, but they also weaken the CRM further. The official record no longer explains what happened.<\/p>\n\n\n\n

This pattern connects directly to the hidden cost of manual handoffs<\/a>. Data quality problems become workflow problems when the next team cannot trust what the previous team recorded.<\/p>\n\n\n\n

Automation Depends On Reliable Records<\/h2>\n\n\n\n

CRM automation depends on reliable records because automation follows the data it receives. If lifecycle stage, owner, status, company size, consent, source, or renewal date is wrong, the automated step will make the wrong move faster.<\/p>\n\n\n\n

A lead routing rule may send a valuable prospect to the wrong person. A renewal workflow may fire too late. A customer segment may include accounts that should be excluded. An AI assistant may summarize the wrong history because duplicate records split the context.<\/p>\n\n\n\n

This is why automation exception handling needs an owner<\/a>. CRM automation should know what to do when required fields are missing, records conflict, ownership is unclear, or the requested action is too risky to complete automatically.<\/p>\n\n\n\n

A Trustworthy CRM Needs Field Discipline<\/h2>\n\n\n\n

A trustworthy CRM needs field discipline, but field discipline does not mean adding more required fields. It means deciding which data is necessary, who owns it, when it should be captured, and how the business knows whether it is still valid.<\/p>\n\n\n\n

  • Accuracy:<\/strong> Does the field reflect the real customer, deal, or account state?<\/li>
  • Completeness:<\/strong> Are required fields present before the next workflow step?<\/li>
  • Uniqueness:<\/strong> Are duplicate contacts, companies, and opportunities controlled?<\/li>
  • Consistency:<\/strong> Do teams use the same definitions across sales, service, and operations?<\/li>
  • Timeliness:<\/strong> Is the record updated while the information still matters?<\/li>
  • Validity:<\/strong> Does the data fit the expected format, range, and workflow rule?<\/li><\/ul>\n\n\n\n

    The practical test is simple. If a field does not support a decision, handoff, compliance need, customer experience, or automation rule, the business should question why the field exists. If a field does support one of those outcomes, the business should decide who owns its quality.<\/p>\n\n\n\n

    Reporting Reveals Whether The CRM Is Trusted<\/h2>\n\n\n\n

    Reporting reveals whether the CRM is trusted because reporting meetings expose the gap between official data and operational belief. If every dashboard triggers a conversation about whether the numbers are real, the report is measuring distrust as much as performance.<\/p>\n\n\n\n

    A useful CRM report should create a decision. Which opportunities need attention? Which accounts are at risk? Which source produces qualified leads? Which sales stage is blocked? Which handoff creates rework?<\/p>\n\n\n\n

    If the report cannot support those decisions, the team should inspect the data path behind it. The issue may be field definitions, missing lifecycle rules, duplicate records, inconsistent ownership, or a workflow that never made the CRM part of the real process.<\/p>\n\n\n\n

    Fix The Operating Model, Not Just The Records<\/h2>\n\n\n\n

    Fixing CRM data quality starts with the operating model, not a one-time cleanup. A cleanup can remove duplicates, fill missing fields, and standardize values. However, the same problems return if the workflow keeps creating bad data.<\/p>\n\n\n\n

    Start with one high-value workflow. Map the intake, qualification, sales handoff, delivery handoff, renewal process, or support escalation. Identify the fields that determine the next step. Then define ownership, validation rules, review cadence, and exception handling.<\/p>\n\n\n\n

    • Make every required field earn its place in the workflow.<\/li>
    • Define field meanings in business language, not admin shorthand.<\/li>
    • Assign owners for account, contact, deal, and lifecycle data.<\/li>
    • Review duplicates, stale records, and missing fields on a schedule.<\/li>
    • Route exceptions to a real owner instead of hiding them in reports.<\/li><\/ul>\n\n\n\n

      A CRM earns system-of-record status when people trust it enough to use it before they create another spreadsheet. That trust comes from workflow fit, data ownership, useful reporting, and maintenance habits.<\/p>\n\n\n\n

      The goal is not a perfect database. The goal is a reliable operating record that helps teams move work, serve customers, and make decisions without rebuilding the truth every week.<\/p>\n","protected":false},"excerpt":{"rendered":"

      CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.<\/p>\n","protected":false},"author":2,"featured_media":1207,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[64],"tags":[69,95,67,62,96,66],"class_list":["post-1208","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-operations","tag-business-process","tag-crm-data-quality","tag-digital-operations","tag-operational-design","tag-sales-operations","tag-workflow-automation"],"yoast_head":"\nCRM Data Quality: When the System of Record Fails<\/title>\n<meta name=\"description\" content=\"CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.\" \/>\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\/crm-data-quality-system-of-record\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CRM Data Quality: When the System of Record Fails\" \/>\n<meta property=\"og:description\" content=\"CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/\" \/>\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-06-16T17:18:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/crm-data-quality-system-of-record-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\\\/crm-data-quality-system-of-record\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/\"},\"author\":{\"name\":\"Chris Eckman\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#\\\/schema\\\/person\\\/cfa32ec7412d4f546a33e3a8f110ff1b\"},\"headline\":\"Your CRM Is Not the System of Record If Nobody Trusts It\",\"datePublished\":\"2026-06-16T17:18:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/\"},\"wordCount\":1222,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/crm-data-quality-system-of-record-featured.webp\",\"keywords\":[\"Business Process\",\"CRM Data Quality\",\"Digital Operations\",\"Operational Design\",\"Sales Operations\",\"Workflow Automation\"],\"articleSection\":[\"Digital Operations\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/\",\"name\":\"CRM Data Quality: When the System of Record Fails\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/crm-data-quality-system-of-record-featured.webp\",\"datePublished\":\"2026-06-16T17:18:02+00:00\",\"description\":\"CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/crm-data-quality-system-of-record-featured.webp\",\"contentUrl\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/crm-data-quality-system-of-record-featured.webp\",\"width\":1600,\"height\":900,\"caption\":\"CRM data quality workflow showing duplicate records, missing fields, handoff paths, reporting, and verified customer records.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/crm-data-quality-system-of-record\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.eckmandesign.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Your CRM Is Not the System of Record If Nobody Trusts It\"}]},{\"@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":"CRM Data Quality: When the System of Record Fails","description":"CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.","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\/crm-data-quality-system-of-record\/","og_locale":"en_US","og_type":"article","og_title":"CRM Data Quality: When the System of Record Fails","og_description":"CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.","og_url":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/","og_site_name":"Eckman Design","article_publisher":"https:\/\/www.facebook.com\/Eckman-Design-913317988788314\/","article_published_time":"2026-06-16T17:18:02+00:00","og_image":[{"width":1600,"height":900,"url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/crm-data-quality-system-of-record-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\/crm-data-quality-system-of-record\/#article","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/"},"author":{"name":"Chris Eckman","@id":"https:\/\/www.eckmandesign.com\/blog\/#\/schema\/person\/cfa32ec7412d4f546a33e3a8f110ff1b"},"headline":"Your CRM Is Not the System of Record If Nobody Trusts It","datePublished":"2026-06-16T17:18:02+00:00","mainEntityOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/"},"wordCount":1222,"commentCount":0,"publisher":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/crm-data-quality-system-of-record-featured.webp","keywords":["Business Process","CRM Data Quality","Digital Operations","Operational Design","Sales Operations","Workflow Automation"],"articleSection":["Digital Operations"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/","url":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/","name":"CRM Data Quality: When the System of Record Fails","isPartOf":{"@id":"https:\/\/www.eckmandesign.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#primaryimage"},"image":{"@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#primaryimage"},"thumbnailUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/crm-data-quality-system-of-record-featured.webp","datePublished":"2026-06-16T17:18:02+00:00","description":"CRM data quality determines whether teams trust the CRM as the system of record for sales, handoffs, reporting, automation, and customer follow-through.","breadcrumb":{"@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#primaryimage","url":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/crm-data-quality-system-of-record-featured.webp","contentUrl":"https:\/\/www.eckmandesign.com\/blog\/wp-content\/uploads\/2026\/05\/crm-data-quality-system-of-record-featured.webp","width":1600,"height":900,"caption":"CRM data quality workflow showing duplicate records, missing fields, handoff paths, reporting, and verified customer records."},{"@type":"BreadcrumbList","@id":"https:\/\/www.eckmandesign.com\/blog\/crm-data-quality-system-of-record\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.eckmandesign.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Your CRM Is Not the System of Record If Nobody Trusts It"}]},{"@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\/1208","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=1208"}],"version-history":[{"count":0,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/posts\/1208\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media\/1207"}],"wp:attachment":[{"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/media?parent=1208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/categories?post=1208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eckmandesign.com\/blog\/wp-json\/wp\/v2\/tags?post=1208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}