<?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 Sharon David Seneviratne on Medium]]></title>
        <description><![CDATA[Stories by Sharon David Seneviratne on Medium]]></description>
        <link>https://medium.com/@srsharondavid?source=rss-b6874b0525a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HrhivxYWZYw2GsZ3.</url>
            <title>Stories by Sharon David Seneviratne on Medium</title>
            <link>https://medium.com/@srsharondavid?source=rss-b6874b0525a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:19:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srsharondavid/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[Does Google Stitch mark the end of the UX Designer?]]></title>
            <link>https://medium.com/insights-by-insighture/does-google-stitch-mark-the-end-of-the-ux-designer-9f31a2abd182?source=rss-b6874b0525a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f31a2abd182</guid>
            <dc:creator><![CDATA[Sharon David Seneviratne]]></dc:creator>
            <pubDate>Tue, 27 May 2025 13:36:29 GMT</pubDate>
            <atom:updated>2025-06-02T08:21:54.351Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX vs. AI: Can Google Stitch Empathise with People?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_OM7M59LTFr2Hhd9x5rBA.png" /></figure><p><strong>AI, AI, AI… It’s buzzing everywhere right now.</strong><br>As a UX designer, I’ve tried more than a few of these tools. Some impressed me; others, not so much.</p><p>Today, I want to talk about my recent experience with <strong>Stitch by Google</strong>, a tool that had me thinking, “<em>Okay…this could actually be something…someday?</em>” I decided to put Stitch to the test on a real design task. What I got was part magic, part meh — and that’s exactly why I’m writing this.</p><blockquote><strong>Stitch is not going to replace UX designers anytime soon.</strong><br>But it’s evolving fast. It’s useful if, and that’s a big if, you know how to guide it.</blockquote><h3>What Is Stitch Actually Good At?</h3><p>Let’s start with the good stuff because Stitch does shine in some areas. I handed over a UI I was working on and asked Stitch to improve it. No user flow, no logic — just polish, and the result?</p><p><strong>Pretty impressive!!!</strong></p><p>Stitch knows how to clean things up. It understands spacing, layout balance, and modern UI aesthetics. It gave my design a nice visual upgrade. Not revolutionary, but enough to make me pause and say, <em>“Okay, this is helpful.”</em></p><h3>What Happened When I Used Stitch on a Real Project?</h3><p>To really test Stitch, I gave it two different design challenges. Here’s how it went down:</p><h4><strong>Challenge 1:</strong> Car auction website redesign</h4><blockquote><strong>Prompt:<em> </em></strong><em>“Redesign this car bidding website to make it feel more modern, trustworthy, and user-friendly.”</em></blockquote><p>I uploaded the existing UI from a real car auction site — cluttered layout, outdated styles, and a bit of a “what-year-is-this?” vibe. The design worked functionally, but it didn’t feel confident, approachable, or intuitive.</p><p><strong>Here’s what happened…</strong></p><p><strong>The Original UI: </strong>A typical listing platform. Lots of vehicles. Lots of filters. But it lacked visual hierarchy, breathing space, and trust indicators.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z87lxo5QThRK-FmQsq-2Tg.png" /></figure><p><strong>Stitch’s First Output: </strong>It gave me a cleaned-up, card-based design with neater spacing, modern typography, and simplified visual structure. It looked better at first glance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGVyWJ4WtyErLvVtcRosug.png" /></figure><p><strong>What Worked:</strong></p><ul><li>Better visual hierarchy.</li><li>Simplified component styling.</li><li>Improved spacing and clarity.</li></ul><p><strong>What Didn’t:</strong></p><ul><li>UX logic wasn’t touched.</li><li>No focus on task flow or user goals.</li><li>Navigation and filtering still felt like an afterthought.</li><li>Trust-building elements were purely visual, not functional.</li></ul><p><strong>Bottom line:</strong> It was a visual reskin, not a UX rethink.</p><h4>Challenge 2: Enhanced User Experience for a Car Auction Website</h4><blockquote><strong>Prompt:</strong> <em>“Redesign this car listing UI to better use space, look modern, and improve user navigation.”</em></blockquote><p><strong>The Original UI: </strong>A fairly polished UI, it had clear filters, strong branding, and good visual consistency, but was a bit heavy on screen space for filters, which limited product visibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHlkHtEyzaet3UULeL1cyQ.png" /></figure><p><strong>Stitch’s Output: </strong>Shifted the visual focus from filters to listings. Increased the number of visible car cards without overwhelming the user. Lightened the UI and redistributed the layout weight more efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GOkBhxgidHATSdzYQ1WnvQ.png" /></figure><p><strong>What Worked:</strong></p><ul><li>More car cards are visible above the fold.</li><li>Cleaner, more minimal left panel</li><li>Better balance between function and visual engagement</li></ul><p><strong>What Didn’t:</strong></p><ul><li>Didn’t reimagine the experience for different user types</li><li>No contextual logic applied (e.g., prioritising popular filters)</li><li>Still lacked strategic UX improvements like saved preferences, filter hierarchy, or empty state handling.</li></ul><h4>Challenge 3: <a href="https://skyu.io/">SkyU</a> Alerts testing Stitch on a functional DevOps UI</h4><blockquote><strong>Prompt 1:</strong> <em>“</em><a href="https://skyu.io/"><em>SkyU</em></a><em> is a DevOps platform that integrates with Prometheus for primitive-based alerts. Using the uploaded design theme, create a UI to display all current alerts.”</em></blockquote><p>This time, I gave Stitch a specific use case of <strong>SkyU’s alert system </strong>and a real UI from our platform. The goal was to see how well Stitch could work within an existing design system while still creating something functional and clean.</p><p><strong>The Original UI: </strong>Focused and practical, but very developer-heavy. It’s data-rich but visually dense and could use better layout balance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JYw59B7IRvu1miFanHt_SQ.png" /></figure><p><strong>Stitch’s First Output: </strong>Surprisingly, this was… not bad. It respected the structure of the original layout and maintained visual consistency with the design theme I provided.</p><p>Stitch also seemed to understand how <strong>Prometheus-based alerts are typically listed</strong>, which was impressive. It grouped the data cleanly, used familiar table structures, and simplified some of the content blocks, making the screen easier to scan and digest without losing key information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3VMnn54dMrBvPpYt3F0cYQ.png" /></figure><blockquote><strong>Follow-up Prompt:</strong> <em>“Can you also give me a summary view of the alerts?”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6EIthU-Z9vaxwU_96-_BA.png" /></figure><p><strong>Stitch’s Summary View Output:</strong><br>It added basic metrics like “Total Alerts,” “Critical,” “Warning,” and “Info,” which helped round out the page. But the layout felt a bit generic, more like surface-level data blocks than a meaningful summary.</p><p>It also didn’t fully adhere to the original design system or colour standards, and visually, it lacked polish. It added some value functionally, but aesthetically, it missed the mark.</p><h3>Can Stitch Handle Real Design Problems?</h3><p>So I pushed Stitch further with full UX narratives, user goals, and flow logic. What came back? Disconnected screens. Generic layouts. No real understanding of user journeys or behavioural context.</p><p>That’s when it hit me:</p><blockquote><strong>Stitch knows how to draw a screen. But it doesn’t know why that screen exists.</strong></blockquote><p><strong>But what if you just want to enhance the UI? </strong>This is Stitch’s sweet spot.<br>It’s great at:</p><ul><li>Visual cleanup.</li><li>Updating styles.</li><li>Enhancing layout aesthetics.</li><li>Reducing noise and creating clarity.</li></ul><p>If you’re looking to modernise a screen quickly, Stitch helps get there faster. But again, <em>you</em> have to guide it.</p><h3><strong>So… is Stitch worth using?</strong></h3><p>Hmmm… Yeah… if you already have something built and just need it to look better, Stitch can help. <br>It’s great for tidying up layouts, refreshing styles, and making things feel more modern. Think of it like a junior designer who’s good with visuals.<br><strong>But that’s about it!</strong></p><p>It’s not going to</p><ul><li>Solve problems, rethink flows, or consider the user.</li><li>It doesn’t know your audience or your goals.</li><li>You still need to do the thinking.</li></ul><p>And like all AI, <strong>it’s only as good as the prompt you give it</strong>. If you don’t guide it, it’s not going to guide you.</p><h3><strong>My Final Take</strong></h3><blockquote>Stitch is learning fast, and yeah, it’s cool. <strong>But it’s not replacing UX designers any time soon</strong>. It’s just a tool. A helpful one, sure. But still just a tool.</blockquote><p>Use it, let it save you time, let it clean things up, but don’t expect it to carry the design!</p><p>Because at the end of the day, it’s still you who knows the user, the problem, and the purpose.</p><p>Stitch can make it pretty, but you make it work…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f31a2abd182" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insights-by-insighture/does-google-stitch-mark-the-end-of-the-ux-designer-9f31a2abd182">Does Google Stitch mark the end of the UX Designer?</a> was originally published in <a href="https://medium.com/insights-by-insighture">Insights by Insighture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Problem, Two Perspectives]]></title>
            <link>https://medium.com/@srsharondavid/one-problem-two-perspectives-e35bb58eb66b?source=rss-b6874b0525a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e35bb58eb66b</guid>
            <dc:creator><![CDATA[Sharon David Seneviratne]]></dc:creator>
            <pubDate>Fri, 04 Apr 2025 07:22:23 GMT</pubDate>
            <atom:updated>2025-04-04T07:22:23.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJEfV4OJDvIlkI6FhyOMQA.jpeg" /><figcaption><a href="https://public-images.interaction-design.org/tags/td-what-is-user-research-illustration-01.png">Source: Interaction Design Foundation — IxDF</a></figcaption></figure><p>Recently, I had the opportunity to conduct a workshop with two different groups of university students, lets call them Group A and Group B. Both were tasked with the same challenge.</p><blockquote><strong>Design a wallet for your neighbour.</strong></blockquote><p>The outcome? A fascinating look into how background, exposure, and user understanding shape problem-solving approaches</p><p>Each group had to design a wallet not just any wallet, but one tailored specifically for their neighbour. This wasn’t about creating a new product for mass market; it was about empathy, understanding real needs, and applying design thinking to build for <em>one</em> user.</p><h3>Group A: Grounded in Simplicity</h3><p>This group took a more traditional route. Their approach:</p><ul><li>Recreated the wallet with slight changes.</li><li>Focused on function, material, and standard layout.</li><li>Designed for someone who likely uses wallets in a basic, conventional way.</li></ul><p>While <strong><em>they didn’t think far outside the box</em></strong>, it doesn’t mean they misunderstood the task.</p><p>In fact, their approach showed that they knew their user group well people who are not yet immersed in modern tech and don’t require complex features.</p><h3>Group B: Bold and Tech Forward</h3><p>Group B, on the other hand, surprised us with innovation:</p><ul><li>Integrated air tag technology for tracking.</li><li>Added app-connectivity features.</li><li>Used unconventional materials.</li><li>Conducted deep research into current tech trends and user neighbour.</li></ul><p>Their designs looked ahead, anticipating what future wallets might be not just what a neighbour might need today.</p><h3>My Takeaway</h3><p>What stood out to me the most was that both groups were right in their own way:</p><ul><li><strong>Group A </strong>showed empathy by designing for a user who lives in the now, with practical and simple needs.</li><li><strong>Group B</strong> embraced innovation, pushing boundaries for what could be.</li></ul><h3>Why This Matters</h3><ul><li><strong>Every user is different</strong> Knowing your user is key.</li><li><strong>Design isn’t about you </strong>It’s about who you’re designing for.</li><li><strong>Context shapes creativity</strong> Your background and exposure impact your design lens.</li></ul><p>This workshop reinforced something I always believed:</p><blockquote>Good design starts with understanding</blockquote><p>When you’re building a product or a feature, don’t assume the need. Talk to the user. Research. And then design something that truly makes a difference for <em>them</em>, not for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35bb58eb66b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Storytelling Matters in Product Design]]></title>
            <link>https://medium.com/insights-by-insighture/why-storytelling-matters-in-product-design-d85ca0611065?source=rss-b6874b0525a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d85ca0611065</guid>
            <dc:creator><![CDATA[Sharon David Seneviratne]]></dc:creator>
            <pubDate>Tue, 03 Sep 2024 07:29:14 GMT</pubDate>
            <atom:updated>2024-10-28T06:07:10.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kc6A8Lh08v2Q0Iob1rdXRA.png" /></figure><p>Storytelling isn’t just for kids, novels and movies. <strong>Storytelling is a powerful tool that brings ideas to life!</strong></p><blockquote>Storytelling is as deeply embedded in our biology as language itself. It’s not just that we like stories; we are addicted to them. We have always told stories, and our lives are organized around them. <br>~Jonathan Gottschall</blockquote><p>Storytelling breathes life into business challenges and user needs, by vividly illustrating them for stakeholders and team members. This engaging approach not only clarifies a user’s journey but also reveals and resolves issues.</p><figure><img alt="A bustling street with people on either side of the road; some are waiting at a pedestrian crossing, and there are small stalls on one side of the road." src="https://cdn-images-1.medium.com/max/910/0*Aqz4RDQ0uPzoX8sp" /></figure><h4>Visualising The Story</h4><p>Take a look at the above picture. <strong><em>What does it convey to you?</em></strong> When you observe a photo, take a moment to pause and imagine yourself in that situation.</p><h4><strong>Ask Yourself:</strong></h4><ul><li><strong>Where</strong> is this place?</li><li><strong>Who</strong> are these people?</li><li><strong>What</strong> are they doing?</li><li><strong>Why</strong> are they here?</li><li><strong>What</strong> am I doing there?</li><li><strong>What</strong> am I trying to accomplish?</li></ul><p>Understanding who the people are and what they care about is crucial for storytelling. By connecting these details, the story is brought to life.</p><h4><strong>Why Is It Important To Tell Stories?</strong></h4><blockquote><strong>Let’s think:</strong> Have you ever struggled to explain what your product does and its features, only to bore your audience and lose their interest?</blockquote><p>Stories help paint a picture for the audience, making it easier for them to understand and relate to your point. A well-told story captures attention and keeps the audience interested.</p><h4><strong>Structuring of a Story</strong></h4><p>A good story follows a clear structure which can be loosely understood as follows: <strong><em>Setting &gt; Plot &amp; Climax &gt; Conclusion</em></strong> <br>This framework for a narrative can guide users through a meaningful journey:</p><ol><li><strong>Setting: </strong><em>Once upon a time…<br></em>Here, we introduce the characters and set the<strong> stage for the story to begin </strong>by providing the necessary background information</li><li><strong>Plot &amp; Climax: </strong><em>the development of the story <br></em>As the story progresses, we describe the challenges the characters encounter, their actions, and their destinations. We also convey their feelings and expressions as they navigate their journey.</li></ol><p><strong>NOTE:</strong> Each story doesn’t follow a straight path to the end. Instead, it features a climax where the direction is uncertain and involves many twists and turns along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*hhy78sQKF_fnvryd.jpg" /></figure><p>3. <strong>Conclusion: </strong><em>and they lived happily ever after…</em></p><p>At the end of the story, we assess how well the plot has been conveyed. This is the point where the story will either reach a happy or sad conclusion.</p><h3>How to Use Storytelling in Product Development?</h3><p>A compelling story begins with a clear picture and these same instruments can be employed for product design.</p><ul><li><strong>Who is in the Story</strong>: Identifying user personas as the “characters”. This helps us understand who the users are, their goals, and how they interact with the product.</li><li><strong>Character Role</strong>: Just as characters have specific roles and entry points in a narrative, understanding user roles and touchpoints helps us grasp the full story more effectively.</li></ul><p>While building products, it’s crucial to use storytelling to ensure that stakeholders, developers, and other actors understand why a certain function is needed.</p><h4>Let’s look at some example scenarios</h4><p><strong>Example 01: </strong>Display product insights and metrics in a separate section.</p><p><strong>Story :</strong><br>Alex, a Product Manager, is having difficulty making strategic decisions due to unclear, unorganised data on monthly, weekly, and daily revenue. Alex needs this data to be visually presented in an organised manner to make informed business decisions and drive strategic planning.</p><p>This story explains why Alex needs the feature and provides the team with a clear understanding of the rationale behind Alex’s request.</p><figure><img alt="sketched illustration of the high-level steps in a new-patient journey" src="https://cdn-images-1.medium.com/max/1024/0*PM2gWn1AosCieXAk.jpg" /><figcaption><em>A “new patient” journey comprises many touchpoints over a long period of time.</em></figcaption></figure><p><strong>Example 02: </strong>Patient appointment screen.</p><p><strong>Story: </strong><br>Sarah, a patient, needs urgent care and wants to book the next available doctor. The current system is confusing and slow. A streamlined appointment screen should show available slots for immediate booking to quickly address her urgent needs.</p><p>This story explains the urgency behind Sarah’s request for an improved appointment screen. The need for a more efficient and straightforward booking process is highlighted in the story and this, helps the development team to understand the requirement of prioritising and designing features that will meet the patient’s urgent care needs effectively.</p><p>……</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/0*1QGk75s0TNn9oyvK.jpg" /></figure><blockquote>Storytelling guides users through their journey from <strong>point A to point B</strong>, offering the audience and team a clear understanding of feature deliverables, user interactions, and potential limitations.</blockquote><p><strong>Key Benefits of Storytelling</strong></p><ol><li><strong>Enhanced Journey Mapping:</strong> Storytelling helps us see and map out each step of the user’s journey, from first contact to reaching their goals, making the design clearer and more engaging.</li><li><strong>Improved Problem Identification:</strong> By looking at the user experience as a story, we can find and fix issues more easily before they affect users, which leads to better problem-solving.</li><li><strong>Clearer Touchpoints and Interactions:</strong> Storytelling shows us important points and interactions in the user journey, ensuring each part is well-designed for a smooth and meaningful user experience.</li></ol><p>In essence, storytelling makes the product design process more dynamic by guiding users smoothly through their journey effectively addressing their needs and resolving their challenges. By viewing the user experience as a story, we design products that not only fulfill user needs but also connect with them on a deeper, more meaningful level.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d85ca0611065" width="1" height="1" alt=""><hr><p><a href="https://medium.com/insights-by-insighture/why-storytelling-matters-in-product-design-d85ca0611065">Why Storytelling Matters in Product Design</a> was originally published in <a href="https://medium.com/insights-by-insighture">Insights by Insighture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>