{"id":26393,"date":"2021-09-14T15:14:22","date_gmt":"2021-09-14T14:14:22","guid":{"rendered":"https:\/\/www.intercom.com\/blog\/?p=26393"},"modified":"2021-09-14T16:33:38","modified_gmt":"2021-09-14T15:33:38","slug":"7-techniques-for-problem-statements","status":"publish","type":"post","link":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/","title":{"rendered":"7 proven techniques for writing a great problem statement"},"content":{"rendered":"

If you want to ship great product that users love, you need to start with a clear understanding of what problem you\u2019re trying to solve for your user and why.<\/p>\n

At Intercom, we always “start with the problem<\/a>” when beginning any project \u2013 it’s part of how we apply the Jobs-to-be-Done framework<\/a>. As product managers, this means we must carefully research and understand the problems we’re actually solving for our customers. To capture our thoughts and give clear definition to our team, we write a document called a problem statement<\/a>.<\/p>\n

“It takes thought, writing, re-writing, and research. And it\u2019s easy to get stuck along the way”<\/p><\/blockquote>\n

Writing a problem statement can seem like a formality, but when you get down to it the process is deceptively hard, requiring a deep understanding of customers and the ability to grapple with abstract concepts.<\/p>\n

I have yet to sit down and simply dash off a problem statement in a single session. It takes thought, writing, re-writing, and research. And it\u2019s easy to get stuck along the way. Here are seven techniques that I\u2019ve found helpful to un-stick yourself as you draft a problem statement.<\/p>\n

1. Start with the solution<\/h2>\n

While a problem statement comes before design in the process of product development, as people we tend to think in solutions. As a result, you\u2019ll often find problems come to you as solutions or feature ideas, and you\u2019ll need to work backwards towards the underlying problem.<\/p>\n

“A\u00a0good problem statement will lay out what you assume matters to customers and force you to describe what\u2019s most useful to customers about your proposed solution”<\/p><\/blockquote>\n

To do this, ask yourself \u201cwhat problem would this solution solve?\u201d and \u201cwhy do I think customers will prefer this solution to the status quo?\u201d Even if you\u2019re already committed to building a particular thing, a good problem statement will lay out what you assume matters to customers and force you to describe what\u2019s most useful to customers about your proposed solution. Having this on paper helps your team focus its energy on the parts of the feature that solve the most important parts of the problem for your customers.<\/p>\n

2. Try wrong answers<\/h2>\n

It\u2019s common to struggle with figuring out what the real problem for a customer is. Using the job story structure<\/a> guides your problem statement to the right zoom level, but thinking up seemingly wrong solutions to your problem helps define the criteria for a good solution.<\/p>\n

Ask yourself what it is about the wrong solution that makes it unacceptable, and include that in your problem statement. If you can\u2019t find a customer-centric justification for eliminating the wrong solution, perhaps it\u2019s actually worthy of consideration.<\/p>\n

3. Talk to customers again<\/h2>\n

Talking to customers is standard advice for PMs, but even when you\u2019ve immersed yourself in your customers\u2019 worlds, you\u2019ll find at times that you struggle to articulate the detail of what a customer wants to achieve, or nail down what\u2019s wrong with the status quo.<\/p>\n

“After even a handful of discussions you\u2019ll quickly uncover what does (and doesn\u2019t) matter to your customers”<\/p><\/blockquote>\n

At this point, the fastest way to make progress is to simply go back and clarify these points with your customers. Concepts that seemed vague or issues that seemed important usually come into sharp relief when you talk to the people who use your product. After even a handful of discussions you\u2019ll quickly uncover what does (and doesn\u2019t) matter to them.<\/p>\n

4. Focus on a person<\/h2>\n

It\u2019s common to struggle with the right level at which to frame a problem: maybe you are trying to resolve a problem for your business, or you see an issue which affects a whole organization rather than one person.<\/p>\n

Because it\u2019s people who buy and use your product, a good problem statement will be focused on a problem (or problems) for a person (or people). If you\u2019re having trouble getting your head around a problem space, try laying out the specific problems felt by the people involved.<\/p>\n

5. Start designing<\/h2>\n

Most problem statements are created iteratively. It\u2019s very difficult to perfectly specify all the constraints in a solution space up front, so sometimes it\u2019s easier to start designing solutions.<\/p>\n

“This approach can open up perspectives and possibilities that you might not have considered beforehand”<\/p><\/blockquote>\n

Particularly when feeling blocked, this approach can open up perspectives and possibilities that you might not have considered beforehand. This can also bring into sharp relief what problems with the status quo are most challenging to resolve.<\/p>\n

6. Skip the preamble<\/h2>\n

For some reason PMs (myself included) are inclined to begin a problem statement with historical scene-setting. Don\u2019t do this, it\u2019s usually an indication that you don\u2019t understand the customer problem.<\/p>\n

Instead of starting with \u201cLast quarter we launched XYZ feature and\u2026\u201d, skip straight to what the customer wants, when this need occurs, and what they\u2019re trying to achieve by wanting this. A focused problem statement will help align the rest of your team throughout the design and build process.<\/p>\n

7. Eliminate judgment words<\/h2>\n

Great problem statements describe facts about your customers and what they want. As such, avoid using judgmental words about your product in your problem frame. Judgment terms such as \u201ctoo slow\u201d, \u201cbadly designed\u201d, or \u201cconfusing\u201d are ambiguous and could be interpreted differently by each person reading the problem statement.<\/p>\n

“If your product doesn\u2019t solve a meaningful problem, then customers just won\u2019t use it”<\/p><\/blockquote>\n

You should replace these with data-based statements. Instead of saying \u201cour onboarding flow is confusing,\u201d clearly state what customers are confused about. Instead of saying \u201cwe need to redesign our settings page,\u201d state what specifically customers can\u2019t do from the settings page that they need to, and why they want to do that.<\/p>\n

\n

Framing problems is hard. But getting it right is of critical importance as it determines the quality of the product your team ships. Regardless of how well-designed and scalable your product ultimately ends up, if it doesn\u2019t solve a meaningful problem, then customers just won\u2019t use it. Hopefully some of these practices can help you get moving again when you\u2019re stuck. Embrace the struggle, it\u2019s worth it.<\/p>\n\n","protected":false},"excerpt":{"rendered":"

Writing a problem statement can be deceptively hard, requiring a deep understanding of customers and abstract concepts. Here are seven techniques to un-stick yourself as you draft a problem statement.<\/p>\n","protected":false},"author":352,"featured_media":26395,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"category":[5],"tags":[26,24808,62],"coauthors":[12705],"class_list":["post-26393","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product-and-design","tag-jobs-to-be-done","tag-problem-statement","tag-product-management"],"yoast_head":"\n7 Proven Techniques for Writing a Great Problem Statement - The Intercom Blog<\/title>\n<meta name=\"description\" content=\"Writing a problem statement can be deceptively hard \u2013\u00a0here are 7 techniques to un-stick yourself as you draft a problem statement.\" \/>\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.intercom.com\/blog\/7-techniques-for-problem-statements\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"7 proven techniques for writing a great problem statement\" \/>\n<meta property=\"og:description\" content=\"Writing a problem statement can be deceptively hard \u2013\u00a0here are 7 techniques to un-stick yourself as you draft a problem statement.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/\" \/>\n<meta property=\"og:site_name\" content=\"The Intercom Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/intercominc\" \/>\n<meta property=\"article:published_time\" content=\"2021-09-14T14:14:22+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-09-14T15:33:38+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"2048\" \/>\n\t<meta property=\"og:image:height\" content=\"969\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Robbie Allan\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@robbiedigi\" \/>\n<meta name=\"twitter:site\" content=\"@intercom\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Robbie Allan\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/\"},\"author\":{\"name\":\"Robbie Allan\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/person\\\/b7476f7ac15e1080e1138c30c10c967d\"},\"headline\":\"7 proven techniques for writing a great problem statement\",\"datePublished\":\"2021-09-14T14:14:22+00:00\",\"dateModified\":\"2021-09-14T15:33:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/\"},\"wordCount\":1060,\"publisher\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/09\\\/Harry-Woodgate.jpeg\",\"keywords\":[\"jobs-to-be-done\",\"problem statement\",\"product management\"],\"articleSection\":[\"Product & Design\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/\",\"name\":\"7 Proven Techniques for Writing a Great Problem Statement - The Intercom Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/09\\\/Harry-Woodgate.jpeg\",\"datePublished\":\"2021-09-14T14:14:22+00:00\",\"dateModified\":\"2021-09-14T15:33:38+00:00\",\"description\":\"Writing a problem statement can be deceptively hard \u2013\u00a0here are 7 techniques to un-stick yourself as you draft a problem statement.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/7-techniques-for-problem-statements\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/09\\\/Harry-Woodgate.jpeg\",\"contentUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/09\\\/Harry-Woodgate.jpeg\",\"width\":2048,\"height\":969,\"caption\":\"Intercom illustration by Harry Woodgate\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/\",\"name\":\"The Intercom Blog\",\"description\":\"Articles and Podcasts on Customer Service, AI and Automation, Product, and more\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\",\"name\":\"The Intercom Blog\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/08\\\/Intercom-logo-sq-black-trans.png\",\"contentUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/08\\\/Intercom-logo-sq-black-trans.png\",\"width\":1000,\"height\":1000,\"caption\":\"The Intercom Blog\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/intercominc\",\"https:\\\/\\\/x.com\\\/intercom\",\"https:\\\/\\\/www.instagram.com\\\/intercom\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/2491343\",\"https:\\\/\\\/www.pinterest.ie\\\/intercom\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCJG0MvLP03kyzzAkD-w98aQ\",\"https:\\\/\\\/en.wikipedia.org\\\/wiki\\\/Intercom_(company)\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/person\\\/b7476f7ac15e1080e1138c30c10c967d\",\"name\":\"Robbie Allan\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/70d3b4dc4762c5f4b2d56d089b0b161bea293a7ab8c018fba18fe5f1556476a6?s=96&d=mm&r=pg9537a06f8279d50cc4bc358cfb4b7343\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/70d3b4dc4762c5f4b2d56d089b0b161bea293a7ab8c018fba18fe5f1556476a6?s=96&d=mm&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/70d3b4dc4762c5f4b2d56d089b0b161bea293a7ab8c018fba18fe5f1556476a6?s=96&d=mm&r=pg\",\"caption\":\"Robbie Allan\"},\"description\":\"Robbie is a Senior Product Manager at Intercom. Previously he worked at Zynga, SurveyMonkey, and McKinsey.\",\"sameAs\":[\"https:\\\/\\\/x.com\\\/robbiedigi\"],\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/author\\\/robbieallan\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"7 Proven Techniques for Writing a Great Problem Statement - The Intercom Blog","description":"Writing a problem statement can be deceptively hard \u2013\u00a0here are 7 techniques to un-stick yourself as you draft a problem statement.","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.intercom.com\/blog\/7-techniques-for-problem-statements\/","og_locale":"en_US","og_type":"article","og_title":"7 proven techniques for writing a great problem statement","og_description":"Writing a problem statement can be deceptively hard \u2013\u00a0here are 7 techniques to un-stick yourself as you draft a problem statement.","og_url":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/","og_site_name":"The Intercom Blog","article_publisher":"https:\/\/www.facebook.com\/intercominc","article_published_time":"2021-09-14T14:14:22+00:00","article_modified_time":"2021-09-14T15:33:38+00:00","og_image":[{"width":2048,"height":969,"url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg","type":"image\/jpeg"}],"author":"Robbie Allan","twitter_card":"summary_large_image","twitter_creator":"@robbiedigi","twitter_site":"@intercom","twitter_misc":{"Written by":"Robbie Allan","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/#article","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/"},"author":{"name":"Robbie Allan","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/person\/b7476f7ac15e1080e1138c30c10c967d"},"headline":"7 proven techniques for writing a great problem statement","datePublished":"2021-09-14T14:14:22+00:00","dateModified":"2021-09-14T15:33:38+00:00","mainEntityOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/"},"wordCount":1060,"publisher":{"@id":"https:\/\/www.intercom.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg","keywords":["jobs-to-be-done","problem statement","product management"],"articleSection":["Product & Design"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/","url":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/","name":"7 Proven Techniques for Writing a Great Problem Statement - The Intercom Blog","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/#primaryimage"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg","datePublished":"2021-09-14T14:14:22+00:00","dateModified":"2021-09-14T15:33:38+00:00","description":"Writing a problem statement can be deceptively hard \u2013\u00a0here are 7 techniques to un-stick yourself as you draft a problem statement.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intercom.com\/blog\/7-techniques-for-problem-statements\/#primaryimage","url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg","contentUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg","width":2048,"height":969,"caption":"Intercom illustration by Harry Woodgate"},{"@type":"WebSite","@id":"https:\/\/www.intercom.com\/blog\/#website","url":"https:\/\/www.intercom.com\/blog\/","name":"The Intercom Blog","description":"Articles and Podcasts on Customer Service, AI and Automation, Product, and more","publisher":{"@id":"https:\/\/www.intercom.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.intercom.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.intercom.com\/blog\/#organization","name":"The Intercom Blog","url":"https:\/\/www.intercom.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2019\/08\/Intercom-logo-sq-black-trans.png","contentUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2019\/08\/Intercom-logo-sq-black-trans.png","width":1000,"height":1000,"caption":"The Intercom Blog"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/intercominc","https:\/\/x.com\/intercom","https:\/\/www.instagram.com\/intercom\/","https:\/\/www.linkedin.com\/company\/2491343","https:\/\/www.pinterest.ie\/intercom\/","https:\/\/www.youtube.com\/channel\/UCJG0MvLP03kyzzAkD-w98aQ","https:\/\/en.wikipedia.org\/wiki\/Intercom_(company)"]},{"@type":"Person","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/person\/b7476f7ac15e1080e1138c30c10c967d","name":"Robbie Allan","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/70d3b4dc4762c5f4b2d56d089b0b161bea293a7ab8c018fba18fe5f1556476a6?s=96&d=mm&r=pg9537a06f8279d50cc4bc358cfb4b7343","url":"https:\/\/secure.gravatar.com\/avatar\/70d3b4dc4762c5f4b2d56d089b0b161bea293a7ab8c018fba18fe5f1556476a6?s=96&d=mm&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/70d3b4dc4762c5f4b2d56d089b0b161bea293a7ab8c018fba18fe5f1556476a6?s=96&d=mm&r=pg","caption":"Robbie Allan"},"description":"Robbie is a Senior Product Manager at Intercom. Previously he worked at Zynga, SurveyMonkey, and McKinsey.","sameAs":["https:\/\/x.com\/robbiedigi"],"url":"https:\/\/www.intercom.com\/blog\/author\/robbieallan\/"}]}},"jetpack_featured_media_url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/09\/Harry-Woodgate.jpeg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/26393","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/users\/352"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/comments?post=26393"}],"version-history":[{"count":0,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/26393\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media\/26395"}],"wp:attachment":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media?parent=26393"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/category?post=26393"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/tags?post=26393"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/coauthors?post=26393"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}