<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Amber Krishan on Medium]]></title>
        <description><![CDATA[Stories by Amber Krishan on Medium]]></description>
        <link>https://medium.com/@DisrupThis?source=rss-b30db98622ab------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jg5lrruOPneqGpMPHfMPFQ.jpeg</url>
            <title>Stories by Amber Krishan on Medium</title>
            <link>https://medium.com/@DisrupThis?source=rss-b30db98622ab------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:29:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DisrupThis/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AI-Native? Future-ready? — Go Design-Led first]]></title>
            <link>https://uxplanet.org/ai-native-future-ready-go-design-led-first-ea8edc242a3b?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea8edc242a3b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Wed, 24 Sep 2025 14:55:18 GMT</pubDate>
            <atom:updated>2025-09-24T14:55:18.634Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI-Native? Future-ready? — Go Design-Led first</h3><p><strong>To unlock real impact from AI, data, or emerging tech — design must lead.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0FcmVVk5u4mXVSmq" /></figure><p>Today, organizations are racing to embed AI, expand data capabilities, and modernize their digital systems — AI, automation, predictive analytics, immersive interfaces. And with it, a familiar pattern plays out:</p><ul><li>Teams rush to plug it in</li><li>Vendors showcase use cases</li><li>Businesses layer the new on top of the old</li></ul><p>But transformation doesn’t happen from plugging in tech.<br> <strong>It happens when you rethink how people experience your product — from exploration to decision, from interaction to trust.</strong></p><p>We need a <strong>design-led approach</strong> that reimagines how people interact, decide, trust, and act inside these systems.</p><h3>You Can’t Just “AIfy” the Lifecycle</h3><p>Most companies approach innovation like this:</p><ul><li>Automate a few flows</li><li>Add chat to support</li><li>Use LLMs to summarize data</li><li>Call it AI-first</li></ul><p>But this doesn’t lead to reinvention. It leads to <strong>patchwork systems</strong> — where complexity increases, but experience doesn’t improve or generates business value.</p><p>The same goes for other trends:</p><ul><li>Pushing personalization without redefining service logic</li><li>Using sensors or wearables without a behavioral model</li><li>Chasing Gen Z with the same CX structure as boomers</li></ul><p><strong>Tech alone won’t solve it. Design has to shape how tech shows up</strong></p><p>Design is often mistaken for cosmetic polish — the “nice to have” layer that comes after the real work is done. But in reality, design strategy is what defines how a business will deliver value in the first place. It connects customer behavior, business objectives, and technology capabilities into a coherent path to ROI. When companies implement new technologies first — and only later try to ‘apply design’ to make them usable or visually appealing — they miss the point. Design isn’t there to decorate technology. It’s there to shape business value.</p><h3>The Enterprise Challenge- Embracing New Tech</h3><p>Whether you’re embracing AI, data, RPA, or agentic architectures — <strong>innovation is ultimately about shaping how humans engage, convert, act, and TRUST</strong>.</p><p>One of the biggest challenges enterprises face when building agentic systems is rethinking how consumers will interact with them. Traditional approaches won’t work. The interaction needs to be reimagined from a lens of innovation and problem solving. What does an agentic-first customer experience look like? How do we build trust with systems that act autonomously — both for customers and operators? These are deep, behavioral questions. And this is where a design-led approach becomes critical.</p><p>Design leads by answering questions like:</p><ul><li>How does this system introduce itself to the user?</li><li>What behaviors are we trying to drive?</li><li>What emotional cues will build trust or motivation?</li><li>What should the system feel like — as a presence, not a UI?</li><li>Where do we step back and let the system lead?</li><li>How does it grow with the user?</li></ul><h3>Reimagining Use cases, Not Just Automating</h3><p>Let’s take one example: digital selling.</p><p>You could use AI to personalize emails, score leads, or generate responses.<br> Or you could <strong>reimagine the entire sales experience</strong>:</p><ul><li>An agentic system that knows your history</li><li>Remembers context</li><li>Understands preferences</li><li>Engages when timing is right</li><li>Helps you navigate decisions without push</li></ul><p>That’s not automation. That’s <strong>relationship at scale</strong>.</p><p>We’ve helped clients imagine similar shifts in:</p><ul><li><strong>Healthcare</strong>: AI-powered care companions that coach, escalate, and track across time</li><li><strong>Finance</strong>: Invisible banking layers that understand lifestyle patterns and automate action</li><li><strong>Commerce</strong>: Semantic journeys where the interface dissolves, and intent drives flow</li></ul><p>But none of these work unless design leads the way.</p><h3>A Design-Led Model for Future-Edge Transformation</h3><p>At <strong>Futurris</strong>, we help companies reframe their transformation efforts by leading with design:</p><ul><li>We envision <strong>new product &amp; customer experiences </strong>that reflect how behavior &amp; technology is shifting</li><li>We design <strong>agentic experiences</strong> that learn, adapt, and serve in real-time</li><li>We build frameworks that help teams move <strong>beyond SDLC</strong> toward behavior-led architecture</li></ul><h3>Tech is evolving fast — Design will Make It Work.</h3><p>AI is evolving rapidly.<br>New capabilities are arriving every month.<br>And customer behavior is shifting just as fast.</p><p>To stay ahead, companies can’t just react.<br> They have to rethink.</p><p>Not just what they build — but <strong>how they build</strong>.</p><blockquote><strong><em>Because in a world of intelligent systems, what wins isn’t just better tech. It’s better strategy &amp; experience.</em></strong></blockquote><p>And design is what makes that possible.</p><p>—</p><p><strong>Futurris helps companies envision, design, and engineer future-edge and agentic-first experiences that create real business outcomes.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea8edc242a3b" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/ai-native-future-ready-go-design-led-first-ea8edc242a3b">AI-Native? Future-ready? — Go Design-Led first</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI is not a Cost Saver. Use it to Reinvent Digital Value]]></title>
            <link>https://uxplanet.org/ai-is-not-a-cost-saver-use-it-to-reinvent-digital-value-a92c797aa9c4?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/a92c797aa9c4</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 10:56:31 GMT</pubDate>
            <atom:updated>2025-08-25T10:56:31.390Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why AI-led experiences must go beyond automation to reshape how we sell, serve, and scale.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xFqJrnnRyLHwfAQo" /></figure><p>For most companies today, AI means one thing: <strong>optimization</strong>.</p><ul><li>Automate repetitive tasks</li><li>Reduce human dependency</li><li>Cut support costs</li><li>Drive process efficiency</li></ul><p>This mindset isn’t wrong — but it’s <em>deeply limiting</em>.</p><p>Because if your entire AI ambition is built around internal savings, you’re missing its far more disruptive potential: <strong>to reinvent how your product creates and delivers value in the first place.</strong></p><h3>AI’s True Potential Lies in System Innovation</h3><p>AI isn’t just a tool to make existing workflows faster. It’s a catalyst to rethink <strong>how entire systems work</strong>.</p><p>We’re entering an era where AI lets us break out of legacy product metaphors — menus, flows, dashboards — and build <strong>intelligent, behavior-led ecosystems</strong> instead.</p><p>Not just smoother UIs.<br>Not just automated support.<br>But new <strong>experience paradigms</strong> across CX, service, and even revenue models.</p><p>This means stitching together different AI capabilities — recommendation, memory, language, prediction, orchestration — to create seamless, evolving, assistive systems that behave more like agents than interfaces.</p><h3>Example: The Future of Digital Selling</h3><p>Today’s e-commerce still looks like a catalog. Users browse, filter, add to cart, check out.</p><p>But now imagine this:</p><blockquote><em>“You returned your last pair. Based on that, and your upcoming travel, here’s a curated list I’ve prepared. Want me to hold them till payday?”</em></blockquote><p>No menus. No effort. Just contextual, memory-aware interaction that behaves like a <strong>personal sales assistant</strong>.</p><p>This is AI applied not for process automation — but for <strong>experience orchestration</strong>.<br> An interface that doesn’t just serve, but <strong>sells</strong>.</p><h3>Example: Redefining Digital Health Products</h3><p>Most health apps still focus on navigation — booking, records, vitals.</p><p>But an AI-powered care system could:</p><ul><li>Recognize stress or hormonal symptoms based on time patterns</li><li>Summarize everything your doctor needs in a contextual briefing</li><li>Adjust lifestyle guidance based on real-world behavior</li><li>Nudge you toward behavior change before the issue worsens</li></ul><p>This isn’t process improvement. It’s a <strong>system-level reimagination</strong> — where the product becomes your care partner.</p><h3>We Can’t Build These Systems with SDLC</h3><p>These kinds of agentic, intelligent, evolving experiences <strong>don’t emerge from feature roadmaps and phased delivery</strong>.</p><p>You can’t treat AI as a bolt-on.</p><p>You need <strong>new frameworks</strong> that start with:</p><ul><li><strong>Value creation</strong>, not screen flows</li><li><strong>Key behaviors</strong>, not requirements docs</li><li><strong>Experience orchestration</strong>, not IA</li><li><strong>Continuous learning</strong>, not static feature stacking</li></ul><p>The SDLC and traditional UX methodologies were built for stable needs, motivated users, and rigid architectures. That world is gone.</p><p>Today, <strong>your product must behave</strong> — respond, adapt, remember, guide.</p><h3>Final Word</h3><p>If you’re still using AI to “automate the flow,”<br> you’ve already missed the point.</p><p>AI isn’t here to improve the way we build.</p><p>It’s here to change <strong>what we build entirely</strong>.</p><p>And companies who understand that will stop shipping faster dashboards and start designing <strong>living systems of value</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a92c797aa9c4" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/ai-is-not-a-cost-saver-use-it-to-reinvent-digital-value-a92c797aa9c4">AI is not a Cost Saver. Use it to Reinvent Digital Value</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Stacking Features to Shaping Value: A New Product Building Model]]></title>
            <link>https://uxplanet.org/from-stacking-features-to-shaping-value-a-new-product-building-model-122c34a4ded2?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/122c34a4ded2</guid>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Fri, 13 Jun 2025 08:48:05 GMT</pubDate>
            <atom:updated>2025-06-13T08:48:05.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eTG-FHCmYuoHlcIi" /><figcaption>Photo by <a href="https://unsplash.com/@rgaleriacom?utm_source=medium&amp;utm_medium=referral">Ricardo Gomez Angel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For decades, software development has mirrored the construction industry — a manpower-heavy model where effort, hierarchy, and sequencing define how value is created. But that model is no longer working. Not for users. Not for businesses. And certainly not for the kind of dynamic, value-led experiences today’s market demands.</p><p>Let’s break it down.</p><h3><strong>Building software like a Construction Project</strong></h3><p>The traditional process of building software is eerily similar to a construction site. First, you collect “requirements” from stakeholders. Then, a budget is discussed, features are scoped, and everything is put into a phased roadmap. That roadmap is handed to product managers, who work with execution teams to begin “building.”</p><p>The metaphor continues:<br>You lay the foundation (the backend and data architecture).<br> You raise the structural skeleton (modules, features, tech stacks).<br> You install the fixtures (pages, flows, user controls).<br> And only then somewhere towards the very end — you call in design for making it “creative”.</p><p>At this point the design teams attempt to improve the product by applying design process. Teams organize features into an information architecture, then bundle them into menus, apply usability fixes, and run some user testing to improve comprehension. The assumption? This methodology of bringing value to end users will ensure that everything is there: a long list of features, ergonomics, and technology.</p><blockquote>why then would the users not love it?</blockquote><blockquote>But more and more, this process ends with a hard truth:<br><strong>The product doesn’t work.</strong></blockquote><blockquote>Users don’t engage. Drop-offs are high. Features are not discovered. Friction is everywhere.</blockquote><p>What happens next is even worse: teams start patch-fixing the product, tweaking labels &amp; features, and applying another round of “lipstick” — without questioning whether the product value, architecture, behavior model, or service logic is even relevant anymore.</p><p>This entire model is built on two faulty assumptions:</p><blockquote>#1 That users are motivated to go find value hidden inside your structure</blockquote><blockquote>#2 That features + IA + Easy UI = a successful product</blockquote><p>Neither holds true today. Users aren’t navigating mega menus. They’re not exploring tabs hoping to discover something useful. Whether it’s consumer apps or enterprise tools, they expect value to find <em>them</em> — immediately, intelligently, and repeatedly.</p><h3><strong>Products Are No Longer Menu Structures. They’re Living Systems of Value</strong></h3><p>The way people engage with digital products has fundamentally changed. The old IA-based approach — “let’s organize features and serve them through menus” — is no longer relevant.</p><p>Today’s users don’t want structure. They want <strong>service</strong>.<br> They expect the product to sense context, surface value, and adapt to their needs in real time. This is true even in complex domains — from productivity tools to trading platforms. The expectation is the same: <strong>“show me what I need, when I need it, enabling me to do what i want.”</strong></p><figure><img alt="https://cloudfresh.com/wp-content/uploads/2022/06/Automation_above_all.png" src="https://cdn-images-1.medium.com/max/1024/0*HkfX3vTYKDu83vTV.png" /><figcaption>Progressive disclosure of features, creating a contextual and clear case for users to do more</figcaption></figure><p>And this is where the traditional software building process breaks down completely. Because we’re still treating product delivery like a cataloging exercise — build the system, then arrange everything into folders and flows.</p><p>What we should be doing is designing <strong>living products</strong> that:</p><blockquote>Start with a powerful zero state</blockquote><blockquote>Use data to understand user context from the first click</blockquote><blockquote>Surface relevant value, information, working surface quickly — before users go hunting</blockquote><blockquote>Progressively disclose &amp; sell deeper features and upsell paths over time</blockquote><blockquote>Build a clear case for users to do more in the tool/surface</blockquote><blockquote>Lead users organically toward monetization</blockquote><blockquote>Keeps building in extensible value to ensure retention</blockquote><blockquote>Feel like they evolve with the user, not against them</blockquote><p>In this model, the product <em>sells itself</em>. It grows, adapts, and justifies its presence in the user’s life — not through frictionless UI, but through value delivered in flow.</p><p>And no, this can’t be achieved by “improving the IA” or running another round of user testing on pre-defined flows. That’s experience optimization. What we need is <strong>value-led product architecture</strong>.</p><h3><strong>VCPB — A New Methodology: Building Products around Value &amp; Behavior</strong></h3><p>The traditional software development process — structured like a construction site — was built for a world that no longer exists. It assumes we can gather all requirements, phase out delivery, and organize features like building blocks. At best, we optimize user flows toward the end. At worst, we mistake infrastructure for impact.</p><p>What we need now is an entirely new methodology — one that starts not with features, menus or screens, but with <strong>value</strong>. One that is shaped around behavior, powered by lean tech, and continuously evolves to serve both the business and the user.</p><p>Here’s how it needs to work:</p><h4><strong>Value: Define the Business Value</strong></h4><p>It is key to understand that businesses are built around value that they can offer their customers. The business needs to deliver this value and needs a vehicle for the same. The confluence of the value and monetization creates the business viability.</p><h4><strong>Service Strategy: Deliver Value Across the Service Experience</strong></h4><p>To create monetization around the value, a service experience strategy has to be created. This strategy aims at creating various ‘key Desired Behaviors’ (KDBs) from customers across the service lifecycle. To summarize to create monetization on the business value, we need to generate some KDBs across the service lifecycle. The ‘moments of connect’ where KDBs intersect the service lifecycle, we get <strong>touchpoints</strong> that will deliver that value. The entire purpose of creating a touchpoint is to create a KDB and deliver value.</p><h4>Behavior Strategy: Create KDBs</h4><p>At each touchpoint, build mechanisms that trigger and reinforce key desired behaviors. Apply ergonomics and psychology at play to influence customers. At each of those touchpoints, you design the logic, flow, and content to <strong>trigger and reinforce real behavior</strong>. This is not about “delight” or “clarity.” It’s about getting users to do what matters — to them and to the business.</p><h4><strong>Interaction Modality: match vehicle to touchpoint</strong></h4><p>Define how the touchpoint behavior strategy would be delivered. What surfaces, UI, interaction modality would be needed. Don’t assume full-screen flows. Explore WhatsApp, embedded PWAs, voice, or smart nudges.</p><p>This is where most teams fail. They assume the solution is always an app, a dashboard, or a full-screen interface. But users today interact with products across a dozen surfaces — and in shorter bursts. Design for the surface/interaction that best serves the behavior.</p><h4><strong>Enable with Technology: Data+AI+ROI</strong></h4><p>The system must feel intelligent — reacting to behavior, tailoring context, and adapting value dynamically. Look at available data, process and anticipate with AI, look at other AI or relevant technologies that would make ROI sense.</p><p>We no longer need massive teams to build feature stacks. Today, <strong>lean teams</strong> can build <strong>agentic systems</strong> — architectures that use data and AI to dynamically adapt, orchestrate workflows, and deliver value with precision.</p><p>Instead of stacking features, you’re <strong>orchestrating value delivery</strong>.<br>Instead of static product roadmaps, you’re building systems that learn and respond.<br>AI is not a bolt-on. It’s part of the core delivery engine.</p><h4><strong>Test for Real Behaviors</strong></h4><p>Not UI mocks. Not polished Figma files. Real, functioning prototypes that let you observe behavior in the wild. This is critical as the traditional software building process is aimed at improving comprehension, but we need to look at how to create real KDBs.</p><h3><strong>Conclusion: Shift from Feature Menu to Value base product Building</strong></h3><p>It’s critical to understand how the golden thread connects:<br><strong>from value → to key behaviors (KDBs) → to touchpoints → to interaction modality → to tech enablement.</strong></p><p>This isn’t just a more evolved way to build products.<br>It’s a complete inversion of how the industry has traditionally operated.</p><p>The SDLC — and everything it inspired — was built for a world of stable requirements, feature stacking, linear delivery, and motivated users. That world no longer exists.</p><p>Today, if your product doesn’t trigger the right behaviors, it doesn’t survive.</p><p>We’re long past the point where structure-first, manpower-driven builds make sense.<br>We can’t afford to treat software like a construction site — stacking features, layering flows, and painting design on top.</p><p>We need a system built around <strong>value creation, not volume delivery</strong>.</p><p>One that starts with the outcome, not the roadmap.<br>That operates in flow, not phases.<br>That learns, adapts, and sells itself — in real time.</p><p>We’re not building digital infrastructure anymore.<br>We’re building <strong>dynamic value systems</strong> that must work — fast, fluid, and alive.<br>And anything less will be forgotten.</p><p><em>I help companies reimagine how they deliver value across their entire digital ecosystem — from strategy to execution, product to service experience. Currently building this vision at www.Futurris.com<br> — Amber Krishan</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=122c34a4ded2" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/from-stacking-features-to-shaping-value-a-new-product-building-model-122c34a4ded2">From Stacking Features to Shaping Value: A New Product Building Model</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innovation ≠ building labs, it’s about survival culture]]></title>
            <link>https://medium.com/design-bootcamp/innovation-building-labs-its-about-survival-culture-36663a169f35?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/36663a169f35</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Sat, 31 May 2025 04:53:44 GMT</pubDate>
            <atom:updated>2025-05-31T11:28:54.309Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EEpjbEBjJwELyBl3" /><figcaption>Photo by <a href="https://unsplash.com/@xrexpo?utm_source=medium&amp;utm_medium=referral">XR Expo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s start with a quick look at the landscape. We see that various companies are striving to make a place in a highly competitive market with an increasingly discerning customer. We see many strategies at play. We see Incumbents trying to hold onto their legacy and established propositions, while the startups are pushing to dislodge them by disrupting models-products-services. Within this arena, the definition of success is mixed, with profitability models, and measurement based on valuation, both existing in the same battle ground, going after the same customers. With companies elbowing each other to gain traction, time-to-market has also become crucial and increasingly shorter. Product teams are racing to push out newer features every month.</p><p>As they race, teams are being pushed by executives to be more ‘innovative’ with every build. ‘Innovation’ is becoming one of the common words thrown around. In fact it is sincerely overused in all contexts where it is not clear on how to win. Yet, there doesn’t seem to be a methodology on how to do this or what does it really mean or what would it achieve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*ba-3whAH43GtKEcYzoP_Mg.png" /><figcaption>Source: Nairobi National Museum</figcaption></figure><p>I think it is imperative in this context to establish an understanding of ‘innovation’. Let me start this by telling you a story. A long time ago, when humans were starting out as a species in the Savannah, their brains developed an ability that is unique amongst animals. They could lie. If you have seen the movie ‘The Invention of Lying’, you would understand the relevance of how powerful this ability is. Lying is the ability to assume and state something that is not there. Most animals can’t do that. So in the Savannah, if there were a herd of buffalo in a valley and their food runs out. A buffalo won’t get up and say ‘I think that valley across 4 hills looks similar to ours and gets a lot of rain and quite likely would have food’, because that is a lie and a Buffalo cant do that. Where as the humans in the Savannah could do that. They could build stories around a future that doesn’t exist but is plausible, in order to increase their chances of survival. This unique ability was born out of the need to survive. What most companies don’t realize is that innovation is not a ‘nice to have’ which would make their PR look better but its about their core existence. Innovation is about survival.</p><blockquote><strong><em>“ </em></strong><em>What most companies don’t realize is that innovation is not a ‘nice to have’ which would make their PR look better but its about their core existence. Innovation is about survival. </em><strong><em>”</em></strong></blockquote><h3><strong>How do companies try doing Innovation?</strong></h3><p>So what happens in companies when the innovation mandate comes up? Well it depends upon the commitment behind the mandate. Very invested companies tend to build expensive innovation centers stocked with state-of-the-art infrastructure. I have had the opportunity of seeing such centres setup in companies in South Africa, South of india and other places of the world. One such centre had touchscreen coffee tables, Multi Smart board rooms, Cisco Telepresence and a giant interactive presentation wall. I was quite amazed at the sheer opulence and wondered on how It would contribute towards incubating innovation. I am of the opinion that great creativity is born out of adversity and not opulence. Which is probably why the best companies were started in someone’s garage with enough budget to keep everyone barely fed.</p><p><a href="https://www.capgemini.com/news/despite-mass-investment-innovation-centers-are-not-making-organizations-more-innovative/">Capgemini: Despite mass investment, innovation centers are not making organizations more innovative</a></p><p>Companies with smaller pockets or focus on innovation may setup teams who are responsible for innovating. So a bunch of people get together ever so often and talk about new and interesting ideas and then pat themselves on the back that they are being innovative and the executives pat themselves on the back that they have ‘innovation’ running within their organization.</p><p>Innovation is not an infrastructure problem or about putting together a team. It is an issue with the company culture. Within a small startup everything they do it innovation, from how they approach their product offering, to HR to finance. They take their core company objectives and attack them through the most plausible solution and then pivot and attack it from another, to get the best result. As the companies grow something happens to it, that prevents it from pivoting quickly and making decisions that are obvious. The construct of a large hierarchy brings in the inflexibility of being wrong and the constant need for being right.</p><p>Coming up with a set of random ‘out-of-box’ ideas through stipulated teams or expensive infrastructure doesn’t help companies survive, but through attacking their core objectives with multiple challenging/competing solutions to see what brings the best result. Often the most innovative solution is right in front but the company construct/culture does not allow for room to move and try such experiments.</p><p><a href="https://www.cbinsights.com/research/corporate-innovation-labs/?utm_source=CB+Insights+Newsletter&amp;utm_campaign=3fc944e5e5-Top_Research_Briefs_07_28_2018&amp;utm_medium=email&amp;utm_term=0_9dc0513989-3fc944e5e5-88188061">CB Insights: From AT&amp;T To Xerox — 73 Corporate Innovation Labs</a></p><h3>Why Innovation Labs Don’t Deliver</h3><p>When most companies say they want innovation, they reach for <strong>infrastructure</strong>:</p><ul><li>Build a shiny new innovation lab</li><li>Fill it with VR headsets, smartboards, beanbags</li><li>Add a Chief Innovation Officer</li><li>Run some workshops</li></ul><p>But what they’re actually doing is outsourcing risk — <strong>externalizing invention away from the business core</strong>. They treat innovation like a parallel stream, not a survival function. Which is why it rarely works.</p><p>The truth is: <strong>you can’t build innovation into a box</strong>.</p><h3>The Innovation That Matters Happens Culturally</h3><p>Real innovation doesn’t start with labs. It starts with behavior.</p><p>With how teams respond to uncertainty.<br>With how leaders react to incomplete data.<br>With how much emotional and operational tolerance an org has for shaping something that isn’t guaranteed.</p><p>You don’t need a million-dollar lab to do that.<br>You need to let your people lie — constructively.</p><p>You need to let them imagine and act on <strong>plausible futures</strong> — not just run efficient retrospectives.<br>Because at the end of the day, innovation is not about optics. It’s about whether your company can survive its next disruption.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36663a169f35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/innovation-building-labs-its-about-survival-culture-36663a169f35">Innovation ≠ building labs, it’s about survival culture</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Backflow Effect: Why Digital Product Building Is Rolling Up the Value Chain]]></title>
            <link>https://medium.com/design-bootcamp/the-backflow-effect-why-digital-product-building-is-rolling-up-the-value-chain-5c795bafaeae?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c795bafaeae</guid>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Fri, 09 May 2025 08:55:27 GMT</pubDate>
            <atom:updated>2025-05-09T09:42:49.101Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VtoxbO8WJ7N0fcvO" /><figcaption>Photo by <a href="https://unsplash.com/@cdd20?utm_source=medium&amp;utm_medium=referral">愚木混株 cdd20</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For years, the digital product landscape expanded outward, creating countless specialized roles and micro-businesses along the value chain. From development to deployment, from design to payment gateways, entire ecosystems of tools and services emerged — each offering a piece of the puzzle.</p><p>But now, a surprising backflow is underway.</p><p>Tools that were once niche — reserved for specific roles or purposes — are now <strong>rolling up the value chain</strong>, reclaiming the end-to-end building process. This shift is reshaping who builds, how they build, and who gets cut out of the picture.</p><h3>The Rise and Roll-Up of DIY Platforms</h3><p>First, we had <strong>Shopify</strong>, a game changer for small businesses. Suddenly, they could launch websites, integrate payment gateways, and manage ecommerce without hiring an entire tech team.</p><p>Next came <strong>Webflow</strong>, which democratized design-to-code workflows. Designers could visually craft websites without touching a line of code, cutting out developers and tightening the build cycle.</p><p>But now, it’s coming full circle with <strong>Figma</strong>.</p><h3>Figma’s New Play: From Design to Deployment</h3><p>Figma was once just a design tool. But as its capabilities evolve, it’s moving closer to being a complete product-building platform.</p><ul><li><strong>Web templates</strong> are being integrated.</li><li><strong>Component libraries</strong> are turning into complete UI systems.</li><li>Soon, we may see <strong>payment gateways</strong> and backend logic enter the mix.</li></ul><p>This is significant because it <strong>removes layers</strong> from the value chain. A designer can go from wireframe to functional product in a single tool, without passing off to separate teams or platforms.</p><h3>The Compression of Roles</h3><p>As tools like Figma absorb capabilities once distributed across multiple roles, we’re seeing a <strong>consolidation of functions</strong>:</p><ul><li>Designers are becoming <strong>product builders</strong>, not just interface creators.</li><li>Product managers can work directly in Figma, rather than interpreting design specs from separate teams.</li><li>Developers may no longer be needed for simple builds — Figma may handle it all.</li></ul><p>This means that many <strong>mid-chain businesses</strong> — agencies, freelancers, tech shops — that relied on handing off specific slices of the product build process may soon find themselves <strong>squeezed out</strong>.</p><h3>What Comes Next: The Rise of Micro Giants</h3><p>The backflow effect has just begun. Platforms like Figma are moving from single-purpose tools to <strong>end-to-end product ecosystems</strong> — where the product manager or business owner can <strong>build, launch, and scale products independently</strong> without needing to pass through multiple service layers.</p><p>This shift will give rise to a new breed of companies — the <strong>Micro Giants</strong>.</p><p><strong>Micro Giants</strong> are companies built with <strong>very small teams</strong> but capable of delivering <strong>large-scale impact</strong>. They don’t need extensive manpower or infrastructure. Instead, they leverage unified platforms that let them design, build, deploy, and monetize directly. The business owner or product manager <strong>becomes the product team</strong>, orchestrating value without outsourcing to a string of specialized roles.</p><p>For existing service providers — agencies, freelancers, and down-the-line tech shops — this backflow will trigger a strategic pivot. If product owners can do more in fewer steps, the middle layers of execution and production will need to <strong>move up the value stream</strong> to stay relevant.</p><p>In this new era, power won’t come from having the biggest team or the widest reach.<br> It will come from the ability to <strong>do more with less, build faster with fewer, and own the entire lifecycle</strong> — from vision to value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c795bafaeae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-backflow-effect-why-digital-product-building-is-rolling-up-the-value-chain-5c795bafaeae">The Backflow Effect: Why Digital Product Building Is Rolling Up the Value Chain</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Commoditization of AI Experience]]></title>
            <link>https://medium.com/nyc-design/commoditization-of-ai-experience-3371db539528?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/3371db539528</guid>
            <category><![CDATA[humancenteredstrategy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Sat, 19 Apr 2025 14:07:57 GMT</pubDate>
            <atom:updated>2025-04-19T14:07:57.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="https://cdn.prod.website-files.com/6401e02706e2048b13d47d12/64b530a7b6715693763b000f_646220dcf8fe494f03fafae9_canva2.png" src="https://cdn-images-1.medium.com/max/1024/0*d7As2saT7f_5JeNz.png" /></figure><p>There’s a lot of noise right now about AI. Boardrooms are buzzing, LinkedIn’s flooded, and every other product pitch has “agentic” or “LLM” bolted onto it. But let’s just pause and ask: do we really understand what AI <em>is</em> — and what it’s <em>not</em>?</p><p>Because somewhere along the way, AI became shorthand for one thing: LLMs. Just because a company called Open AI launched a sexy POC called chatgpt which dazzled the world and made it believe that “AI is finally here!…Chat interfaces, agents that sound vaguely human. And while that’s a sexy narrative, it’s a dangerously narrow lens.</p><p><strong>AI isn’t new.</strong><br> It’s not some magical force that was born in 2023. Computer vision, NLP, pattern recognition, predictive modeling — these have been in play for years. AI isn’t just one thing. It’s a field. A spectrum. To reduce it to “chat with your data” is like reducing the internet to email.</p><p>What’s happening now is less of a revolution and more of a reckoning. We’re not in the era of <em>AI-ification</em>. We’re in the era of <em>AI commoditization</em>. That’s a subtle but crucial distinction.</p><p>Let me explain.</p><h4><strong>The Metaverse déjà vu</strong></h4><p>A few years ago, I had a client ask me — with great urgency — why we weren’t building something in the metaverse for them. Not <em>what</em>, not <em>how</em>, just why we weren’t on the bandwagon.</p><blockquote>My only question was: <em>Why do you want it?</em><br>What’s the problem it solves?<br>What’s the value for your customer?<br>There was no clear answer. Just trend-chasing.</blockquote><p>AI is walking into the same trap. And this time, the stakes are higher.</p><h4><strong>Tech ≠ Experience</strong></h4><p>Good design, good products, good services — they don’t begin with tech. They begin with humans. With needs. With anxieties, habits, hopes. The moment you start AI-ifying an entire service lifecycle just because you <em>can</em>, you’ve lost the plot.</p><p>AI should be invisible. Integrated. Intelligent. Not plastered everywhere like a badge of futurism. Just like cloud, IoT, blockchain …the value is in the <em>application</em>, not the label.</p><h4><strong>So what’s really coming?</strong></h4><p>AI <em>will</em> be everywhere — but not in the way you think.</p><p>You won’t see massive banners saying “powered by GPT” on every flow. Instead, AI will get embedded silently — in onboarding journeys, support touchpoints, predictive nudges, backend intelligence. Not sexy. But deeply impactful.</p><blockquote>And that’s commoditization.<br>Not every product will become AI.<br>But every product will have AI in it — in ways you won’t even notice. That’s the turning point we’re at.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3371db539528" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/commoditization-of-ai-experience-3371db539528">Commoditization of AI Experience</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Is Failing Neo Businesses]]></title>
            <link>https://uxplanet.org/ux-is-failing-neo-businesses-99431c1e3874?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/99431c1e3874</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Mon, 14 Apr 2025 13:06:19 GMT</pubDate>
            <atom:updated>2025-04-14T13:06:19.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kTb3OxSakf1G2hDsMm2Zsg.jpeg" /><figcaption>Original Visualization of Transition to Disruption Economy, © 2018, Amber Krishan</figcaption></figure><h4>Rise of Neo Businesses</h4><p>The nature of building digital businesses has changed. Fundamentally.</p><p>We’re not just digitizing old models anymore. We’re operating in what can only be called the <strong>Disruption Economy</strong> — where customers have leapfrogged in behavior, and a new breed of companies has emerged to serve them in ways incumbents simply can’t keep up with.</p><p>These are <strong>Neo Businesses</strong>.<br>Fast, agile, tech-native — yes. But more importantly, they are <strong>thin</strong>, in-context, and behaviorally tuned. They don’t push customers into apps or long journeys. They meet them in moments — through WhatsApp, PWAs, mini-apps, voice interfaces, or embedded flows. No friction. No waiting. No bloated UIs.</p><p>In contrast, traditional businesses are still clinging to a <strong>transient economy mindset</strong>.<br>Heavy field ops. SMS engagement. Call center dependencies. Thick UI platforms loaded with menus and effort. It worked once — but the market has moved on. And so have the users.</p><p>Customers, having been hyper-exposed to digital choices, are no longer impressed by availability. They expect value — unique, fast, seamless value. They aren’t waiting to be onboarded. They want to be served <em>in flow</em>, <em>in context</em>, and <em>with minimal effort</em>.</p><p>This shift has broken the backbone of how we traditionally think about UX.</p><h4>Traditional UX process is failing in the disruption economy</h4><p>The UX process, in its current form, was built for a slower, more predictable world. But that world is long gone. In the disruption economy, where customer expectations have leapt forward, the old methods not only fall short — they actively hold businesses back.</p><p>Let’s break down why.</p><p><strong>It is</strong> <strong>Still Focused on Reskinning Channels: </strong>Too often, UX is mistaken for visual refreshes — UI cleanups, reorganized menus, minor flow improvements. There’s little reflection on whether the underlying interaction model is still relevant at all.</p><p>I remember when companies invested heavily in desktop website redesigns, even as mobile usage had already overtaken. It took years — and lost opportunities — for them to pivot. We’re now repeating the same mistake with mobile apps. Customers have moved to micro-touchpoints: chat interfaces, embedded flows, voice prompts, and thin experiences. Yet the UX process still optimizes for pages and screens.</p><p>The challenge with the UX process remains as it still does not focus on really understanding how customers want to engage with businesses through various channels. UX teams are polishing surfaces while the floor beneath has already shifted.</p><p><strong>It Overlooks Value in Favor of Usability: </strong>Traditional UX focuses heavily on improving flow — reducing friction, clarifying labels, improving discoverability. All important. But none of it matters if the product itself doesn’t deliver value that feels immediate and relevant.</p><p>Today, users judge a product by its utility — not just its aesthetics. If there’s no clear value in the first 30 seconds, the experience is dead on arrival. Customers now more than ever engage with the value of the product first than how smooth the experience is made out to be. Optimizing journeys means little if you haven’t evaluated whether those journeys are worth taking at all.</p><p><strong>Speed to Market: </strong>The old UX process assumes time: time to research, to design, to iterate, to test. But Neo Businesses are operating in a hyper-competitive space where time is the biggest risk.</p><p>If a process takes months to deliver validated designs, the market may have moved on. Startups need to launch quickly, test real behavior, and adapt in real time. UX can no longer be a standalone pre-build phase. It has to run in parallel with product strategy, engineering, and growth.</p><p>Anything slower becomes drag.</p><p><strong>Prioritizes visual/conceptual wow Over Buildability: </strong>Designing the experience is one thing. Getting it built to a high level of quality — fast — is another. In many cases, the handoff between design and development is where things fall apart.</p><p>Today’s customers compare your product experience not to your category competitors, but to everything else on their phone. If your app feels less polished than Uber, Swiggy, or Instagram, it fails. The expectation bar has risen — and UX has to design with real constraints, tech feasibility, and delivery clarity in mind.</p><p>Buildability isn’t a technical concern anymore. It’s a user experience concern. With the multitude of well-crafted experiences to compare with customers will now be quite finicky when it comes to evaluating your product experience. A high focus on buildability is key for experience design to be successful.</p><p><strong>Ends Too Early: </strong>In many organizations, the UX team is involved during the early stages — research, flows, mockups. Once the handoff happens, they step back.</p><p>But Neo Businesses don’t operate in phases. They operate in loops. You can’t create a meaningful experience without staying through launch, post-launch, stabilization, and optimization. You have to see what performs, what doesn’t, and how real behavior unfolds. To enable success for the product, a partnership along the whole product lifecycle is needed. It is only when you have seen the product launch, stabilize, and grow that certainty of success can be attained.</p><p>Otherwise, you’re designing in theory — not reality.</p><h4><strong>The Path Forward</strong></h4><p>UX process has to be revisited. Not as a set of deliverables, but as a system that ties business value to behavior, behavior to design, and design to outcome. It needs to work across atypical channels. It must prioritize thin interactions, real-time adaptation, and continuous presence across the product lifecycle.</p><blockquote>Because Neo Businesses don’t need more interfaces.<br>They need outcomes.<br>And UX, if it wants to stay relevant, must become the engine that drives them.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99431c1e3874" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/ux-is-failing-neo-businesses-99431c1e3874">UX Is Failing Neo Businesses</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thin Era: Evolution of Service Experience Beyond UI]]></title>
            <link>https://medium.com/nyc-design/thin-era-evolution-of-service-experience-beyond-ui-ee32c791de40?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee32c791de40</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Fri, 11 Apr 2025 12:50:56 GMT</pubDate>
            <atom:updated>2025-04-11T12:50:56.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pG7-mk1fKnXGBPR5" /><figcaption>Photo by <a href="https://unsplash.com/@alvarordesign?utm_source=medium&amp;utm_medium=referral">Alvaro Reyes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We didn’t notice it happen.</p><p>One moment we were designing apps and dashboards, the next — the software had all but disappeared. Interfaces started thinning out, intelligence crept into the background, and customers began expecting more from less.</p><p>We are in the middle of a service transformation so fundamental, it’s hard to even label it. But if we must — let’s call it beginning of <em>The Thin Era</em>. And it didn’t arrive out of nowhere. It’s been decades in the making.</p><p>Let’s rewind.</p><p><strong>The Manual Era</strong></p><p>There was a time when service meant physical effort. You wanted to pay your bills? You stood in line. You needed groceries? You went where they were available — and prayed there wasn’t a crowd.</p><p>Customers were trained to make peace with inconvenience. Interaction <em>was</em> the experience. It was slow, manual, painful — and that was just how the world worked.</p><p><strong>The Expansion Era</strong></p><p>Eventually, access became the battleground. More bank branches, more retail stores, more physical points of service. The decentralization of service was a massive step forward. For the first time, convenience was location-driven. Brands felt closer, more reachable. But the experience still lived in brick and mortar.</p><p><strong>The Call Center Era</strong></p><p>Then came the leap — not in technology, but in thinking.</p><p>What if customers didn’t need to go anywhere? What if service came to them — via a call, a menu, a polite voice in a different city?</p><p>This was the telephony + cheap labor combo that gave rise to giant call centers. From India to the Philippines, intelligence was outsourced — and service became something you accessed through a number, not a door.</p><p>It was clunky, but it worked. For a while.</p><p><strong>The Automation Era</strong></p><p>But as margins shrank and cost of operations grew, even call centers started feeling expensive. This ushered in automation.</p><p>Service became a decision-tree — masked as a voice. IVRs, SMS, pre-recorded instructions — the goal was no longer delight, it was deflection. Get the customer what they need without ever needing a human. Automation wasn’t a strategy — it was a cost-saving imperative.</p><p><strong>The DIY + UI Era</strong></p><p>Somewhere in between, smartphones happened. Suddenly, everyone wanted control — and no one wanted to talk. This was the rise of self-service.</p><p>Apps, websites, PWAs — the customer journey was now a fully digitized maze of screens. Every service needed a UI. Every task became a flow. Brands invested in design systems, user journeys, and accessibility audits. The idea was: if we can’t serve them faster, let’s at least make it feel smoother.</p><p>But smooth is not always smart.</p><p><strong>The Conversational Era</strong></p><p>Design started realizing its limits. Apps were great, but they made users <em>work</em>. So we reintroduced conversation. Not the clunky kind from IVRs — but bots that typed, listened, and learned.</p><p>Except… not really.</p><p>The bots were mostly glorified scripts, with a thin layer of NLP sprinkled on top. The intelligence was still limited. And while the user experience improved, the service delivery model remained rooted in triggers, flows, and pre-set paths.</p><p><strong>And now: The Thin Era</strong></p><p>We’re entering a fundamentally different phase — one that isn’t being led by UI, or even conversation. It’s being led by <strong>architecture</strong>.</p><p>Service delivery is no longer screen-first. It’s intelligence-first.</p><p>AI — not just as an LLM or a chatbot, but in multiple embedded forms — is now becoming the core of the experience. It’s not bolted on. It’s baked in.</p><p>This shift is reshaping the service paradigm in five big ways:</p><p><strong>Anticipation, not navigation</strong>: Users don’t want to search, dig, or tap through menus. They expect the system to know. To sense. To suggest. Thin experiences remove the burden of decision-making by using data and inference, not just UI.</p><p><strong>Omni-awareness</strong>: When a customer starts on a website and ends up on WhatsApp, the system shouldn’t start from scratch. There’s a rising expectation that brands remember — not just your name, but your last action, your intent, and your context.</p><p><strong>Omni baton-passing</strong>: Not just omnichannel journeys, but intelligent handovers. A conversation started on one touchpoint picks up exactly where it left off, across another — seamlessly. No more repeating yourself.</p><p><strong>Hyper-personalization</strong>: The system knows if you’re a parent, a business owner, or a first-timer. It adapts responses, nudges, even pricing. This is real-time intelligence shaping micro-experiences.</p><p><strong>Cost of intelligence drops further</strong>: Earlier, intelligent service was powered by humans in faraway centers. Now, it’s powered by embedded AI that scales infinitely, learns endlessly, and costs marginally. This isn’t just automation. This is cognitive deflation.</p><p><strong>Design, data, content, and commerce are no longer separate teams. They are one fused system — delivering service invisibly.</strong></p><p>When service becomes this thin, it starts to feel almost magical.</p><p>But it’s not magic. It’s a new architecture. One that demands new thinking, new talent, and a very different mindset for product builders.</p><p>So if you’re still mapping screens, you might already be behind.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee32c791de40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/thin-era-evolution-of-service-experience-beyond-ui-ee32c791de40">Thin Era: Evolution of Service Experience Beyond UI</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Business Empathy?]]></title>
            <link>https://uxplanet.org/what-is-business-empathy-80df7c5c9463?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/80df7c5c9463</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 12:47:13 GMT</pubDate>
            <atom:updated>2024-06-24T12:47:13.136Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hint: You need it to design digital products</h4><p>In the context where businesses have recognized the value of UX design as part of building successful digital products and great businesses, it is no longer the question of “Do we need to hire designers”.</p><p>As someone who interacts with many young designers &amp; students who are starting their journey, the common question I now get is…” What do designers do in a company”.</p><p>Do they…</p><ul><li>Conduct research with users</li><li>Deliver designs made in Figma</li><li>Make products user friendly &amp; easy</li><li>Reduce the number of clicks</li><li>Make the digital product more aesthetically pleasing</li></ul><p>The real answer of course is…” It depends”…for each company tends to use designers differently. In some companies it may be for strategic work, in some, it could be crafting customer experience, and in some, it is purely executing what is sketched for you on paper. I digress… let’s get back on topic.</p><p>Let&#39;s talk about the term usability or user-friendly. Commonly used terms that both businesses and designers feel are the end value of doing digital design work. Is it all about just making things easier?…so if we make the product easier what would happen? Would it ensure that the business would see the impact on their revenue or bottom line?… maybe not.</p><p>Making things easier or reducing clicks does not give certainty of business success. Users still may not onboard, perform transactions, sign up for offerings, or want to pay you just because the experience of using the product is easy.</p><blockquote>It is very critical to understand that designers are not in the business of making things “user friendly”</blockquote><p><strong>Designers craft experiences that create behaviors that achieve business outcomes.</strong> You are in the business of creating or changing behavior to drive business numbers. To be able to craft such business-centric behavior what does it take?</p><h3>You need “Business Empathy”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Kd2UbSsfgaoZyHUd" /><figcaption>Photo by <a href="https://unsplash.com/@victoriano?utm_source=medium&amp;utm_medium=referral">Victoriano Izquierdo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>While most product teams hail “User empathy” as the secret sauce, to make products user-friendly &amp; successful…The critical ingredient may be ‘Business empathy’. The ability to influence user behavior to create business outcomes lies within the unique context of the business you are building the product. This ability to understand each business’s unique context is called business empathy.</p><p>Some critical questions to ask to build ‘business empathy’</p><ul><li>What customer types are you trying to influence?</li><li>What is your unique value to these customer types?</li><li>How exactly do you make or save money in this context?</li><li>How does the market landscape look in terms of your approach to these customers vs how competition is attacking them?</li><li>What do you know is already going to happen in the near future and how are you strategically placed to respond?</li><li>What objective are you trying to achieve agnostic of the envisioned digital product?</li><li>How do you think you will win?</li></ul><h3>Focus on Key Desired Behaviors (KDBs)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Is-EGEqx6JPlraYB" /><figcaption>Photo by <a href="https://unsplash.com/@aginsbrook?utm_source=medium&amp;utm_medium=referral">Anthony Fomin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For businesses to win the next critical ingredient is ‘Key Desired Behaviors’. Businesses are built on behaviors that they can manifest and thus make money off of. These desired behaviors may or may not be natural to the target customers and this requires careful strategies to actually create them.</p><p>The ability to create a behavior always stems from understanding existing ‘Real Behavior…but how?</p><p>We must conduct user research! because that is the genesis of understanding human behavior and the possibilities of how we may influence the same. This is definitely, a critical piece since our ability to influence behavior lies very clearly within the context of existing behavior. Observing their natural conduct and exploring what could possibly trigger, motivate, and then finally create behavior is key. Focus on…</p><ul><li>What are your customers actually doing and not just saying?</li><li>What part of their natural behavior presents an opportunity for you to trigger and then create additional behaviors that benefit you?</li><li>What behaviors do you need to influence or create to succeed?</li></ul><h3>Strategy with applied psychology &amp; ergonomics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P4Rg3BuAnH9dX_-U" /><figcaption>Photo by <a href="https://unsplash.com/@halacious?utm_source=medium&amp;utm_medium=referral">Hal Gatewood</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Once the KDBs are identified and you have significant clarity on the real behaviors within which these would lie…create your strategy.</p><p>Craft and imagine an experience…a storyboard if you may. That would describe how the user within their real behavior would get started &amp; deliver the KDB. What tools in your ergonomics or psychology arsenal would you use to create this?</p><p>Trigger: It starts with a clear trigger within real behavior which would catch the customer’s interest, create intrigue, and seed an idea.</p><p>Build up: To take the customer deeper, a layer of tools could be used to raise motivation levels to cross the threshold of creating behavior.</p><p>Pressure: Building motivation brings the customer to a crescendo but does not create the urgency of ‘Now’. What tools would you use to drive the user to perform the KDB at the moment, preventing them from deferring the act or how would you ensure that they would perform the same in a relevant moment later?</p><p>Imagine all this coming together, like a movie director…imagining and crafting each moment to create a desired emotion and end effect. Agnostics of channels, UI, &amp; technology… it&#39;s about defining how the KDB would manifest across touchpoints and not about sketching a UI flow needed to stitch together an app.</p><h3>Bringing it to life with Technology</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NFY2ZxkewNsHwbWw" /><figcaption>Photo by <a href="https://unsplash.com/@rafahansen?utm_source=medium&amp;utm_medium=referral">RAFA HANSEN</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Post testing &amp; iterating your strategy through prototypes and other constructs, it&#39;s time to build the touchpoints. Focus on how you would enable each touchpoint across surfaces rather than crafting together information architectures &amp; enabling navigation.</p><p>Each touchpoint will require the right front-end and back-end technologies to enable the experience. Keeping an eye on ROI is key as it may not be practical to implement AI-based or high-investment solutions. Critical to not get carried away with the trending technology…so if AI is cool…everything about your experience design can&#39;t be AI.</p><p>Ask the following critical questions…</p><ul><li>to enable these touchpoints do I need a multi-channel, omni-channel, or cross-channel strategy?</li><li>What all surfaces &amp; modalities will work in tandem to deliver the experience?</li><li>What part will you enable through AI, UI, Object, Or Human?</li><li>Given the tech stack availability, what is the practicality of the implementation? In terms of cost &amp; GTM?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aSDQwONEg-enKgZG" /><figcaption>Photo by <a href="https://unsplash.com/@mehdisepehri?utm_source=medium&amp;utm_medium=referral">Mehdi Sepehri</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a quick summary…</p><p>As a designer, you will be bombarded with philosophies on ‘Ease of Use’ or UX optimization. It is quite easy to lose focus and drive away from the clear purpose of how you are helping businesses succeed. So remember…</p><blockquote>Designers craft experiences that create behaviors that achieve business outcomes.</blockquote><ul><li>Develop ‘Business Empathy’ to define the context in which you have to win</li><li>Identify the KDBs</li><li>Create strategies with applied psychology &amp; ergonomics to create the KDBs</li><li>Bring strategies to life with technology, pragmatically</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80df7c5c9463" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/what-is-business-empathy-80df7c5c9463">What is Business Empathy?</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business-Centric UX Design]]></title>
            <link>https://uxplanet.org/business-centric-ux-design-fc1d5b0f3434?source=rss-b30db98622ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc1d5b0f3434</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Amber Krishan]]></dc:creator>
            <pubDate>Sun, 20 Jun 2021 07:12:21 GMT</pubDate>
            <atom:updated>2021-06-20T07:12:21.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*DpqMNFnh_V5K04Y-mZjfxw.png" /><figcaption>Photo by <a href="https://unsplash.com/@sstoppo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">SUNBEAM PHOTOGRAPHY</a> on <a href="https://unsplash.com/s/photos/innovation?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>So you want to do UX design, and then start with learning Figma, some After effects, add some card sorting for information architecture, protocols for research sounds like fun, Wireframing+Design thinking, Visual Styling, and then you are all set!</p><p>Is it that simple? Why do products fail then after so much hard work being put behind applying the process and all these great abilities to build beautiful screens?</p><p>Is there something UX designers are missing out on? Well…it might be the depth of their understanding of business and value proposition.</p><p>Before requirements are crafted and then land at your desk for you to start building screens and flows around, a lot of groundwork has gone into place. A score of people from across the business, product, marketing, finance, etc got together and came up with what they thought would be successful as an Idea and now they want you to make it. The challenge is that they may have already set you up for failure!</p><p>If you want to save yourself from building the wrong thing it&#39;s time for you to go deep diving into business. What should you understand about business? well…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p3zeeXb5G0qHGlFEA_1RBg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lino_thaesler?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lino Thaesler</a> on <a href="https://unsplash.com/s/photos/diving?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Business domain</strong> is not just about understanding business terms &amp; concepts. It has to do with getting a sense of the nature of business and how it works in a particular domain. This can tell you a great deal about where you can add value. If the nature of business is very dependent upon how customers perceive it, then you could help in transforming the upfront surfaces like public website, marketing collateral, onboarding journeys. In another case it might be that business primarily runs on client relationships then you could help with enabling their sales team better or improving the product funnel points such that they can show better performance numbers.</p><p><strong>The business context</strong> will take you deep into how the company was built, the legacy, where have they reached, what market &amp; competitive challenges are they facing. How have they built their solutions is also key to give you a sense of what technology challenges may be coming your way.</p><p><strong>The model</strong> is about how do they make money. It is a percentage on each transaction, is it Ad revenue, is it commission or is the model still being realized. This helps you to design your product experience around the various facets of how the model works.</p><p><strong>Strategic abilities &amp; advantages</strong> help with understanding what can be leveraged to further the success of the product. It might be a strong brand, tech stack, specific product capability, or suite of other products that you could build on top of. This is key for you to understand why they are likely to win in the venture they are undertaking.</p><p><strong>Landscape momentum</strong> is complex and crucial. It is about looking at multiple moving parts, like icebergs that are floating with their own momentum that may collide in various ways. What are all the type of target customers within the landscape, how are these customer changing over time, what propositions are competitors bringing into the landscape over time to go after these, how is the company bringing their own value over time to own more of the market, what would disrupt the market, what other forces are at play? This is imperative to understand as the product experience you build will be launched into a state of flux. Remember the world doesn&#39;t stand still for you to launch your product proposition and it is always about hitting the ground running!</p><p><strong>Target audience</strong> is a no-brainer but then what about the target audience should you understand. Not the typical demographic data which then has barely any relation to what you end up designing. Focus on the user’s objectives in context to your product. Also the key behaviors you expect around how they would use the product in context. We design for behaviors, not for demographics.</p><p><strong>Vision &amp; Business objectives </strong>are about how do they imagine the product to work in the future and what business objectives would they meet. Its imagination from the business point of view if all goes well and they are celebrating their success and year down the line. Then it is just about how you make this all together ‘no so hard’ vision happen.</p><p><strong>Why Now?</strong> Important to get a sense of what are they trying to achieve in the current context? Do they have to launch something before the competitor does or their sales team is struggling without a clear brand they can market? Is it something that should get launched during the pandemic time as it is a dire need? What are they trying to achieve and why?</p><p><strong>Product value</strong> is about clarity on what exactly provides the strongest customer motivation. It is not about a laundry list of features but explaining in one single sentence what is so great about the product that customers will be driven to signup and start using it immediately.</p><p><strong>Brand expectations</strong> are beyond color palette, images, and fonts. It is about how do they want their customers to feel when interacting with their service. Then interaction experience, communication tonality, and visual styling are derivatives of the same.</p><p><strong>Competitive context </strong>is not about looking at the UI of competitors and seeing what we could learn from that. It is a bit like investigating what is going on behind the scenes. What are they building now and in the future? How could they stand to win? How would you have to position yourself to win?</p><p><strong>Key desired behaviors</strong> that they would like their customers to start doing such that in correlation their business objectives will start looking real. Key means 4–5 and not a wishlist of 80. The more clear and focussed we are about this, the better the product design structure and flows are going to work overall.</p><p><strong>Known challenges, Customer feedback &amp; Product Data</strong> are a must-have. Dig through what they have on this. Rummage through strategy decks, previous projects, etc to build a robust understanding of this.</p><p>As a designer in today’s context, we are constantly looking to upskill to then build products of higher visual, emotive, and business value. And online content is teaming with courses, articles, and sermons on what you should learn. Coming from my experience in the design education field as well as being a design practitioner/leader, when it comes to UX you have to start becoming business-centric to give direction &amp; shape to your creative talents. Try to look at the business from the lens that I have shared above from across my career of building for wide range of businesses and see if it gives you a whole new context on how you could design &amp; build successful products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc1d5b0f3434" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/business-centric-ux-design-fc1d5b0f3434">Business-Centric UX Design</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>