<?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 Omid Iravani on Medium]]></title>
        <description><![CDATA[Stories by Omid Iravani on Medium]]></description>
        <link>https://medium.com/@omidiravani?source=rss-ea8c5f4ff212------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Cu7YblATfFY_lNXlmmLVsQ.jpeg</url>
            <title>Stories by Omid Iravani on Medium</title>
            <link>https://medium.com/@omidiravani?source=rss-ea8c5f4ff212------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:29:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@omidiravani/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[When Numbers Speak: Rethinking a Contact Experience Through Data]]></title>
            <link>https://omidiravani.medium.com/when-numbers-speak-rethinking-a-contact-experience-through-data-c1ba24606e57?source=rss-ea8c5f4ff212------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1ba24606e57</guid>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[conversion-optimization]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Omid Iravani]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 08:22:37 GMT</pubDate>
            <atom:updated>2025-11-04T08:22:37.545Z</atom:updated>
            <content:encoded><![CDATA[<p>It started with a simple contact form.<br>A few fields. A submit button. And the quiet assumption that people would actually use it.</p><blockquote>They didn’t.</blockquote><p>Analytics told us something we hadn’t noticed. Users hesitated, scrolled, and left. The numbers weren’t just numbers. They were signals, showing what our design missed.</p><p>At first, it seemed like a minor UX issue. But the more we looked, the more we realized this was bigger. A story about trust, intent, and friction how even the smallest interface can reveal them.</p><p>We weren’t just redesigning a form. We were redesigning the first impression the gateway to a better experience.</p><p>This article walks through what the numbers taught us, the hypotheses we tested, the solutions we tried, and why some ideas didn’t make the cut.</p><p>Because conversions aren’t won by flashy buttons or shiny visuals. They’re won by understanding what the numbers are really saying.</p><h3>What the Numbers Mean?</h3><p>When we say <em>“the numbers,”</em> we’re talking about more than just counts or percentages. We mean the signals that show how users are actually behaving and where friction happens.</p><p>Some of the metrics we looked at:</p><ul><li><strong>Conversion rate:</strong> the percentage of visitors who actually submitted the form. For example, if 1,000 people visited the page and only 20 submitted, the conversion rate is 2%.</li><li><strong>Drop-off points:</strong> places where users start filling the form but leave before finishing. Session recordings and heatmaps help us spot these exact moments.</li><li><strong>Field hesitation</strong>: how long users pause before entering information in each field. Long hesitation can mean confusion or mistrust.</li><li><strong>Device behavior:</strong> differences between desktop and mobile users. Are mobile visitors more likely to leave? Are they scrolling less?</li></ul><p>These numbers don’t just tell us <em>what</em> happened. They tell us <em>why</em> it happened. For example, a low conversion rate could be a sign that the form feels intimidating, unclear, or simply untrustworthy. Hesitation on one field can reveal exactly where we’re losing people.</p><p>By looking closely at these metrics, we can turn raw data into insights and insights into better design decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WF0rwDwo2TPtDEKtW-sCCg.png" /><figcaption>Every hover, scroll, and click tells a story. Analytics turns behavior into insight.</figcaption></figure><h3>What the Numbers Told Us</h3><p>Before we touched a single pixel, we dove into Google Analytics to understand how users were interacting with the contact form. The data told a clear story.</p><h4><strong>Key metrics we tracked:</strong></h4><ul><li><strong>Pageviews:</strong> The contact page received <strong>2,500 unique visits</strong> per month. Plenty of traffic, but…</li><li><strong>Form submissions (conversion rate):</strong> Only <strong>2.8%</strong> of visitors actually submitted the form.</li></ul><h4><strong>Field-specific drop-offs (tracked via event tracking):</strong></h4><ul><li><strong>Name field:</strong> 10% abandoned here.</li><li><strong>Email field:</strong> 25% abandoned.</li><li><strong>Phone number field:</strong> 35% abandoned.</li><li><strong>Message field:</strong> 40% abandoned.</li><li><strong>CTA click rate:</strong> Only 3.5% of users clicked the submit button before leaving.</li><li><strong>Scroll depth:</strong> 45% of users didn’t scroll past the first screen, meaning they might not have seen all form instructions or disclaimers.</li></ul><h4><strong>Device breakdown:</strong></h4><ul><li><strong>Mobile:</strong> 60% of visits, with a <strong>3x higher abandonment</strong> than desktop.</li><li><strong>Desktop:</strong> 40% of visits, lower drop-off but still a weak conversion rate.</li><li><strong>Session duration on page:</strong> Average <strong>45 seconds</strong>, indicating hesitation or confusion.</li></ul><h4><strong>Event tracking insights:</strong></h4><ul><li>Hovering on input fields was frequent, but no interaction followed in some cases.</li><li>Clicks on the form outside the CTA button (like trying to click labels or placeholders) were common a sign of unclear affordances.</li></ul><p><strong>What this told us:</strong></p><ul><li>Users hesitated most on the fields where personal information was required.</li><li>Mobile experience was significantly more fragile than desktop.</li><li>The page had enough traffic, but the form itself was the bottleneck.</li><li>Micro-interactions (hovering, scrolling, partial typing) showed intent, but not completion friction was the main issue.</li></ul><blockquote><em>This analysis gave us a clear starting point: </em><strong><em>any redesign had to reduce friction, clarify intent, and improve trust</em></strong><em>, especially for mobile users.</em></blockquote><h3>User Behavior Insights</h3><p>Before touching a single pixel, we dove into the data. Not just pageviews or submissions we looked at <strong>how users actually interacted</strong> with the Contact Us form.</p><p>Here’s what we found:</p><ul><li><strong>Hover and hesitation:</strong> Users often hovered over fields, paused for several seconds, then moved on. Long hesitation signals confusion or mistrust.</li><li><strong>Partial typing:</strong> Many started typing and abandoned mid-field, revealing friction before completion.</li><li><strong>Clicks outside CTA:</strong> Clicking on labels, placeholders, or empty space instead of the submit button indicated unclear affordances.</li><li><strong>Scroll behavior:</strong> Nearly half the visitors didn’t scroll past the first screen they missed instructions or disclaimers entirely.</li></ul><p>Understanding these behaviors gave us a <strong>starting point for redesign</strong>: reduce friction, clarify intent, and improve trust especially for mobile users. Micro-interactions like these were <strong>early warnings</strong>, showing us exactly where users would drop off if nothing changed.</p><h3>What We Learned from the Fields</h3><p>One of the clearest insights we gained from analytics was how <strong>form length directly affected conversion</strong>. The data showed that users were dropping off at a much higher rate once they reached the third input field and almost completely abandoning the process when faced with more than four.</p><p>This wasn’t just our assumption; it’s consistent with broader research.<br> According to a <a href="https://blog.hubspot.com/blog/tabid/6307/bid/6746/Which-Types-of-Form-Fields-Lower-Landing-Page-Conversions.aspx">HubSpot study</a> analyzing over 40,000 landing pages, <strong>conversion rates drop significantly when forms go from three to four fields.</strong> The difference might look small on the surface -<strong>a single field</strong>- but in user behavior, that extra step often becomes a breaking point.</p><p>Interestingly, it wasn’t just about the <strong>number</strong> of fields, but also their <strong>type</strong>.<br> Text areas and dropdowns performed notably worse than simple text inputs, especially when users needed to “think” about their answers instead of simply typing or selecting a short value. Every extra second of hesitation multiplied the risk of abandonment.</p><p>We also saw that users hesitated longer on optional fields proof that even <em>asking</em> for too much information can create friction, regardless of whether it’s required. Simplifying structure and grouping fields contextually (for instance, asking for contact details after intent is confirmed) helped reduce cognitive load and made the form feel faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ciwi_2cfcez0EOyvtnd52w.jpeg" /><figcaption>Highlight that 3-field forms have the highest conversion</figcaption></figure><h3>Column Layout: One vs. Two</h3><p>When it comes to form design, layout is just as important as the number of fields. In a <a href="https://blog.hubspot.com/marketing/one-vs-two-column-form-conversion-test">conversion test by HubSpot</a>, switching from a <strong>single-column</strong> to a <strong>two-column</strong> layout actually increased submission rates by <strong>22%,</strong> a surprising result for something most designers assume is a settled rule.</p><p>The reason? Context. HubSpot’s form had <strong>13 fields</strong>, and stacking them vertically made the page look long, intimidating, and heavy. By placing related fields side by side like “First Name” and “Last Name” the form felt shorter and more approachable without sacrificing clarity.</p><p>This finding highlights an important truth:<br><strong>There’s no universal best practice.</strong> The ideal layout depends on your form length, device context, and user behavior.<br>In our tests, we found that combining both patterns a <strong>hybrid layout</strong> with a clean vertical flow and subtle horizontal grouping often delivers the best results.</p><h3>Button Color: Why It Matters but Isn’t Everything</h3><p>When redesigning a contact form, button color often becomes one of the most debated design details. But data (and research) shows: <strong>it’s not about having the “perfect” color, it’s about visibility and context.</strong></p><p><strong>What the analytics and research told us:</strong></p><ul><li>CTA click-through rate before redesign was <strong>around 3-4%</strong>.</li><li>A study by <a href="https://optinmonster.com/which-color-button-converts-best/">OptinMonster</a> found that red buttons often outperform others because of contrast, not because red itself “converts better.”</li><li>In one example, red outperformed green only because the page background was predominantly green. The real driver was <strong>contrast</strong>, not color preference.</li></ul><p><strong>Design takeaway:</strong></p><ul><li>High-contrast colors tend to draw attention more effectively.</li><li>Button color should always align with the page’s visual hierarchy and brand tone.</li><li>Overly aggressive hues (like bright red) may boost clicks short-term but can reduce perceived trust in premium or service-oriented contexts.</li></ul><blockquote><em>The best CTA color is the one that stands out without shouting.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kTV-bvvYVRX8ZRbYnlTpPw.jpeg" /><figcaption>Red, green, blue… what feels right?</figcaption></figure><h3>Setting the Right Expectations After Submission</h3><p>When users fill out a <strong>Contact Us form</strong>, they’re already taking a small leap of trust and sharing their information without knowing what happens next. That uncertainty can easily cause hesitation right before submission.</p><p>As highlighted in <a href="https://wpforms.com/wpforms-submit-button-best-practices/">WPForms’ guide on submit button best practices</a>, generic labels like <em>“Submit”</em> don’t give users enough clarity or confidence. Replacing them with action-oriented and context-aware phrases like <em>“Send Message”</em>, <em>“Request a Call”</em>, or <em>“Get in Touch”</em> can make a measurable difference and improving conversion rates by <strong>25–30%</strong> in some cases.</p><blockquote><em>By clearly communicating what happens after clicking the button, you reduce friction and build trust</em></blockquote><h3>Why We Focused on the Contact Form</h3><p>Contact forms are notoriously prone to abandonment. According to <a href="https://formstory.io/learn/form-abandonment-statistics/">FormStory</a> Across industries, the average abandonment rates are staggering:</p><ul><li><strong>Automotive:</strong> 82%</li><li><strong>Airlines:</strong> 81%</li><li><strong>Nonprofits:</strong> 77.9%</li><li><strong>Finance:</strong> 75.7%</li><li><strong>Retail:</strong> 75.8%</li><li><strong>Travel:</strong> 49%</li><li><strong>E-commerce:</strong> 49%</li><li><strong>Property:</strong> 48%</li></ul><p>At first glance, a “simple” form might not seem worth the fuss. But with over <strong>50% of users abandoning forms</strong>, even in property at <strong>48%</strong>, this single touchpoint can make or break a lead. Fixing it isn’t just design it’s <strong>turning interest into action</strong>.</p><p>For us, it wasn’t just any form. In the property sector, the <strong>Contact Us form is often the primary bridge between user interest and actionable business opportunities</strong>. Potential buyers rarely engage without this, it’s the first real step toward a conversation, a viewing, or a contract.</p><p>So even though forms are easily abandoned, <strong>optimizing this one touchpoint had the potential for outsized impact</strong>. Every drop-off prevented meant a higher chance of turning a visitor into a lead, and a lead into a satisfied customer. The stakes justified the effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T3uIkTLcdfa2vrC7meJ5rg.jpeg" /><figcaption>sleek, professional look suitable for property websites</figcaption></figure><h3>Testing, Results &amp; Key Takeaways</h3><p>Redesigning a form isn’t about guessing what might work it’s about <strong>testing, observing, and iterating</strong>.</p><p>We started with a set of hypotheses:</p><ol><li><strong>Fewer fields = higher completion</strong>: We suspected that shortening the form would reduce drop-offs.</li><li><strong>Clear CTA copy = more clicks</strong>: Changing “Submit” to a descriptive, action-oriented label could boost conversion.</li><li><strong>Visual hierarchy matters</strong>: Users respond better when the form guides them visually from top to bottom, especially on mobile.</li><li><strong>Trust signals reduce hesitation</strong>: Adding small microcopy cues (“We respect your privacy”) could reassure hesitant users.</li></ol><p>Each hypothesis was tested using event tracking, scroll depth, and micro-interaction analysis from Google Analytics.</p><p><strong>What the data showed:</strong></p><ul><li>Reducing fields from 5 to 3 improved completion rates by almost <strong>40%</strong>.</li><li>Changing the CTA to something descriptive increased clicks by <strong>25–30%</strong></li><li>Reordering fields based on user intent and grouping optional info at the end reduced hesitation on key fields.</li><li>Trust microcopy led to fewer abandonments on sensitive fields like phone numbers and emails.</li></ul><p><strong>Lessons learned:</strong></p><ul><li>Data-driven tweaks, even small ones, can have <strong>outsized impact</strong> on conversion.</li><li>Observing <strong>micro-behaviors</strong> hovering, partial typing, scroll depth reveals friction points that raw conversion rates hide.</li><li>What works for one industry or user segment might not work for another; testing in context is key.</li><li>Every change should <strong>align UX with user intent</strong>: clarity, trust, and friction reduction are the real drivers behind better performance.</li></ul><blockquote>In short: <strong>don’t guess, measure. Don’t assume, test. And always turn insights into actionable design decisions.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1ba24606e57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Machines Design: A Critique of AI-Driven UX Decisions]]></title>
            <link>https://omidiravani.medium.com/when-machines-design-a-critique-of-ai-driven-ux-decisions-0a7b675cdcc1?source=rss-ea8c5f4ff212------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a7b675cdcc1</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Omid Iravani]]></dc:creator>
            <pubDate>Sun, 25 May 2025 07:20:12 GMT</pubDate>
            <atom:updated>2025-05-25T09:16:13.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wRQxZQHhCWFNeyTb4xHkTA.png" /></figure><p>We’ve all seen them, those AI-generated UI screens that look… almost right. The colors are balanced, the layout is familiar, and nothing’s exactly wrong. But it also feels like no one really thought about <strong>you</strong> when designing it. That’s because, well, no one did.</p><p>AI might be fast, even impressive. But when it comes to <strong>user experience</strong>, speed and beauty aren’t enough. There’s a deeper layer, one that understands frustration, habits, context, and emotion. And that’s where AI still struggles.</p><h3>A quick look at how AI “sees” your designs</h3><p>Models like CNN (Convolutional Neural Networks) are the go-to for visual processing. They work by scanning an image and looking for patterns, edges, shapes, shadows, and repetitions. They don’t “see” an image the way we do; they analyze it layer by layer, from pixels to patterns.</p><p>Sure, they can tell that a rectangle with text and a drop shadow is probably a button. But they don’t know if that button causes anxiety, confusion, or even joy. They don’t know the <strong>why</strong>, and that’s what UX is built on.</p><h3>So, how does a CNN actually work?</h3><p>Convolutional Neural Networks (CNNs) are one of the most common models used in image processing, especially when the task involves recognizing objects, faces, or interface elements.</p><p>To put it simply, a CNN sees an image as a matrix of numbers. Each pixel is just a number representing how bright it is or what color it has. Then the image goes through several stages:</p><ul><li><strong>Convolution:</strong> Filters (also called kernels) slide over the image like magnifying glasses, looking for simple patterns, edges, lines, textures.</li><li><strong>Activation:</strong> Functions like ReLU decide which patterns are meaningful and ignore the rest.</li><li><strong>Pooling:</strong> The data gets compressed, keeping only the most important features and reducing the complexity.</li><li><strong>Fully Connected Layers:</strong> At the end, all this data turns into a prediction like “this looks like a button” or “there’s a pizza in this image.”</li></ul><blockquote>CNNs are good at learning <em>what looks like what</em> but not <em>why</em> something is there, or <em>how</em> it makes someone feel. And that’s where human designers still have the upper hand.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*zEB8z_TS_loA7BKOfK4NMQ.gif" /><figcaption><a href="https://poloclub.github.io/cnn-explainer/">Watch how the CNN</a> starts to “see” — this filter is scanning the image to pick up basic patterns like edges and lines.</figcaption></figure><h3>UX isn’t about shapes, it’s about meaning</h3><p>Let’s be clear: machines are getting better at spotting visual patterns. But UX is more than that. It’s about asking:</p><ul><li>What’s the user trying to do here?</li><li>What’s stopping them?</li><li>What do they feel at this moment?</li></ul><p>A machine can’t answer those. It can simulate understanding, sure. But simulation is not the same as <strong>empathy</strong>.</p><blockquote><em>“Good design is about clarity. Great design is about empathy.”<br> — </em>Dan Saffer</blockquote><h3>More data ≠ more understanding</h3><p>Some systems go even further, using models like RNNs to track user behavior over time, or GNNs to analyze relationships between actions. That might sound like personalization. But often, it’s just prediction.</p><p>AI sees that users like dark themes and shorter forms. Great. But it doesn’t ask <strong>why</strong>. And that’s dangerous , because designing from patterns alone can lead to lazy decisions. You end up building interfaces that feel generic, even manipulative.</p><p>Figma put it well in one of their blog posts:</p><blockquote><em>“AI won’t replace designers. But designers who use AI will replace those who don’t.”<br> — </em>Figma blog, 2023</blockquote><p>That’s true. But it also means <strong>we’re still responsible.</strong></p><h3><strong>So what do we do?</strong></h3><p>Use AI. It’s a great assistant. Let it suggest things, save time, automate boring stuff. But don’t hand it the keys to the user experience. It doesn’t know what it means to be human.</p><blockquote>And UX, at its core, is about humans, not just pixels.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a7b675cdcc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Guessing What Users Want: Focus on What They Really Need with ODI]]></title>
            <link>https://omidiravani.medium.com/stop-guessing-what-users-want-focus-on-what-they-really-need-with-odi-e0f771df17b1?source=rss-ea8c5f4ff212------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0f771df17b1</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Omid Iravani]]></dc:creator>
            <pubDate>Sun, 09 Mar 2025 08:47:28 GMT</pubDate>
            <atom:updated>2025-03-09T12:55:31.411Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Some people say, ‘Give the customers what they want.’ But that’s not my approach. Our job is to figure out what they’re going to want before they do.”</blockquote><blockquote>— <strong>Steve Jobs</strong></blockquote><blockquote>“If I had asked people what they wanted, they would have said faster horses.”</blockquote><blockquote>— <strong>Henry Ford</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gb6gCzHdqSIv5Atb5j6wFA.jpeg" /><figcaption><a href="https://de.wikipedia.org/wiki/Datei:Ford_1921.jpg">Ford knew that true innovation wasn’t about faster horses</a></figcaption></figure><p>These famous quotes show a fundamental difference among what customers say they need and <strong>what they really want</strong>. Many companies design products based totally on consumer requests, which regularly ends in ignored opportunities to create absolutely revolutionary answers. While users often understand what they like, they are not continually privy to the deeper issues they are going through or the better solutions that would meet their unspoken wishes. This is where <strong>Outcome-Driven Innovation (ODI)</strong> will become a game-changer.</p><p><strong>ODI </strong>changes the point of interest from merely fulfilling user needs to understanding the actual results users are seeking for. It’s approximately designing products that address the basis reasons of user frustration and offer meaningful, long-time period price. Instead of reacting to requests for more features, ODI allows designers to work on what customers <strong>sincerely need</strong>, even if they didn&#39;t express it.</p><h3>Traditional Product Design vs. ODI</h3><p>In traditional product design, there’s often a <strong>one-size-fits-all</strong> vision, where the focus is placed on responding to <strong>direct feedback</strong> from users and making instant improvements. However, this doesn’t always lead to development innovations or real user satisfaction. Let’s break it down:</p><h4><strong>Traditional Approach:</strong></h4><ul><li><strong>Relies on direct user feedback:</strong> Companies frequently ask users what they want and build features around those responses.</li><li><strong>Adds features users ask for:</strong> The focus is on simply improving or adding new features that users can see and immediately work with.</li><li><strong>Competes on market:</strong> Product design decisions are often based on what is trending in the market or what competitors are doing right now.</li></ul><p>Conversely, <strong>ODI is concerned with the larger picture:</strong></p><h4><strong>ODI Approach:</strong></h4><ul><li><strong>Prioritizes the “Job-to-be-Done”:</strong> Identifying the primary problem that users are attempting to resolve and designing around that.</li><li><strong>Captures hidden user needs:</strong> It far exceeds what is said by users and uncovers greater understanding of their needs and frustrations.</li><li><strong>It optimizes for desired outcomes, not just new features:</strong> Instead of delivering new features users ask for, ODI will aim to optimize the product to produce significant outcomes.</li></ul><p>Take smartphones, for instance. When users complained regarding <strong>battery life</strong>, every company would simply include <strong>larger batteries</strong>, hoping that would do the trick. <strong>Apple </strong>took a different approach: instead of simply designing larger batteries, they focused on <strong>power efficiency</strong>. By making the software lighter and using power-efficient chips, Apple provided a solution that fulfilled the real-world requirements of more usage time with less need to recharge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HS9ngOY2DT3vmL05wtwQgQ.jpeg" /><figcaption><a href="https://www.amazon.de/What-Customers-Want-Outcome-Driven-Breakthrough-ebook/dp/B000RG17R2">What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services</a></figcaption></figure><h3>How to Implement ODI in Product Design</h3><p>Implementing ODI involves a shift in how you approach product design. It requires deep user empathy, data-driven decisions, and a focus on real-world outcomes. Here’s how you can apply ODI in your product design process:</p><h4><strong>Find the Essential Job-to-be-Done</strong></h4><ul><li>What exact issue is the user trying to fix?</li><li>Is this issue particularly critical to the user?<br>Start by finding the underlying “job” people are leasing the product to accomplish. This isn’t a skin-deep need — it’s finding the underlying job people are trying to accomplish.</li></ul><h4><strong>Define Desired Outcomes</strong></h4><ul><li>What does success for users look like in solving this issue?</li><li>What makes their experience better?<br>Define what a success result would be. What measurable outcome would indicate that the user is satisfied? Discussing measurable outcomes guarantees that you design solutions that truly make a difference in users’ lives.</li></ul><h4><strong>Assess Pain Points &amp; Gaps</strong></h4><ul><li>Where are the users having most of the pains in the current process or product?</li><li>What’s missing in the current solutions that would address the user’s job-to-be-done?<br>Dive deep into the user journey and identify where current products or solutions are falling short. These pain points will guide you to areas where innovation is needed the most.</li></ul><h4><strong>Design for Real Solutions</strong></h4><ul><li>Focus on creating solutions that directly address users’ real needs, not just their requests.</li><li><strong>Optimize the user experience (UX)</strong> to provide meaningful value, rather than just adding features for the sake of it.<br>Ensure that your design addresses the pain points you’ve identified and leads to the desired outcomes. This will require prioritizing usability and intuitive design over feature overload.</li></ul><h4><strong>Test, Iterate, and Improve</strong></h4><ul><li>Continuously gather real-world data post-launch to validate whether you’ve achieved the desired outcomes.</li><li>Iterate based on feedback and insights from real users to refine and improve your product over time.<br>ODI is a <strong>continuous process</strong> — you must keep testing, iterating, and improving based on actual user behavior, not just what you think they want.</li></ul><h3>Real-World Examples of ODI in Action</h3><h4>1. Spotify — Rethinking Music Consumption</h4><p>Before Spotify, people were accustomed to downloading and owning music. But instead of focusing on <strong>improving ownership</strong>, Spotify understood the <strong>real user need</strong> — instant, unlimited access to a vast library of music. They introduced a <strong>subscription-based service</strong> that allowed users to listen to any song they wanted, at any time, on any device. This shift from ownership to <strong>access</strong> transformed the music industry.</p><h4>2. Amazon Kindle — A Better Reading Experience</h4><p>While people loved the idea of physical books, their real need was a <strong>convenient, portable, and comfortable reading experience</strong>. Kindle addressed this need with an <strong>e-ink display</strong> that mimicked the feel of paper and a lightweight design that allowed users to carry hundreds of books in one device. Instead of simply digitizing physical books, Kindle optimized the experience for <strong>reading anywhere, anytime</strong>.</p><h4>3. Tesla — Beyond Just an Electric Car</h4><p>Tesla didn’t just build another electric car; they focused on creating a <strong>superior driving experience</strong>. Their vehicles are designed with <strong>fast-charging stations</strong>, <strong>autonomous driving features</strong>, and <strong>performance capabilities</strong> that go beyond just the electric powertrain. Tesla’s focus on the <strong>overall driving experience</strong> rather than just an electric vehicle revolutionized the automotive industry.</p><h3>Final Thoughts</h3><p>🔹 <strong>ODI helps companies move beyond surface-level user requests</strong> and uncover the <strong>true needs and desired outcomes</strong> of users.<br> 🔹 Traditional methods focus on what users say they want, but ODI targets the <strong>real results they seek</strong> — driving innovation that is impactful and sustainable.<br> 🔹 Companies like <strong>Apple, Spotify, Amazon, and Tesla</strong> have leveraged ODI to create <strong>transformative user experiences</strong> and maintain competitive advantages.</p><p><strong>Next time you design a product, ask yourself: ‘What real outcome does the user want?’</strong> By adopting <strong>ODI</strong>, you’ll focus on <strong>solving problems at their core</strong>, leading to more effective solutions and satisfied users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0f771df17b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>