<?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 Sima Ercevic on Medium]]></title>
        <description><![CDATA[Stories by Sima Ercevic on Medium]]></description>
        <link>https://medium.com/@sima.ercevic?source=rss-ad9cff53a13a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OiCYdNZoLhzRo5IS</url>
            <title>Stories by Sima Ercevic on Medium</title>
            <link>https://medium.com/@sima.ercevic?source=rss-ad9cff53a13a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:25:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sima.ercevic/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[Measuring Feature Success Without Losing Sight of the User]]></title>
            <link>https://medium.com/the-design-loop/measuring-feature-success-without-losing-sight-of-the-user-fb22440f5b0a?source=rss-ad9cff53a13a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb22440f5b0a</guid>
            <category><![CDATA[product-analytics]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[carpooling]]></category>
            <dc:creator><![CDATA[Sima Ercevic]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 11:16:01 GMT</pubDate>
            <atom:updated>2026-07-31T11:16:01.317Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When a feature ships, the real question isn’t whether we built it. It’s whether it’s quietly working for the people we built it for, and whether we’d even notice if it wasn’t.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TeYjjzz9WpF_kGFn5a16aQ.png" /></figure><p>There’s a moment every product team knows well.</p><p>A feature ships. The demo goes smoothly. Everyone claps, and everyone moves on to the next thing on the roadmap. And then, weeks later, someone asks a deceptively simple question in a standup:</p><p><em>“Is anyone actually using it?”</em></p><p>More often than we’d like to admit, the honest answer is <em>we’re not sure.</em></p><p>We can usually say how many people opened the screen. We can pull a chart of taps. But those numbers rarely tell us the thing we actually care about: whether the feature is solving the problem it was meant to solve, for the person it was meant to help. Without that, we’re quietly designing the next iteration on instinct rather than evidence.</p><p>This is a story about closing that gap. Not with a heavyweight analytics programme or a dedicated data team, but with something surprisingly lightweight. And it’s about a realisation I didn’t expect: that measuring a feature’s success, done well, brings you <em>closer</em> to your users rather than reducing them to a row in a spreadsheet.</p><p>I’ll use a real example throughout: the <strong>Booked Carpool</strong> feature in <strong>KINTO Join</strong>, our mobile app for sustainable commuting. It lets a driver plan a carpool in advance and then, on the day of the trip, record the journey so it counts. Simple enough, but exactly the kind of feature where “did people use it?” and “did people <em>actually</em> use it the way we intended?” turn out to be very different questions.</p><h3>Start From the Need, Not the Feature</h3><p>The easiest numbers to collect are almost always the least useful. Page views. Total taps. Session length. The UX community has a well-earned name for these: <em>vanity metrics.</em> The simplest test is whether you ever actually act on them. App downloads always go up. Pageviews always climb. Neither tells you if a single person got what they came for.</p><p>The critique isn’t new. In his 2023 paper <em>“</em><a href="https://uxdesign.cc/so-how-can-we-measure-ux-93fad8a8ddc9"><em>So, How Can We Measure UX?</em></a><em>”</em>, Maximilian Speicher argued that none of the metrics readily available from standard analytics can reliably measure experience on their own. They don’t tell you where someone got confused, what they were trying to do, or why they gave up.</p><p>So before measuring anything, there’s a better question to sit with: <em>what did this feature promise the user?</em></p><p>Not what it does. What it <em>promises</em>. A booking feature doesn’t promise “a form.” It promises <em>certainty</em>: I’ve secured what I need, and I don’t have to worry about it. A journey-recording feature doesn’t promise “a button.” It promises <em>effortless proof</em>, where my contribution is captured without me having to think about it.</p><p>Frame it that way and the thing to measure becomes obvious. You’re no longer asking “how many people tapped the button?” You’re asking “did the person get the certainty we promised them?”</p><p>This is also, quietly, where user needs and business needs stop being in tension. A reservation that’s made but never used doesn’t serve the user, because they didn’t get what they came for. And it doesn’t serve the business either, because the value the feature was meant to create never materialised. When you measure whether the user’s need was genuinely met, you’re very often measuring the business outcome at the same time. They turn out to be the same question, asked from two directions.</p><h3>Three Lenses on the Same Experience</h3><p>Here’s the mental model that made all of this click. Good feature measurement isn’t one tool or one number. It’s three lenses pointed at the same human experience, each answering a different question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6va0cT0VKHHRXWJOoyktDg.png" /></figure><p>A <strong>funnel</strong> shows you <em>where</em> people fall away in a flow. A <strong>session replay</strong> shows you <em>why</em> they hesitated or gave up. A <strong>heatmap</strong> shows you <em>what</em> drew their attention, and what they missed entirely.</p><p>None of these on its own is enough. A funnel without a replay is a number without a reason. A replay without a funnel is a single anecdote with no sense of scale. Layered together, they stop being analytics and start becoming <em>observation</em>.</p><p>The tool I used for all three was <a href="https://uxcam.com/">UXCam</a>, a mobile-first experience analytics platform that keeps funnels, session replays, and heatmaps in one place, and lets you jump straight from a drop-off point in a funnel into the recordings of the exact people who dropped there. What made it click for me wasn’t any single feature but that connection: the numbers and the human behaviour behind them live one click apart.</p><h3>The Funnel: Where People Fall Away</h3><p>A funnel is the sequence of steps a person moves through to get what they came for, and it shows you where they fall away. Not <em>that</em> people drop off, but <em>where</em>. That distinction is everything, because “the feature isn’t working” and “step three isn’t working” lead to completely different responses. One sends you back to the drawing board. The other sends you to fix one screen.</p><p>For Booked Carpool I set up a simple three-step funnel: <em>created the reservation → opened it on the departure day → started recording the journey.</em> Here’s one month of real drivers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXsaU1sSZUKQZ3Oz2aS7iA.png" /></figure><p>Read as a single completion number, around 64% of drivers who created a reservation went on to record the journey. It’s easy to shrug at. But the funnel showed something I wouldn’t have guessed from that one figure.</p><p>Almost everyone who <em>opened</em> the booking on the day went on to record: about 91% of them. The final step worked. The real loss was happening <em>earlier</em>. Nearly a third of drivers never came back to the app on the day at all.</p><p>There’s a second detail in that funnel worth pausing on: the average time to conversion was over sixteen hours. This flow doesn’t happen in one sitting. Someone books on Monday evening and records on Tuesday morning, which means the measurement has to span sessions and days to see the whole thing. Get that setup wrong and the feature looks broken when it isn’t.</p><p>That drop-off is a completely different problem than the one I’d have assumed from a low completion number. It’s not a broken screen. It might be a missing reminder, a notification that never lands, or friction in getting back into the app. The funnel didn’t just hand me a percentage. It pointed me at the <em>right question</em>, and at a specific group of people to go and understand.</p><p>This lines up with a principle running through most serious writing on UX measurement, from <a href="https://www.heartframework.com/">Google’s HEART framework</a> onwards: measure the <em>critical</em> flows, not everything. A small number of key moments explain most of what you need to know. Chasing every possible metric buries the signal under noise.</p><h3>The Session Replay: Understanding the Why</h3><p>Here’s where measurement stops being cold arithmetic and starts becoming empathy at a distance.</p><p>A funnel tells you <em>where</em> someone dropped off. Session replays let you ask <em>why</em>. You can watch the actual session of a real person moving through the flow. Not their identity, nothing invasive, just the interaction. Where they hesitated. What they tapped. Where they went instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFsCGI3ITnnMkDtpgTeFMA.png" /></figure><p>Look at the timeline on the right. This driver spent fourteen seconds on the bookings list, opened the ride details, swiped up, tapped the start button, and the detail event fired <em>again</em> before the journey finally started at twenty-five seconds. That small stutter, a swipe and a repeat, is invisible in any funnel. It’s someone checking themselves, making sure they’ve got the right trip before committing.</p><p>A percentage on a chart is abstract. Watching someone hesitate, swipe, pause, and check again is not abstract at all. It’s a person interacting with something we made, in a way we didn’t fully anticipate. You can’t un-see it, and you can’t argue with it in a review meeting the way you can argue with a number.</p><p>This is what “friction-first” thinking is really about. Some of the strongest signals about an experience aren’t in surveys. They’re in behaviour. Repeated taps. Backtracking. Rage taps. Abandoning halfway. These are things people simply <em>wouldn’t do</em> if the product were doing its job perfectly, and exactly the things a survey would never catch, because the person might not consciously remember the friction at all.</p><h3>The Heatmap: What Gets Noticed, and What Doesn’t</h3><p>The third lens answers a question the other two can’t: on a single screen, what is actually pulling people’s attention?</p><p>A heatmap aggregates where people tap, scroll, and linger, and paints it over the screen itself. I pulled up the one for the bookings screen, where a driver lands when they open the app on their departure day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WTFf9p0jyhrUe66Me0fNkA.png" /></figure><p>Two things jumped out. The first is the average visit duration: barely a few seconds. People are not browsing this screen, they’re glancing at it and acting. The second is where the heat actually lands. It clusters on the booking cards themselves rather than spreading evenly, which tells me people arrive knowing which trip they want and go straight for it.</p><p>The reassuring part is what <em>isn’t</em> there. Rage taps appear in under 1% of visits, and swipes make up only a small share of gestures, which is normal scanning behaviour rather than frustrated hunting. Combined with the funnel result, this reinforces the same conclusion from a different angle: the screen isn’t the problem. Once a driver is here, the experience works. The loss happens before they ever open the app.</p><p>Put the three lenses together and you have a complete picture. The funnel tells you <em>where</em> people are lost. The heatmap tells you <em>what</em> they’re drawn to when they arrive. The replay lets you watch it happen and understand <em>why</em>.</p><h3>Why This Belongs on Every Feature</h3><p>Setting this up was remarkably lightweight: a small handful of key moments marked in the flow, being the point of intent, the point of action, and the point of completion. Once those are defined, the funnel essentially builds itself, and I could go from “I wonder if this works” to “here’s exactly where it doesn’t” in the same afternoon.</p><p>That speed changes the relationship between design and evidence. When answers are slow and expensive, you ration your questions and fall back on assumption. When they’re fast and cheap, curiosity becomes routine.</p><p>Which is why I’d like to see measurement stop being a special project reserved for flagship launches, and become a quiet habit attached to nearly everything we ship. If defining a few key moments is cheap, the question stops being “is this feature important enough to measure?” It becomes “why would we ship anything <em>without</em> knowing whether it worked?”</p><p>Metrics are also most useful tracked <em>over time</em>. Your own trajectory, such as a flow climbing from 61% to 74% over two releases, tells you far more about your product’s health than any external benchmark. But that only works if measuring is something you do consistently, feature after feature.</p><p>One last principle worth borrowing: Google’s HEART framework deliberately pairs <em>task success</em> with <em>happiness</em>. Behaviour and feeling, side by side. The tools I’ve described are strongest on the “what they do” side. The most complete practices pair them with the occasional lightweight check on how people <em>feel</em>, whether that’s a short in-context survey, a usability session, or a conversation. The number tells you there’s friction. The person tells you what it costs them.</p><h3>Final Thoughts</h3><p>It would be easy to read all of this as an argument for more data. It isn’t.</p><p>It’s an argument for staying close to the people we design for <em>after</em> launch, precisely when it’s most tempting to look away and move on. Measurement, done thoughtfully, isn’t the opposite of empathy. It’s a way of <em>extending</em> it past the moment the feature goes live.</p><p>A funnel is a way of noticing that someone is struggling. A session recording is a way of watching what they’re struggling <em>with</em>. A heatmap is a way of seeing the screen through their eyes.</p><p>The numbers, on their own, don’t understand anyone. But used well, as a starting point rather than a conclusion, they point us back toward the person. They tell us where to look, then get out of the way and let us watch, and understand, and improve.</p><p>And when the user’s need is genuinely met, the business outcome tends to follow. Not because we chased the metric, but because we stayed close to the person the metric was really about.</p><h3>References and Further Reading</h3><p>Kerry Rodden, Hilary Hutchinson &amp; Xin Fu, <a href="https://research.google.com/pubs/archive/36299.pdf"><em>Measuring the User Experience on a Large Scale: User-Centered Metrics for Web Applications</em></a> — the original Google paper introducing the HEART framework and the Goals–Signals–Metrics process (ACM CHI, 2010).</p><p><a href="https://uxdesign.cc/so-how-can-we-measure-ux-93fad8a8ddc9">Maximilian Speicher, <em>So, How Can We Measure UX?</em></a> (2023) — on the limits of standard analytics metrics as proxies for experience.</p><p><a href="https://uxcam.com/">UXCam</a> — the mobile experience analytics platform used for the funnels, session replays, and heatmaps in this article.</p><p><em>If you’ve been measuring your features mostly through taps and pageviews, try this on your next release: pick the one moment that represents the user actually getting what they came for, and measure the path to it. Then go watch a few of the people who didn’t make it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb22440f5b0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-design-loop/measuring-feature-success-without-losing-sight-of-the-user-fb22440f5b0a">Measuring Feature Success Without Losing Sight of the User</a> was originally published in <a href="https://medium.com/the-design-loop">The Design Loop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Storyboarding At Any Stage in a Product’s Lifecycle]]></title>
            <link>https://medium.com/the-design-loop/the-power-of-storyboarding-at-any-stage-in-a-products-lifecycle-276478d9e38e?source=rss-ad9cff53a13a------2</link>
            <guid isPermaLink="false">https://medium.com/p/276478d9e38e</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[storyboarding]]></category>
            <dc:creator><![CDATA[Sima Ercevic]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 09:32:36 GMT</pubDate>
            <atom:updated>2025-12-16T09:39:51.212Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Across long-running product teams, I saw a familiar pattern: everyone thinks they understand the user journey, but each group imagines it slightly differently.</em></p><p>Design focuses on interactions.<br>Engineering focuses on logic.<br>Product owners focus on requirements.<br>Stakeholders focus on outcomes.<br>Client teams focus on communication.</p><p>Individually, these perspectives make sense, but together they create small misalignments that grow over time. The product remains the same, yet the story of how people use it appears differently depending on who you ask.</p><p>As the product evolves and knowledge spreads across many people, that shared understanding becomes more fragmented. The journey becomes something everyone ‘knows’ but visualises differently.</p><p>This is where storyboards become an exciting opportunity. Even if introduced later, they can create a clearer and more consistent picture of the user’s world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcmTJNxkf5yGn4RuOOTpUg.png" /></figure><h3><strong>Why Storyboards Became Necessary</strong></h3><p>Even with detailed flows, personas and prototypes, a few recurring challenges surfaced throughout my work.</p><h4>1. Stakeholder conversations often relied on assumptions rather than complete evidence</h4><p>Not deliberately, but assumptions were often based on limited views, such as a user comment, a client impression, market feedback or a personal interpretation.</p><h4>2. Teams understood the journey, but not always in the same way</h4><p>No one lacked awareness. What was missing was a shared visualisation of that awareness. Different roles naturally form different mental models. Without a visual reference, the same journey turns into several versions of the truth.</p><h4>3. Existing UX artefacts didn’t capture the human context</h4><p>Flows and diagrams show actions, not situational context. They don’t show rushing, waiting, coordinating or multitasking, even though these moments shape real-world usage.</p><p>A more human, scene-based representation was needed.</p><h3><strong>Finding the Right Balance When Creating Storyboards</strong></h3><p>While working on the storyboards, one question kept coming back to me:<br><em>How detailed is detailed enough?</em></p><p>What I needed were visuals that were clear enough to tell a story, but lightweight enough to be changed without friction.</p><p>That meant letting go of polish and focusing instead on intent. Each frame had to communicate a moment. If a scene was readable at a glance, it was doing its job. If it needed explanation, it was probably too complex.</p><p>I also had to constantly remind myself that the storyboards were not the goal. They were a means to spark conversation, align understanding, and surface questions. Speed and flexibility mattered more than perfection.</p><h4><strong>What Worked Well</strong></h4><p>Looking back, a few things made the process feel effective:</p><ul><li><strong>Moving fast without overthinking</strong><br>Being able to explore multiple versions of the same scenario helped me understand which moments actually mattered and which didn’t.</li><li><strong>Keeping a consistent visual language</strong><br>Once I stopped tweaking style decisions, I could focus entirely on the story I was trying to tell.</li><li><strong>Making small, intentional adjustments</strong><br>Changing posture, facial expression, or the position of an object often clarified a moment more than adding extra detail ever could.</li><li><strong>Using rough visuals as a discussion starter<br></strong>The fact that the storyboards weren’t “finished” made people more comfortable questioning them and sharing their own interpretations.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*57OVRMasu1_uytps7B6r4w.png" /></figure><h3><strong>How Storyboards Can Shape Collaboration Across Teams</strong></h3><p>This approach is still new, and I can’t claim these changes have fully transformed every team yet. But based on what I’ve observed and what I believe can happen, storyboards have the potential to influence collaboration in several positive ways.</p><h4>UX and the product development team</h4><p>They can give everyone a clearer sense of context, timing, emotions and environment. This helps reveal friction that’s hard to see through screens alone.</p><h4>Product Owners</h4><p>Scenarios can make requirements easier to explain and understand because the conversation becomes grounded in real-life moments instead of abstract descriptions.</p><h4>Designers and Engineers</h4><p>Storyboards can shift discussions away from isolated UI elements and toward a more contextual view of what the person is experiencing.</p><h4>Sales and Client Teams</h4><p>They can help communicate value more naturally by showing relatable moments instead of static feature lists.</p><h4>Stakeholders and Non-Technical Teams</h4><p>They can turn abstract flows into intuitive stories that reduce misunderstandings.</p><h4>Marketing</h4><p>Storyboards can act as a narrative blueprint for campaign direction, landing page messaging, video planning and social content. They don’t have to use the exact drawings, but they use the story behind them.</p><p>These are possibilities, not yet fully validated outcomes. But early reactions show that storyboards are making our conversations easier and more grounded.</p><h3><strong>Why Storyboards Matter, Even When Added Late</strong></h3><p>Personas describe <strong><em>who</em></strong> the user is.<br>Flows describe <strong><em>what</em></strong><em> </em>they do.<br>Prototypes describe <strong><em>how</em></strong> it works.</p><p>Storyboards reveal<strong> <em>what it feels like</em></strong> to be the user.</p><p>They bring back the emotional, situational and environmental details that often fade as products grow. When teams see these moments visually, conversations become clearer, and alignment becomes more natural, even if the storyboards are introduced late.</p><h3><strong>Final Thoughts</strong></h3><p>Using storyboarding has been fast, flexible and creatively energising in my experience.</p><p>But I’m also aware of something important:</p><p><strong>This is just one piece of the puzzle. </strong>Storyboards won’t solve alignment on their own or replace deeper research. They are simply a powerful complement, a visual layer that helps teams talk about the same thing in the same way.</p><p>If anything, they’ve reminded me how much clarity comes from showing the journey, not just describing it, and how much potential visual storytelling still has, even later in the lifecycle of a product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=276478d9e38e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-design-loop/the-power-of-storyboarding-at-any-stage-in-a-products-lifecycle-276478d9e38e">The Power of Storyboarding At Any Stage in a Product’s Lifecycle</a> was originally published in <a href="https://medium.com/the-design-loop">The Design Loop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>