{"id":18,"date":"2022-11-06T03:19:15","date_gmt":"2022-11-06T03:19:15","guid":{"rendered":"https:\/\/chaitanyachopra.com\/blog\/?p=18"},"modified":"2022-11-06T18:59:19","modified_gmt":"2022-11-06T18:59:19","slug":"matchup-product-features-vs-platform-scalability-guess-who-wins","status":"publish","type":"post","link":"https:\/\/chaitanyachopra.com\/blog\/index.php\/2022\/11\/06\/matchup-product-features-vs-platform-scalability-guess-who-wins\/","title":{"rendered":"Matchup: Product Features vs. Platform Scalability (Guess who wins?)"},"content":{"rendered":"\n

This article was originally published at Medium<\/a> on Jun 27, 2020<\/strong><\/p>\n\n\n\n

Over the number of years, there has been an enraging debate on whether investing significant resources to define a complete architecture makes sense, while product decisions still need to be determined and carved for readiness. Introducing iterative delivery framework is immensely helpful but also becomes increasingly difficult to understand and map the business expectations, however granular they might be, versus the architecture decisions to be made to provide value to the customers. In essence, architecture is about trust.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The product manager collaborates with stakeholders to understand their features and pins them down on benefits of feature requests, the stakeholder expects their features to be delivered, exactly the way they have in their head, and architecture is supposed to understand all the business priorities, that might come up during design phase, and make sure they all can be accounted for any opportunity that hasn\u2019t been unlocked or realized yet. I know it is a worded statement but a perfect case for Catch-22<\/a>.<\/p>\n\n\n\n

Value Proposition isn\u2019t linear.<\/h1>\n\n\n\n

Unlocking customer value is harder than it looks. There is an unlimited amount of permutations and combinations that can uncover a value proposition. Millennials, Gen X, Gen Y, Baby Boomers, and realize value radically different than each other. Let\u2019s take an example of a drastically simple example of purchase pattern:<\/p>\n\n\n\n

Baby Boomers<\/strong>: They won\u2019t trust the product until they feel it themselves. More importantly, the reputation and longevity of an outlet matter to them deeply. In many cases, they might be buying from the same mom-and-pop shop even if this point of sale hasn\u2019t upgraded their offering. Learning here is not to radically modify their experience. Whichever product line you might be working with, if they are your targeted audience, these will struggle the most and could eventually become a target of the less-savvy-more-copy-cat product line offering from a competitor.<\/p>\n\n\n\n

Millennials<\/strong>: They are less motivated by the perceived value of the product but more focused on the value proposition of their intended purchase. Is the company socially responsible? Does the sustenance outweigh an artificial value of the product? But, don\u2019t make the mistake of all the Millenials being the same. They also value the celebrity value of the product. Are their influencers attached to the product? Fyre Festival<\/a> got it right (at least, that part) by using their social influencers to promote something humanly impossible. And it worked, and Millenials showed up.<\/p>\n\n\n\n

\n

\u201cWhile Fyre itself was a disaster, the marketing choices behind it were not. It just shows how powerful influencers can be.\u201d<\/em><\/p>\n-Rohan Midha, PMYB<\/em><\/cite><\/blockquote>\n\n\n\n

Gen Z<\/strong>: They are a notch level above Millenials. While they follow most of their principles, their brand loyalty is close to none<\/a>. They respect the brands for what they represent, far more than how millennials look at them. The brands should be authentic, not copy-paste from other products with similar offerings, and should uniquely reflect on Gen Z\u2019s personality.<\/p>\n\n\n\n

\"\"
Something as predictable as Grocery shopping can also have generational variances.<\/em><\/figcaption><\/figure>\n\n\n\n

Now, I might seem like I\u2018m\u2019 slightly deviating from the topic; these underpinnings are far greater <\/em>than just designing a product. Imagine designing experiences with product managers and then architecting them in an evolving phase while keeping your targetted generation(s) content and connected.<\/p>\n\n\n\n

From Point A to B \u2014 Consistently.<\/h1>\n\n\n\n

I won\u2019t call myself savvy in chess, but I am constantly amazed by the powers of the queen in this mastermind game. While king could make you lose the game, often losing her during any point of the game is inching you closer to defeat anyways. The market is stacked with products, willing to offer the most bang for the buck to your customers. The focus is on features enablement, but it is expensive to lose sight of CX. CX isn\u2019t just about UX; it also ensures that your customer can consistently complete their intended journey all the time.<\/p>\n\n\n\n

\"\"
CX is the soul of your product, but it requires continuous nurturing.<\/em><\/figcaption><\/figure>\n\n\n\n

Product features continuously evolve and aim to provide a rich experience to the targeted audience. Amid this value proposition, architecture scalability justifies its importance in terms of gaining an edge with your customers. Everyone loves to give an example of Amazon, so let\u2019s take one from that page. I have rarely seen my journey interrupted while browsing for wonderful gadgets (that I rarely need but still buy them). Is their CX perfect? Heck, no. But is it consistent: I\u2019d repeat: Hasn\u2019t interrupted my intended journey (yet). But having a Subaru, running reliably and predictably, is much better than a Ferrari breaking down often. Well, unless you have a lot of cash to burn.<\/p>\n\n\n\n

Scale It or Nail It<\/h1>\n\n\n\n

There is always a battle between building features vs. scalability: Product Manager consistently keeps it in the back of their mind while driving CX and adding features to a product line for themes and Architecture is constantly battling with technical scalability of the underlying codebase supporting the product line. But scalability is a dual-faceted. There is often a cascading effect of not starting with a scalability-first approach, but it should also be done analytically.<\/p>\n\n\n\n

\"\"
Dave has an excellent blog post<\/a> on the methodical approach to scaling your digital product. Source: Boldare<\/figcaption><\/figure>\n\n\n\n

When a Feature is being dissected, two most important roles should be present and actively participating (other than a product manager): An Architecture SME and Principal Architect leading the feature team. Why two architects? Doesn\u2019t that sound like overkill? Let me attempt to convince you.<\/p>\n\n\n\n

Architecture SME<\/strong>: By definition, this individual drives the strategic direction of the product from a technical perspective. They are worried about Enterprise Scalability to be able to offer products in multiple facets. This is critical because it sets the GPS to the desired destination strategically. Let\u2019s elaborate on this with a specific example. When the product is in envisioning stages, the market segment is identified along with the delivery mechanism. If you product is specializing in digital delivery, you have to be conscious of platform selection, revenue models, delivery modes, and, more importantly, the future path of evolution of the product. Knowing this, even at a 30K foot level, guides the Architecture SME to get into tool selection with a focus on future scalability. It doesn\u2019t need to be addressed today but cannot be ignored, either.<\/p>\n\n\n\n

Principal Architect<\/strong>: Just like a wine sommelier knows more than just the wine, they can also advise one in pairings. These architects understand the underlying technology, powering these features extremely well. They can lend their expertise in advising in possibilities and also making the right decisions to account for scalability. And it just doesn\u2019t end there \u2014 Consider them as an expert that pairs with technical delivery teams to ensure this scalability embeds in the heart of the implementation. Think in our earlier example; the beta product should be identified and implemented with strategic guidance from Architecture SME. So, if a mobile device is the focus area for launch, but it also has a Desktop delivery mechanism in the future, you want to ensure that your functions will be available and compatible with additional platforms on the roadmap. I\u2019ll end this article with a great quote from the lead programmer<\/a> of my favorite childhood games (Quake, Doom).<\/p>\n\n\n\n

\n

The cost of adding a feature isn\u2019t just the time it takes to code it. The cost also includes the addition of an obstacle to future expansion. The trick is to pick the features that don\u2019t fight each other.<\/em><\/p>\n– John Carmack<\/em><\/cite><\/blockquote>\n\n\n\n

PS: It would be unfair to end this article by calling a winner: Gist of it is that they both are. You cannot ignore one while continue to build castles on others. Features are as important as scalability and vice versa.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

This article was originally published at Medium on Jun 27, 2020 Over the number of years, there has been an enraging debate on whether investing significant resources to define a complete architecture makes sense, while product decisions still need to be determined and carved for readiness. Introducing iterative delivery framework is immensely helpful but also…<\/p>\n","protected":false},"author":1,"featured_media":20,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[8],"tags":[5,6],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/18"}],"collection":[{"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=18"}],"version-history":[{"count":0,"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/18\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/media\/20"}],"wp:attachment":[{"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=18"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=18"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chaitanyachopra.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=18"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}