{"id":12497,"date":"2016-02-19T19:16:11","date_gmt":"2016-02-20T03:16:11","guid":{"rendered":"https:\/\/www.uxpin.com\/studio\/?p=12497"},"modified":"2020-04-22T06:37:09","modified_gmt":"2020-04-22T13:37:09","slug":"how-to-avoid-a-bloated-product-ux-when-considering-new-features","status":"publish","type":"post","link":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/","title":{"rendered":"4 Bottom-Line Questions for Avoiding Feature Bloat"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">New feature requests are something we face everyday on a product team. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, managing those requests doesn\u2019t mean automatically saying \u201cyes\u201d to them. As a product manager or product designer, your responsibility is to ensure the integrity and value of your product\u2014and a harmonized user experience is absolutely essential to that integrity and value. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you add features to a product at the drop of a hat, the product will eventually suffer from Franken-UX: bits and pieces that individually make sense, but when put together create confusion, waste time, and add zero value for your users.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">So what\u2019s the best way to avoid Franken-UX? Ask yourself these 4<\/span> <span style=\"font-weight: 400;\">questions next time someone insists that you add a new feature.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">1. \u00a0What is the <\/span><i><span style=\"font-weight: 400;\">actual <\/span><\/i><span style=\"font-weight: 400;\">functional\/business goal we must achieve? <\/span><\/h2>\n<p><span style=\"font-weight: 400;\">It\u2019s very common for customers or even internal team members to ask for features. By features, I mean \u201ccan we have a button that allows me to filter X?\u201d or \u201ccan we add field Z to the existing report columns?\u201d<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-12499\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image0111.png\" alt=\"image01\" width=\"520\" height=\"245\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Photo credit: <\/span><\/i><a href=\"http:\/\/thenextweb.com\/creativity\/2015\/04\/27\/user-testing-explained\/\" target=\"_blank\" rel=\"noopener noreferrer\"><i><span style=\"font-weight: 400;\">The Next Web<\/span><\/i><\/a><\/p>\n<p><span style=\"font-weight: 400;\">Anyone familiar with an existing application will always think within the limits of that application. And this is not a good thing because we end up trying to find ways to simply \u201cfit\u201d new features into an existing screen. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">If someone requests a specific button or menu on the interface, ask them a series of <\/span><a href=\"http:\/\/www.productplan.com\/questions-product-managers-ask-customers\/\"><span style=\"font-weight: 400;\">questions<\/span><\/a><span style=\"font-weight: 400;\"> so that you can understand what actually trying to achieve. Some general questions that can help you probe more deeply and efficiently are:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Why do you need this functionality?<\/span><\/li>\n<\/ul>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">What do you expect to gain by having this functionality (save time, work faster, increase conversion by X%, etc.)?<\/span><\/li>\n<\/ul>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">Can you explain your business need to me without referencing the current interface?<\/span><\/li>\n<\/ul>\n<ul>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">What percentage of users will this feature positively impact?<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Once you\u2019ve collected more information about the actual functional\/business need, you should analyze the data to understand if, and how, it can be addressed satisfactorily. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">During your analysis you might realize that there\u2019s already a workaround that addresses the need. This can help to temporarily appease customers while you work toward figuring out the overall relevance of the need for your business and for your overall product vision.<br \/>\n<\/span><br \/>\n<span style=\"font-weight: 400;\">Once you understand the actual need, you may find that the current product already has everything required to accomplish this goal, but it just requires users proceed through multiple screens or processes. While an exhaustive multi-step process isn\u2019t great, you can at least articulate a workaround for customers who need a quick fix. This saves you from adding yet one more item to the interface. Most importantly, you buy yourself time to think more clearly about how to simplify the current multi-step process.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">2. Is the goal aligned with our short-term and long-term objectives?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">When a new feature request pops up, check if it fits into the short or long-term bucket. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let\u2019s say that as a company, one of your goals is to convert more \u201cfree trial\u201d customers into paying customers and ultimately increase the number of new customers by 10% within 1.5 years. You decide that in order to increase the conversion rate in that time period, one of the required actions is to create an engaging onboarding process.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-12501\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image036-1024x582.png\" alt=\"image03\" width=\"660\" height=\"375\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image036-1024x582.png 1024w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image036-528x300.png 528w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image036.png 1200w\" sizes=\"auto, (max-width: 660px) 100vw, 660px\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Photo credit: <\/span><\/i><a href=\"http:\/\/blog.kiip.me\/developers\/guide-successful-user-onboarding\/\" target=\"_blank\" rel=\"noopener noreferrer\"><i><span style=\"font-weight: 400;\">Kiip<\/span><\/i><\/a><\/p>\n<p><span style=\"font-weight: 400;\">The goal of increasing conversion rate would then fall into the \u201clong-term bucket\u201d and the creation of an engaging onboarding process would fall into the \u201cshort-term bucket\u201d. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">You may have two dev teams running in parallel: one to support existing functionality (so that existing customers don\u2019t feel neglected) and another to build the new educational content library. Any new feature requests would then have to be evaluated to see if it fits into that short-term objective. Anything that doesn\u2019t enhance the success of that that short-term objective must be set aside until it makes sense for the business to tackle the request. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">It\u2019s often deadly to try to sneak in something that doesn\u2019t clearly fit into the two buckets mentioned in this section because the feature is often hacked into the interface, without the proper care and attention from product managers and UX designers.<\/span><\/p>\n<\/section><section class=\"related-books-section\"><h3>Grab design ebooks created by best designers<\/h3><p class=\"section-desc\">All for free<\/p><ul class=\"related-books-list\"><li><figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/free-ui-ux-design-trends-2015-2016-ebook-bundle\/\" class=\"action-get-ebook\" data-name=\"The Definitive 2016 UX Design Trends Bundle\"><img loading=\"lazy\" decoding=\"async\" width=\"262\" height=\"375\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/12\/the-book_bundle1.png\" class=\"attachment-ebook-cover size-ebook-cover wp-post-image\" alt=\"the book bundle1\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/12\/the-book_bundle1.png 262w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/12\/the-book_bundle1-210x300.png 210w\" sizes=\"auto, (max-width: 262px) 100vw, 262px\" \/><\/a><\/figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/free-ui-ux-design-trends-2015-2016-ebook-bundle\/\" class=\"btn btn-ghost action-get-ebook\" data-name=\"The Definitive 2016 UX Design Trends Bundle\">Download<\/a><\/li><li><figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/ux-strategy-field-guide\/\" class=\"action-get-ebook\" data-name=\"The Field Guide to UX Strategy\"><img loading=\"lazy\" decoding=\"async\" width=\"262\" height=\"375\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/01\/the-book.png\" class=\"attachment-ebook-cover size-ebook-cover wp-post-image\" alt=\"the book\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/01\/the-book.png 262w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/01\/the-book-210x300.png 210w\" sizes=\"auto, (max-width: 262px) 100vw, 262px\" \/><\/a><\/figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/ux-strategy-field-guide\/\" class=\"btn btn-ghost action-get-ebook\" data-name=\"The Field Guide to UX Strategy\">Download<\/a><\/li><li><figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/ux-design-process-documentation-best-practices\/\" class=\"action-get-ebook\" data-name=\"UX Design Process Best Practices\"><img loading=\"lazy\" decoding=\"async\" width=\"262\" height=\"375\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/10\/book-knowledge-262x375.png\" class=\"attachment-ebook-cover size-ebook-cover wp-post-image\" alt=\"book knowledge\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/10\/book-knowledge-262x375.png 262w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/10\/book-knowledge-210x300.png 210w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/10\/book-knowledge.png 332w\" sizes=\"auto, (max-width: 262px) 100vw, 262px\" \/><\/a><\/figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/ux-design-process-documentation-best-practices\/\" class=\"btn btn-ghost action-get-ebook\" data-name=\"UX Design Process Best Practices\">Download<\/a><\/li><li><figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/guide-to-ux-design-process-and-documentation\/\" class=\"action-get-ebook\" data-name=\"The Guide to UX Design Process &#038; Documentation\"><img loading=\"lazy\" decoding=\"async\" width=\"262\" height=\"372\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/09\/The-Guide-to-UX-Design-Process-Documentation-262x372.jpg\" class=\"attachment-ebook-cover size-ebook-cover wp-post-image\" alt=\"The Guide to UX Design Process Documentation\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/09\/The-Guide-to-UX-Design-Process-Documentation.jpg 262w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/09\/The-Guide-to-UX-Design-Process-Documentation-211x300.jpg 211w\" sizes=\"auto, (max-width: 262px) 100vw, 262px\" \/><\/a><\/figure><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/guide-to-ux-design-process-and-documentation\/\" class=\"btn btn-ghost action-get-ebook\" data-name=\"The Guide to UX Design Process &#038; Documentation\">Download<\/a><\/li><\/ul><\/section><section class=\"related-books-section-single\"><section class=\"post-content-wrapper\"><figure><img loading=\"lazy\" decoding=\"async\" width=\"262\" height=\"372\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/09\/The-Guide-to-UX-Design-Process-Documentation-262x372.jpg\" class=\"attachment-ebook-cover size-ebook-cover wp-post-image\" alt=\"The Guide to UX Design Process Documentation\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/09\/The-Guide-to-UX-Design-Process-Documentation.jpg 262w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2015\/09\/The-Guide-to-UX-Design-Process-Documentation-211x300.jpg 211w\" sizes=\"auto, (max-width: 262px) 100vw, 262px\" \/><\/figure><article><h3>Do you want to know more about UI Design?<\/h3><p>Download 'The Guide to UX Design Process &#038; Documentation' <span>FOR FREE!<\/span><\/p><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/guide-to-ux-design-process-and-documentation\/\" class=\"btn btn-flat btn-darker action-get-ebook\">Download e-book for free<\/a><\/article><\/section><a href=\"#closeEbookPanel\" class=\"icon-close action-close-ebook-panel\">Close<\/a><\/section><section class=\"post-content-wrapper\">\n<h2><span style=\"font-weight: 400;\">3. Does it fit into our brand experience?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The phrase \u201cour competitors have it\u201d is often repeated as a reason for why a new feature should be implemented. But if a new feature cannot live up to or exceed your brand experience, then it shouldn\u2019t be implemented. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Coherence and consistency of your brand and user experience must go hand-in-hand.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let\u2019s say Competitor A has a \u201cMinimalist View\u201d that you decide to add into your product. Four months, later you notice that Competitor B has added a new reporting function, so you add it to your report interface. Then 12 later now Competitor C has added an \u201cexport to PDF\u201d functionality, so you do the same.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-12498\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image0011.png\" alt=\"image00\" width=\"721\" height=\"448\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image0011.png 740w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image0011-483x300.png 483w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image0011-290x180.png 290w\" sizes=\"auto, (max-width: 721px) 100vw, 721px\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Photo credit: <a href=\"https:\/\/blog.intercom.io\/what-does-feature-creep-look-like\/\" target=\"_blank\" rel=\"noopener noreferrer\">What Does Feature Creep Look Like?<\/a> by\u00a0<\/span><\/i><a href=\"http:\/\/intercom.io\" target=\"_blank\" rel=\"noopener noreferrer\"><i><span style=\"font-weight: 400;\">Intercom.io<\/span><\/i><\/a><\/p>\n<p><span style=\"font-weight: 400;\">As you continually try to keep up with your competitor, you enter a reactionary state of mind where it\u2019s simply about \u201cYou can do it, so I can do it too\u201d. And this is a surefire way to create a product that will show the tell-tale symptoms of Franken-UX. Over time it will become clear to users that there\u2019s isn\u2019t harmony in terms of the functionality offered, how it\u2019s implemented, and how it fits into the overall brand offering. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Your brand experience is something that needs to sit at the forefront of your mind whenever you\u2019re managing new feature requests. For some brands, their experience is defined by top-of-the-line security. For other brands, their experience centers on file collaboration. For other brands, it\u2019s high-end design editing capabilities. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Whatever you do, each new feature needs to represent that brand experience.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">4. Will it help us attract a new market?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">For companies looking to attract a new market of users\u2014be it demographically or geographically\u2014a new feature request needs to be analyzed within cultural and social contexts. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">If your company is currently considering an expansion to another country, then all new feature requests should be considered for your existing and future markets. Maybe a given feature isn\u2019t relevant for your current market but would be great for users in another region.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-12500\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image025-1024x503.png\" alt=\"image02\" width=\"660\" height=\"324\" srcset=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image025-1024x503.png 1024w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image025-611x300.png 611w, https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/image025.png 1956w\" sizes=\"auto, (max-width: 660px) 100vw, 660px\" \/><\/p>\n<p><i><span style=\"font-weight: 400;\">Photo credit: <\/span><\/i><a href=\"http:\/\/www.webdesignerdepot.com\/2015\/05\/how-we-redesigned-yelps-ux-with-remote-usability-testing\/\"><i><span style=\"font-weight: 400;\">Web Designer Depot<\/span><\/i><\/a><\/p>\n<p><span style=\"font-weight: 400;\">If each market will have its own region-specific product, then all you have to do is implement the feature for the relevant market(s) only. However, if all users across geographical zones will be using the same product, then it\u2019s essential to think about how the feature will be accessed. Should the feature be activated by a user setting or as an extra offering in a special subscription plan? <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Users in one region should not be penalized with features that are irrelevant for them. Faced with the evidence of your Franken-UX, they could very quickly lose interest in your product<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Conclusion<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Saying no to new product requests is never easy to do. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">And it\u2019s often very tempting to let a few things slide through the cracks because they appear to be \u201cquick wins\u201d (like rewriting the text in an error or confirmation message to make it more user-friendly). Anything outside of that can easily be a small, \u201cmanageable\u201d update or a beast that wreaks havoc on your UX. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">The culture of \u201cquick wins\u201d, however, can be a slippery slope. When new requests come in it\u2019s best to evaluate them against the 4 questions listed in this article.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">You have a responsibility to the business and users to protect the integrity of the product. By taking the time to evaluate each new feature request, you\u2019re ensuring that you, and the product team that relies heavily on you, are building engaging and relevant products for your users.<\/span><\/p>\n<p>For more UX and product design advice, check out the free 109-page guide <a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/ux-design-successful-elements-for-products\/\" target=\"_blank\" rel=\"noopener noreferrer\">The Elements of Successful UX Design<\/a>. The book deconstructs 24 examples from today&#8217;s top companies.<\/p>\n<p><a href=\"https:\/\/www.uxpin.com\/studio\/ebooks\/ux-design-successful-elements-for-products\/\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" src=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/87042076806348.waLDIkkTHQ2gbuX1fRvQ_height640.png\" alt=\"\" width=\"720\" height=\"377\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions. <\/p>\n","protected":false},"author":53,"featured_media":12502,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,17,172,6],"tags":[],"class_list":["post-12497","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-collaboration-2","category-product-design","category-ux-design"],"yoast_title":"","yoast_metadesc":"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.","acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.6 (Yoast SEO v27.6) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>4 Bottom-Line Questions for Avoiding Feature Bloat | UXPin<\/title>\n<meta name=\"description\" content=\"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.\" \/>\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.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"4 Bottom-Line Questions for Avoiding Feature Bloat\" \/>\n<meta property=\"og:description\" content=\"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/\" \/>\n<meta property=\"og:site_name\" content=\"Studio by UXPin\" \/>\n<meta property=\"article:published_time\" content=\"2016-02-20T03:16:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-04-22T13:37:09+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/simplicity-inline-1024x768.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"768\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Germaine Satia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Germaine Satia\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/\"},\"author\":{\"name\":\"Germaine Satia\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/#\\\/schema\\\/person\\\/ba090c81c0ad31a0f2e3b9e63f10f512\"},\"headline\":\"4 Bottom-Line Questions for Avoiding Feature Bloat\",\"datePublished\":\"2016-02-20T03:16:11+00:00\",\"dateModified\":\"2020-04-22T13:37:09+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/\"},\"wordCount\":1335,\"image\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/simplicity-inline-1024x768.jpg\",\"articleSection\":[\"Blog\",\"Collaboration\",\"Product Design\",\"UX Design\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/\",\"url\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/\",\"name\":\"4 Bottom-Line Questions for Avoiding Feature Bloat | UXPin\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/simplicity-inline-1024x768.jpg\",\"datePublished\":\"2016-02-20T03:16:11+00:00\",\"dateModified\":\"2020-04-22T13:37:09+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/#\\\/schema\\\/person\\\/ba090c81c0ad31a0f2e3b9e63f10f512\"},\"description\":\"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/simplicity-inline-1024x768.jpg\",\"contentUrl\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/wp-content\\\/uploads\\\/2016\\\/02\\\/simplicity-inline-1024x768.jpg\",\"width\":1024,\"height\":768,\"caption\":\"simplicity inline 1024x768\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/blog\\\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"4 Bottom-Line Questions for Avoiding Feature Bloat\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/#website\",\"url\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/\",\"name\":\"Studio by UXPin\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/#\\\/schema\\\/person\\\/ba090c81c0ad31a0f2e3b9e63f10f512\",\"name\":\"Germaine Satia\",\"description\":\"With knowledge of the U.S, European and African markets, Germaine is a Product Manager who uses her 14 years of experience to help companies build products and services that resonate with users. Her varied skillset - Product Management, Writing, UX, Training, QA - allows her to evaluate the needs of each brand, and team to propose solutions that work best for each context.\",\"url\":\"https:\\\/\\\/www.uxpin.com\\\/studio\\\/author\\\/germaine-satia\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"4 Bottom-Line Questions for Avoiding Feature Bloat | UXPin","description":"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.","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.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/","og_locale":"en_US","og_type":"article","og_title":"4 Bottom-Line Questions for Avoiding Feature Bloat","og_description":"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.","og_url":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/","og_site_name":"Studio by UXPin","article_published_time":"2016-02-20T03:16:11+00:00","article_modified_time":"2020-04-22T13:37:09+00:00","og_image":[{"width":1024,"height":768,"url":"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/simplicity-inline-1024x768.jpg","type":"image\/jpeg"}],"author":"Germaine Satia","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Germaine Satia","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#article","isPartOf":{"@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/"},"author":{"name":"Germaine Satia","@id":"https:\/\/www.uxpin.com\/studio\/#\/schema\/person\/ba090c81c0ad31a0f2e3b9e63f10f512"},"headline":"4 Bottom-Line Questions for Avoiding Feature Bloat","datePublished":"2016-02-20T03:16:11+00:00","dateModified":"2020-04-22T13:37:09+00:00","mainEntityOfPage":{"@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/"},"wordCount":1335,"image":{"@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#primaryimage"},"thumbnailUrl":"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/simplicity-inline-1024x768.jpg","articleSection":["Blog","Collaboration","Product Design","UX Design"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/","url":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/","name":"4 Bottom-Line Questions for Avoiding Feature Bloat | UXPin","isPartOf":{"@id":"https:\/\/www.uxpin.com\/studio\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#primaryimage"},"image":{"@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#primaryimage"},"thumbnailUrl":"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/simplicity-inline-1024x768.jpg","datePublished":"2016-02-20T03:16:11+00:00","dateModified":"2020-04-22T13:37:09+00:00","author":{"@id":"https:\/\/www.uxpin.com\/studio\/#\/schema\/person\/ba090c81c0ad31a0f2e3b9e63f10f512"},"description":"Product manager Germaine Satia explains how to focus your UX design despite feature requests from multiple directions.","breadcrumb":{"@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#primaryimage","url":"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/simplicity-inline-1024x768.jpg","contentUrl":"https:\/\/www.uxpin.com\/studio\/wp-content\/uploads\/2016\/02\/simplicity-inline-1024x768.jpg","width":1024,"height":768,"caption":"simplicity inline 1024x768"},{"@type":"BreadcrumbList","@id":"https:\/\/www.uxpin.com\/studio\/blog\/how-to-avoid-a-bloated-product-ux-when-considering-new-features\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.uxpin.com\/studio\/"},{"@type":"ListItem","position":2,"name":"4 Bottom-Line Questions for Avoiding Feature Bloat"}]},{"@type":"WebSite","@id":"https:\/\/www.uxpin.com\/studio\/#website","url":"https:\/\/www.uxpin.com\/studio\/","name":"Studio by UXPin","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.uxpin.com\/studio\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.uxpin.com\/studio\/#\/schema\/person\/ba090c81c0ad31a0f2e3b9e63f10f512","name":"Germaine Satia","description":"With knowledge of the U.S, European and African markets, Germaine is a Product Manager who uses her 14 years of experience to help companies build products and services that resonate with users. Her varied skillset - Product Management, Writing, UX, Training, QA - allows her to evaluate the needs of each brand, and team to propose solutions that work best for each context.","url":"https:\/\/www.uxpin.com\/studio\/author\/germaine-satia\/"}]}},"_links":{"self":[{"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/posts\/12497","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/users\/53"}],"replies":[{"embeddable":true,"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/comments?post=12497"}],"version-history":[{"count":0,"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/posts\/12497\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/media\/12502"}],"wp:attachment":[{"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/media?parent=12497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/categories?post=12497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.uxpin.com\/studio\/wp-json\/wp\/v2\/tags?post=12497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}