{"id":6676,"date":"2016-09-01T17:23:55","date_gmt":"2016-09-01T17:23:55","guid":{"rendered":"https:\/\/www.gosquared.com\/blog\/?p=6676"},"modified":"2019-11-28T11:25:23","modified_gmt":"2019-11-28T11:25:23","slug":"how-bad-features-are-born","status":"publish","type":"post","link":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born","title":{"rendered":"How bad features are born"},"content":{"rendered":"<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_12.png\" alt=\"Avoid building bad features\"\/><\/p>\n<p>Building new features in your product can seem <a href=\"https:\/\/www.gosquared.com\/blog\/simplicity\">simple<\/a> at first.<\/p>\n<p>But building features that really work for your customers is an incredibly difficult process, and one that requires stepping back from the superficial. Good features come from focusing on the customer and their problem before ever touching a line of code or a pixel of the user interface.<\/p>\n<h2>How a bad feature begins its life<\/h2>\n<p>We\u2019ve seen plenty of features progress from inception for the wrong reasons. Here\u2019s a common example of how bad features get off the ground.<\/p>\n<h3>They don\u2019t start with the customer<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_01.png\" alt=\"The wrong way to get ideas for features\" \/><\/p>\n<p>Often, bad features will start from an internal discussion, rather than a genuine customer need.<\/p>\n<h3>They\u2019re perceived as being easy to implement<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_02.png\" alt=\"Features can seem easy to build at first\" \/><\/p>\n<p>Sometimes bad features seem easy to implement and on the surface they may look small and focused.<\/p>\n<h3>They\u2019re not designed thoroughly enough<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_03.png\" alt=\"Jumping into development too soon is dangerous\" \/><\/p>\n<p>It\u2019s easy to draw a screen \u2013 the screen that customers will see when this feature is working exactly the way you imagine it to. This is the most obvious piece of the design process. But good features are not born out of designing a single screen.<\/p>\n<h3>Too many compromises are made in development<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_04.png\" alt=\"Too many cooks can spoil the broth in development with a lack of design\" \/><\/p>\n<p>If there&#8217;s a lack of design and thought early on, the development of the feature inevitably suffers. Decisions that would normally come easy and naturally to the engineering team, become challenging because the high level goals and vision for the feature are not clear. <\/p>\n<h2>What are the warning signs of a bad feature?<\/h2>\n<p>Bad features cause problems because they\u2019re not thought through deeply enough. More often than not bad features start with failing to think about the \u201cJob To Be Done\u201d the customer is hiring you for.<\/p>\n<p>It is sometimes possible to build good features without extensive customer research and user testing, but it\u2019s generally more difficult. When you rely solely on your instinct and empathy for your customers, sometimes you can get it right. But chances are you won\u2019t.<\/p>\n<p>Even when you\u2019re building something with the best intentions, it\u2019s still easy to execute poorly on an idea for a feature. You can forget to design key elements of the user experience that are essential to the product feeling complete.<\/p>\n<p>The closer a feature gets to production, the easier it gets to evaluate whether it\u2019s a winner or a loser.<\/p>\n<h3>The announcement of the feature is difficult to write<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_05.png\" alt=\"A blank page is a sign that you do not know why you built the feature\" \/><\/p>\n<p>When there aren\u2019t well defined reasons for building the feature nor a clear target audience, it\u2019s hard to articulate how it could be valuable and helpful to your customer base.<\/p>\n<h3>The feature is received by customers with a mediocre response<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_06.png\" alt=\"If customers do not care is it a good feature?\" \/><\/p>\n<p>With an unclear announcement, a muddled development process, and a lack of vision for the feature, the response from customers will most likely be underwhelming. Not only in the audience reaction on social media, but in actual usage \u2013 customers don\u2019t engage with the feature and they don\u2019t see the need for it.<\/p>\n<p>When a feature wasn\u2019t built for a specific pain point your customers were experiencing, they don\u2019t find the need to use it. You\u2019ve built a feature for the wrong people, the wrong problem, and the wrong reasons.<\/p>\n<h2>How to avoid building bad features<\/h2>\n<h3>Have a clear idea of what job the customer is hiring you for<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_07.png\" alt=\"Jobs to be done helps build better features\" \/><\/p>\n<p>Most importantly, does this feature deserve to exist? Why are you working on it?<\/p>\n<p>If you\u2019re embarking on a new feature primarily because you\u2019ve seen a competitor release something similar, then you probably haven\u2019t thoroughly considered or even identified the problem you\u2019re trying to solve. If you\u2019re jumping into a new feature because it seems like \u201cit wouldn\u2019t be too hard to do\u201d that\u2019s great, but does it actually deserve to be built right now?<\/p>\n<p>We utilise the \u201cJobs To Be Done\u201d framework extensively to focus on the problems we\u2019re being hired to solve. This means we\u2019re building features that form part of a logical workflow that helps our customers. We also use <a href=\"https:\/\/www.gosquared.com\/software\/chat\/\" target=\"_blank\" rel=\"noopener noreferrer\">live chat<\/a> for continuing communication with customers \u2013 we regularly ask them questions, but often <em>they approach us<\/em> requesting changes and improvements that we\u2019re always evaluating against our own roadmap.<\/p>\n<h3>Write a simple explanation of why this feature is valuable to the customer<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_08.png\" alt=\"Write the press release first\" \/><\/p>\n<p><a href=\"http:\/\/www.allthingsdistributed.com\/2006\/11\/working_backwards.html\" target=\"_blank\" rel=\"noopener noreferrer\">Amazon<\/a> famously writes their press releases for new products before they start working on them. We\u2019ve always found this to be a helpful process to go through before embarking on building new features \u2013 write at least a few sentences to outline why customers will benefit from the work you\u2019re doing.<\/p>\n<p>Aside from helping with the product development process, writing the press release first helps with the marketing and sales when the feature finally hits production.<\/p>\n<h3>Design the screen before and the screen after<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_09.png\" alt=\"Design a flow of screens rather than just one screen\" \/><\/p>\n<p>Most features are part of a flow. Rarely is there just one static screen to design. Run through the feature step-by-step to find out how you arrive at the feature, what happens when you interact with it, and where the user goes after they\u2019ve used the feature.<\/p>\n<p>Using a prototyping tool like <a href=\"https:\/\/marvelapp.com\" target=\"_blank\" rel=\"noopener noreferrer\">Marvel<\/a> helps encourage you to think about how the feature fits into a flow \u2013 you have to design the interaction and go beyond just a static screen.<\/p>\n<h3>Design the empty state<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_10.png\" alt=\"Design the empty state\" \/><\/p>\n<p>It\u2019s easy to think of a feature in use with all the data and information in the screen when everything\u2019s fully set up. But many users never get to your \u201cdream\u201d state \u2013 they\u2019ll likely see the feature when it\u2019s not yet being used. Have <em>you<\/em> thought about the feature when it\u2019s not being used? Designing the empty state of a feature can help encourage users to interact with the feature in the first place.<\/p>\n<h3>Design the error state<\/h3>\n<p><img decoding=\"async\" src=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_11.png\" alt=\"Design the error states\" \/><\/p>\n<p>Things don\u2019t always go to plan. Considering what happens to a feature when an API is throwing an error or when the user\u2019s internet goes offline helps ensure the feature feels solid and reliable.<\/p>\n<p>It\u2019s easy to forget the error states when designing in a protective environment (like on a local machine with super fast wired network access), but when your product is used in the real world real problems happen. It\u2019s easy for an entire product to start feeling brittle and fragile if you don\u2019t consider error states and fallbacks.<\/p>\n<h2>Good features start with problems<\/h2>\n<p>If there\u2019s one sure-fire way to spot a bad feature, it\u2019s when the value to customers isn\u2019t immediately obvious. Whenever you\u2019re struggling to explain why a new feature is going to help your customers, stop and run through these points to check you\u2019re not building for the wrong reasons.<\/p>\n<p>Good luck, go build something great!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Building new features in your product can seem simple at first. But building features that really work for your customers&#8230;<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1587],"tags":[1158,1227,1101],"class_list":["post-6676","post","type-post","status-publish","format-standard","hentry","category-product-design","tag-design","tag-product-design","tag-product-management"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v18.6 (Yoast SEO v19.0) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How bad features are born - GoSquared Blog<\/title>\n<meta name=\"description\" content=\"The web is scattered with products that have useless, bad features. We look at how to avoid building bad features into your product.\" \/>\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.gosquared.com\/blog\/how-bad-features-are-born\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How bad features are born\" \/>\n<meta property=\"og:description\" content=\"The web is scattered with products that have useless, bad features. We look at how to avoid building bad features into your product.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born\" \/>\n<meta property=\"og:site_name\" content=\"GoSquared Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/GoSquared\" \/>\n<meta property=\"article:published_time\" content=\"2016-09-01T17:23:55+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-11-28T11:25:23+00:00\" \/>\n<meta property=\"og:image\" content=\"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_12.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.gosquared.com\/blog\/wp-content\/uploads\/2016\/09\/16_09_01_badfeatures_twitter_01.png\" \/>\n<meta name=\"twitter:creator\" content=\"@JamesJGill\" \/>\n<meta name=\"twitter:site\" content=\"@GoSquared\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"James Gill\" \/>\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\":\"Organization\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/#organization\",\"name\":\"GoSquared\",\"url\":\"https:\/\/www.gosquared.com\/blog\/\",\"sameAs\":[\"https:\/\/instagram.com\/gosquaredteam\",\"https:\/\/www.linkedin.com\/company\/go-squared-ltd.\",\"https:\/\/www.facebook.com\/GoSquared\",\"https:\/\/twitter.com\/GoSquared\"],\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.gosquared.com\/blog\/wp-content\/uploads\/2015\/07\/gosquared.png\",\"contentUrl\":\"https:\/\/www.gosquared.com\/blog\/wp-content\/uploads\/2015\/07\/gosquared.png\",\"width\":1270,\"height\":250,\"caption\":\"GoSquared\"},\"image\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/#website\",\"url\":\"https:\/\/www.gosquared.com\/blog\/\",\"name\":\"GoSquared Blog\",\"description\":\"Turn visitors into customers.\",\"publisher\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.gosquared.com\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#primaryimage\",\"url\":\"\",\"contentUrl\":\"\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#webpage\",\"url\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born\",\"name\":\"How bad features are born - GoSquared Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#primaryimage\"},\"datePublished\":\"2016-09-01T17:23:55+00:00\",\"dateModified\":\"2019-11-28T11:25:23+00:00\",\"description\":\"The web is scattered with products that have useless, bad features. We look at how to avoid building bad features into your product.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.gosquared.com\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How bad features are born\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#webpage\"},\"author\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/#\/schema\/person\/7b8729da7ca77395a2281bad91768fbe\"},\"headline\":\"How bad features are born\",\"datePublished\":\"2016-09-01T17:23:55+00:00\",\"dateModified\":\"2019-11-28T11:25:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#webpage\"},\"wordCount\":1142,\"commentCount\":10,\"publisher\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#primaryimage\"},\"thumbnailUrl\":\"\",\"keywords\":[\"Design\",\"Product Design\",\"Product Management\"],\"articleSection\":[\"Product Design\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/#\/schema\/person\/7b8729da7ca77395a2281bad91768fbe\",\"name\":\"James Gill\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.gosquared.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/46c3ae1aefe2bdb6765a3153018aeba55de419fa36083b8dcdf9ee49ffcb5a2f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/46c3ae1aefe2bdb6765a3153018aeba55de419fa36083b8dcdf9ee49ffcb5a2f?s=96&d=mm&r=g\",\"caption\":\"James Gill\"},\"description\":\"James is CEO and one of the co-founders of GoSquared. He also likes to talk about design.\",\"sameAs\":[\"http:\/\/www.gosquared.com\/\",\"https:\/\/twitter.com\/JamesJGill\"],\"url\":\"https:\/\/www.gosquared.com\/blog\/author\/g\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How bad features are born - GoSquared Blog","description":"The web is scattered with products that have useless, bad features. We look at how to avoid building bad features into your product.","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.gosquared.com\/blog\/how-bad-features-are-born","og_locale":"en_US","og_type":"article","og_title":"How bad features are born","og_description":"The web is scattered with products that have useless, bad features. We look at how to avoid building bad features into your product.","og_url":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born","og_site_name":"GoSquared Blog","article_publisher":"https:\/\/www.facebook.com\/GoSquared","article_published_time":"2016-09-01T17:23:55+00:00","article_modified_time":"2019-11-28T11:25:23+00:00","og_image":[{"url":"\/\/static.gosquared.com\/images\/liquidicity\/16_09_01_badfeatures_12.png"}],"twitter_card":"summary_large_image","twitter_image":"https:\/\/www.gosquared.com\/blog\/wp-content\/uploads\/2016\/09\/16_09_01_badfeatures_twitter_01.png","twitter_creator":"@JamesJGill","twitter_site":"@GoSquared","twitter_misc":{"Written by":"James Gill","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Organization","@id":"https:\/\/www.gosquared.com\/blog\/#organization","name":"GoSquared","url":"https:\/\/www.gosquared.com\/blog\/","sameAs":["https:\/\/instagram.com\/gosquaredteam","https:\/\/www.linkedin.com\/company\/go-squared-ltd.","https:\/\/www.facebook.com\/GoSquared","https:\/\/twitter.com\/GoSquared"],"logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.gosquared.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.gosquared.com\/blog\/wp-content\/uploads\/2015\/07\/gosquared.png","contentUrl":"https:\/\/www.gosquared.com\/blog\/wp-content\/uploads\/2015\/07\/gosquared.png","width":1270,"height":250,"caption":"GoSquared"},"image":{"@id":"https:\/\/www.gosquared.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"WebSite","@id":"https:\/\/www.gosquared.com\/blog\/#website","url":"https:\/\/www.gosquared.com\/blog\/","name":"GoSquared Blog","description":"Turn visitors into customers.","publisher":{"@id":"https:\/\/www.gosquared.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.gosquared.com\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#primaryimage","url":"","contentUrl":""},{"@type":"WebPage","@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#webpage","url":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born","name":"How bad features are born - GoSquared Blog","isPartOf":{"@id":"https:\/\/www.gosquared.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#primaryimage"},"datePublished":"2016-09-01T17:23:55+00:00","dateModified":"2019-11-28T11:25:23+00:00","description":"The web is scattered with products that have useless, bad features. We look at how to avoid building bad features into your product.","breadcrumb":{"@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.gosquared.com\/blog"},{"@type":"ListItem","position":2,"name":"How bad features are born"}]},{"@type":"Article","@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#article","isPartOf":{"@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#webpage"},"author":{"@id":"https:\/\/www.gosquared.com\/blog\/#\/schema\/person\/7b8729da7ca77395a2281bad91768fbe"},"headline":"How bad features are born","datePublished":"2016-09-01T17:23:55+00:00","dateModified":"2019-11-28T11:25:23+00:00","mainEntityOfPage":{"@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#webpage"},"wordCount":1142,"commentCount":10,"publisher":{"@id":"https:\/\/www.gosquared.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#primaryimage"},"thumbnailUrl":"","keywords":["Design","Product Design","Product Management"],"articleSection":["Product Design"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.gosquared.com\/blog\/how-bad-features-are-born#respond"]}]},{"@type":"Person","@id":"https:\/\/www.gosquared.com\/blog\/#\/schema\/person\/7b8729da7ca77395a2281bad91768fbe","name":"James Gill","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.gosquared.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/46c3ae1aefe2bdb6765a3153018aeba55de419fa36083b8dcdf9ee49ffcb5a2f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/46c3ae1aefe2bdb6765a3153018aeba55de419fa36083b8dcdf9ee49ffcb5a2f?s=96&d=mm&r=g","caption":"James Gill"},"description":"James is CEO and one of the co-founders of GoSquared. He also likes to talk about design.","sameAs":["http:\/\/www.gosquared.com\/","https:\/\/twitter.com\/JamesJGill"],"url":"https:\/\/www.gosquared.com\/blog\/author\/g"}]}},"wps_subtitle":"Spot bad features before they make it to your customers","_links":{"self":[{"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/posts\/6676","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/comments?post=6676"}],"version-history":[{"count":0,"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/posts\/6676\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/media?parent=6676"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/categories?post=6676"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gosquared.com\/blog\/wp-json\/wp\/v2\/tags?post=6676"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}