<?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 James Skinner on Medium]]></title>
        <description><![CDATA[Stories by James Skinner on Medium]]></description>
        <link>https://medium.com/@james.skinner1999?source=rss-e140b6f5f08a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Kf0PVYgihiss5wCgtW4PgQ.jpeg</url>
            <title>Stories by James Skinner on Medium</title>
            <link>https://medium.com/@james.skinner1999?source=rss-e140b6f5f08a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:10:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@james.skinner1999/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[Talking Squares]]></title>
            <link>https://medium.com/design-bootcamp/talking-squares-399450aab448?source=rss-e140b6f5f08a------2</link>
            <guid isPermaLink="false">https://medium.com/p/399450aab448</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[James Skinner]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 08:37:31 GMT</pubDate>
            <atom:updated>2026-04-07T08:37:31.904Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we can restore meetings from the guise of the interface to promote presence over UI features</h4><p>Part 1 of a writing series, <a href="https://medium.com/design-bootcamp/humanising-apps-d79ed0b32ffe">Humanising Apps</a>.</p><figure><img alt="A sketch by the author illustrating a face framed by a series of screen devices." src="https://cdn-images-1.medium.com/max/1024/1*GNvymgnFli6INnv9OkpcHw.png" /><figcaption>Talking Squares ©James Skinner</figcaption></figure><p>We’re <strong>six</strong> years post-COVID, and honestly? Looking back feels like scrolling through a fever dream. The shift in how we work hasn’t just been a <em>change</em>; it’s been a total structural rewrite of industries and our daily lives.</p><p>As a Gen Z professional, I’ll be the first to admit that <strong>I don’t know any other way of working.</strong> For my cohort, the “office” wasn’t a physical destination; it was a digital interface. Working from home is my norm and has been since my bedroom was turned into a lecture hall in March 2020. While the physical world hit the pause button, tools like Google Meet stepped in as an attempt to keep us human, albeit channelled through varying sizes of 16:9 video squares.</p><p>But that was a mere <strong>six</strong> years ago, a lifetime in tech years. Since then, we’re still grappling with what the “office” actually means. Mass-consumer AI has sprung onto the scene with a force that makes those early Zoom calls feel prehistoric, moving us away from “Can you hear me?” to “Can AI do this for me?” at breakneck speed. We are once again at a crossroads, questioning our ways of working. But regardless of where your team logs in (Remote or in-person), the goal remains the same: our tools must be designed for our <strong>humanity</strong>, not just our output.</p><p>And so, Google Meet and other video conferencing tools are stuck in 2020. It’s time for a human upgrade.</p><h3>The medium is the message</h3><p>This evolution reminds us of Marshall McLuhan’s foundational theory that <strong>“the medium is the message.”</strong> The tools we use don’t just facilitate work; they define it. In a UX context, this means that the specific communication system, the video grid, the AI chatbot, and the AI-generated summary are more influential than the actual content being shared. The medium of video conferencing didn’t just transmit our meetings; it reshaped our social cues, our attention spans, and our relationship with “the office” and our colleagues. We didn’t just change <em>where</em> we worked; the tools changed <em>how</em> we think about work itself.</p><p>As McLuhan famously noted in 1964:</p><blockquote><strong>‘We shape our tools, and then our tools shape us’</strong></blockquote><figure><img alt="An illustration of two hands pointing in alternate directions" src="https://cdn-images-1.medium.com/max/1024/1*Hlgabr7qXLOIqqM6BZumJg.png" /><figcaption>Are we progressing forwards or backwards? ©James Skinner</figcaption></figure><p>Despite years of this “new norm,” industries are still searching for the perfect workflow, ranging from remote work to full-time office mandates. The perfect workflow hasn’t been found; it’s still being iterated on. If our tools are meant to serve us, they need to be more than just a digital window; they need to be intentional and continue to emulate the best form of communication — In-person, IRL. In this V2 vision, I explore how we can sharpen Google Meet to be more human-centric, moving from rigid AI transcribers to more meaningful interpersonal connections.</p><p>This article isn’t a vendetta against Google Meet, my preferred video tool, which I use daily. It’s a critique of the sterile state of video conferencing tools as a whole. We’ve perfected the utility of the video call, but at the expense of the ‘relationship,’ ignoring the social cues that make face-to-face interaction meaningful. We lost the humanity of the conversation. I want to explore how we might build upon this functional baseline and iterate to design for the organic, messy social cues that foster real connection.</p><h3>Let&#39;s take a look at Google Meet</h3><p>With technology exponentially progressing, it begs the question: How has Google Meet evolved since users were forced to adopt it in March 2020?</p><figure><img alt="An image showcasing two adjacent screenshots of Google Meet’s UI in 2020 vs 2026" src="https://cdn-images-1.medium.com/max/1024/1*kIJsfAeK8Ox5LI5ualLZqw.png" /><figcaption>Google meet UI in 2020 (left) vs 2026 (right)</figcaption></figure><p>Frankly, we’re not much further on from V1; Google Meet appears to have lived in MVP limbo. The tool meets a functional need. It allows us to communicate whilst being miles apart from the person(s) we’re talking to. Albeit a grid layout of 16:9 rectangles of faces that facilitates talk, it ignores how humans actually work and interact. We’ve optimised for ‘the call,’ but we’ve sacrificed what happens outside of the call, the wider office culture. To fix our fragmented workdays, we don’t need more pixels or more tech; we need tools that respect our time and our offline world.</p><p>Google Meet is a great example of inclusive UI (it’s well documented <a href="https://support.google.com/meet/answer/16175468?hl=en&amp;co=GENIE.Platform%3DDesktop">here</a>), but it could go way further. Utility &amp; accessibility have become a baseline expectation rather than a competitive edge, and so the stakes have shifted. For Google to maintain its lead, the tool needs to move beyond functional reliability and start solving for the deeper complexities of human collaboration.</p><p>I concede that, in the subsequent years since its initial release, the UI has had a little polish, and users can now react with animated emoji. The emojis are a fun touch of colour to dry meetings — every time I see the crab curb across my screen, I eek a little smile and a giggle that one of the senior execs has just thrown down a crab emoji. Albeit with every animation, my attention is taken away from the speaker’s message. I zone out when I see the 3-second distraction to zone back in. The medium is louder than the message. And so this begs the question: does this surface animation enhance communication or merely add a gimmick that was a quick win on a product roadmap?</p><h3>Some design interventions to save you in your next meeting…</h3><p>I’ve put together a few UI experiments, some practical, others admittedly satirical, to see if we can design our way back to basic human eye contact and better the quality of our communication. These concepts explore what happens when we stop optimising for “features” and start optimising for “presence.”</p><p>How might we design for <strong>intentional presence</strong> rather than just <strong>functional parity</strong>?</p><figure><img alt="A meeting with 1000s of participants. Our tools should make us think twice before hitting ‘Invite All’." src="https://cdn-images-1.medium.com/max/1024/1*eV_yX8NVC8uaWHi5ZrZLvQ.png" /><figcaption>Our tools should make us think twice before hitting ‘Invite All’ ©James Skinner</figcaption></figure><h4>No agenda, no attenda</h4><p>To start, it goes without saying that we should respect other people’s time. Our tools should make us conscious of that fact. <strong>Digital tools shouldn’t just save time; they should teach us to respect it. </strong>Our tools should make us think twice before hitting ‘Invite All’ or allowing us to schedule recurring weekly “James/John” meetings. By limiting attendee counts for standard calls, we shift the culture from passive observation to active participation.</p><p>Hey, and whilst we’re on the subject, meeting agendas should be a prerequisite, not an afterthought. When a meeting tool allows us to claim someone’s time without a clearly defined purpose, it isn’t just enabling a call, it’s promoting ‘<a href="https://hbr.org/2025/09/ai-generated-workslop-is-destroying-productivity">workslop</a>.’ We need to design friction into the scheduling process to protect our collective focus and productivity.</p><figure><img alt="A concept UI, in the style of Google Meet, of a dialogue suggesting the user has ran out of time, requiring them to move onto the next agenda item." src="https://cdn-images-1.medium.com/max/1024/1*7985RnAG4Ede53SeSVv0jA.png" /><figcaption>AI Timekeeper keeps you to schedule ©James Skinner</figcaption></figure><h4>Time&#39;s up, I’m afraid, James! 🔔</h4><p>Current tools merely adopt AI as meeting transcribers (a job formerly referred to as a stenographer). They record our ramblings without fixing them or suggesting ways in which we could improve. We don’t need better transcriptions of bad meetings; we need active mediation. Imagine a tool that understands the agenda’s weight and nudges the room back to life when a two-minute point turns into a ten-minute tangent.</p><p>We’ve all been there. A meeting that seems to drone on; a colleague is using 1,000 words which could have been distilled into a single sentence or a 2-minute interlude. “James, you seem to have exhausted the point — shall we move to the next line-item?”</p><figure><img alt="A concept UI, in the style of Google Meet, of a dialogue suggesting the user join their team in Pod B if they’re in the same location." src="https://cdn-images-1.medium.com/max/1024/1*OuuhqGrLNMf6s6NYU2Yypg.png" /><figcaption>Don’t be a recluse. Join your team in IRL! ©James Skinner</figcaption></figure><h4>“What? No way! You’re in the office too?”</h4><p>In our hybrid reality, location is fluid. But while there’s a certain novelty in seeing a colleague dial in from a remote beach, or at least their background would allow us to believe, the charm disappears when you realise they’re actually sitting three desks away…!</p><p>Google Meet’s “merged audio” feature, introduced in 2025, was designed to stop the dreaded echo, allowing two people to sync their audio while sitting together. But this feels like a step backwards for collaboration. Before, we’d huddle around a single screen, forcing a shared experience. Now, we stay slumped over our separate devices, physically present but digitally siloed.</p><p>Could a series of quick, low-effort features turn the tide and encourage colleagues to meet IRL for a richer interaction, instead of promoting distance? How do we design for <strong>intentional presence</strong> and active engagement rather than just passive <strong>functional parity</strong>?</p><p>If Google Calendar sees two people in the same building have the same meeting, it sends a push notification: <em>“You’re both in the Office — Huddle in Pod B?”</em> and automatically books the meeting for the allotted meeting slot. This would promote IRL connection by removing the mental load of coordinating a meeting spot, making the in-person path the path of least resistance.</p><p>There is a specific kind of modern loneliness: sitting one foot away from a colleague, yet feeling like they’re in another world because they’re staring at your digital avatar instead of you — or worse, checking their Slack messages.</p><p>When “Merged Audio” is active, the UI should make a bold design decision to <strong>collapse individual video feeds into a single “Room Tile.”</strong> If users can’t see their own face or their neighbour’s face in their laptop screen, they’ll be forced to look up and make eye contact with the human adjacent to them. When we remove the digital mirror, the vanity of our own tiles and the distraction of our neighbour’s, we’ll be forced to look up. By intentionally limiting the laptop to a tool (a microphone) rather than a destination (a screen), we reclaim eye contact and foster genuine communication and connection. I don’t need to see Tony’s 2D rendered face when I can see the side profile of his expressive eyes, nose, and ears!</p><figure><img alt="A concept UI, in the style of Google Meet, of a performance dashboard for instant feedback after every call." src="https://cdn-images-1.medium.com/max/1024/1*qQD7Qx1dDYXXkGtHprJFgw.png" /><figcaption>AI Summaries to promote personal development ©James Skinner</figcaption></figure><h4>From your AI Coach: Hey James, that meeting could have been a message</h4><p>One of my main areas for development, as a designer, is communication. A fundamental skill that I’m constantly refining. Could Google Meet provide timely feedback?</p><p>Meeting summaries shouldn’t just document the past; they should help you design a better future version of yourself. Beyond tracking takeaways, imagine a tool that critiques your delivery. Whether you’re trying to sound more authoritative or simply more concise, your meeting tool becomes your personal communications coach.</p><p>For real impact, for better or worse, for companies now back to the office full-time, we could design video conferencing tools to create “FOMO” (Fear Of Missing Out) effect in the digital experience to promote the physical one.</p><p>Imagine a UI that provides a richer collaborative toolkit for those in the room, while limiting certain capabilities for those dialling in. It’s a controversial shift, and some might argue it’s just a regression to pre-COVID norms. But there’s a difference between “reverting” and “restoring value.” By making the IRL experience the <em>premium tier</em> of collaboration, we stop treating the office as a place to sit with a laptop and start treating it as a high-performance environment for human connection.</p><figure><img alt="A jagged pen-drawn horizontal line from one side to the other." src="https://cdn-images-1.medium.com/max/1024/1*dBGawvcSttvP2r0pazCLfA.png" /><figcaption>Humanising our lines of communication ©James Skinner</figcaption></figure><p>In 2026, our video conferencing tools need to embrace a little humility. These tools were a lifesaver when we were forced miles apart in quarantine, but they’re a distraction when we’re a foot away. We should design interfaces that know when to take a step back and allow the real world to take over. At the end of the day, “In Real Life” is still the gold standard of UX. We’re starting to acknowledge that the most high-fidelity connection we have isn’t 4K, it’s across the table.</p><h3>Further Reading</h3><p><a href="https://research.library.fordham.edu/cgi/viewcontent.cgi?article=1008&amp;context=comm_facultypubs"><em>Understanding Media: The Extensions of Man</em></a><em>. </em>Marshall McLuhan (1964)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=399450aab448" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/talking-squares-399450aab448">Talking Squares</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[Humanising Apps]]></title>
            <link>https://medium.com/design-bootcamp/humanising-apps-d79ed0b32ffe?source=rss-e140b6f5f08a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d79ed0b32ffe</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[humanising-apps]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[visual-identity]]></category>
            <dc:creator><![CDATA[James Skinner]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 21:36:29 GMT</pubDate>
            <atom:updated>2026-03-30T21:36:29.940Z</atom:updated>
            <content:encoded><![CDATA[<h4>A UI series on bridging the gap between function and emotion.</h4><p>We’ve optimised our products for machines, but we’re designing for people. While AI has made our tools faster, it has also made our products feel colder. Our pursuit of the ‘perfect’ UI has left us with generic designs that lack a vital ingredient: empathy. Users are now turning to chatbots to find the warmth they can’t find in our interfaces.</p><figure><img alt="An illustration of a sketched finger print with organic shapes by the author" src="https://cdn-images-1.medium.com/max/1024/1*D9m94DC1e9qfLfht3gCQyw.jpeg" /><figcaption>©James Skinner</figcaption></figure><p>Building on my last piece, <a href="https://medium.com/user-experience-design-1/escaping-ai-sludge-why-mvps-should-be-delightful-04d267292458"><em>Escaping AI Sludge</em></a>, I’ve been reflecting on how these lessons could apply to the products we touch every day. If seamless functionality is now the “baseline” expectation, where do we go from here?</p><p>I’ve noticed a paradox is unfolding in product design: as we lean harder into AI during discovery and build, our users are craving more humanity in our products we produce. Users, of course, expect products to work, but they <em>desire</em> a quality that feels organic, perhaps even sentient. This craving isn’t just anecdotal; it is supported by a recent study published by the <a href="https://www.bps.org.uk/research-digest/chatbot-vs-random-human-which-better-tackling-loneliness">British Psychological Society</a> (March 2026)<strong>, </strong>which found that individuals seeking connection actually rated chatbots as <em>more</em> empathetic and better listeners than random human partners. There is a growing emotional deficit in our modern lives. While this insight is shocking, it highlights AI’s efficiency, but more importantly, reveals a serious “empathy gap” in today’s public sphere. Users are so starved for authentic connection that they are finding it in the simulated warmth of an algorithm.</p><figure><img alt="A hand-drawn, wavy black line spans from one horizontal to the other with small white dots along its centre." src="https://cdn-images-1.medium.com/max/1024/1*dBGawvcSttvP2r0pazCLfA.png" /><figcaption>Celebrating the unvarnished ©James Skinner</figcaption></figure><p>I’m starting a new series, <strong>Humanising Apps</strong>, to mock up quick UI studies of how brands might bridge the gap between function and emotion; the user’s focus is shifting from “it works” to “it understands me; it feels human.” As <a href="https://hbr.org/2025/09/ai-generated-workslop-is-destroying-productivity">AI slop</a> begins to clutter the digital landscape, human craft is becoming a competitive advantage. You can see this throughout Anthropic’s brand identity: a deliberate move away from the hyper-technical toward interfaces that feel built by, and for, people.</p><figure><img alt="Anthropic’s brand indentity: Installing a sense of humanity in their illustrations" src="https://cdn-images-1.medium.com/max/1024/0*7QRVIBfFQzbGEM30" /><figcaption>Anthropic’s brand indentity: Installing a sense of humanity in their illustrations</figcaption></figure><p>My constant use of AI has sharpened my understanding of the line between art and commerce. There is a core of humanity, the way we connect, laugh and exist, that remains outside the reach of the machine. My reliance on this technology hasn’t replaced my humanity; it has actually made me value the organic world more. Of course, parts of our interactions, like humour and body language, are irreducible to a single screen or chatbot; we can still design products that feel less like synthetic tools and more like empathetic companions.</p><blockquote>Do the simple thing that works, and that often aligns to more human expressions.</blockquote><p>Anthropic’s Creative Director, Tim Belonax (March 2025)</p><figure><img alt="An illustration of a sketched finger print with organic shapes by the author. Scaled down to make a good thumbnail…!" src="https://cdn-images-1.medium.com/max/1024/1*pOpVTjdngAkZWN2mqCNMiw.png" /></figure><h3>References</h3><p><a href="https://www.bps.org.uk/research-digest/chatbot-vs-random-human-which-better-tackling-loneliness">Chatbot Vs. Random Human: Which is better at tackling loneliness?</a> Emma Barratt, The British Psychological Society (March 2026).</p><p><a href="https://www.thesubtext.online/all/anthropic-interview">Anthropic Brand Team Interview</a>, Carissa Justic, The Subtext (June 2025).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d79ed0b32ffe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/humanising-apps-d79ed0b32ffe">Humanising Apps</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[Escaping AI sludge: why MVPs should be delightful]]></title>
            <link>https://uxdesign.cc/escaping-ai-sludge-why-mvps-should-be-delightful-04d267292458?source=rss-e140b6f5f08a------2</link>
            <guid isPermaLink="false">https://medium.com/p/04d267292458</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[editor-picks]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[James Skinner]]></dc:creator>
            <pubDate>Fri, 02 Jan 2026 14:27:44 GMT</pubDate>
            <atom:updated>2026-01-02T14:27:44.466Z</atom:updated>
            <content:encoded><![CDATA[<h4>Function is the floor, not the ceiling. It’s time to raise the bar and prove that the most viable products are the ones that feel human.</h4><figure><img alt="Hand-drawn sheep, all identitical, face the same direction in a grid layout — baaaaa one. The odd-one-out is highlighted in pink and facing the opposite direction." src="https://cdn-images-1.medium.com/max/1024/1*ZSRvWvjMzqAy0DvT-1J3bg.png" /><figcaption>Escaping the AI Sludge</figcaption></figure><p>AI is now omnipresent in our workflows, but it&#39;s come at a cost: a sea of sameness. Lately, products have begun to look and feel homogeneous &amp; indistinguishable, leading to diluted brands and increasingly sterile interactions. Big tech paves the way for others to follow; It’s time to stop settling for “good enough” and blindly following established conventions. Let’s continue to solve user problems and challenge the attitudes of an MVP (Minimum Viable Product) through the use of craft.</p><p>As explored in a recent <a href="https://www.nytimes.com/interactive/2024/08/26/upshot/ai-synthetic-data.html">New York Times interactive</a>, an LLM’s output is tethered to its training data, revealing a fundamental limitation we must be aware of: AI is a master of regurgitation, not revelation. By drawing from a finite pool of existing designs, these models produce an exponential volume of garbled content — similar to a game of Chinese Whispers where the quality of the message degrades with every time it is retold. While these outputs meet functional requirements, they lack the distinct emotional character and style typically derived from an organic human-design process, required to stand out in a crowded marketplace.</p><p>In this article, I address a growing concern regarding the current state of MVP delivery in consumer products. We stand at a precarious intersection: the pressure to ship fast is colliding with a rising tide of generic AI outputs. We must dissect how designers can retain their creative edge in this environment and empower them to push back against stakeholders for the product&#39;s success. The challenge before us is not just to learn how to use new tools, but to continue to push past what’s been done before and continuously set new standards for the products we ship.</p><p>And so, we need to continue to elevate our craft. We must move beyond the basic utility of the MVP and change our attitudes on experiential standards — creating work that proves, unequivocally, that there is a human behind the design of every screen.</p><p>As popularised by Maya Angelou, American poet and civil rights activist:</p><blockquote>“At the end of the day, people won’t remember what you said or did; they will remember how you made them feel.”</blockquote><p><em>While Angelou may have popularised the sentiment later, </em><a href="https://speeches.byu.edu/speakers/carl-w-buehner/"><em>Buehner</em></a><em> is the earliest recorded source.</em></p><figure><img alt="A hand-drawn illustration, by Ryan Gillet, of a two people carrying freshly prepared food from the oven. The pair seem to very pleased with the delights of their cooking." src="https://cdn-images-1.medium.com/max/1024/1*xgMch7zKNt_CbWfjJDQ3QQ.png" /><figcaption>Illustration by Ryan Gillet</figcaption></figure><h3>The common misconception of MVPs</h3><p>The MVP, popularised by Eric Ries in <a href="https://www.startuplessonslearned.com/2009/08/minimum-viable-product-guide.html"><em>Lean Startup (2011)</em></a>, is often viewed as a functional baseline; it is a stripped-back product intended to prove viability today, with the future promise of augmentation reserved for tomorrow (subject to demand, resources &amp; budget — to name a few!) While many MVPs successfully meet basic user needs, they often fail to deliver a unique or engaging experience. This ordinary quality makes them bland and easily imitated by competitors, making it difficult for a brand to stand out and become compelling.</p><p>To understand the <strong>gap between function and value</strong>, consider a parallel from the physical world: the newly constructed house. At its core, a new build fulfils a functional requirement, providing essential shelter and space. Yet, without personalisation and decoration, it remains a generic structure, a standard configuration of walls and windows that is often repeated worldwide; We’ve seen it all before. It is a commodity, not a destination.</p><p>A house only becomes truly <em>desirable</em> when it transcends its utility. It requires the texture of life: the specific choice of paint, the curated furniture, and the family photos on the mantle. Without these personal touches, the structure creates no emotional resonance. It lacks the essential ingredients that transform a house into a home.</p><p>In product design, as in architecture, the structure is merely the canvas. It’s not until you apply a layer of craft that the screen turns from a habitable space into a valuable one.</p><p>And so, product teams must go beyond just a bare-bones MVP and strive for something desirable. This means crafting a superior user experience unlike other products that meet &amp; surpass a user’s needs &amp; expectations. This approach is crucial for gaining a competitive advantage and establishing a strong, lasting connection with your customers.</p><figure><img alt="A joyful hand-drawn illustration, by Ryan Gillet, of a couple seasoning their food." src="https://cdn-images-1.medium.com/max/1024/1*YcfK92q9XNakNjSlCUT3ZA.png" /><figcaption>Illustration by Ryan Gillet</figcaption></figure><h3>We need to change our attitudes toward MVPs</h3><p>The real issue, in my opinion, however, isn’t solved by a new acronym (something the tech industry already has plenty of!) [<a href="https://excited.agency/blog/minimum-lovable-product#:~:text=Conclusion-,What&#39;s%20a%20minimum%20lovable%20product%3F,bestselling%20book%2C%20%22Lovability%22">MLP — Minimum Loveable Product</a>]. The issue is that we often fail to build truly <em>viable</em> MVPs from the start. Henrik Ståhl’s article, <a href="https://medium.com/user-experience-design-1/minimum-viable-whatever-ae78c5ad1e3d"><em>Minimal Viable Whatever</em></a><em>,</em> earlier this year, made me question my work when throwing about the acronym “MVP”.</p><blockquote>How do we know that the minimum thing we’re doing is viable enough?</blockquote><p>A consumer product, put simply, cannot be viable (from a business perspective) without a strong <strong>brand voice</strong> and a delightful <strong>customer experience</strong>. To further the house metaphor, a family is unlikely to have bought the house in the first place if all the inner services of the building were exposed &amp; its walls laid bare. Typically, a property developer would furnish the space to give it the best chance of a sale and further enhance their ROI. And so, maybe the issue lies with companies shipping half-baked MVPs in a need to generate revenue.</p><p>Building an enjoyable and satisfying product shouldn’t be seen as an additional arduous task to be deferred until after the delivery of an MVP. It’s too late by then; users will have already formed an opinion about the product &amp; the wider brand. It’s hard to change someone’s first impressions. Similar to property developers, tech companies would likely achieve a greater return on investment if they were to delay launch until version one of their product was “finished.”</p><figure><img alt="A hand-drawn illustration, by Ryan Gillet, of a chef revealling a present otherwise hidden by their chef’s hat." src="https://cdn-images-1.medium.com/max/1024/1*4n6y3DPJpyAzMD6zDMepbg.png" /><figcaption>Illustration by Ryan Gillet</figcaption></figure><h3>What do I mean by delightful experiences?</h3><p>If “craft” has established itself as the <a href="https://trends.uxdesign.cc/">defining design buzzword in 2024–2025</a> in light of AI assurgence, then “<em>delight</em>” is its emotional predecessor — and perhaps its most crucial outcome. While the two concepts are deeply intertwined, distinguishing them helps us understand what actually elevates a product from “good” to “beloved.”</p><p>To understand delight, we have to look past the code and the pixels. When done well, delight is the bridge that takes a user interaction beyond the baseline requirements of functionality and usability. As UX researcher <a href="https://www.tandfonline.com/doi/abs/10.1207/S15327590IJHC1304_07">Marc Hassenzahl notes</a>, true delight isn’t found in the product’s surface features, but in its ability to satisfy ‘Hedonic’ needs — such as competence and stimulation — while seamlessly handling and optimising ‘Pragmatic’ tasks like time efficiencies.</p><h4>What <em>delights</em> us as Humans?</h4><p>Why do some tools make us feel empowered while others leave us drained? As psychologists Edward Deci and Richard Ryan demonstrated through <a href="https://selfdeterminationtheory.org/theory/">Self-Determination Theory</a>, our most meaningful experiences are rooted in how well a tool supports our human needs. They identified three essential drivers that must be met for us to feel truly motivated and ‘delighted’ by an experience:</p><ul><li><strong>Autonomy:</strong> The need to feel in control of one’s own actions and choices.</li><li><strong>Competence:</strong> The need to feel effective, capable, and “smart” while performing a task.</li><li><strong>Relatedness:</strong> The need to feel connected to others or valued within a community.</li></ul><p>In the words of Shipra Kayan in <a href="https://medium.com/medium.com/r?url=https%3A%2F%2Fuxdesign.cc%2Fdelight-is-not-cute-flourishes-2a1ce118ced5"><em>Delight is not cute flourishes</em></a><em>:</em></p><blockquote>Moments of delight can only happen when products help people be smarter, feel fulfilled, and avoid mundane tasks.</blockquote><p>We must stop equating delight with cute decorative florishes. Real delight is the quiet satisfaction of a tool that anticipates and fulfils a user’s needs.</p><p>Here are some nice examples I’ve come across:</p><ol><li>Apple: Helping users when they’re not expecting it</li></ol><figure><img alt="3 screenshots of Apple’s iphone Wifi sharing flow. The bottom sheet appears when a contact is wanting to join a new wifi router, catching the user by surprise." src="https://cdn-images-1.medium.com/max/1024/1*324-MA4fv6Bywm_omyz23A.png" /></figure><p>2. Duolingo — Welcome back message</p><figure><img alt="a series of 3 screens detailing Duolingo UI recalling when a user has been inactive for a prolonged period of time. The Duo owl welcomes users back." src="https://cdn-images-1.medium.com/max/1024/1*X_cPwZKMsaQO6f32xLJpqQ.png" /></figure><p>3. Monzo — Get paid early</p><figure><img alt="Monzo’s get paid early flow where users interact by dragging the cash illustration down into a wallet to complete the task." src="https://cdn-images-1.medium.com/max/1024/1*9kJQjy1kOMSyFBptabj-pw.png" /></figure><h3>What delight is not…</h3><p>To understand the value of delight, we must first dismantle the misconceptions that have diluted its meaning. There is a tendency in product design to treat delight as the “cherry on top” — the final step to be taken only if the budget and resourcing permit.</p><p><strong>It is not decoration.</strong> Delight is not an expensive afterthought or a superficial layer of polish applied to a finished product. Single UI alone cannot mask a poor experience. If the core functionality is broken, no amount of charming illustrations or witty copy can save it. In fact, applying “delight” to a screen in a frustrating user flow often feels more patronising than enjoyable.</p><p><strong>It is not a gimmick.</strong> True delight is not merely a fleeting “wow” moment. Flashy animations or unexpected interactions that are disconnected from the user’s core needs are distractions, not delight. If an interaction dazzles the user but ultimately slows them down or confuses their progress, it has failed.</p><p><strong>It is not a checkbox.</strong> Perhaps most importantly, delight is not a line item on a product roadmap to be marked “done” and forgotten. It cannot be treated as an optional extra, dependent on whether the team has leftover capacity.</p><p>Instead, real delight is the result of a <strong>holistic and intentional approach</strong>. It is woven into the product&#39;s architecture from day one, demonstrating that the designers respect the user’s time, intelligence, and emotional state.</p><h3>Delight only works when basic expectations are met</h3><p><a href="https://www.nngroup.com/articles/theory-user-delight/?source=post_page-----4c96e0bf00f4---------------------------------------">Abraham Maslow’s hierarchy of needs</a> taught us that basic needs act as a gateway to higher motivations (love, self-esteem, and creativity). Our basic survival needs must be met before any higher motivations can influence behaviour. Put simply, you don’t worry about “creativity” when you’re worried about finding your next meal.</p><p>Product development requires the same discipline. We must ruthlessly prioritise utility first. Until the software runs without bugs and the core problem is solved, emotional design is merely decoration. You cannot charm a user who is struggling to log in…!</p><p>This brings us to the crux of the issue: In an era where AI tools are democratizing development and efficiency, utility is no longer a differentiator — it is a commodity. When any competitor can use an LLM to generate functional code or optimise a workflow, simply “working error-free” becomes the bare minimum requirement for entry. To build a product that is not only commercially viable but truly “sticky,” <strong>utility alone is not a competitive advantage — it’s just the baseline. </strong>To create a commercially viable product, teams must move beyond a product that works to a product that <em>feels right</em>. This is where design craft will continue to be a product differentiator.</p><figure><img alt="A hand-drawn illustration, by Ryan Gillet, of a giant palm guiding the user through their journey." src="https://cdn-images-1.medium.com/max/1024/1*aBQ3rfdWcQd9YsWkmZsefw.png" /><figcaption>Illustration by Ryan Gillet</figcaption></figure><h3>Delight vs User Satisfaction</h3><p>Delight and user satisfaction are not the same thing. While both are positive outcomes in user experience, they represent different levels of emotional engagement.</p><p><strong>User satisfaction</strong> refers to a user’s contentment with a product or service. It’s the feeling of having their needs met by achieving something or having a want met. A user is satisfied when a product works as expected, is easy to use, and fulfils its intended purpose. This is the <strong>non-negotiable prerequisite</strong> for quality.</p><p><strong>Delight</strong> goes a step further. It’s an emotional response that exceeds a user’s expectations. <a href="https://www.oxfordlearnersdictionaries.com/definition/english/delight_1">Delight is the feeling of great pleasure</a>, joy, or even awe that comes from an interaction with a product or service. It’s what transforms a good experience into a great one. For example, a user is satisfied when a mobile banking app processes a transaction quickly. They are delighted when the app congratulates them on their first successful deposit with a celebratory animation.</p><p><strong>Frequency</strong> plays a pivotal role in this distinction. “Think of delight as a crescendo — a powerful, high-impact climax to an experience. However, not every click and interaction in a user flow is going to generate excitement. And that’s ok, otherwise the experience would be overstimulating and just irritating. User<strong> </strong>satisfaction, on the other hand, operates differently: it may offer a lower perceived value in the moment, but it sustains the product experience through a steady, reliable rhythm.</p><figure><img alt="A pen-drawn illustrative arrow pointing down" src="https://cdn-images-1.medium.com/max/1024/1*h93bIqp-7TQQ-z2_LZE7AA.png" /></figure><blockquote>That’s great and all but how can we put this theory into practice…?</blockquote><figure><img alt="A simple flow diagram of a typical product delivery roadmap: First the product is designed &amp; developed, then typically the MVP is shipped &amp; then teams give the product personality &amp; soul via a Minimum Loveable Product." src="https://cdn-images-1.medium.com/max/1024/1*_r_kCziOcO1U6ButNyb7dA.png" /><figcaption>Is a product truly ‘viable’ if it doesn’t connect emotionally? We need to rethink why personality is often cut from the MVP.</figcaption></figure><h3>Delight is not at the end of a product roadmap</h3><p>Delight should not be viewed as a nice-to-have garnish or a static end destination, as illustrated above — It’s a Foundation. To treat design as a purely functional ‘Point A to Point B’ exercise is like approaching a first date with zero personality or charisma. You may have technically shown up, but nobody builds a relationship devoid of emotion. Would you expect a second date? Absolutely not — and products are no different. <strong>When we strip away emotion, we strip away the incentive to return. </strong>Crucially, if that first encounter is defined by generic experiences that are indifferent, you aren’t getting a second chance. First impressions are notoriously difficult to rewrite, which is why deferring ‘personality’ until after the MVP is a strategic oversight. By then, the user has already judged the brand; if you didn’t delight them at the start, you’ve likely lost them for good.</p><p>Brands that create emotional experiences with their audiences are the most commercially viable (The proof is in the previous example: Apple, Monzo, and Duolingo have already set the gold standard for this approach). While often relegated to the ‘nice-to-have’ category, designing for delight represents a significant, untapped lever for product performance. Far from being an aesthetic indulgence, designing for delight is a high-impact lever for product performance. It drives the metrics that matter most: long-term retention, stickiness, and Lifetime Value (LTV). Moreover, it turns users into a self-sustaining marketing engine, slashing customer acquisition costs (CAC) through natural, fan-led referrals. In this light, delight is a key component of “viability.” <strong>When build resources are tight, emotional resonance shouldn’t be the first thing we descope — it should be the reason we build in the first place.</strong></p><figure><img alt="Whimsical, hand-drawn illustration, by Ryan Gillet, of a waiter or chef in a tall toque lifting a cloche from a serving tray with a flourish." src="https://cdn-images-1.medium.com/max/1024/1*iSw4Hxb6nGnOUJR4RpL71Q.png" /><figcaption>Illustration by Ryan Gillet</figcaption></figure><h3>Let’s build desirable MVPs</h3><p>Successful product teams enhance a Minimum Viable Product (MVP) by focusing on a continuous cycle of building, measuring, and learning. The process is not about launching a single, final product, but rather viewing the product as organic and ever-evolving based on an active user feedback loop. In my opinion, the term delight should be intrinsic to the product’s “viability” as it should be a byproduct of a business and product agenda.</p><h4>Strategies the best teams adopt:</h4><ul><li>Establish a <strong>continuous discovery process</strong>, ensuring that every product/business evolution is anchored in real-world user insights rather than assumptions.</li><li>Let the <strong>data lead</strong>: the best teams prioritise development cycles by weighing features against hard metrics and validated user needs.</li><li><strong>Design for the user, not the workflow: </strong>Create resonant experiences that move past utility and acknowledge the emotional intent behind a task, ensuring that completion feels like a win rather than a digital chore.</li><li>Teams <strong>own &amp; champion emotional design</strong>, acknowledging its commercial benefit.</li><li>View <strong>every release as a hypothesis</strong>: replace guesswork with continual validation to ensure product refinements evolve in tandem with user behaviour.</li><li><strong>Delight cannot exist in a vacuum. </strong>Teams prioritise a functional baseline, ensuring products adhere to the highest accessibility standards before attempting to layer on emotional resonance.</li></ul><figure><img alt="Whimsical, hand-drawn illustration, by Ryan Gillet, of a joyful character in a pillbox hat and jacket, waving enthusiastically with energetic motion lines." src="https://cdn-images-1.medium.com/max/1024/1*yivYkv7DYHnIiWHYXJHgGw.png" /><figcaption>Illustration by Ryan Gillet</figcaption></figure><h3>Key principles to adopt</h3><h4>For design &amp; product teams</h4><ol><li><strong>Change product attitudes</strong>: Delight should not be seen as an additive or a nice-to-have; it should be baked into our product design experience.</li><li>Even in an MVP, <strong>delight should be intrinsic</strong> to the product’s “viability”.</li><li><strong>How we communicate:</strong> When presenting our work, we should not frame delight as an add-on or an extra. It is the solution that meets the brief. Without the added delight, the product does not perform as well as it could against its goals.</li><li><strong>Hold ourselves to account:</strong> Designing for delight focuses on delivering an emotive experience &amp; unexpected rewards to users, rather than solely on the products themselves. We should aim to make the experience a pleasure, not a chore.</li><li><strong>Don’t ship half-baked features;</strong> ship fully viable products.</li><li><strong>Experiment!</strong> Designers should foster a culture of experimentation and rapid refinement. Through data collection, we’ll build evidence on the impact of delight through in-app tests.</li><li><strong>Continual active feedback loop:</strong> Many MVPs are released without delight, and without action, we will still be descoping delight going forward. However, if we better analyse MVPs post-release, we’ll have an active feedback loop that will inform us where to make enhancements and create a business case for delightful improvements.</li></ol><h4>For products</h4><p>While the pursuit of deep delight may feel utopian, it forces us to sharpen our craft and further brands&#39; relationships with their customers. Consequently, products must:</p><ul><li><strong>Anticipate and Adapt:</strong> Predict user needs and adjust the interface to the individual.</li><li><strong>Deliver Reliability:</strong> Work as expected (or better), every single time.</li><li><strong>Maintain Consistency:</strong> Unify form, tone, and voice so the product feels like a single entity.</li><li><strong>Promote authentic emotion over artificial celebration.</strong> We must stop using “confetti” for benign tasks. Users don’t need a digital party for simply logging in. For example, we must remember that a user doesn’t want a bank account; they want the financial control that an account offers. True delight doesn’t celebrate the tool; it connects directly to the user’s feelings about what they are achieving with it.</li><li><strong>Don’t mistake a functional product for a successful one. </strong>The real competitive edge isn’t just solving a problem — the most successful products are emotive, proving there’s a person behind the solution.</li></ul><h3>References</h3><p>For more illustrations, please check out the brilliant Ryan Gillet! <a href="https://www.ryangillett.com/work">https://www.ryangillett.com/work</a></p><p>Luke Murphy, Zero Heights, Building Delight into Your Design System <a href="https://webinars.zeroheight.com/register/zeroheight-ds-live-luke-murphy-building-delight-into-your-design-system">https://webinars.zeroheight.com/register/zeroheight-ds-live-luke-murphy-building-delight-into-your-design-system</a></p><p>Don Norman. 2005. Emotional Design: Why We Love (or Hate) Everyday Things (1st ed.). Basic Books, New York, NY.</p><p><em>Have you noticed any recent shortcomings of MVPs lacking emotion? Please share any recent examples!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04d267292458" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/escaping-ai-sludge-why-mvps-should-be-delightful-04d267292458">Escaping AI sludge: why MVPs should be delightful</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>