<?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 Vidhyasagar H.V on Medium]]></title>
        <description><![CDATA[Stories by Vidhyasagar H.V on Medium]]></description>
        <link>https://medium.com/@uxsagarv?source=rss-40a0cf3033c6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jp3KjO6H5tb22jaJUP_Y_g.jpeg</url>
            <title>Stories by Vidhyasagar H.V on Medium</title>
            <link>https://medium.com/@uxsagarv?source=rss-40a0cf3033c6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:15:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@uxsagarv/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[Crafting UX for Elderly: A Unique and Special Interview]]></title>
            <link>https://medium.com/@uxsagarv/crafting-ux-for-elderly-tcs-disq-unveiling-personal-insights-and-key-learnings-7940ca4cdb87?source=rss-40a0cf3033c6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7940ca4cdb87</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[designing-for-elderly]]></category>
            <dc:creator><![CDATA[Vidhyasagar H.V]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 12:23:50 GMT</pubDate>
            <atom:updated>2023-09-06T14:26:44.607Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I’m excited to highlight some personal experiences and the interview process as a key highlight of the research and share how my personal interviews influenced our next steps while designing for elders/seniors. 🌟👵.</p><h3><strong>Background</strong></h3><p>While <strong>I interned at @humcommunities</strong>, an innovative social enterprise in India, focused on empowering retirees and seniors in their “Second Innings.” — <strong><em>A Social Enterprise for the Elders in India</em></strong></p><p>The platform 3 core functionalities are —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G1VBgc5txssqLI5ActX0Qg.png" /><figcaption><a href="https://www.humcommunities.in/">https://www.humcommunities.in/</a></figcaption></figure><p>Humcommunities was in<strong> aim to create India’s first all-in-one age-tech venture</strong> to tackle challenges like financial dependency, imbalanced Ikigai, and social isolation among seniors.</p><p>Let’s Dive in..</p><h4><strong>Facts about Designing for the Elderly <em>(desk research Insights)</em></strong></h4><ul><li>By 2030, <strong>1 in 6 people in the world will be aged 60 years or over.</strong></li><li><strong>The digital divide is a recognized global issue,</strong> Evidence shows older adults self-exclude, and experts in the digital technology realm sometimes contribute to this divide.</li><li><strong>The lifespan of the elderly</strong> who are more than 65 years old, <strong>is increasing.</strong> Thanks to advancements in science and technology</li><li><strong>More senior citizens rely on Smartphones than the younger generation,</strong> The survey conducted by YouGuv among over 1,000 citizens in India, shows that 79% of respondents aged 60–65 need their smartphones the most.</li></ul><blockquote>However, the important question is that <strong><em>Are the currently designed and implemented applications suitable for elderly people?</em></strong></blockquote><h4>Interview process (primary research)</h4><p><em>(Emphasizing my interview experience, it stood out distinctly from other interviews as it delved into a unique and uncharted territory.)</em></p><h3><strong>Problem Statement:</strong></h3><blockquote>Analyze and Propose a Roadmap for a User-Friendly Feature to Enable Elderly Users to Conduct Meetings Flawlessly on the “Humcommunities” Platform.</blockquote><h3>Why?</h3><p>Company’s mission to <strong>contribute towards creating Hum Communities as a one-stop portal,</strong> to address all their aspirations and desires, evoking the feeling that this platform is <em>“made just for me !”</em></p><p>To empower elderly users to host and participate in live sessions and meetings. Currently, the platform relies on traditional methods, such as sharing Zoom meeting links, to facilitate these meetings.</p><h3>Gearing up</h3><p>So,</p><p>before beginning, I made a few Key Considerations:<em> ( Considerations were made based on the last few week’s hands-on experience designing posters for hum platform)</em></p><ol><li>Elderly users may face unique challenges related to technology adoption, physical capabilities, and cognitive abilities.</li><li>The goal is to create a user-friendly interface that minimizes confusion, caters to accessibility needs, and simplifies the meeting organization process.</li><li>The roadmap should align with best practices in user experience design for elderly users.</li></ol><h3>What can I learn from traditionally used “ZOOM and TEAMS” for meetings and Live sessions?</h3><p>As someone who regularly observed elderly individuals at Humcommunities using Zoom for live sessions, I sought to uphold the platform’s best practices, Not to reinvent the wheel but get inspire, Enhance and Tailor the existing.</p><p>which also align with Jacob’s Law “<em>Jacob’s Law emphasizes the significance of familiarity and consistency in user interface design”</em></p><h4>In preparation for my task, I needed to gain insights into the usability challenges that elderly individuals encounter when setting up Zoom and Teams meetings.</h4><p>Through a heuristic analysis of the Zoom and Teams platforms, I made some assumptions about potential obstacles that could be encountered by elderly users. The following understanding from secondary research made me see through clearer lenses</p><ul><li>To Use minimal design to prevent cognitive issues in senior citizens.</li><li>Avoid irrelevant content on the screen.</li><li>Provide clear instructions on how to use the Feature.</li><li>Provide only those features that are required by the person.</li><li>Should have simple and easy navigation.</li><li>Limited gesture control within the app.</li></ul><h3>Heuristic analysis (Zoom and Teams)</h3><ul><li>Elderly users may face challenges in discerning whether their microphone and camera are active or muted due to small, indistinct icons. Additionally, they might find it difficult to locate visual cues for ongoing screen sharing or chat notifications. — <strong>Visibility of system status</strong></li><li>The use of technical jargon and icons that do not align with everyday language and concepts may pose a significant barrier for elderly users. For instance, terms like “Share Screen” or “Participants” may not immediately convey their functions — <strong>Match Between System and the Real World</strong></li><li>Elderly users may have difficulty remembering complex steps for tasks like scheduling meetings, setting preferences, or accessing advanced features between sessions. The need to recall these steps could hinder their usability- <strong>Recognition Rather Than Recall</strong></li><li>In the event of technical errors or connection issues, elderly users might struggle to interpret cryptic error messages, leading to confusion and anxiety. Without clear guidance on how to resolve issues, they may experience difficulties recovering from errors.- <strong>Help Users Recognize, Diagnose, and Recover from Errors</strong></li><li>Elderly users may inadvertently make settings changes or leave meetings due to unclear prompts or a lack of confirmation dialogs — <strong>Error Prevention</strong></li></ul><h3><strong>USABILITY STUDY</strong></h3><p>My approach is to conduct a qualitative focusing on the collection of firsthand information from users, documenting their experiences through note-taking, and subsequently deriving behavioral patterns and insights from this gathered data.</p><p>Using simple random sampling, to avoid bias that could arise from selecting users I already know, making my research more reliable and generalizable to the broader population of elderly users.</p><p>Think out loud technique — Explain and probe while they get confused and need to be written down before the interview</p><p>Setting Observation points — not just while interviewing and want to note down few observation points before hands.</p><h3><strong>Questions :-</strong></h3><blockquote><strong>1. General Impressions:</strong></blockquote><blockquote>Question: What are your initial thoughts about using this application for online meetings?</blockquote><blockquote>Behaviors/Notes: Observe their first impressions, including ease of navigating the interface and any comments on the overall look and feel.</blockquote><blockquote><strong>2. Starting or Joining a Meeting:</strong></blockquote><blockquote>Question: Can you show me how you would start or join a meeting using this application?</blockquote><blockquote>Behaviors/Notes: Note if they struggle to locate the options or buttons for initiating or joining a meeting. Pay attention to any hesitation or confusion in the process.</blockquote><blockquote><strong>3. Adjusting Settings:</strong></blockquote><blockquote>Question: How would you go about adjusting audio and video settings for your meeting?</blockquote><blockquote>Behaviors/Notes: Look for difficulties in finding and modifying audio and video settings. Note if they encounter any issues with terminology or icons.</blockquote><blockquote><strong>4. Screen Sharing:</strong></blockquote><blockquote>Question: Could you demonstrate how you would share your screen with others in a meeting?</blockquote><blockquote>Behaviors/Notes: Observe any challenges they face in initiating screen sharing, selecting the content to share, or navigating through screen sharing options.</blockquote><blockquote><strong>5. Managing Participants:</strong></blockquote><blockquote>Question: If you wanted to mute or unmute someone in the meeting, how would you do that?</blockquote><blockquote>Behaviors/Notes: Pay attention to their ability to manage participants, including muting/unmuting and removing participants if necessary.</blockquote><blockquote><strong>6. Using Chat and Messaging:</strong></blockquote><blockquote>Question: Can you show me how you would send a chat message to someone in the meeting?</blockquote><blockquote>Behaviors/Notes: Note any difficulties in using the chat feature, including typing messages, sending, and responding to messages.</blockquote><blockquote><strong>7. Troubleshooting Issues:</strong></blockquote><blockquote>Question: Imagine you encounter a problem during the meeting, like audio not working. What steps would you take to troubleshoot it?</blockquote><blockquote>Behaviors/Notes: Assess their problem-solving skills and their ability to navigate troubleshooting options within the application.</blockquote><blockquote><strong>8. Accessibility Features:</strong></blockquote><blockquote>Question: Are you aware of any accessibility features in this application? If so, could you show me how you would use them?</blockquote><blockquote>Behaviors/Notes: Observe if they are aware of and able to utilize accessibility features and if these features are effective for them.</blockquote><blockquote><strong>9. Overall Satisfaction:</strong></blockquote><blockquote>Question: On a scale from 1 to 10, how satisfied are you with your experience using this application for online meetings? What do you like or dislike about it?</blockquote><blockquote>Behaviors/Notes: Summarize their overall satisfaction level and capture key likes and dislikes.</blockquote><h3>After validating my assumptions and connecting notes</h3><p>Below is a detailed UI roadmap and flow proposal that incorporates elements inspired by Zoom and Teams while addressing elderly users’ drawbacks. This roadmap is designed to create a Minimum Viable Product (MVP) that prioritizes essential features and accessibility improvements.</p><p><a href="https://docs.google.com/document/d/1lH6Rc4lxZby4wBXsYZFc5hVtB9c833fhMFt4A9wA0Y8/edit?usp=sharing">https://docs.google.com/document/d/1lH6Rc4lxZby4wBXsYZFc5hVtB9c833fhMFt4A9wA0Y8/edit?usp=sharing</a></p><h4><strong>Moving ahead, other MAJOT personal learnings to highlight were</strong></h4><ol><li><strong>Use of Confusing Jargon:</strong> Use of technical jargon or terminology that is unfamiliar to older users.</li></ol><blockquote>In response, steering clear of non-universal icons and abbreviations when designing for the elderly is not just a good practice; it’s a strategic move to ensure your app’s success, accessibility, and user satisfaction across the board.</blockquote><p><strong>2. Privacy Concerns:</strong> Concerns about data privacy and sharing personal information with apps and online services.</p><blockquote>In response, Building empathy and patience when designing for this demographic is key. I learned to consider their unique needs and preferences.</blockquote><p><strong>3. Cognitive Overload</strong>: Difficulty in processing large amounts of information or complex navigation paths within apps.</p><blockquote>In response, I learned to present information in smaller, digestible chunks and avoid unnecessary complexity.</blockquote><p><strong>4. Navigation:</strong> Struggles with navigating due to unfamiliar gestures or interactions, such as swiping or pinching.</p><blockquote>In response, Understanding the real-life context of elderly users helped tailor the app to their daily routines and interests. <strong>“Match between system and real world”</strong></blockquote><p><strong>If the above is not taken care may lead to </strong>Resistance to learning new technologies and a preference for familiar, traditional methods of communication and information.</p><h4><strong>Looking back, What I could have done better, which I learnt later</strong></h4><ul><li>To tailor User Interviews and do a little research on the person I am interviewing better, and not be just Q&amp;A but rather a fun jovial interview session.</li><li>Ensuring that I map behavioral insights accurately to gain a better understanding of the interviewee’s perspectives and motivations. “By not being hesitant to ask if I can reach out to them again in case further probing is required”</li><li>Properly structuring the questionnaire to include essential components such as a clear goal, timeline, fundamental questions, probing inquiries, and a conclusive discussion. This strategy aims to prevent any confusion and ensure a well-rounded interview process.</li></ul><p><strong>PFA Link to the checklist I followed:-</strong></p><p><a href="https://docs.google.com/spreadsheets/d/1Qb5AyQiIJrG328cxDAhMSqAMJYEj6QFFaAbxUIaHQm4/edit?usp=sharing">Design Checklist - Vidhyasagar</a></p><p><strong>Conclusion</strong></p><p>I was part of the strategy, and design department, and very thankful to Humcommunities. When I joined The company was in its early stages of implementation and experimentation, which provided me with the freedom to pitch my ideas. I also had room to make mistakes and experiment. Which I will always be grateful for.</p><p><strong>Why is there a gap while designing for Ealderly? (My understanding)</strong></p><ul><li>Little experience with Older Adults</li><li>Tendency to ignore pure data on Older Adults</li><li>Exclusion of Older Adults from design, evaluation</li><li>Perceived lack of market incentive</li><li>Aging not a “sexy” topic</li></ul><p><strong>Summing up</strong></p><p>Additionally while Interviewing,</p><ul><li>Adapt study protocols for older adults</li><li>Special considerations: recruitment, retention, compensation</li><li>Be sensitive in communication</li><li>Be respectful, patient, supportive, grateful</li><li>Minimize distractions</li><li>Keep sessions short; build in breaks</li><li>Allow extra time for everything</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I92rMTr76rVARpOU.jpg" /><figcaption>Random Cute Granny&#39;s</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7940ca4cdb87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revamping the Kitchen Experience: Key Learnings from Applying Design Thinking]]></title>
            <link>https://medium.com/@uxsagarv/revamping-the-kitchen-experience-key-learnings-from-applying-design-thinking-731caf64dff3?source=rss-40a0cf3033c6------2</link>
            <guid isPermaLink="false">https://medium.com/p/731caf64dff3</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Vidhyasagar H.V]]></dc:creator>
            <pubDate>Mon, 27 Mar 2023 07:30:51 GMT</pubDate>
            <atom:updated>2023-03-27T18:20:16.607Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this case study I emphasize on major Unlearnings and learnings that I had from my mistakes. This case study is written in a conversational manner between Me(Vidhya) and my Mentor(Anudeep).</em></p><h3><strong>About the Project</strong></h3><p>As a Brand strategist, I have done Design thinking projects before to formulate business strategies, but this project is unique as the outcome is focused on three major factors.</p><ol><li>This case study is to <strong>document the valuables I learned</strong> and the <strong>perspectives that shaped my way to approach</strong> the design thinking process.</li><li><strong>Unlearning things</strong> — which allowed me to learn from a previous experience while making room for new learning.</li><li><strong>Learning from Mistakes</strong> after critical reviews by my mentor.</li></ol><p>Also, as my Mentor Anudeep Quoted —</p><p><strong><em>“This exercise is all about self learning and through non templated and non- Text book approach”</em></strong></p><p><strong>But first, a little bit more About me</strong></p><p>I am Vidhyasagar, A Brand Strategist upskilling to UX Designer. Currently perusing a UXM mastery course under the expert guidance of my Anudeep Ayyagari (UX Designer @ Amazon) from GrowthSchool.</p><h3><strong>Phase 1 — Why, How and What’s of Design Thinking.</strong></h3><blockquote>Vidhya : — Hi Anudeep, I am a Brand strategist enrolled your mentorship programme to transform into a UX designer — How do I start the process?</blockquote><blockquote>Anudeep : — As you transition you need to —</blockquote><p>👉 <strong>Become a Designer first</strong> — On the journey of becoming a product designer working for impacting businesses, you need to become a <strong>Designer</strong> first and a Design thinking project helps us become designers.</p><p>👉 <strong>Unlearn Things </strong>— Unlearning is important to understand the heart of design thinking or you might end up as an artificial designer. In other words you will be doing a of of things other UX designers as templated copy but will be missing the heart of the design.</p><p>👉 <strong>Make Mistakes and Learn</strong> — I have designed this project in trapping you into making the maximum possible mistakes and Eradicating <strong>Perfectionist approach</strong>.</p><p>👉 <strong>Should not think problems backward</strong> — Shouldn’t think of problem backward for that we need to become Design thinkers first, That’s how we are valuable people and DTP helps achieve that.</p><p>Insights after discussion with Anudeep:-</p><ul><li>I need to Participate<strong> </strong>— by <strong>Keeping a perfectionist mentality aside</strong>— It’s okay to make mistakes and Anudeep will correct it because that’s how I learn.</li><li>Becoming the person first — I am going to focus on unlearning first to <strong>break the misconceptions that are prenotion what UX designers</strong> are and minimize personal bias that I may carry from past experiences.</li></ul><h3>BTS — The Beginning of DTP</h3><p><em>(Group allocation and Rules, Selection of problem statement/Area , Fight for topics, Learnings)</em></p><p>I was added to a group consisting of 8 students. All of our team members will be working on different areas of the house, <strong>Around 11 areas were given and each had to work on different areas of the house with no overlap for that we had to FIGHT for our Topics.</strong></p><blockquote>Our Group : — Why fight for topics? Why are we working on physical products and not digital ones?</blockquote><blockquote>Anudeep : —</blockquote><p>👉 The more we fight the more convection we will have about this topic, <strong>develop the reasoning skills, Build rationale and connect the dots</strong> of thought process.</p><p>👉 <strong>Why areas of the house? </strong>We are very comfortable living in the house and when we question ourselves some might say I don’t want to change anything in my house or we say problems to solve what we personally face in the house.</p><p>👉 <strong>“Select the topic which is most uncomfortable”</strong> so you will have the maximum amount of learning and least amount of bias in pre notioned solutions.</p><h3>The Fight</h3><p>I choose Kitchen and the reasoning I gave</p><p>“ Hi guys I will be taking Kitchen area as my DTP topic, because I believe the kitchen is something where all the hustle and bustle happens. Kitchen is also a place where hazardous things lie such as knives and flammables and cockroaches lol. This topic interests me as I will be putting myself out-of my comfort zone(bedroom) and solving problems in a territory unfamiliar to me. It will help my broaden my perspective on deep thinking and problem identification. I am willing to vibe with the roaches. Also I hope I’ll help solving kitchen-related issues.”</p><h3>Phase 2 — Design thinking Process (Kitchen)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*GKoOEsWzufgCOwVE.png" /></figure><h3>1️⃣ EMPATHIZE</h3><p><em>(Preparing questions to understand your users’ problems → Interviewing users 1v1 → Taking notes.)</em></p><p>To understand the USERs’ perspective! At this stage, I need to connect with the users(at least 5 people in the group) and understand and immerse in THEIR perspectives/experiences about Kitchen.</p><p><strong>Context Before Interviewing — </strong><em>(Insights from Mentor and work book guidelines)</em></p><ul><li>I need to write down at least 5 or more ( keep the limit to 15) questions that I would want to ask and speak to my users about.</li><li>The interview is not for giving them solutions to their problems. It is <strong>about identifying their problems.</strong></li><li>My questions should revolve around identifying what problems my users have in the topic area. At this stage I need to connect with the users and understand and immerse in <strong>their perspective.</strong></li><li><em>no way,</em> I bring in your own answers or answers from people I know. <strong>I must completely avoid any bias</strong> which leads to you putting in what ‘I’ think is the answer.</li><li>When I am interviewing my user, <strong>strictly avoid suggesting to them what you think is the solution.</strong></li><li>Avoid directly asking what problems your users have. My users will usually not tell you what problems they have, because they don’t even realize that they have problems. <strong>It is my job to understand problems</strong> from the conversation you have with them.</li></ul><p><strong>Execution</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*baz7x8AFZKsvf-IvuvjumA.png" /><figcaption><strong>Questionnaire I prepared</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*mI2pKEGs0OUg1wuY6tnXlA.png" /><figcaption><strong>Insights noted — Example 1 of 5 users</strong></figcaption></figure><p>📝 <strong>Learnings after Feedback from Peers and Mentor</strong></p><ul><li><strong>You ≠ User?</strong> It is very important to unlearn and learn this simple yet significant mindset.</li><li><strong>We are not doing consultations as UX designers,</strong> It is all about collecting data, Don’t suggest solutions until the last. We are not giving back and we shouldn’t also.</li><li>Don’t think of any ideas that you have to build product or concept at this stage, <strong>Just understand the problems and keep ideas aside and bring it back in ideate stage</strong></li><li>Idea Ultimately we will end up solving one particular problem in that area, I<strong>n order to build a product to make sense and solve the problems we are interviewing real uses making research.</strong></li><li>Make sure the questions are conversational in nature. Our questions should indicate what I want to Know and act as a mere guide.</li></ul><p>Mistakes I made in Questionnaire</p><ul><li>Avoid questions that get you only one-word answers.</li><li>Vague Question to be avoided.</li><li>leading questions needs to be avoided.</li><li>Biased and gave options to choose.</li></ul><p><em>About Note-taking</em></p><ul><li>Make notes of every interview you take, either digitally or physically in a notebook. Keep the notes handy and well-organized.</li><li>Take notes as soon as you finish your interviews. Or else you will forget!</li></ul><h3>2️⃣ DEFINE</h3><p><em>( Go through the insights you have written in previous section → Write down all the problems of all the users here -&gt; Write down WHY each of those problems are important to the users.)</em></p><p>This is the stage at which I typically would frame problem statements based on what I have observed from the Empathize stage. <strong>To DEFINE and write ALL the problems </strong>that could be solved for all the users that I have interviewed. <strong>Write it from the users’ perspective</strong></p><p><strong>Context before Defining — </strong><em>(Insights from Mentor and work book guidelines)</em></p><ul><li>Try and frame problem statements, don’t make them too long. Keep it contextual of the users’ problems.</li><li>It is very important to focus only on the problem here. <strong>Strictly avoid getting into solutions for the problem</strong>!</li><li>Also to avoid writing problems which are not related to the topic area given to me. <strong>We are not here to solve every problem in the world!</strong></li></ul><p><strong>Execution — What</strong>⚠️<strong> and Why</strong>❓ (Some examples)</p><blockquote>⚠️<strong>Issues with learning how to cook mostly for guys</strong> — ❓ It is important to solve the this issue because people who are not accustomed to kitchen need to know how to cook at their later part of their lives.</blockquote><blockquote>⚠️<strong> I have issues with managing the waste generated in the kitchen </strong>— Lack of knowledge about waste management, Lack of space, Lack of organization, Limited access to recycling and composting facilities, Habits and behaviors.</blockquote><blockquote>⚠️I have issues related to bugs/ Unwanted crickets in the kitchen</blockquote><blockquote>⚠️Cleaning up issues after i get tired working in the kitchen</blockquote><blockquote>⚠️I face space Storage issue and Less kitchen space</blockquote><blockquote>⚠️Storage and Discarding issues identified</blockquote><blockquote>⚠️Attention to things before checkout</blockquote><blockquote>⚠️Fridge is a messy place</blockquote><blockquote>⚠️Cleaning corners of the kitchen is a hassle</blockquote><blockquote>⚠️Too many people may accompany in kitchen</blockquote><blockquote>⚠️Sometimes it gets boring in kitchen</blockquote><blockquote>⚠️Things are kept and forgotten. Doubtfulness on things</blockquote><blockquote>⚠️Smell and Waste segregation issues</blockquote><blockquote>…………………………….. (Cont.. +30)</blockquote><p>📝 <strong>Learnings after Feedback from Peers and Mentor</strong></p><ul><li>Good notes and good documentation in the Empathize section, will lead me with a lot of problems that your users don’t even realize that should be solved!</li><li>We shouldn’t define problem solution backwards. when we define problems there should not be a solution in it. we should understand the root problems.</li><li>To Identify and write why is also very important — avoid generic reasons be specific.</li></ul><h3>3️⃣IDEATE</h3><p><em>(Write down all the ideas you came up with -&gt; Using Crazy 8Write down your top 3 ideas here? 🥇🥈🥉 You must give reasoning why these ideas are the best)</em></p><p>This is the stage when I should start thinking of solutions to the users’ problems. YES, I need to get to solutions only now, after I understand what the problems are. That is why it was important to not jump to solutions until this stage.</p><p><strong>Crazy 8 Technique</strong></p><ul><li>To Each problem now state each problem and put a timer of 8 minutes and come up with 8 ideas for the problem and Come up with 800 ideas.</li><li>Why 8 minutes only? to put our brain in time limit to exercise it better — We might fail after getting 3 ideas and that’s when we will go back and define the problems better and come back.</li><li>The heart of the ideas is to human brain will automatically start thinking about ideas ( 1 or 2 ) when a problem id put forth after 3 our brain will clog and run out of ideas.</li><li>Exercise your brain — Will enable — Think deeper — define deeper — more definition you add to it the more you will understand to get specific ideas and more ideas.</li></ul><p><strong>Context before Ideating — </strong><em>(Insights from Mentor and work book guidelines)</em></p><ul><li>Keep the problem statements in front of you, DON’T deviate from the topic.</li><li>You will choose top 3 ideas from all the ideas you have written.</li><li>For example, if you have written 42 ideas, you will keep ranking them and come up with top 3 ideas. You can also use your buddies’ help optionally.</li><li>Idea and top 3 ideas — converge them — Have logical reasoning for yourself.</li></ul><p><strong>Execution — By using crazy 8</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*9bVKFDhu1m_8giw-zwgLJA.png" /><figcaption>Workbook snap shot of Crazy 8 for all the Problems</figcaption></figure><p>for all the problems…………….</p><blockquote>Now I realized that I haven’t defined the problems well enough so I went back to define stage to understand the problems better. After re defining and Ideating my Top 3 Ideas were</blockquote><h3>1💡Issues with learning how to cook mostly for guys — A e-journal</h3><p><strong>Reason you picked this idea: </strong>I picked up this idea because from user interviews i found that people are not exposed to cooking since childhood so once they move into other cities they might face problems on learning cooking from scratch.</p><h3>2💡Attention to things before checkout — A fridge magnet checklister</h3><p><strong>Reason you picked this idea: </strong>From user interviews i noted that people are forgetful on things, Mostly in kitchen where there is constant activity of turning things on and off it is important to have indicators or double check on things. If you’re out have you ever wondered if / if not you have turned off your stove? Well this is common happening.</p><h3>3💡Cleaning near Sink — by Inventing a device to soak dishes in hot water</h3><p><strong>Reason I picked this idea: </strong>In the case of the kitchen, the sink area is a commonly used space where users may encounter a range of challenges. Here’s an example of how I could have figured out that the sink area is one of the main problematic areas in the kitchen</p><p>📝 <strong>Learnings after Feedback from Peers and Mentor</strong></p><ul><li>I cant solve all the problems and its difficult to pick one problem and solve it.</li><li>Designing is not a linear process, I went back to the Define stage again which is totally okay.</li><li>Adapting tools like crazy 8 is totally need based/Opt tools which will aid you to reach your end goals.</li></ul><h3>4️⃣ PROTOTYPE</h3><p>( Selection one idea of the 3 best ideas I choose -&gt; Prototype my idea)</p><p>I will select one idea of the 3 best ideas you choose. I need not combine the ideas. This is the stage where I actually make a representational model of the solution you came up with.</p><p><strong>Finalizing Idea no 3</strong></p><h3>3💡Cleaning near Sink — by Inventing a device to soak dishes in hot water</h3><p>If you’ve ever had to deal with a pile of dirty dishes, you know how much of a chore it can be to clean them all. Especially if you have dishes that have been sitting for a while and have hardened food stuck on them. This is where my invention of a device that soaks dishes in hot water comes in.</p><p>The idea behind this device is to make the process of cleaning dishes faster and more efficient. By soaking dishes in hot water, the hardened food and grease can be easily loosened, making it easier to scrub them clean. This is a tried and true method of cleaning dishes that has been used for generations, but my device would make the process even more effective.</p><p><strong>Context before Prototyping — </strong><em>(Insights from Mentor and work book guidelines)</em></p><ul><li>I will prototype our idea with anything available in my house, paper, clay, waste or unused items, or I can also do a simple sketch, an origami, drawing, anything I can think of.</li><li>Not to spend too much time in prototyping. The point of this exercise is to quickly test your ideas.</li><li>This is the stage where you actually make a representational model of the solution you came up with.</li></ul><p><strong>Prototype</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o0xEJIP5HjEeumUsAdTfoA.jpeg" /><figcaption>Initial Prototype</figcaption></figure><p>📝 <strong>Learnings after Feedback from Peers and Mentor</strong></p><p><strong><em>learnings while Prioritizing</em></strong></p><ul><li>What problems to solve we need to prioritize and have a logic and reason to convenience stake holders that this is the problem to solve that matters a lot.</li><li>Reason why we are picking these ideas. Why we are doing this. To convince your stakeholders that your decisions are valuable.</li></ul><p><strong><em>learnings while Prototyping</em></strong></p><ul><li>The more effort we put the more unwilling we will be changing the design and hence prototyping should be very basic without much effors. Also, if you love your design too much you will refuse to receive feedback.</li><li><strong>The main thing to unlearn here is being perfect. This is the stage where I renounce my perfectionist mentality.</strong></li></ul><h3>5️⃣ TEST</h3><p><em>(Write down the feedback the users gave to your idea along with their reasons -&gt; Write down the changes you will make in your solutions after incorporating the feedback from your users.)</em></p><p>I don’t know if it works or not. So All of us participated in testing stage, We decide to have a call and present a prototype and work on feedback. To Present my workbook in the call. Everyone will first listen to you without interrupting you. When you are done, ask for feedback. Ask others to give feedback on your idea on and ask them to share their reason for the feedback.</p><p><strong>Context before Testing — </strong><em>(Insights from Mentor and work book guidelines)</em></p><ul><li>Write down the feedback and work on insights — Make a revised prototype and finish it. By this stage, we come to a point where we would test the prototype we have built. By testing, we mean, getting feedback on it.</li><li>Solving the problem is just not enough. It is important that it works!</li></ul><p><strong>Explanation notes to Peers for testing</strong></p><p>Advantages of inventing a device to soak dishes in hot water.</p><ol><li>Time-saving: By soaking dishes in hot water, the device can help to loosen hardened food and grease, making it easier to clean the dishes.</li><li>Energy-saving: By using a container that holds hot water and a platform for the dishes, the amount of water used can be reduced, which can save on water bills.</li><li>Environmentally-friendly: By using less water and requiring less energy to heat the water, the device can help to reduce your carbon footprint.</li><li>Improved cleaning: By loosening the food and grease, the device can help to remove stubborn stains and make the dishes look like new again.</li><li>Safe and easy to use: The device can be designed to be easy to use, with a heating element to keep the water hot and a timer to ensure that the dishes are soaked for the optimal amount of time.</li></ol><p>Hot water can be very effective in cleaning dishes for several reasons:</p><ol><li>It helps to dissolve grease and oil: Hot water breaks down grease and oil, making it easier to remove from dishes.</li><li>It kills germs and bacteria: Hot water can help to sanitize dishes, killing any bacteria or germs that may be present.</li><li>It softens stuck-on food: Hot water can help to loosen and soften any food that may be stuck to dishes, making it easier to scrub off.</li><li>It can speed up the cleaning process: Hot water can help to speed up the cleaning process by making it easier to remove food and grease from dishes.</li></ol><p><strong>Feedback I received</strong></p><ul><li>Electricity bill</li><li>Too many dishes</li><li>Smell of stagnant water</li><li>Some dishes ware out because of delicacy and long exposure to warm water</li><li>Pouring and Unpouring of hot water</li><li>Electric connection or Manually pouring the Hot water.</li></ul><p><strong>Final Product after revamping from Feedback</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XKhaOQ9t0J18DZ9etTGkug.jpeg" /><figcaption>Final Prototype</figcaption></figure><p><strong>📝 Learnings after Feedback from Peers and Mentor</strong></p><ul><li><strong>When others give feedback. Listen to them. Let them finish.</strong> Don’t justify it immediately. The idea of this exercise is not to justify. The idea is to understand what works and what doesn’t work.</li><li>Answer the questions with what you have already done. Don’t answer hypothetically, or make up answers on the spot.</li><li>When you get feedback, it is important that they share the reason. Ask them for a reason if they don’t state it</li><li>Put some effort into getting feedback. Don’t let your brain tell you that there is no feedback and everything is perfect. There will always be feedback.</li><li><strong>Don’t take anything personal.</strong> To realize that the feedback on your ideas is different from feedback about you. I realized that, until I test my prototype back with my users, I wouldn’t completely know if solution worked or not.</li></ul><h3>Phase 3 — Summary of My Key Learnings &amp; Future Scope of work</h3><h3>Learnings</h3><p>👉<strong>Its not a strictly Linear approach</strong> — A design thinker is not the person who follows the process but the person who automatically follows the Design thinking without even realizing that you are following the process.</p><p>👉 <strong>Problem solving is not a philanthropic thought — </strong>If I build solutions for myself I wont build a business with it, instead I will end up solving my own problems. I need to go and understand what works for others/What work for large no of people only then I will be able to keep my bias aside and have will to learn what works for others and make impact the business.</p><p>👉<strong> Unique strength they bring to the team. — </strong>One of my core strengths is Record keeping and moderating tasks/Events. I am also good at critical thinking and providing insights/Feedbacks when necessary.</p><ul><li>Non textbook way of approaching projects.</li><li>solving Majority is not to be used as judgement to make a solution/decisions because it is a qualitative study.</li><li>how to make sense of interview notes</li><li>how one person’s problem is not absolute problems to solve</li><li>how to handle and channelize interviews You not user Perfectionist mentality Learn by mistakes How to reason and win the title by healthy reasoning</li></ul><p>👉 <strong><em>Personal learnings</em></strong></p><ul><li>how to overcome mind block</li><li>Articulating design decisions</li><li>student for life</li><li>how to motivate yourself</li><li>how to eradicate biased and first ideas using crazy 8 techniques</li><li>opening the third eye — looking at things in different perspectives</li></ul><h3>UnLearnings</h3><ul><li>Personal Bias is not good, keep it aside.</li><li>Mistakes are not bad but they are the way you learn.</li><li>Results are not the only aim, but showing the process is too.</li><li>Perfectionism is not the goal at the start of anything.</li></ul><h3>Conclusion</h3><p>Design thinking gave me an opportunity to take a look at problems from a completely different perspective. I have realized how much my perspective about solving problems have changed!</p><p>Design thinking today is a powerful framework for innovation, collaboration, and product/process improvement, whichever industry I am in. I will apply this process and prove to others and yourselves, how I <strong><em>can actually take a next step</em></strong> from my ideas, and not be stuck at ideas dying as ideas! 🤘</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pe-I78G8pPu90Ra8eT9VlQ.jpeg" /></figure><p>And I will never forget to be a, #<strong><em>StudentForLife</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=731caf64dff3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>