<?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 Pratyush Verma on Medium]]></title>
        <description><![CDATA[Stories by Pratyush Verma on Medium]]></description>
        <link>https://medium.com/@pratyushvrm98?source=rss-f9967b5bc50b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FVik7V2tC5ULP24P</url>
            <title>Stories by Pratyush Verma on Medium</title>
            <link>https://medium.com/@pratyushvrm98?source=rss-f9967b5bc50b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:39:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pratyushvrm98/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[What happens when your music library grows too big to be useful]]></title>
            <link>https://medium.com/@pratyushvrm98/what-happens-when-your-music-library-grows-too-big-to-be-useful-8c18c759000e?source=rss-f9967b5bc50b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c18c759000e</guid>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Pratyush Verma]]></dc:creator>
            <pubDate>Wed, 18 Feb 2026 10:21:29 GMT</pubDate>
            <atom:updated>2026-02-18T10:25:53.087Z</atom:updated>
            <content:encoded><![CDATA[<p>Open your Spotify. Go to Liked Songs. Look at that number.<br>For me, it’s <strong>3,800.</strong></p><p>That’s not a flex — <strong>it’s a problem</strong>. Because somewhere around the 1,000-song mark, your library stops being useful and starts being chaos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*HTFgYmlyvGc5wBU17-6W-w.gif" /><figcaption>My actual Spotify Liked Songs screen. 3,800 songs. Genre filters at the top. The moment I tap one, everything changes.</figcaption></figure><p>Here’s what you just saw in that 15-second clip:</p><ul><li><strong>3,800 songs</strong> with genre filters at the top</li><li><strong>One tap</strong> → library reorganizes to show only that genre</li><li><strong>New playlist created</strong> directly from the filtered results in seconds</li></ul><p><strong>That’s it. That’s the whole feature.</strong></p><p>But this tiny UI change fundamentally altered how I interact with music I already own.</p><h3>Let me show you why.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yy5biK9vtD2NaMMeHMAaWA.png" /></figure><h3>The Multi-Personality Archive</h3><p>Your Liked Songs becomes a museum. Beautiful. Impressive but<em> also </em>crammed into one endlessly scrolling list with zero organisational logic.</p><p>You can see it in the video — songs like “Wall of Sound” by Charli xcx next to “Insomnia” by Faithless next to “Die With a Smile” by Bad Bunny and Lady Gaga. Genre chaos. Mood chaos. Energy chaos.</p><p>lets get this clear: <strong>Spotify solved discovery years ago.</strong> Discover Weekly works. Daily Mix works. Radio works.</p><p>What broke at scale was <strong>retrieval</strong> — the ability to go from “I need high-energy music right now” to actually hearing it in under 10 seconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*VBpnHHfI35NDhQqzX-DKOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*ouB8UwCbFEQh8tXwN-L1uw.png" /></figure><p>No scrolling. No filtering through the wrong mood. No “emotional jump scares” where a sad song ruins your workout warm-up.</p><p><strong>One tap. Right headspace. Done.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*oxdDRnVdA7DYcFMCvAyOLA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*TmWoJozCWxmjHZpX5vomIg.png" /></figure><h3>The Part That Surprised Me</h3><p>I thought filters would replace playlists. They didn’t. They made playlist creation <strong>way easier.</strong></p><p>Now: “I should make a workout playlist” → <em>taps “Rap” filter</em> → <em>browses 300 relevant songs instead of 3,800 random ones</em> → <em>actually finishes the playlist</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*94SmSwWlazvxGiM9iU1EyQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*QTD3oSEOZ-0JrKKC9uxq2g.png" /></figure><h3><strong>What Spotify Actually Did</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*VvHZBgWK9Hj-tyNdduPLww.png" /></figure><h3>The Bigger Pattern</h3><p>This isn’t just about Spotify.</p><p>It’s about what happens when your product’s value grows faster than its usability.</p><p>At 100 songs, Liked Songs works fine. At 1,000, it’s messy. At 3,800? Basically unusable without structure.</p><p>The best product teams notice when <strong>scale breaks the original UX</strong> — and they ship small, elegant fixes that unlock the value already sitting there.</p><p>Not flashy. Not revolutionary. Just deeply, immediately useful.</p><p>That’s the kind of design that compounds. Because the longer you use Spotify, the more valuable this feature becomes. Your library grows. The filters get more useful. The friction keeps dropping.</p><p>Most features lose value over time. This one gains it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c18c759000e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Musical Puzzle for Kids (3–7): A UX Case Study]]></title>
            <link>https://medium.com/@pratyushvrm98/designing-a-musical-puzzle-for-kids-3-7-a-ux-case-study-5aed780569e2?source=rss-f9967b5bc50b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5aed780569e2</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Pratyush Verma]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 06:22:50 GMT</pubDate>
            <atom:updated>2026-02-09T06:22:50.893Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I Designed a Musical Puzzle Game to Make Learning Fun for Kids</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VSwEs1zTFCuISIG48jyuqg.png" /></figure><p>A couple of days ago, I took on a <strong>design assignment for a kids’ learning app</strong> (part of a challenge for SKIDOS) with one goal in mind: <strong>make learning playful and engaging for children aged 3–7</strong>. The task was to design a <strong>micro-game where kids could drag and drop musical blocks to create their own tunes</strong>, combining sight, sound, and interaction.</p><p>The challenge was simple to state but tricky to solve: <strong>how do you create a game that’s intuitive for young children, fun, and educational at the same time?</strong> Over two days, I worked to balance <strong>clarity, playfulness, and responsiveness</strong> in both the visuals and interactions.</p><h3><strong>Here’s what I delivered:</strong></h3><figure><img alt="Splash Screen Design: A colorful, inviting entry point that reflects the game’s playful theme." src="https://cdn-images-1.medium.com/max/890/0*8H5TOWOJRdRqMGiI.gif" /><figcaption><strong>Splash Screen Design transitioning into Main Game Screen. </strong>Although the assignment did not mandate a specific device, I chose to design using a tablet frame to reflect realistic usage in homes and classrooms. Tablets are commonly used for shared play between children and caregivers, making reachability, touch comfort, and sustained interaction important considerations from the start.</figcaption></figure><ul><li><strong>Splash Screen Design:</strong> A colorful, inviting entry point that reflects the game’s playful theme.</li><li><strong>Game Screen UI &amp; Interaction:</strong> Five draggable sound blocks, five sequencing slots, interactive animations, and sequential playback.</li><li><strong>Figma Prototype:</strong> Fully functional drag-and-drop interactions with visual feedback and sound mapping.</li><li><strong>Design Rationale:</strong> A one-page explanation of design decisions, sound choices, accessibility considerations, and Figma file structure.</li></ul><p>This case study walks through my <strong>process, prototyping decisions, and learnings</strong>, showing how I turned a small musical puzzle into an engaging learning experience for kids.</p><h3>Target Users &amp; Context:</h3><p>This experience was designed for <strong>children aged 3–7</strong>, which is a deceptively wide range in terms of ability, behavior, and expectations.</p><p>Instead of treating this as one uniform group, I approached it as <strong>two broad behavioral clusters</strong>, based on general age-related patterns and common usage contexts in kids’ learning apps.</p><blockquote>The following user understanding is based on general age-related behavior and commonly observed patterns in children’s learning apps, rather than formal user research</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RERmrPNClwbiYdArdJK8xQ.png" /></figure><p>To ground my assumptions, I reviewed <strong>child-centric UX design principles and commonly cited patterns from kids’ learning apps</strong> (such as designing for developing motor skills, short attention spans, and learning through cause-and-effect). This wasn’t formal research, but it helped validate key considerations around touch target size, feedback loops, visual affordances, and emotional safety — all critical when designing for young children.</p><h3><strong>Design Process (2 Day Assignment):</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DC1H5v2dCkNYluINejLLpg.png" /></figure><blockquote>In a production environment, this process would be extended with user testing and iteration, but for this assignment, the focus was on making assumptions explicit and designing responsibly within scope.</blockquote><p>These principles helped me define a few non-negotiable constraints early on —<strong> large touch targets</strong>, <strong>minimal reliance on text &amp; immediate feedback</strong>, — which then directly shaped my layout and interaction decisions.</p><h4>Because the assignment centered around a single, interaction-driven experience, I moved directly into high-fidelity to validate touch sizes, spacing, and mapping — aspects that are critical when designing for young children and difficult to assess in low-fidelity wireframes.</h4><h3><strong>Getting Started:</strong></h3><p>Before getting into specific UI decisions, it was important to define the <strong>core mental model</strong> of the game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Cxi3SlC0o7LaIoU_qFjJA.png" /></figure><blockquote>I imagined this as a digital version of a physical puzzle: children pick up a piece, place it somewhere meaningful, and immediately see (and hear) the result of their action. Everything else in the interface exists to support this simple interaction loop.</blockquote><p>With that mental model in place, the rest of the design became a series of decisions around <strong>where things live, how they move, and how much guidance is needed</strong>.</p><h3><strong>Critical decisions</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MYp2eeGwd5QiJiKDyntKKQ.png" /></figure><p>One of the earliest questions was how children should move between the musical blocks and the sequencing slots.</p><p>I explored both <strong>top-to-bottom</strong> and <strong>bottom-to-top</strong> layouts. In theory, either could work — children are capable of dragging in both directions. The real difference came down to <strong>interaction comfort</strong>, not direction alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*icTUxnhj7mleqJ3mwNqp1A.png" /><figcaption>When choosing between the two layouts, reachability became the deciding factor.</figcaption></figure><blockquote>The experience was designed using a tablet frame to reflect real-world usage in homes and classrooms. This made reachability and repeated interaction comfort a key consideration in layout decisions.</blockquote><p>In a tablet-based experience, a child’s hands naturally rest closer to the lower half of the screen. Since musical blocks are used repeatedly, placing them there reduces unnecessary arm movement over time. While this slightly increases the distance between action and result, the added comfort during repeated play — especially for smaller hands — was prioritized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qRJrekBRi0IbeEzr79WUEA.png" /></figure><p>Another trade-off was deciding how strict interactions should be.</p><p>Drag-and-drop is playful and intuitive, but relying on it alone can be challenging for younger children — especially those aged <strong>3–4</strong>, whose motor control is still developing. For some, precise dragging can feel more frustrating than fun.</p><h3><strong>To make the experience more accessible, I explored supporting both dragging and tapping as valid inputs</strong>.</h3><h4>This allows children who enjoy the tactile nature of dragging to play freely, while others can simply tap to place blocks without struggling.</h4><p><strong>The learning goal remains the same — understanding sequence</strong> — but the path to get there becomes more forgiving, ensuring that difficulty in interaction doesn’t overshadow the learning itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0VXw9D3gTVCTag-gAaAVg.png" /></figure><p>A key decision was <strong>how much guidance to provide</strong> — especially knowing that children aged <strong>3–4</strong> are unlikely to open and navigate the game entirely on their own.</p><p>Instead of removing instructions altogether, I chose to include <strong>lightweight, supportive guidance</strong> that works at two levels:</p><ul><li>A short instruction line helps <strong>parents or caregivers</strong> understand how the game works so they can guide the child during first use.</li><li>At the same time, the interface itself relies on <strong>visual cues</strong> — such as dashed slots and clear grouping — to communicate what can be done, even without reading.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qrwh0uPTBVbik1HTx5d6Pw.png" /></figure><p>This balance ensures that guidance is available when needed, without turning the experience into a text-heavy or instruction-driven flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RvOMpBOshFEd5JiOT_QLvQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*l3qzp04lErhq3lnxgv9pmA.gif" /></figure><h3>Key decision was to provide <strong>immediate feedback on every interaction</strong>, rather than validating actions only after the full sequence was completed.</h3><p>As soon as a block is placed into a slot:</p><ul><li>the corresponding sound plays instantly,</li><li>and the slot visually responds.</li></ul><p>This means children don’t have to wait until all five slots are filled or press the “Play” button to understand whether their action worked. Each interaction closes the feedback loop immediately, reinforcing the connection between action and outcome.</p><p>The alternative — requiring completion before feedback — would have added unnecessary uncertainty, especially for younger children. Instead, immediate audio-visual responses make the experience feel responsive and rewarding at every step.</p><p>The “Play Sequence” button acts as an extra moment of delight, letting children replay the tune they’ve built without being essential to understanding the interaction.</p><h3>Thinking in Components and States</h3><blockquote>For completeness, key UI elements were documented as reusable components to keep interaction states consistent during prototyping.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5yiUWRrjKgJg3iFvo1QoyQ.png" /></figure><h3>FINAL OUTCOME</h3><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.figma.com%2Fproto%2F8BxiDeyE7j7dF109KExIbp%2FBuild-a-Tune---PD-Assignment-by-Pratyush-Verma%3Fnode-id%3D1-751%26t%3DXCsOt0CUhPuX1kkH-0%26scaling%3Dscale-down%26content-scaling%3Dfixed%26page-id%3D0%253A1%26starting-point-node-id%3D1%253A732&amp;type=text%2Fhtml&amp;schema=figma&amp;display_name=Figma&amp;src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2F8BxiDeyE7j7dF109KExIbp%2FBuild-a-Tune---PD-Assignment-by-Pratyush-Verma%3Fnode-id%3D1-751%26t%3DXCsOt0CUhPuX1kkH-0%26scaling%3Dscale-down%26content-scaling%3Dfixed%26page-id%3D0%253A1%26starting-point-node-id%3D1%253A732" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/fbf1502c25d2fae199e1b16fbe432b41/href">https://medium.com/media/fbf1502c25d2fae199e1b16fbe432b41/href</a></iframe><h3>What I’d Explore With More Time &amp; Access to Users</h3><p>Given more time and access to real users, I would focus on validating key interaction assumptions through lightweight testing.</p><ul><li><strong>Observational testing across age groups (3–5 vs 6–7):</strong><br>Watching how children discover and use the interaction without guidance would help validate whether visual cues like dashed slots are sufficient on their own.</li><li><strong>Comparative testing of layout direction (top-to-bottom vs bottom-to-top):</strong><br>I would test both layouts in short, structured play sessions to understand which version feels more comfortable during repeated interaction, especially on tablets. Rather than optimizing for completion speed, the goal would be to observe reachability, hesitation, and frustration signals.</li><li><strong>Refining affordance cues:</strong><br>If some children struggle to identify drop targets, I’d explore subtle animations or micro-interactions to improve discoverability without adding instructional text.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5aed780569e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Enhancing Dining Experiences: Introducing Smart Plates — Redefining Mealtime Communication with…]]></title>
            <link>https://medium.com/@pratyushvrm98/enhancing-dining-experiences-introducing-smart-plates-redefining-mealtime-communication-with-54f66f8b0786?source=rss-f9967b5bc50b------2</link>
            <guid isPermaLink="false">https://medium.com/p/54f66f8b0786</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Pratyush Verma]]></dc:creator>
            <pubDate>Sun, 04 Jun 2023 22:20:59 GMT</pubDate>
            <atom:updated>2023-06-05T06:45:35.569Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Enhancing Dining Experiences: Introducing Smart Plates — Redefining Mealtime Communication with Seamless Technology”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T70dBtfbr8KkM8wm5HAJyQ.png" /></figure><h3>Background:</h3><p>Hi Everyone! My name is Pratyush Verma, a Computer Science engineer who recently turned into a UX Designer. I am thrilled to share with you the exciting journey of my latest design project, Smart Plates. Although I have made case studies before, this is the first time I am writing a case study on Medium.</p><p>It all started when we we are required to undertake a Design Thinking project aimed at improving the user experience across various aspects of the home.</p><h3>Brief:</h3><p>We were divided into groups of 10 and each participant had to pick an area of interest in the home setup they wanna work on. I happen to take the space of “Dining Area”.</p><p>I did this project as a part of Growthschool’s UX Mastery program and under the mentorship of Anudeep Ayyagari.</p><h3>Project:</h3><ol><li><strong>Duration</strong>: 4 weeks</li><li><strong>Aim</strong>: to understand the challenges faced by users in the Dining Area and work on a design solution that solves a problem and can be used by multiple people. The goal was to generate diverse ideas that could empower users, enhance their dining experience, and provide solutions to the identified problem(s).</li><li><strong>Problem Identified</strong>: Users face challenges in achieving transparency, control, and effective communication regarding the status of food preparation and serving during their dining experience. <br><em>This is the problem I have identified and defined. In the later sections, you will see how I came down to this problem and solved it</em></li><li><strong>Solution</strong>: I came up with a product named “Smart Plates” which solves the problem defined above.</li></ol><p><strong>Here is what my product offers:</strong></p><ol><li><strong>Signal food preferences and hunger levels:</strong><br><em>Smart Plates use LED lights to indicate the user’s hunger level and food preferences.</em></li><li><strong>Facilitate effective communication between users and servers</strong> (hosts/people in the kitchen):<br><em>Smart Plates enable seamless communication between users and servers in the kitchen without the need for verbal communication.</em></li><li><strong>Enable active participation and anticipation in the dining experience:</strong> <em>The colour-changing LED light on the plate provides a visual cue for users and servers. When the plate is green, it indicates that the user is eating or doesn’t want more food. This active participation eliminates the need for manual communication or assistance.</em></li><li><strong>Reduced Waiting Time</strong>: Smart <em>Plates</em> streamlines the dining process and enables more efficient service. <em>Servers in the kitchen can prioritize serving the users who have activated their plates, ensuring that their food is prepared and served promptly. As a result, the waiting time for users is reduced, enhancing their overall dining experience.</em></li><li><strong>Convenience and Control</strong>: <em>With the switch to turn the Smart Plate on and off, users have control over signalling their hunger level. They can easily activate the plate when they are ready to eat and deactivate it when they are done.</em></li></ol><h3>Let&#39;s Dive right into the project now:</h3><blockquote><strong>Exploring</strong></blockquote><p>In order to gain a deeper understanding of the dining experience and potential pain points, I began by examining my own dining area. I carefully observed the layout, dynamics, and interactions during mealtime. I also considered various dining setups and scenarios beyond my own by looking at the different dining setups to gather potential hypotheses which I can validate by conducting interviews.</p><p>To explore the potential problems in the dining area, I utilized your hypotheses as a starting point to frame interview questions. These questions were designed to gather insights and validate your assumptions regarding the dining experience. By conducting user interviews, I aimed to understand users’ perspectives, frustrations, and suggestions related to dining.</p><p><strong>Interview questions revolved around:</strong></p><ol><li><strong>Activities that are done in the dining room.</strong></li><li><strong>Dynamics in the dining room along with other members.</strong></li><li><strong>Spacing and organisation issues in the dining room.</strong></li><li><strong>Accessibility issues in the Dining table and chair</strong></li><li><strong>External factors like Temperature and humidity affect the dining experience.</strong></li><li><strong>Cleanliness of the Dining table.</strong></li><li><strong>Factors of gadgets like phones and laptops in the dining space. It is a problem or not?</strong></li><li><strong>The situation when guests come to the user’s home</strong></li></ol><p>I interviewed 5 users who were part of my group only. The interviews lasted for approximately 25 mins and I had asked for permission to record the interview sessions for later use. I also realised that not all the Interviewees had dining tables/chairs so I had to cut down on a few questions which were not relevant to the Interviewee. To ensure a meaningful conversation, I adjusted your approach by tailoring follow-up questions based on the answers provided by the interviewee. This allowed you to gather more targeted insights and explore their dining experience in a way that was relevant to their unique setup.</p><blockquote><strong>Note-making and analysing:</strong></blockquote><p>I again went back to the recordings and was making notes regarding the observations and the problems users were facing. This also included direct quotations from the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPGaoGVHiS7RvhAKLSF3UA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ioJ4bJEQfCnHv7SDofJLnA.png" /></figure><p>I won’t punish you with every note I had taken. Here’s a zoomed version of what it looked like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlOeUqo6byrRBwbX3UqIiA.png" /></figure><p>After the note-making was done for all 5 users, I jumped to creating insights. I carefully read each note and tried to analyse what I understood from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-MYDujAeilyc9z1YCpA_w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*byIMS17frnKS7EdnkumLXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BruBLKoV00BkoNwFXd575Q.png" /></figure><p><em>You probably saw the thumbs-up and the number I have given to some insight notes. Let me explain what is going on.</em></p><p>I carefully reviewed and analyzed a large number of insights from the interviews. I identified certain insights that stood out to me as they highlighted specific problems and pain points experienced by the users.</p><p><strong>Recognizing their potential significance, I marked these insights with a thumbs-up symbol, indicating that they could potentially serve as valuable inputs for defining problem statements that are worth addressing or supporting insights I could use for defining problem statements.</strong></p><blockquote><strong>Defining problems:</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4vIcpkX7NGke1uNg3isRQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eu2Urjtq1HwQtuEPf8KlTw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i931gnHA_1KHtClOc0p6qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dj4JUN21FP1jB_BNlKYgdQ.png" /></figure><p>and it went til I had 10 defined problem statements!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5XKjYcLjjRhFcIzkhqi7mg.png" /></figure><p>After selecting the insightful observations, you proceeded to formulate problem statements based on those insights. I carefully examined each insight and determined whether it represented a surface-level problem or a root problem. For those that appeared to be surface-level problems, I engaged in deep thinking and analysis to identify the underlying root problem.</p><p>By digging deeper and focusing on the core issues, I aimed to address the fundamental challenges faced by users rather than just their immediate concerns. This approach allowed me to uncover the root causes behind the observed problems and paved the way for more effective and impactful solutions.</p><p><strong>Once I had identified a set of root problem statements, I cross-referenced them with the insight notes that you had previously marked with a thumbs-up. <br></strong>By examining the relationship between the root problems and the corresponding insightful observations, I could identify common threads and patterns. <br><strong>To organize and streamline this process, you assigned numerical labels such as 1, 2, and so on to group together the insight notes that shared the same root problem.</strong></p><p>After that, I thought about why should I solve this problem. I prioritized them based on their significance and potential impact</p><p>Upon careful consideration, <strong>I chose that problem statement 10, which addresses the challenges users face in achieving transparency, control, and effective communication regarding the status of food preparation and serving during their dining experience</strong> was a compelling problem to solve.</p><p>This problem statement resonated with me as I recognized that this problem had broad applicability and would be relevant to multiple users. I also thought that I could potentially solve multiple use cases by going ahead with this problem</p><blockquote><strong>Now let’s ideate and prototype!</strong></blockquote><p>Keeping the problem in mind, I ideated using Crazy 8. I built on the top of early ideas like “<strong>light system</strong>”, “<strong>when the user sits on the dining chair, the kitchen staff gets alerted</strong>” &amp; “<strong>use a loudspeaker in kitchen and microphone in the Dining</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-W8h5vOhw4kkBBeiNG2_dw.png" /></figure><p><strong>Combining these ideas led me to the realisation of “Smart plates”. Let me take you to the early version of Smart Plates.</strong></p><p><strong>Smart plate can:</strong></p><ul><li>can detect weight through sensors: When the user puts food on the plate, the sensor detects the weight of the food by measuring the pressure exerted on it. It translates this pressure into a weight measurement.</li><li>has switches On and off: When the smart plate is turned OFF, it behaves like a normal plate</li><li>has wifi/bluetooth(it was undecided which one to take forward or enable both technologies).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*NijscrjZKv47vTeugxYudg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjyqvyDcLNsCDg9Eju5YTQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*8GiGIdKsszhWGIT93yCalw.png" /></figure><p>And this was the realized flow of information the product will do:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gU3y4RQiG1SF2ialpf7t4g.png" /></figure><p><em>Here I was questioning myself am I making the product too complicated? Is this practical? Should I remove Bluetooth/wifi functionality? Will It make my product dependent on an external device? Will anyone use this? Can I make it simpler by not attaching the whole amazon alexa/echo part to it?<br></em><strong><em>I held on to my thoughts and let the users test and validate.</em></strong></p><blockquote><strong>Testing and Re-iterating!</strong></blockquote><p>My groupmates tested out this product, I collected feedback from the participants, and here are some of the key observations:</p><p>Criticism/concerns:</p><ol><li><em>will it be heavy when I&#39;m eating and putting the plate on my lap? What if we are taking it to/from the kitchen?</em></li><li><em>will it be expensive? I don&#39;t have Alexa in my home, so how will I use it?</em></li><li><em>It seems like I’m ordering food rudely.</em></li><li><em>Shouldn’t we make this to people can socialise more and make up for a family time?</em></li><li><em>I would be uncomfortable dining with a plate having switches and all the electrical stuff added to it.</em></li><li><em>How will I wash the plate? Can I wash the plate?</em></li></ol><p>Suggestions:</p><ol><li><em>When anyone touches the plate, the lights can turn on. so no need for a switch.</em></li><li><em>Can try charging it with contact pads.</em></li><li><strong>One user said “There is a similar product which already exists in the market at pubs and clubs called “coasters beer led</strong>”. I used this suggestion as an opportunity to improvise upon the product design and study its functionality and use case. <strong>This also gave me validation of the market demand for such a product but also provided insights into potential design improvements</strong>. “Coasters Beer LED” product may have a specific focus on beer-related features, your product aimed to expand and refine the concept for a broader dining experience.</li></ol><p>Appreciations:</p><ol><li>“I can see it working”</li><li>the idea is a unique one”</li></ol><h3><strong>Time to work on the second iteration!</strong></h3><p><strong>I did not solve every criticism/concern, I will be moving forward with the following:</strong></p><ul><li><em>will it be expensive? I don’t have Alexa in my home, so how will I use it?</em></li></ul><p><strong>This was confirmed by the doubt I had earlier. From the validation I got from my group, I decided to make it simple and less dependent on external devices or gadgets.</strong> <strong>I realised that maybe this product could only be used by very rich, elitist people and an average user might not have devices like Alexa or Echo for audio communication.</strong> <strong>At this time, I was also thinking from a selling point of you/product owner&#39;s point of view.</strong> I also thought from an average Indian household, the kitchen and the dining area are small in area and in close vicinity, so the LED lights of the smart plate itself are enough for communication of food status. I concluded to make the less tech-heavy version as the follow-up to my product. This would not require Bluetooth or any connection to external devices. <strong>This would also reduce the selling price of the product.</strong></p><ul><li><em>I would be uncomfortable dining with a plate having switches and all the electrical stuff added to it.</em></li></ul><p><strong>After studying and getting inspiration from coasters beer led and this user issue, I decided to take a different approach</strong> and design the smart plates as a base or platform onto which users can place their existing plates, bowls, or other food containers. <strong>This design choice not only addresses the safety concerns but also provides flexibility for users to use their own preferred tableware while still benefiting from the smart features of the underlying base.</strong></p><ul><li><em>How will I wash the plate? Can I wash the plate?</em></li></ul><p>Now<strong> users wouldn’t need to wash the plate</strong>, all they need to do is put their regular plate or bowl on top of the smart plate to enjoy the functionality of the product. <strong>No need to compromise on convenience or practicality!</strong></p><ul><li><em>will it be heavy when I’m eating and putting the plate on my lap? What if we are taking it to/from the kitchen?</em></li></ul><p>the <strong>all-new re-designed Smart plate doesn&#39;t need to be carried all that often</strong>,<strong> it can stay in a place and the actual plate/bowl for dining can be placed on top of it.</strong></p><blockquote><strong>ADDITIONAL ITERATIONS I DID FOR THIS:</strong></blockquote><ol><li><strong>I decided to do more research on the material of the product and decided to go with ABS plastic</strong> as ABS plastic <strong>offers sufficient durability and strength </strong>for regular use, making the plates resistant to potential impacts or accidental drops. Also, can <strong>accommodate</strong> the integration of electronic components, such as <strong>LED lights and circuitry. </strong>ABS plastic is a widely available material and can be mass-produced at a relatively lower cost.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*CcOnLTisVDAVhIU7uUiQ-Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-hTc9gbA0eTX9fXwRN27IQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlMhMmVTgWlUUQ9-o4sypA.png" /></figure><p>2. In the new iteration of the smart plate concept, when a cup, bowl, or normal plate is placed on top of the smart plate and the device is switched on, the weight registered by the smart plate would initially be zero. However, as soon as food items such as gravy or bread or any other food is added to the cup or plate, the weight will increase, triggering the green light to turn on.</p><p>T<strong>his approach ensures that the smart plate only detects the presence of food when it is actually placed on top of the cup, bowl, or plate.</strong> The weight-sensing mechanism allows for a more accurate indication of whether the user is ready to eat or not. When no food is present, the smart plate will not register any weight and therefore will not turn on the green light, indicating that the user is not hungry.</p><p>3. <strong>unlocked another use case: </strong>In the new use case, the smart plate can be utilized by servers to monitor the food consumption of multiple users dining together. Let’s consider a scenario where three users are eating together and a large bowl of food is placed on the smart plate at the centre of the table by the server.</p><p>As the users consume the food from the bowl, the weight registered by the smart plate decreases. When the food level reaches a certain threshold, indicating that it is almost empty, the smart plate can activate a red light to indicate to the server that more food is needed for the users who are currently eating. This eliminates the need for users to individually ask the server to refill their plates.</p><p><strong>Here’s an illustration for the second iteration of the product. I wanted to go the extra mile and used midjourney to realise the product.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T70dBtfbr8KkM8wm5HAJyQ.png" /></figure><p><em>on the left( assume the product colour is green) || On the right, the red colour indicates the need for food.</em></p><h3>Future Scope for Improvement in the product design:</h3><p>The product has the potential for further improvement in order to enhance the overall usability experience for the user. Some areas of future development and refinement include:</p><ol><li>User Testing on the second version of the product</li><li>Mobile App Integration: developing a companion mobile app that pairs with smart plates. This app could provide users with real-time updates on the status of their food, allow them to customize settings, and track their dining preferences over time.</li><li>Customizable Portion Control: Introduce a portion control feature that allows users to customize their serving sizes based on their preferences and dietary goals. The smart plates can provide visual cues or notifications to help users maintain portion control and promote healthy eating habits.</li></ol><h3>learning and realisations:</h3><ol><li>Realised the importance of testing and validation of the prototype from the users. Working on the feedback will always get you a better product.</li><li>Realised that there is always going to be scope for improvement yet I can’t make products that can satisfy everyone.</li><li>Understood it is also important for your product to be practically useful.</li><li>If your product is similar to an already existing product, You can take it in the form of validation and drive further improvement and work on use cases.</li><li>Learn the importance of getting the hypothesis validated with actual user, early on in the design process.</li><li>I learnt prototypes needn’t necessarily be fancy or time-consuming as long as they communicate the idea.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54f66f8b0786" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>