{"id":5412,"date":"2014-05-08T16:51:04","date_gmt":"2014-05-08T16:51:04","guid":{"rendered":"http:\/\/insideintercom.io\/?p=5412"},"modified":"2025-01-07T16:56:17","modified_gmt":"2025-01-07T16:56:17","slug":"what-we-can-learn-from-google-plus","status":"publish","type":"post","link":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/","title":{"rendered":"8 product lessons we can learn from Google+"},"content":{"rendered":"

The\u00a0reshuffles in management<\/a> in Google+ recently attracted a lot of press comment and speculation. I thought it an appropriate time to look back on the last couple of years and see what broader product lessons we can learn from the inception, launch and evolution of Google+.<\/p>\n

Note that whilst I worked on the original Google+ team and invented the ideas behind Circles, I have long since left, and have no insider knowledge about what is happening, nor does this post have any confidential information. I\u2019m simply sharing what I think are clear product lessons that may help many of us build better things, all of which can be deduced from public information.<\/em><\/p>\n

1. Build around people problems, not company problems<\/h2>\n

A dominant theme in the discussion of what is happening with Google+ has been a focus on the problems Google faced with the rise of Facebook, and whether those problems still exist now. Everything I have read in the past few weeks discusses this from a company problem<\/em> point of view. There has been little discussion on which problems Google+ should or could solve for people, or what new inventions they could build to make people’s lives better. Contrast this with other parts of Google, where clear problems that people have are being solved. If Google+ wants to see engagement numbers similar to Facebook, it needs to focus on how Google+ makes people’s lives markedly better. The vast majority of people don\u2019t care about Google\u2019s problems. Likewise, they don\u2019t use Facebook in order to collect data about themselves so they can be targeted with better advertising. They simply want better tools to help them live a more fulfilling and happier life, and often they\u00a0can\u2019t foresee tools they will later come to value.<\/p>\n

The point here is that social software is not done.<\/strong> Do people want better ways to build, maintain and grow relationships? Of course. Better ways to share their experiences with the people they care about no matter where they are? Of course. None of these problems are solved. People don\u2019t even yet know how they will share experiences in the future; this is why the Facebook acquisition of Oculus Rift<\/a> is so interesting. Large parts of Google+ don’t offer anything beyond what exists elsewhere.<\/p>\n

There is so much room for invention, so much opportunity to make people\u2019s lives better, the Internet is in its infancy. There is no need to worry so deeply about competitive threats, as if it is a zero sum game and there is a foregone product conclusion.<\/p>\n

2. Perceived benefits need to be greater than perceived effort<\/h2>\n

My mobile phone’s address book is full of people I don\u2019t recognise. It is a pretty comprehensive list of all the people in my life, yet woefully managed. One of the most personal parts of my most personal device is full of strangers. This is the same for almost everyone and the reason is simple: it\u2019s not worth the effort to keep it up to date. This is the problem with Google Circles.<\/strong><\/p>\n

The perceived benefit was clear to everyone. Circles more clearly mapped to how life works offline, where people typically share different parts of their life with different groups of people. It was a clear Achilles heel for Facebook at the time, as Facebook\u2019s primary design pattern was to share everything with all your friends, which limited what people were comfortable sharing.<\/p>\n

But this is a very hard design problem, and identifying \u00a0a clear user benefit alone isn\u2019t enough. Execution is as important as initial insight or unique value proposition. Looking at most mobile phone address books indicated people would not manually put their friends into Circles, and more importantly, that they wouldn\u2019t keep them up to date. Circles requires ongoing manual work, and despite the perceived value, it\u2019s simply not worth the effort. It doesn\u2019t matter how beautiful the UI is, how polished the transitions and animations are, how much fun has been added to the experience, people will simply not do it because the perceived effort outweighs the perceived value.<\/p>\n

\"\"<\/div>\n

Personally I don\u2019t think this can be fixed. Circles as a literal interpretation, and manual execution, of how real life social networks work will not succeed. It\u2019s time for a rethink, but more on that later.<\/p>\n

3. Ruthlessly focus and descope, be patient, the Internet is young<\/h2>\n

We have a very big, broad mission at Intercom<\/a> and aspire to build something that is used by millions of apps and billions of people. But we know that if we are successful, this will take many years. Other than incredibly rare outliers like Instagram, social networks take a long time to build out and deepen, just as real life relationships do. This requires patience and deliberate focus. It\u2019s too easy to chase too many things.<\/p>\n

Google+ tried to be everything, all at once.<\/strong> As well as the rise of Facebook, there was the growth of Twitter, and Google+ attempted to compete with both. Facebook and Twitter are very different products and often serve independent needs for people. The product complexity within Google+, and the lack of aggressively killing off features people don’t use, suggests that this remains an issue.<\/p>\n

\"\"<\/div>\n

This lack of focus adds huge complexity to the product, and huge cognitive effort on the parts of users, therefore increasing the effort required. All of the massively successful social products of the last few years have started out by doing one thing really well, then growing organically and expanding.<\/p>\n

4. Embrace the idea that life is messy<\/h2>\n

I once did a large research project trying to help Vodafone understand how their call centre staff shared information. When debriefing, I showed two images to explain that life is messy, and not as neat as when your brain post-rationalizes experiences.<\/p>\n

\"\"<\/div>\n

Of all the things we need to deal with in life, relationships with other people are the most complicated and messy. All the way from marriages to initial introductions. They involve the deepest of human emotions, from who we see ourselves as, how we project ourselves to others, what we desire, who we want to become, the groups we feel a part of, who and how we love, how we think about mortality. No wonder that social design is hard.<\/p>\n

There is a deep dichotomy between this messy reality and software builders\u2019 desire for structured data.<\/strong> Maybe someday we\u2019ll figure out that our brain is all nodes and links, deep and shallow pathways between objects, and we can directly map to it with software. But likely not in our lifetime.<\/p>\n

I believe that one reason behind the rise of WhatsApp is that it solves the \u201cCircles\u201d problem in a way that embraces the idea that life is messy. Whilst Circles, and indeed Facebook Lists<\/a> and Facebook Groups<\/a>, all assume that the group is the defining object, with clear boundaries, WhatsApp does not. Much of WhatsApp usage is group conversations but the subtle, critical difference is that these groups are typically not permanent or sustaining. It is not a stable set of people discussing multiple things in sequence over time. It is one-off combinations of people grouped together for something temporal, like an event, a concert, a party, a weekend away. The groups then decay gracefully. When necessary they are rebuilt from scratch. Often there is a defining event that brings a group of people together, people are added, they communicate, share content, it gets messy, but then it dies.<\/p>\n

In this sense, email works the same way as WhatApp. We email the same groups of people over and over again, rebuilding the same list manually every single time. To many engineers, this is crazy, leading to horrible inefficiencies in data processing and storage. Duplication everywhere. But this is the messy reality. The cognitive effort to add in people\u2019s email addresses is low. So doing it over and over again makes sense. Suggesting others to add based on common patterns (like Gmail does)\u00a0makes this faster for people, reduces the effort, and makes it a better experience.<\/p>\n

\"\"<\/div>\n

One wonders whether this is how Circles should have worked, or more importantly, how it should work in the future. Circles as temporary rather than permanent.<\/p>\n

5. A fast follow product strategy doesn\u2019t work when you have network effects<\/h2>\n

There is a nightclub close to our office. It\u2019s pretty run down, it plays questionable music, it serves questionable beer. And it\u2019s packed every night. People love it. Many new nightclubs have opened up next door, only to close their doors months later. They had better decor, better music, better beer. But they didn\u2019t have the one thing necessary for success: people\u2019s friends. People want to be where their friends are, and this trumps everything.<\/p>\n

Google+ applied a fast follow<\/a> product strategy. The theory of fast follow is to copy a competitors features, emulate the core offering, and then outperform on one other area, bypassing the incumbent product. The objectively better product wins. There are many successful examples of this strategy, including Android, Windows, Google search. For Google+, it is clear that many parts of Facebook were emulated: the Stream, Photos, User Profiles, Company Profiles, Notifications. But the one thing that couldn\u2019t be emulated was people\u2019s friends.<\/p>\n

Network effects take time to build. This requires an entirely different product strategy than fast follow. And it requires patience and focus.<\/p>\n

6. Google+ suffered shiny object syndrome<\/h2>\n
<\/div>\n

Looking back, Google had an arsenal of social products prior to Google+. The list is an incredible lineup (and I\u2019m not the first to point this out).<\/p>\n

Gmail:<\/strong> Asynchronous messaging, inline multimedia support
\nG Chat:<\/strong>\u00a0Synchronous messaging, text and video
\nPicasa:<\/strong> Photos and Videos with inbuilt private sharing
\nYouTube:<\/strong> Videos with a public audience and community
\nReader:<\/strong> Magazines
\nBlogger:<\/strong> Longer form publishing and journaling
\nVoice<\/strong>: Voice calls and SMS<\/p>\n

I\u2019m sure there was a ton of legacy to deal with here, but you have to wonder about what might have been if an identity layer had simply been applied across all these products and they were invested in. The same way Google applied a consistent visual design across all its products. The incredible irony is that Facebook is currently unbundling it\u2019s apps into distinct functions with a common identity layer.<\/strong> Google+ didn\u2019t necessarily need a Newsfeed for example, and it certainly didn\u2019t need to look or be structured like Facebook. And to put the elephant in the room to bed, Google didn\u2019t need real names, they simply needed one common way to refer to individual people. Most of the rest of the world still use email addresses to accomplish this, another irony for people working on Gmail.<\/p>\n

7. People need clear conceptual models that exist in real life<\/h2>\n

Many of our friends aren’t punctual. I remember a time before mobile phones where we had to wait at a pre-arranged meeting spot, and then wonder and wonder how late our friends were going to be. One of the best things about mobile phones was that those experiences went away. Yet Hangouts brings that experience back. Should I just wait? Should I open a new tab and do other things?<\/p>\n

\"\"<\/div>\n

It feels broken to have to use another channel, like email or a messaging app, to talk to someone who is supposed to have joined the Hangout.\u00a0The move from Google Chat to Hangouts is an interesting one. I\u2019d love to see normalised engagement numbers on Gchat versus Hangouts, and Gchat IM conversations versus the current Hangout oriented implementation of chatting in Gmail. I wonder how successful Hangouts really is? It’s Play store rating<\/a> is 3.8. I personally find the conceptual model behind Hangouts confusing and much preferred the simplicity of Gchat. I know many others feel the same.<\/p>\n

Looking back at the history of communication, most successful social software has an analogous offline experience.<\/strong> Even something like a Newsfeed can be easily compared to a local town square as the primary source of news and gossip. With a new tool, people need an established way of thinking about it to reduce the perceived effort of use. I can only think of one real life experience with the same conceptual model as Hangouts – where one person puts themselves out into a place without pre-arrangement and waits for someone to join them – and it\u2019s illegal in almost every country. It seems that to set up a Hangout, you first have to do other work, like ask someone if they are available, or create a calendar event, or at best deal with an awkward social metaphor and new abstraction: \u2019the hangout’.<\/p>\n

The concept of calling someone just seems so much simpler. Hangouts are possibly great for work and meetings, not so much for calling your family and friends.<\/p>\n

8. Distribution often trumps product<\/h2>\n

Not withstanding these issues it\u2019s entirely plausible that Google+ succeeded in this first wave of its life. If the goal was to get hundreds of millions of people signed in to Google every day then it looks like it achieved that. Whether knowingly or unknowingly, an order of magnitude more people are now signed in under one identity, searching, emailing, watching videos. Once you have distribution, and Google have that in spades with Android, Chrome, and Search, there are many paths to success.<\/p>\n

So what to do next?<\/h2>\n

What would one do if we applied these lessons to figure out what to do next? I think Google+ is actually in a reasonable spot. It just needs to go back to absolute fundamentals and have ruthless focus. Remember that product strategy means saying no<\/a>. To\u00a0understand what people problems Google+ might solve, focus on a tiny number of these, possibly even just one, and make this simple to understand, just as Instagram, Snapchat, WhatsApp, Secret have done.<\/p>\n

Google+ is incredibly complex and hard to understand. Simplify the product offering by killing features,\u00a0and lowering the effort required to get value out of it by killing many of the choices in the UI.<\/p>\n

Finally, and most importantly, it needs to build upon established real world social norms and conceptual models. We’re still only getting started with social software. Whilst social science patterns are very well established, there are no established ways to build social products. Copying competitors is unnecessary. There are so many things we can make better for people if we carefully and deliberately observe and understand their world.<\/p>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

What broader product lessons we can learn from the inception, launch and evolution of Google+?<\/p>\n","protected":false},"author":16,"featured_media":9391,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"category":[5],"tags":[54,26,153,161,254],"coauthors":[358],"class_list":["post-5412","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product-and-design","tag-google","tag-jobs-to-be-done","tag-product-design","tag-product-development","tag-social-networks"],"yoast_head":"\n8 product lessons we can learn from Google+ - The Intercom Blog<\/title>\n<meta name=\"description\" content=\"What broader product lessons we can learn from the inception, launch and evolution of Google+?\" \/>\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\/what-we-can-learn-from-google-plus\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"8 product lessons we can learn from Google+\" \/>\n<meta property=\"og:description\" content=\"What broader product lessons we can learn from the inception, launch and evolution of Google+?\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/\" \/>\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=\"2014-05-08T16:51:04+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-01-07T16:56:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1968\" \/>\n\t<meta property=\"og:image:height\" content=\"932\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Paul Adams\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@padday\" \/>\n<meta name=\"twitter:site\" content=\"@intercom\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Paul Adams\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/\"},\"author\":{\"name\":\"Paul Adams\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#\\\/schema\\\/person\\\/8b2507bf414e874ac7b55da405aabaf5\"},\"headline\":\"8 product lessons we can learn from Google+\",\"datePublished\":\"2014-05-08T16:51:04+00:00\",\"dateModified\":\"2025-01-07T16:56:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/\"},\"wordCount\":2437,\"publisher\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/05\\\/Intercom_Programming-1.jpg\",\"keywords\":[\"Google\",\"jobs-to-be-done\",\"product design\",\"product development\",\"social networks\"],\"articleSection\":[\"Product & Design\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/\",\"name\":\"8 product lessons we can learn from Google+ - The Intercom Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/05\\\/Intercom_Programming-1.jpg\",\"datePublished\":\"2014-05-08T16:51:04+00:00\",\"dateModified\":\"2025-01-07T16:56:17+00:00\",\"description\":\"What broader product lessons we can learn from the inception, launch and evolution of Google+?\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/what-we-can-learn-from-google-plus\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/05\\\/Intercom_Programming-1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/wp-content\\\/uploads\\\/2016\\\/05\\\/Intercom_Programming-1.jpg\",\"width\":1968,\"height\":932},{\"@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\\\/8b2507bf414e874ac7b55da405aabaf5\",\"name\":\"Paul Adams\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/38af9dc1542cbca7c47f4a9fcea826af21c2129dc2ef285c029a45a3d96c144a?s=96&d=mm&r=pg2b4e786619e7dec06c6d0579c6a4cc11\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/38af9dc1542cbca7c47f4a9fcea826af21c2129dc2ef285c029a45a3d96c144a?s=96&d=mm&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/38af9dc1542cbca7c47f4a9fcea826af21c2129dc2ef285c029a45a3d96c144a?s=96&d=mm&r=pg\",\"caption\":\"Paul Adams\"},\"description\":\"Chief Product Officer at Intercom, Paul oversees our product, design and research teams, and co-hosts the Intercom on Product podcast series with Des Traynor. Previously, Paul worked in brand, product and UX design at Facebook, Google, YouTube and Dyson. He is the author of Grouped: How small groups of friends are the key to influence on the social web..\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/pauladams\\\/\",\"https:\\\/\\\/x.com\\\/padday\"],\"url\":\"https:\\\/\\\/www.intercom.com\\\/blog\\\/author\\\/pauladams\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"8 product lessons we can learn from Google+ - The Intercom Blog","description":"What broader product lessons we can learn from the inception, launch and evolution of Google+?","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\/what-we-can-learn-from-google-plus\/","og_locale":"en_US","og_type":"article","og_title":"8 product lessons we can learn from Google+","og_description":"What broader product lessons we can learn from the inception, launch and evolution of Google+?","og_url":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/","og_site_name":"The Intercom Blog","article_publisher":"https:\/\/www.facebook.com\/intercominc","article_published_time":"2014-05-08T16:51:04+00:00","article_modified_time":"2025-01-07T16:56:17+00:00","og_image":[{"width":1968,"height":932,"url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg","type":"image\/jpeg"}],"author":"Paul Adams","twitter_card":"summary_large_image","twitter_creator":"@padday","twitter_site":"@intercom","twitter_misc":{"Written by":"Paul Adams","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/#article","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/"},"author":{"name":"Paul Adams","@id":"https:\/\/www.intercom.com\/blog\/#\/schema\/person\/8b2507bf414e874ac7b55da405aabaf5"},"headline":"8 product lessons we can learn from Google+","datePublished":"2014-05-08T16:51:04+00:00","dateModified":"2025-01-07T16:56:17+00:00","mainEntityOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/"},"wordCount":2437,"publisher":{"@id":"https:\/\/www.intercom.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg","keywords":["Google","jobs-to-be-done","product design","product development","social networks"],"articleSection":["Product & Design"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/","url":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/","name":"8 product lessons we can learn from Google+ - The Intercom Blog","isPartOf":{"@id":"https:\/\/www.intercom.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/#primaryimage"},"image":{"@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/#primaryimage"},"thumbnailUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg","datePublished":"2014-05-08T16:51:04+00:00","dateModified":"2025-01-07T16:56:17+00:00","description":"What broader product lessons we can learn from the inception, launch and evolution of Google+?","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.intercom.com\/blog\/what-we-can-learn-from-google-plus\/#primaryimage","url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg","contentUrl":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg","width":1968,"height":932},{"@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\/8b2507bf414e874ac7b55da405aabaf5","name":"Paul Adams","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/38af9dc1542cbca7c47f4a9fcea826af21c2129dc2ef285c029a45a3d96c144a?s=96&d=mm&r=pg2b4e786619e7dec06c6d0579c6a4cc11","url":"https:\/\/secure.gravatar.com\/avatar\/38af9dc1542cbca7c47f4a9fcea826af21c2129dc2ef285c029a45a3d96c144a?s=96&d=mm&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/38af9dc1542cbca7c47f4a9fcea826af21c2129dc2ef285c029a45a3d96c144a?s=96&d=mm&r=pg","caption":"Paul Adams"},"description":"Chief Product Officer at Intercom, Paul oversees our product, design and research teams, and co-hosts the Intercom on Product podcast series with Des Traynor. Previously, Paul worked in brand, product and UX design at Facebook, Google, YouTube and Dyson. He is the author of Grouped: How small groups of friends are the key to influence on the social web..","sameAs":["https:\/\/www.linkedin.com\/in\/pauladams\/","https:\/\/x.com\/padday"],"url":"https:\/\/www.intercom.com\/blog\/author\/pauladams\/"}]}},"jetpack_featured_media_url":"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2016\/05\/Intercom_Programming-1.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/5412","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\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/comments?post=5412"}],"version-history":[{"count":0,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/posts\/5412\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media\/9391"}],"wp:attachment":[{"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/media?parent=5412"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/category?post=5412"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/tags?post=5412"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.intercom.com\/blog\/wp-json\/wp\/v2\/coauthors?post=5412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}