<?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[Vyomesh Iyengar - Medium]]></title>
        <description><![CDATA[Writing some thoughts &amp; sharing some work - Medium]]></description>
        <link>https://medium.com/vyomesh-iyengar?source=rss----4711c77d4950---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Vyomesh Iyengar - Medium</title>
            <link>https://medium.com/vyomesh-iyengar?source=rss----4711c77d4950---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:37:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/vyomesh-iyengar" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Home]]></title>
            <link>https://medium.com/vyomesh-iyengar/home-51c932204d1c?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/51c932204d1c</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 00:31:19 GMT</pubDate>
            <atom:updated>2022-02-15T03:27:30.296Z</atom:updated>
            <content:encoded><![CDATA[<p>I bought a shirt from H&amp;M the other day and I was shocked at how it smelt like my grandma’s laundry detergent. It smelt like home.</p><p>It brought me back to standing in my grandparents living room back in India with the laundry machine rumbling beside the kitchen sink, blocking off the hallway to the bedroom, the intermingling sounds of motorcycles and tweeting birds floating in through the open windows. Leaning over their terrace, sweating buckets as the sun would hit my face as I watched the crows eating yesterdays rice, and the beautiful orange flowers sprouting. It made me think of home.</p><p>Home is so many places, feelings, and people. Home is eating <em>puliyotharai </em>and<em> urulaikizhangu </em>at a random rest area in America while driving 14 hours to Pittsburgh and blasting the OK Kanmani soundtrack. Home is being wrapped in a blanket beside my roommates, while eating hot queso and watching Community. Home is the memory of sitting in the English hall with my friends talking about absolutely nothing.</p><p>But I wonder if home ever changes. I wonder how it would feel going back to our apartment across Bramalea City Center. Would that be home? Would I remember the place where my little sister first came home, where I cried after I scraped my knees running down Queen Street, where my grandpa would comfort me as I refused to go to school because “no, math is too hard”.</p><p>More than the moment, event, or the place itself, I think home is just a specific feeling of comfort, joy, and happiness.</p><p>Maybe that’s why seeing the places I associate with home don’t have the same effect as smelling a familiar scent or hearing a song from a distant memory. Maybe it has something to do with how smells and sound stays constant in our head whereas our external environments are always changing. Or maybe it’s related to our ways of learning.</p><p>In any case, this piece is a reminisce of the homes I have had, the people that have made it, and the future that is ahead.</p><p>But anyways, thank you H&amp;M for reminding me of home and shoutout to my sister for not thinking I was crazy when I ran up to her yelling to smell my shirt. On an unrelated note, I now have four Mickey Mouse themed shirts, how many till I can call it a collection instead of just adult who wears too many graphic tees?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51c932204d1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/home-51c932204d1c">Home</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Click click]]></title>
            <link>https://medium.com/vyomesh-iyengar/click-click-a3228d808cce?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/a3228d808cce</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Thu, 03 Feb 2022 03:22:36 GMT</pubDate>
            <atom:updated>2022-02-03T03:24:48.540Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been obsessed with pictures for as long as I can remember. I love looking at a specific image and being brought back to the moment and emotions associated with whatever was happening. Pictures can tell a story which doesn’t really need telling, and that’s the magic of it.</p><p>But I do think pictures have its own drawbacks, sometimes it stores moments you’d rather forget. It cements the feelings you’d rather not have etched into permanency, or the memories you’re trying to pretend never happened. But as with anything that stores the reality of a moment be it writing, video, or photo- it captures the good and the bad.</p><p>It brings me a different type of joy to be able to look up at my wall and see so many times of joy on my wall. I think that’s the reason I walk around with a photographic device like its another part of my arm. Making sure that I remember the little moments, the moments which I may have otherwise forgotten, the moments of chaos. One day I want to have an album, which is just filled with all the people and all the memories of my life. From starting off in Sunnyvale, to the middle school days, all the way to wherever I am at the time- a constantly updating collection of photos.</p><p>Well now that I have another device to capture good quality photos don’t expect me to stop anytime soon (shoutout to my family and friends who enable my love for taking photos everywhere). Just stand and pose while I take a picture of the sky instead of you. Click click catch ya on the flip.</p><p>Anyways side note, it’s been a while since I’ve been to Panera Bread I could go for some good soup.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3228d808cce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/click-click-a3228d808cce">Click click</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s the thesis?]]></title>
            <link>https://medium.com/vyomesh-iyengar/whats-the-thesis-ef4ad2425175?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/ef4ad2425175</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 05:35:12 GMT</pubDate>
            <atom:updated>2022-01-27T05:35:12.834Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, good morning, good afternoon, good evening, welcome to whatever this space evolves into.</p><p>I’ve come to realize that while words in itself have power, its impact comes in the context and surroundings. Having solely written for professional or educational purposes, I analyze the words I use and the reasons I use them beyond a point of reason to ensure that I find the right way to convey meaning.</p><p>So this time, we’re switching it up.</p><p>Unlike with almost everything I’ve done in the past, I’m just going to use this space to write whenever I want to write. Call it a product of being raised in the generation of technology, or just being surrounded by tech kids, but I think there is a sort of power or intrigue to just putting thoughts out in the world and seeing what becomes of it. I also think there is some accountability in having thoughts in a “public” (public because 3 people follow this) lens, and piecing together how the world works all at the same time.</p><p>Now I have no idea what this space will become, maybe I’ll write about work, my musings about the world, or about my love for raisin bread, but the definition of this page is: Vyomesh thinks. Thanks Ms. Hanemann for the hours of teaching me how to write a perfect introductory paragraph, but I’m sticking with Vyomesh thinks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef4ad2425175" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/whats-the-thesis-ef4ad2425175">What’s the thesis?</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[leafup.]]></title>
            <link>https://medium.com/vyomesh-iyengar/leafup-b4653891495f?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/b4653891495f</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Mon, 31 May 2021 22:21:32 GMT</pubDate>
            <atom:updated>2021-05-31T22:20:14.618Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This project was created for the </em><a href="https://www.hackworks.com/en/design-for-change"><em>2021 Design for Change</em></a><em> challenge, based on the following challenge statement: </em><strong><em>How might we create social transformation that shifts users towards greener behaviour and sustainable practices?</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s7ySHKEc2eEi7o3nkqk_Lg.png" /></figure><h3>Case Summary</h3><h4>Problem</h4><p>People often throw out items that are unused or do not serve its initial purpose anymore. This causes a huge problem for the environment, as the items build up in landfills and increase the amount of waste generated. When looking for new products, individuals simply purchase new items from stores, and continue this cycle of purchasing, and throwing out.</p><h4>Solution</h4><p>Creating a platform where users can find inspiration for what they can do with their disposable items, and provide incentives for users to create sustainable alternatives for store purchased goods.</p><h4>My Role + My Team</h4><p>During the project, I focused on<strong> user experience</strong> <strong>research </strong>to understand the users and also worked with the users when conducting <strong>usability testing </strong>to develop our iterations. I also worked on <strong>wireframing</strong> and initial <strong>ideation</strong> of the concept into the high fidelity prototype.</p><p>I worked in a team of three people, with the talented Yi Nan Zhang and Janice Chen</p><h4>Timeline</h4><p>This project was done across four weeks, in March 2021. We spent a week each on the User Research, Ideation + Prototyping, Testing, and Presentation parts of the project.</p><p><a href="#5462"><strong>Click here to skip to the final product.</strong></a></p><h3>Ideation and Research</h3><h4>Determining the Problem Space</h4><p>When it coming to tackling such a huge problem space such as “social transformation towards greener behaviour and sustainable social practices” there are a world of accompanying problems and potential solutions to go along with it. In order to determine the particular space we wanted to solve, we chose to look at problems that were within our understanding which we experienced as students.</p><p>We narrowed it down to one of the following topics:</p><ol><li>Reducing food waste by creating an application to manage what can be made with the food in the user’s fridge</li><li>Reducing heavy meat production by showcasing vegan alternatives</li><li>Promoting ideas for repurposing unused items to reduce waste and landfill use.</li></ol><p>We found that while the first two solutions required a lot of initial setup on the part of the user and could result in a lack of adoption, the third solution was both useful and easy to take integrate into the users daily lives.</p><h4>Understanding Our Issue</h4><p>The concept we chose to explore was upcycling. Upcycling is the process of transforming unwanted and unused materials into new products of greater quality. We chose to take tackle this problem because it is applicable to a wide audience and can easily help alter social behaviours without additional resources.</p><p>Upcycling is something that is commonly practiced in many households already by simply repurposing an old jar as a pencil holder or a using old clothes as cleaning rags. However, we wanted to focus on expanding this by making upcycling a common practice that people actively chose to engage in instead of constantly purchasing and throwing out store-bought items.</p><p>An important aspect of having a large population adopt a specific trend is implementing some way to measure that the individual is doing well compared to others, and also having methods of continuous improvement that can be tangibly seen.</p><h4>Secondary Research</h4><p>In order to understand if this was a problem space that actually needed to be addressed, and to understand how best to approach it, we conducted secondary research on how often upcycling is currently done, as well as examples of large companies and individuals that currently upcycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mtYqs0aYgUxy_cZ5I2gdiQ.png" /></figure><p>Based on our research, we found that while a significant amount of adults, and large companies are accustomed to upcycling and implement this in their daily practices, there are still a large group of people who do not. Our goal was to target the demographic of individuals who did not know much about upcycling, or even how easy it is to implement it in their lives with minimal changes to their current practices.</p><h4>User Surveys</h4><p>In order to get an understanding of the general public’s knowledge of upcycling and gauge their enthusiasm to start learning, we created and distributed a survey which collected basic demographic information, current familiarity, and willingness to start upcycling if they learnt more about the process. Collecting demographic information allowed us to understand what parts of the population we were getting input from, and who was being excluded so that we could make more informed decisions for future iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rd39pt7ZBOuMjkYyB3CClQ.png" /></figure><p>Based on our user survey, we found that a little over half of the respondents currently do not upcycle, but almost all would be willing to start given that they had more information. This data informed us that we would have to include an educational component during both the onboarding and throughout the application experience as well in order to continuously provide new knowledge on upcycling habits. Since majority of our respondents were in the age group of 18–24, we decided to gear our design and user interface to be more modern, and using topical design methods.</p><h4>User Interviews</h4><p>To get a deeper understanding of peoples main motivations and frustrations in the current upcycling process, we conducted user interviews with 7 individuals, who fell under three main categories: undergraduate student, teenager, and adult. Through this process we aimed to pinpoint exactly what could be improved on, and find methods we could tackle it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9i3chyUs_FtTVuD6G_Vqpg.png" /></figure><p>Based on the interviews, we came to the following conclusions:</p><p><em>Biggest obstacles:</em></p><ol><li>Access to information: there is a lack of information regarding how upcycling works and what/how people can do, which causes hesitancy to start due to unfamiliarity.</li><li>Inconvenience: users don’t know what items they have to use or how much time it will take to create new items.</li><li>Lack of ideas: it is difficult to come up with ideas for creations based on the items that people have at home, especially when just starting up.</li></ol><p><em>Biggest motivators:</em></p><ol><li>Competition: people are motivated by competing against their friends, and getting ideas based on what others have done.</li><li>Impact visualization: showing their actual impact will motivate them to do more and give back.</li><li>Saving money: people tend to keep used packaging materials and reuse it for other purposes as this retains quality.</li></ol><p>Based on these obstacles and motivators, we came up with our list of system requirements for the MVP of the product.</p><h4>User Persona</h4><p>In order to summarize all the data we found from our user interviews and surveys, we created a user persona which describes the main user base we were targeting the application to be for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdvgTH7IO2xarSMsJd_Y6Q.jpeg" /></figure><p>Based on the user persona we decided to implement the following features:</p><ul><li><em>Inspiration page </em>for users to view others creations, as well as find instructions to create similar products</li><li><em>Create function </em>for users to post their own creations, difficulty level and required materials</li><li><em>Points system and leaderboard</em> to encourage friendly competition and create a gamified aspect to creating more sustainable solutions</li><li><em>Visualized impact</em> in the profile page for individuals to get a quantitative understanding of the impact they have made: we chose to do this in amount of CO2 saved, and number of trees planted (where 100 points equaled to 1 tree)</li></ul><h4>Journey Mapping</h4><p>To ensure that the features we ideated and journey we created actually made a noticeably positive impact on the users’ journeys, we mapped out a user journey of purchasing a new item to its end of usability, and compared the process with and without the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGir4kUCJrJsiq5U2EASsw.png" /></figure><p>We found that while there was still a dip in user emotion when the usability of a product ended, instead of continuing that dip downwards, the new application allowed for the feeling to be reversed. Since the user now had a new challenge to tackle, and was able to both be educated and take part in friendly competition, they felt better about their impact on the world compared to if they had simply thrown out their product.</p><h3>Wireframing and Initial Designs</h3><h4>Wireframes</h4><p>Based on our user research, we created wireframes for each of the main features we planned on including. After deciding the finer points of what each of the features consisted of, we drew out multiple layout options for each of them in order to visualize how a user would navigate through it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gp4kiSS_EeOv0xcSl5GEjw.png" /></figure><p>Doing this helped us get an idea of which features provided the most benefits to the user and contributed to the user journey. By exploring various layout options in each of the sections, we found common UX principles which could be applied to make the features as easy to access as possible.</p><h4>Mid-Fi Prototypes</h4><p>Based on our initial wireframes, we created mid-fi prototypes on Figma. Throughout this process, we focused on the most important features we wanted to test, so that we could then get feedback on what to improve for future iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JhoPQuhGWqAEr4gDuc8QQ.png" /></figure><p>Instead of implementing a comprehensive design system, we chose to use a style guide which consisted of our branding colours, typography choices, and select components to use. We also decided to call the product ‘leafup.’, which was a play on leveling up while helping the environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1sh4tPBZIVx2YAH966WO4Q.png" /></figure><h4>Understanding Accessibility</h4><p>Since this product was targeted at an extremely large audience, it was important to have an inclusive and accessible design. This was done by ensuring that our colour use met the WCAG standards, and that all the icons we used had some form of text accompanying it so as to avoid assumptions for a diverse audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*euoSOxgxlXTSEAPNXM9BGw.png" /><figcaption>Image showing the colour combinations we used and the WCAG rating for each of them</figcaption></figure><h4>User Testing</h4><p>Reason for user testing</p><p>In order to get an unbiased response to the application, we used non-leading questions such as the following:</p><ol><li>What is the first task you would do?</li><li>How do you find the information on the page?</li><li>What is your thought process when seeing this screen?</li><li>What do you expect to happen based on your actions?</li><li>What do you like/dislike the most?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVhHnDcJkhnA05X98uGWhw.png" /></figure><p>Based on our user testing, we made the following changes:</p><ul><li>Revamped the impact section to include more tangible numbers which helps quantify the users impact in more common terms</li><li>Added more labels, titles and descriptions to explain the more niche aspects of the application</li><li>Implemented an onboarding process to explain the leaf points system</li><li>Refined the leaderboard to be more indicative of where the user fell in the group, as well as how they could reach the next level</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6fxP0cZYa-lrXv8huDsziQ.png" /></figure><h3>Final Prototype</h3><h4>Onboarding</h4><p>Through a comprehensive onboarding, users are both able to understand the product and also set up their personal preferences to allow for customized recommendations to populate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b2DA-1FM-NHZxX-u8PL6kA.gif" /></figure><h4>Home Screen</h4><p>Users can read the fact of the day for informative environmental news, and view their current standing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0QtB5mh26F2ADOqRznFgbw.gif" /></figure><h4>Uploading</h4><p>One of the main features of the application is to easily allow users to upload their upcycled creation as a post for the global community to see. This allows them to get inspired by millions of people and their creations from across the world!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hWMQTrzrDgCP91ayFaEhsQ.gif" /></figure><h4>Inspiration</h4><p>Users can follow quick blogs or videos for an easy tutorial on hundreds of creations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cjafjMS_bSu7Zd5E12yC-A.gif" /></figure><h4>Leaderboard</h4><p>They can also collect leaf points to compete with their friends, and check their standings on the leaderboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GimyaQvKWSelDdiQq4_SRg.gif" /></figure><h4>Profile</h4><p>Users can admire their previous creations and collections, as well as view, share, and save their impact on the environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bx2zjyi3xdAfoW5Gb1FFOQ.gif" /></figure><h3>Learning and Future Changes</h3><p>Throughout this project, I learnt the importance of having a standardized design system and building with a consistent set of design principles, not only to present a cohesive feel to the application but also to make sure the original goal of the application is fulfilled.</p><p>In the future, there are both more features and more learnings which can be implemented.</p><p>Firstly, implementing a ‘work together’ feature would be extremely useful for users who want to work together to create a product, which would really foster a community environment. In addition, growing the amount of inspiration we had by sourcing from other upcycling websites and working in a partnership would improve the content the users would have, and keep drawing them back in.</p><p>In future iterations, it is extremely important for us to conduct more user research and iteratively conduct usability testing on the product. Since our timeline only allowed for one week of research, validating our findings will allow us to develop more fleshed out features. However in our research, we must also seek out groups that we originally did not hear from in an effort to be more accessible and inclusive in the content that we develop. Since certain demographics were not heard from in the original findings, specifically reaching out to them will ensure that all voices are heard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4653891495f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/leafup-b4653891495f">leafup.</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HOWL]]></title>
            <link>https://medium.com/vyomesh-iyengar/howl-acaff6e4d4fd?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/acaff6e4d4fd</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Sat, 09 Jan 2021 08:31:30 GMT</pubDate>
            <atom:updated>2021-01-16T02:59:54.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elNhBujuauUgcWoYVcTfwQ.png" /></figure><figure><a href="https://www.figma.com/proto/HvTaKQ4asdqjNVy4zD15Ex/Howl?node-id=56%3A1591&amp;viewport=-180%2C183%2C0.10800599306821823&amp;scaling=scale-down"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QxQ57AOT4ySR_9uZgC5ZZw.png" /></a><figcaption>Select image above to view high-fidelity prototype of HOWL!</figcaption></figure><h3>Case Summary</h3><h4>Problem</h4><p>How can we improve the efficiency of work, and collaboration between members of a team to ensure optimal output of tasks and the completion of the team’s purpose while maintaining team relations?</p><h4>Solution</h4><p>By gathering information regarding each member to assign them to tasks which play to their strengths/interests, and providing the team with a methodology to follow which removes a strict order of project phases, but instead focuses on constantly evolving processes through rapid iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zrm_KdEIq2AntOQQzsiDLw.png" /></figure><p>Working through a semester of online school, like many others I found efficiency in teams to be difficult to arrange, especially working in different time zones on multiple parts of a project. It becomes difficult to get to know those you are working with, and successfully be able to understand each member’s strengths and weaknesses. When working on my <a href="https://medium.com/vyomesh-iyengar/vba-team-decision-making-tool-7fd4b656aea6">VBA Team Project</a>, I found that creating a task-assigning platform would be a great feature to have, however I wanted to build more on this. Looking to address the various problems which come with planning and individual member growth, I came up with the idea for HOWL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*igBT1DPFuQvU8zZ5uH0qng.png" /></figure><h3>Research</h3><p>Before closing in on one idea or feature, I sought out to think of any and all problems which could possibly be addressed during the process. In order to do this, I created a <strong><em>How Might We Board</em></strong><em> </em>where I listed every single possible feature or impact that this tool could have. The main theme I was brainstorming under was team management. During this process I brainstormed all the ideas I could think of, instead of focusing on the feasibility, or work required- I simply looked at “what are some problems”, and phrased them as a question which could be solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EOyUoBwRu9Iw-vXdh6zjqg.jpeg" /><figcaption>How Might We Board</figcaption></figure><p>The <em>How Might We Board</em> is a very divergent process where no ideas are eliminated but instead considered to come up with deeper and more in depth solutions. In the end, the result is to narrow down to the top areas of opportunity and digging down to the root of the problem. Some of the <strong>questions </strong>I considered when coming up with the <em>How Might We </em>were:</p><blockquote>What could go wrong?</blockquote><blockquote>What am I overlooking, simple processes such as closing/going back are often glossed over.</blockquote><blockquote>Who is this helping?</blockquote><blockquote>What emotions am I helping to avoid/bring out?</blockquote><blockquote>What are the problems each user ‘type’ is facing?</blockquote><blockquote>When considering an end-to-end process, what are the steps that a user would have to take?</blockquote><blockquote>Where is the destination to the experience?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NxqrWMBo_iDr4RZEgws7EQ.jpeg" /><figcaption>How Might We Board — Grouped</figcaption></figure><p>After having a jumble of ideas all together, I put them in different groups. This allowed me to remove any <strong>redundancies </strong>and determine which concepts came up multiple times, as well as the depth of each group. By doing this I was planning out clear <strong>classes of concepts </strong>I wanted to address in the objective of the application. In doing so I noticed a couple overarching <strong>themes </strong>which were present across all the groups. I combined these smaller groups into supergroups which I displayed in an<strong> <em>Affinity Map</em></strong>.</p><p>In the <em>Affinity Map</em>, I listed out the supergroups that were derived from the <em>How Might We</em> grouping, in order to find an <strong>overarching theme </strong>to address. Conducting thematic analysis allows me to come up with the following objective:</p><blockquote>How can we improve the efficiency of work, and collaboration between members of a team to ensure optimal output of tasks and the completion of the team’s purpose while maintaining team relations?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9UdBHYF74BrbmrOOWcnx2A.jpeg" /><figcaption>Affinity Map</figcaption></figure><h3>Background Information</h3><p>After determining one half of my main objective to be tacking efficiency of work and collaboration between team members, I looked into the progression of member relationships within a team. I explored <strong><em>Tuckman’s Stages of Development</em></strong> which illustrated a relationship between the efficiency in the project and the time that had passed, as a result of establishing team roles and personal development.</p><p>At the beginning of any team project comes <strong>Forming</strong>, where team members do not know what to do, how to do it, or why they are doing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*Pgfbq6JlI7ZxCWyAjq3Dcw.jpeg" /><figcaption>Tuckman’s Stages of Development</figcaption></figure><p>Next comes <strong>Storming</strong>, a clearer understanding of the purpose is developed and a hierarchy is developed. However team members are reluctant to lean on each other, and collaborate. This results in a lack of coherence between team members, as individuals do not see their personal benefits.</p><p>The third stage is <strong>Norming</strong>, where members understand each other’s importance and the commonalities they share as a team. Members are willing to listen to each other and receive feedback. They are more willing to participate in team activities as they see the benefits it brings to them, and will contribute to the team.</p><p>After this is <strong>Performing; </strong>the teams performance is at its peak, there is an understood flow of decisions, and roles are interchangeable as required. The system is much more independent and requires little oversight.</p><p>The last stage is <strong>Adjourning</strong>, which occurs at the end of the project and simply provides a chance for members to reflect on the team’s progress, as well as their individual development.</p><blockquote>Looking at the shape of the Tuckman Curve, it is similar to an<strong> empathy map </strong>where the user faces some sort of difficulty causing a drop in their emotions.</blockquote><p>When searching for the root of the problem, eliminating this ‘drop’ is an important part of the objective. Since the user experience is the present consideration, it is important to ensure that all stages of the process are well-done, not simply the start and the finish, but the entire journey.</p><p>In order to minimize the impact of the storming stage on productivity and instead move onto norming and performing, it is important to have established information provided to the members right at the forming stage. This eliminates uncertainty, confusion, and overall disarray.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*mv89DePYvjcQ6uJ4oqsqYA.jpeg" /></figure><p>To gain an in-depth understanding of each team member, it is important to understand how they work, their strengths, and their weaknesses. Doing the Myers–Briggs Type Indicator Test will allow individuals to see their personal areas for improvement, and also allow other team members to ask for advice in areas they may be lacking in. Coupled with a list of goals, interests, and skills each member has, knowing each others MBTI type will allow for increased collaboration.</p><p>Addressing the second part of the objective, project preparedness through coherent planning, I decided to apply Agile concepts and frameworks within the project to allow for the use of sprints and iterative project changes being made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*jQZn-9vObhgnX1moKiJRQA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*nRuI3z1srC6Y5ZgDmbfoww.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*cdfPEVQGtdRm_pKdUXxFfg.jpeg" /></figure><p>Using the <strong>Agile </strong>framework of <strong>scrum </strong>I implemented product/sprint backlogs to keep track of work that still had to be completed as well as a sprint burndown for work that had already been completed. During each sprint the team would also have short meetings for updates at a set occurrence (daily, every other day, etc.) to keep everyone updated on the status of tasks. This ensures that changes do not come as a surprise and can be made quickly with little problems.</p><p>Using sprints is extremely beneficial as the entire project is planned at the start and allows for the production of deliverables throughout the process, instead of focusing simply on the end result.</p><p>The use of <strong>Kanban Boards and Gantt Charts</strong> are excellent visual aids in keeping up with how much work is left in the project, what has been completed, and any dependencies on project tasks. This is useful for both project leads and team members as they are both aware of the project’s current health.</p><p>After completing relevant research, I had an understanding of concepts I wanted to apply within the system needed to go back to the initial objective of the system and ensure that each part of the objective met with the needs of each potential user of the project.</p><p>To consider this, I created five different <strong>roles</strong>, for whom this project was directed at. These five roles have different responsibilities in any team, and will be completing different actions at each part of the project cycle. The project manager is in charge of the overall project, the sprint manager takes care of their respective sprint, team members work on all the sprints, the talent manager allocates members to teams based on their skills, and the resource manager adds and removes team members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V5ksnjHkbyGqh4msLrEtpg.jpeg" /></figure><p>However since not every project would be able to allocate different individuals to each role, I ensured scalability of the tool by creating two <strong>user personas</strong> to use the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*7O7yljSTh5C3WnqspK9OOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*N9pQKQWxXjhrRB6DXQ-Yhw.png" /></figure><p>The first one was a businessperson, who would be managing multiple projects, but would have various other individuals who would be doing the actual work. This individual would also likely have an talent/resource manager on hand, who would be able to work with managing members.</p><p>The second persona created was of a university student who was using the project to collaborate with others across many teams. This was much different than the previous one as the student would often play all the roles in the team, including that of the team members. They would have to ensure that they can both manage multiple teams, and work in them.</p><p>The last part of the research stage is gathering all the information to list out the <strong>system requirements</strong> in the project. Doing this is extremely important as it allows for developers to understand the importance of each function, how it works, and what it does to improve the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJOAWBZUeZnbZoTl4N_0jg.jpeg" /><figcaption>Systems Requirements Mapping</figcaption></figure><p>The features marked as ‘High’ priority are those which directly connect to the objective of the platform. These contribute towards solving the immediate root of the problem, and are essential for success. Those marked as ‘Medium’ and ‘Low’ respectively are add-ons, and can be used as additions if resources are available. While not required for the success of the platform, it adds extra features which could be helpful in avoiding future problems.</p><h3>Ideation</h3><p>After deciding what features are to be included in the platform, I created a <strong>low fidelity wireframe</strong> which illustrated the basics of each major screen that was going to be present. I used colours to highlight the relationships between different screens, and indicated my flow of thought.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d0ZpYDPvig7hBrmGYpd9Ig.png" /><figcaption>Low Fidelity Mockup</figcaption></figure><p>From the low-fidelity model I separated the actions the user could take into three groups, which would be decided at the login button. They could either create a profile, create a team, or sign in. While these screens have the potential of leading to each other, separating them allows for easier grouping of ideas.</p><p>In order to break down the attributes of each group and what commands the system would have to provide to the user for ease of use, I created a <strong>sitemap </strong>with an overview of all pages (blue), actions required (red), and system commands (green). Doing this allows for a clear outline of every page in the application and how it causes further actions down the line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7msBoJ6Orl0HHxXznIM3cw.jpeg" /><figcaption>Sitemap</figcaption></figure><p>While through the sitemap, I laid out the flow of the pages, in the <strong>medium fidelity mockup</strong> I specified what components would be in which page, the input fields required, and the overall action items which would be present on each screen. This laid a basis for the prototype as it provides a basic understanding of the resources which need to be allocated towards each section, as well as advises the flow of the entire system. It is important to ensure intuitiveness for the user, and the mockup presents a check for this. While there are not any images or colour present, the overall ideas remain the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*dOhfDYW56Z2THnfN2gfmgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rte85lA-5DxgGP5R2Uuy5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrYClYL2JwM0xrN7ucOrig.png" /><figcaption>Medium Fidelity Mockup</figcaption></figure><p>Prior to prototyping, the last aspect which needed to be considered was the <strong>typography</strong>, and fonts for the application itself. Since the focus group was for any type of team, the colour scheme would have to remain traditionally professional, leaning towards darker colours. However, since the theme was surrounding wolves and packs, I focused on purples and dark blues with light pink used for accentuating important information. The fonts used were Open Sans, Montserrat, PT Sans and Source Sans Pro in various sizes and highlights. The <strong>Serif</strong> fonts lent themselves to the professional theme throughout, and the use of Montserrat as a geometric sans typeface was used for titles and headings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*yNeXRBLbLFRnCPR5uF8g9A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HVA85BqF0UMbVBJGPaRgNg.jpeg" /></figure><h3>Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0craZtsu2wbTq1DbBvZniw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSiZJ9SvJEu8EXxxKvZCJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QDpffiaTrVdYJUX2LIyqHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BF6OLO-dGcEAAObL5E5PUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kv_vu4zX6GIfKQbVGDSorQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bma-8okLFImVmaZzPLBjgw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c5fx8PweuzYPAgEBsgOCqw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7eP25ZFkGsnhePSRJ6YYZg.png" /></figure><h4>Feel free to click through the high-fidelity prototype of HOWL!</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FHvTaKQ4asdqjNVy4zD15Ex%2FHowl%3Fnode-id%3D56%253A1591%26viewport%3D341%252C-70%252C0.30028897523880005%26scaling%3Dscale-down&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FHvTaKQ4asdqjNVy4zD15Ex%2FHowl%3Fnode-id%3D56%253A1591%26viewport%3D341%252C-70%252C0.30028897523880005%26scaling%3Dscale-down&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F7197df7c-42cb-4b45-b5bd-f8e577aae2dc%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/d79da5438c7923d0378e1d14230d0d02/href">https://medium.com/media/d79da5438c7923d0378e1d14230d0d02/href</a></iframe><h3>Evaluation</h3><p>During this process, I expanded my knowledge on user research methods through exploring user personas for various roles and understood how to scale an application. I developed an understanding of web app prototyping and the differences that come from mobile development.</p><p>In a future iteration of the project, I would include more features such as presenting a Kanban Board and Gantt Chart for easier visualization, as well as the ability to integrate the system with other pre-existing platforms to be able to view the work completed within HOWL itself. Instead of navigating throughout various platform, doing this would allow for a more efficient user experience.</p><p>With regards to design improvements, I would like to work on a larger project, and implement more user testing to understand how to improve usability, as well as create my own vector art to fit with the overall theme.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acaff6e4d4fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/howl-acaff6e4d4fd">HOWL</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[VBA Personal Planner Project]]></title>
            <link>https://medium.com/vyomesh-iyengar/vba-personal-planner-project-7e36ec5ef58e?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e36ec5ef58e</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Wed, 06 Jan 2021 18:24:04 GMT</pubDate>
            <atom:updated>2021-01-06T18:24:04.726Z</atom:updated>
            <content:encoded><![CDATA[<h3>Summary</h3><h4>Problem</h4><p>With many courses, extracurriculars and other tasks to get done each day, it is extremely important for me to keep track of when I can get everything done, and prerequisites for each tasks. Currently I use a variety of applications to get this done, but I need it to be streamlined for increased efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Su_uqZVJh8_DufNEo8wVTA.jpeg" /><figcaption>Glenn Carstens-Peters on Unsplash</figcaption></figure><p><em>Unlike my other projects, this one was quite different as I was not only the designer and developer, but also the client. Since this was a project as part of my MSCI 100 class, I had to gear the requirements towards what I wanted and understand my own personal requirements for what I wanted in a planner, organizing various parts of my life.</em></p><h3>Case Overview</h3><h4>Scope</h4><p>Throughout this project, the problem I addressed was creating a personal, term management tool to keep track of the various deadlines I have, my schedule, habits, and finances. The goal of the project was to increase the efficiency of the organizational tools in my life. I used a variety of different systems and wanted a way to be able to standardize the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*krljPC854A4O9hBBUswQCA.png" /></figure><h4>Functional Requirements</h4><p>In order to create the product, I set out my functional requirements under the categories of Scheduling, Academics, Finances and Health. Each of these were important parts of my life which would be better managed by having one cohesive system which keeps track of all inputs and outputs. The following outlined my requirements for the minimum viable product:</p><ol><li>The system must have a delete and update information button.</li><li>The system must display a dashboard in calendar format on the dashboard with various views: day view, week view, and month view. The dashboard must also display an overview of my ‘stats’ throughout the week.</li><li>The system must have a dashboard for each individual class, with a breakdown of assignments and tests, as well as what lectures I must watch for the week.</li><li>The system must allow me to input my current grades to find my current mark, as well as forecast what I need to get on subsequent assignments to get a predetermined desired final mark.</li><li>The system must have a space for reflection on each assignment and test.</li><li>The system must have a planner for all for midterms, assignments, quizzes, and lectures. Each of the categories must have the course, due date, how much it is worth, desired mark and time required to complete. All the tasks must also have a reflection area here I must be able to add the amount of time spent, and the reasons behind the discrepancies.</li><li>All tests/quizzes must also have a breakdown of what is covered on it, and how much time should be allocated to each topic.</li><li>All lectures must be spread out throughout the year, with each unit being covered per week.</li><li>The system must also have a way for me to add special events/meetings I must have to attend. These include family events, temple events, professional events, and meetings with my coach.</li><li>The system must also have a general to-do list for administrative work I need to get done, this will be similar to my class schedule where I will separate it by priority, deadline and how long it will take.</li><li>The system must have an input of all my purchases, and my inputs for money coming in. The system must include a budget function with alerts when I have reached 50%, 75% and 90% to the limit.</li><li>The system must create a daily mood-entering system based on numbers from 1–10 ranking how my day went allowing me to write a one line comment (with a character limit).</li><li>The system must also create a sleep tracker documenting how much I have slept each day which will also be on my dashboard.</li></ol><h4>Risk Management Plan</h4><p>In the case that I was not able to follow through with the plan I set out for myself, I decided that I would analyze the trajectory of the project depending on which part I have missed and if it is possible to make up for it. If the part of the project I missed was a part of the critical path, then I eliminated parts of the project, beginning from the least priority. This reduced the workload and allowed me to get back on track faster. If the part missed was not on the critical path, I analyzed how much work I had left in that particular section and either removed objectives or decreased the time required for a future task.</p><p>In an effort to ensure that I am keeping up with my work, I had repeated check-ins with my plan once a week to make sure that I completed everything I had set out for that week. If I had not completed everything I set out to do, then I realigned my goals to work with what I have that week. After each major development part of the process, I assessed if my understanding on the level of difficulty of each process has changed, and if it had then I revaluated the final functional requirements. Since the functional requirements were in the order of most to least important, it was easy to determine which ones were required for the minimum viable product.</p><h4>User Interface Concepts</h4><p>The user interface is the main ‘face’ of the entire system, it deals with all the graphical elements, functionalities and how the system will all flow together to create one comprehensive unit. User interface is concerned with the overall feel of a design and should follow a set of guidelines to adhere to a continuous principle throughout. The guidelines I set out were based on the UI design principles of placing users in control, having maximal comfortability for interactions, reducing cognitive load and keeping the interface consistent. My criteria for success was based on ensuring that the following principles are upheld throughout the project.</p><p><strong>1. Each page should have a major theme (Academics, Health, etc.) to separate the different functions and reduce the information given to the user</strong></p><ul><li>Having one major theme per page makes it easier for the user to navigate the system and understand where to go to get their problem solved. Specifically labelling each page makes it easier for the tools to be separated.</li><li>This ensures maximal comfortability and reduces the cognitive load on the user in trying to figure out how the system actually works.</li></ul><p><strong>2. Use visual cues that are intuitive to the user and should be very simple and efficient to use.</strong></p><ul><li>Using large, intuitive icons (garbage for deletion, pencil for editing, etc.) will make the user feel more comfortable with the system and will provide them with an intuitive understanding of how to use it. Varying the size of the icon based on its relative importance will draw the user to the features which the system was primarily created for.</li><li>In order to reduce frustration for the user, each task should be easily accessible with a maximum of three clicks to accomplish a required task. This will reduce the cognitive load for the users by reducing the number of inputs they have to give to receive their required output.</li></ul><p><strong>3. The interface should have a consistent look and feel (colours, fonts, etc.)</strong></p><ul><li>Having a consistent interface makes it visually appealing for the user to use, and reduces their strain in adjusting to a new layout for each page. For my individual pages, I used a combination of the Bento Box and Alt-Burger layouts for the various pages. I also used consistent typography (fonts, sizing) to provide a unified front of the system.</li></ul><p><strong>4. Separate data and user interface</strong></p><ul><li>When using the system, the user does not need to see all the background work and data being used to complete each required task, they simply want to get an output for the inputs they provide.</li><li>Due to this it is important to separate what the user sees from the background content being used to compute the functions. Doing this will make the user feel more comfortable with using the system as they will not have to see any of the processing going on.</li></ul><p><strong>5. All actions must be reversible</strong></p><ul><li>Due to how quickly life changes on the daily, it is important to be able to reflect that within the system. Having irreversible functions is often not recommended because it puts a strain on the user to evaluate the implications their actions will have on future tasks.</li><li>By placing an undo/edit/delete button for certain tasks, the user will feel more in control with the system and be inclined to use it for general use.</li></ul><p><strong>6. Define user requirements</strong></p><ul><li>When creating any system, it is important to understand the user and what their main requirements are. This allows for tailoring of specific features or even the overall display of the system to the user.</li><li>Since I was the only user for this system, this was not be a problem as I was the one creating, testing, and using the final product and made changes to suit my preferences as I worked.</li></ul><h4>Low Fidelity Wireframe</h4><p>In order to understand how I wanted to split up each of the screens I planned on making, I created a wireframe indicating where each element would be, how the information would be processes and what would change between the screens. The wireframes included more than my final product, as my final product was the minimum viable product created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*lLs8T-YUf-T5y-2hj3WvbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*fVdQ40mI5B2NWw9LtD3vkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*IYbvvAcJFNgWYn7USLSuug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*5sJFjLTQjpjYcmgcJEz4qg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*twhYnnG_wTRr6arZvZyhQg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*7rE_6qvP0Br6LqXh_9ZqTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*4s1XqU-HTle2c2eBSPJWJg.png" /></figure><h4>Final Product</h4><p><strong><em>Dashboard (Workspace 1) </em></strong><em>—</em>This serves as a landing base for the application, and allows for an overview of the work I have for this week/month as well as the individual tasks and event for the day. It also has tracker graphs on the side indicating my health and fitness.</p><ul><li><em>Organize Tasks</em> — Automatically sorts tasks based on date and sets a colour based on the type of task.</li><li><em>Input Data</em> — Allows for user to input data for the sleep, workout, and mood trackers.</li><li><em>Hyperlink to Graphs — </em>Provides easier access to the graphs.</li><li><em>Welcome Alert</em> — Shows the user an affirming message when opening up the sheet.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6DSpemPuzVsAHk719Y3MdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JK5Q7D0e_G5I0PqCxhidNg.png" /></figure><p><strong><em>Finances (Workspace 2) </em></strong><em>— </em>This area acts as a pseudo-bank account tracker where I keep track of the money going in and out of my account. By having an area where I can allocate funds towards purchases I want to make, I will be gradually planning and saving up for major purchases instead of doing so impulsively.</p><ul><li><em>Input Money</em> — Allows user to add money to their ‘account’.</li><li><em>Output Money</em> — Allows user to remove spent money from their ‘account’.</li><li><em>Check Balance</em> — Allows user to check how much is left in their ‘account’.</li><li><em>Check Spendable Balance</em> — Check how much is left for spending in their ‘account’.</li><li><em>Add Item to Purchase List</em> — Add item to list of items looking to purchase.</li><li><em>Reallocate to Items </em>— Move money from spendable balance in ‘account’ to amount being saved up for a future purchase.</li><li><em>Remove Item from Purchase List</em> — Remove purchased item from list of items waiting to purchase.</li><li><em>Goal Reached Alert</em> —Alert when an there is enough saved to purchase an item.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*f2Wx9U_ZYATPz_TTVv3org.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TxPJQBHNIJidfZifbpNdrQ.png" /></figure><p><strong><em>Academics (Workspace 3) </em></strong><em>— </em>This section helps keep track of all the university work I have to get done, what online lectures I need to watch, and a record of what marks I have in the class.</p><ul><li><em>Add Class</em>— Allows user to add a new class, up to a limit of five classes. The user is prompted to add information regarding instructor name, hours and if there are any asynchronous components. This also changes the name of the respective hyperlink found at the top.</li><li><em>Add Assignment</em> — Adds an assignment to an already created class, prompts to add information regarding task name, type, weight, deadline and expected mark.</li><li><em>Add Lecture</em> — Adds a lecture to watch for a preexisting class.</li><li><em>Delete Class</em> — Allows user to get rid of all information pertaining to a class, presents a message confirming the user’s actions before initiating. This also changes the name of the respective hyperlink to ‘Unassigned’.</li><li><em>Hyperlink</em> — Allows user to have faster navigation to a certain class.</li><li><em>Edit Task/Add Reflection</em> — Allows user to change/add information for any assignment in the respective class.</li><li><em>Delete Task</em> — Deletes a task under the class.</li><li><em>Calculate Current Grade</em> — Using the actual grades inputted, the current grade in the class is calculated.</li><li><em>Calculate Required Mark</em> —Calculates the required mark on an assignment based on current grade, assignment weighting and desired final mark.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gAjV1sgegzh07_EgCI3P6Q.png" /></figure><p><strong><em>Scheduling (Workspace 4) </em></strong><em>—</em>This section is an overall planner of non-school related tasks and events I have to attend/complete. There is space to add what task I need to complete after, the task/event name and date, notes and the event type.</p><ul><li><em>Add Event/Task</em> — Add event/task for a certain date, and add possibility for repetition.</li><li><em>Edit Event/Task</em> — Chose an instance of the task/event to edit.</li><li><em>Delete Event/Task</em> — Chose an instance of the task/event to delete.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MRCxI7qEJO921xZRFh9gMg.png" /></figure><h4>Evaluation</h4><p>Throughout the process I learnt a lot about working as a designer and a developer. I learnt how to create mockups which were easy to understand for a developer, and how to work with logic to create algorithms which synthesized mass amounts of information. During the process I also wrote out documentation such as Project Plans, Functional Requirements, Scopes, and Design Specifications. All of these helped me organize my thoughts in determining what to include in the minimum viable product that I created.</p><p>In the future, a change I would make is to add more sections regarding my portfolio plans and a section for my travel plans. Both of these are important aspects of any planning platform I use, and would be great additions to this as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e36ec5ef58e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/vba-personal-planner-project-7e36ec5ef58e">VBA Personal Planner Project</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Industry 4.0 Competition]]></title>
            <link>https://medium.com/vyomesh-iyengar/industry-4-0-competition-c78add0db3d1?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/c78add0db3d1</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Tue, 05 Jan 2021 00:42:44 GMT</pubDate>
            <atom:updated>2021-01-05T00:48:20.235Z</atom:updated>
            <content:encoded><![CDATA[<p>The Industry 4.0 Competition is a fully virtual competition for high school students focused on management engineering concepts such as process and flow analysis, data analysis and how to consider various factors when coming to conclusions with empirical information. The team is focused on data analytics where Industry 4.0 concepts will be prevalent, in situations almost everywhere, ranging from travel to hospitals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cBYET4mKN6266f48.png" /></figure><h3>Marking Team Member, 2020</h3><p>I joined the Industry 4.0 team as a marketing team member, helping to improve relations with between high schools and the Industry 4.0 team. My focus was on schools in the Peel Region (Brampton, Mississauga, Caledon) and I worked with both administration and students to spread the purpose of the competition.</p><h4>2021 Admissions Guide</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VbIrrFB_3-sZW9d1.jpg" /></figure><p>Working with high school students, one of our main purposes is to provide a benefit to those who are coming, not only with regards to Industry 4.0, but also for any other goals they may have with regards to University and their future career paths. Many high school students are interested in what holds once they enter university, and are always eager to learn more.</p><p>In order to facilitate this, members of the team and I wrote a ‘2021 Admissions Guide’ for aspiring Management Engineering students. We found that these type of publications were something high school students sought out, and thought would be beneficial to many of them.</p><p><a href="https://industry4team.medium.com/2021-admissions-guide-for-waterloo-engineering-applicants-ad5baf01892">2021 Admissions Guide for Waterloo Engineering Applicants</a></p><h4>User Research</h4><p>In order to understand why students would want to come to the competition itself, we needed to understand the basis of what motivated the students. After talking to a pool of high school students, I found that many of them wanted the experience of taking part in a competition which had real-world applications. Not only would it bolster their experience, but also their knowledge when applying for universities and jobs. As a team we found that highlighting these benefits to the students would be essential in future marketing campaigns and would allow us to garner more interest.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c78add0db3d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/industry-4-0-competition-c78add0db3d1">Industry 4.0 Competition</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[VBA Team Decision Making Tool]]></title>
            <link>https://medium.com/vyomesh-iyengar/vba-team-decision-making-tool-7fd4b656aea6?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/7fd4b656aea6</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 23:51:05 GMT</pubDate>
            <atom:updated>2021-01-16T18:06:14.936Z</atom:updated>
            <content:encoded><![CDATA[<h3>Summary</h3><blockquote>As part of my 1A Management Sciences class, we were given a term project to work with an alumni student, who would be our client to come up with a decision support tool which they could have used during their final year design project. The project was done using Visual Basic for Applications, and required us to go through an extensive documentation process.</blockquote><h4>Problem Addressed</h4><p>The problem our client wanted us to address was the lack of organization and time management within the team, leading to rushed work, inconsistent meeting times, and inability to keep track of who had to complete what task by which date. She was looking for an automated generator for meeting dates, assigning tasks, and an overview of all deadlines within a certain timeframe.</p><h4>Solution Presented</h4><p>Across the span of four months, my team and I worked to create a fully functional Agile based decision making tool which automatically assigned tasks to each team member based on their weekly workload/skill level, outlined each team member’s individual suggested weekly hours for the project, generated times for team meetings, provided an alert with upcoming tasks, and had an automatically updating Calendar and Gantt Chart. All of the functions were fully created using VBA for Excel, and are fully functional at the time this is written.</p><h4>My Role</h4><p>Since this was a team project, all of us wore many hats throughout the project. During the planning stages of the project I was the <strong>Lead UI/UX Designer.</strong> I conducted user research to determine the importance of each system requirement, and created a low-fidelity wireframe for how we wanted the product to look. In the production stage, I was a part of the development team and wrote code for various functionalities in the project, acting as one of the <strong>Developers</strong>. Throughout the project, I kept track of deliverables, ensured that we were on track, and helped write the various documentation we provided, such as our Functional Requirements, Test Specifications, Design Specifications, User Manual, and Project Plan Updates.</p><h4>Timeline</h4><p>Sept 2020 — Dec 2020</p><h3>Research</h3><h4>Client Meetings</h4><p>Prior to finalizing the scope of the project, we had multiple meetings with our client where we discussed the main problem she was facing, where the root of the problem came from, and any side effects that needed to be mitigated as a result of the problem. We then worked together to hone in on how our solution would solve her problem and created a two-part system where one side handled project management, and the other was an alert system.</p><blockquote>The project management system would ensure that the team members are kept up to date regarding all the tasks that need to be handed in, and schedule meetings.</blockquote><blockquote>The alert system would provide weekly schedules and reminders to each team member to guide them through the week.</blockquote><p>After presenting this idea to the client, we worked to create a plan for the <strong>minimum viable product</strong> we wanted to create, as well as determine which of the features we wanted to present could be add-ons. In the duration of the project we had 4 meetings to conduct preliminary research, and 3 meetings for getting feedback on various product models during different stages of production.</p><h4>User Research</h4><p>Since the primary user was going to be our client, I worked with her to prioritize/map out all the parts of the System Requirements that we set out, and understand how in-depth she wanted each function. Doing this provided the team with a central focal point for the project which we were able to refer back to when creating each function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*jtcQT1sjW5i9rhyXkwB0lQ.png" /></figure><p>As the function of the project was a team management application, we conducted internal testing by having members who were developing one part of the application test out different parts. We also shared our project with another group, and used their feedback to improve user accessibility for certain features.</p><h3>Ideation</h3><h4>Scope</h4><p>The solution was focused on two primary sections, which are explained in the following processes:</p><h4>Project Management</h4><ol><li>Sorting tasks to each team member based on their weekly workload</li><li>A calendar that updates with every input</li><li>A Gantt chart</li><li>Outlining each team member’s individual suggested weekly hours for the team project</li><li>Automatically suggesting times when the team has meetings</li></ol><h4>Alert System</h4><ol><li>Upcoming deadlines displayed on a dashboard for each team member</li><li>Automatic message box that pops up when the tool starts to let the user know about upcoming tasks coming up</li></ol><h4>Sitemap</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*UgeuzzZlrybNEY0MHAazQQ.png" /></figure><p>In order to plan out how we wanted the system to function, and the commands we needed to develop, we created a sitemap of the entire product, going through each of the possible paths a user could take, and how they would go to/from them. Doing this was very beneficial as it allowed us to understand how many moving/static parts we had, and which ones relied on the others.</p><h4>Low Fidelity Wireframing</h4><p>Prior to starting development, we set out the design specifications for the project by creating a data flow diagram and low-fidelity mockups of how the system would look. It has a brief overview of the various functions the system will have and how we want the data to flow between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R7l47xl_sQlUn6k92e0VXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYlgHdOfCdAwaVZSxi8iVw.png" /><figcaption>Dashboard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-yQx96M5-SjEXCfK" /><figcaption>Calendar</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0N-uRfhJEWdtWa7p" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AWbtfAbTWMg8gIAG" /><figcaption>Team Member Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*slOcW08qIQMJEMb4" /><figcaption>Datasheet</figcaption></figure><h4>Deliverable Criteria</h4><p>In order to ensure that the program works as per its functionalities, we set out a test plan identifier to ensure the success of each feature. Throughout the process we focused on unit testing, performance testing, repression testing and usability testing. In order to maintain usability we also tested for consistency, conscience and functionality. The following criteria was set out for individual feature functionality testing:</p><ol><li>For the insert button we will determine if it passes our criteria if it can successfully implement the task/assignment into the correct places such as the individual member sheet and into the dashboard. We will consider it a fail if it either does not ask for the data or if the data is not implemented into the charts.</li><li>The edit button will be considered a pass if it allows us to choose which previously implemented task and go through it to change specifics about that task. We will consider the edit button a fail if it cannot make the changes to the task and implement the changes where necessary.</li><li>The update button needs to sort through the data and include the correct items to pass our testing.</li><li>For the calendar, it needs to extract data correctly for each individual and place it in their respective sheet. Additionally, it needs to take the key dates and information onto the dashboard for all members to view. The testing will be considered a fail if all information is not extracted correctly.</li><li>The Gantt Chart needs to be able to display the entirety of the assignment presented, this means showing the milestones and an overview of when to do each task. We will consider the Gantt Chart a fail if it cannot show an overview of the assignment and/or if the data implemented into it cannot be expressed into other sheets</li><li>All buttons acting as hyperlinks need to lead to the correct function in the program for them to be considered a pass.</li></ol><h3>Final Product</h3><p>The system comprises five main workspaces, with 4 of them being used for the project management/alert system and one being used as a collection of information from where the data is extracted. Workspace I is used for setting up various parts of the project, Workspace II is the main landing page for the users, Workspace III and IV host the calendar and Gantt Chart respectively, and Workspace V has the information for each individual team member and compiles the information from the above sheets.</p><h4>Workspace I — Data Sheet</h4><p>The following are the different <strong>options </strong>which come up when the ‘Insert Task’ button is brought up. Each option provides various constraints and fits the boundaries which have been set out.</p><ol><li>Insert Asynchronous Project</li><li>Insert Synchronous Project</li><li>Insert Asynchronous non-Project</li><li>Insert Synchronous non-Project</li><li>Edit Item</li><li>Delete Task</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/0*ISlV_ZEX35NxP85p" /></figure><h4>Workspace II — Dashboard</h4><ol><li><strong>Insert Task</strong> — This brings you to a user form where you are able to input the type of task (related to project or unrelated), the synchronicity, and the details of the task which then shows up in both the raw data sheet and Dashboard.</li><li><strong>View Upcoming Deadlines for Team </strong>— The tasks that the team has to complete within a given time frame will be shown on the dashboard.</li><li><strong>View Upcoming Deadlines for each Member</strong> — The tasks that each individual group member has to complete within a given time frame will be shown on the dashboard.</li></ol><p><em>Hyperlinks </em>— These are “shortcuts” to every other sheet on the document. By clicking on these it would bring you to another sheet. The following are the hyperlinks available on the first Workspace.</p><ul><li><em>Calendar</em>: This redirects to the overall calendar for the team.</li><li><em>Individual Team Member Sheet</em>: This redirects to the page for each individual team member</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*X9FY2tPOG1wjPbXe" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gKvLbGCWSakBfXOv" /></figure><h4>Workspace III — Calendar</h4><p>Key dates and information are extracted from the data sheet and displayed on a calendar. Users will be able to view deadlines for each month.</p><ol><li><strong>Hyperlinks </strong>— The hyperlinks will bring you to the specific month selected or allow you to sort the dates by colour/date.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*34bGgXgZtQkj9Dkj" /></figure><h4>Workspace IV — Gantt Chart</h4><ol><li><strong>Start Project </strong>— This brings up a UserForm which allows the Project Name, Start Date, and Duration to be inputted. Using this information, there is a timeline automatically brought up starting from the Sunday before the inputted date. This is used to set up the project and will only need to be used once at the beginning of the project.</li><li><strong>Update Tasks</strong> — This brings in the most updated version of all the tasks, their duration, the start date, and end date from the data sheet. This is used to match with the dates in the timeline and block out time slots.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XPGWgtNtmEomMMD-" /></figure><h4>Workspace V — Individual Team Member Sheet</h4><ol><li><strong>Insert Task</strong> — This brings up the aforementioned form which allows for individual members’ tasks to be added.</li><li><strong>Edit Task</strong> — Allows the user to edit the information regarding the member tasks.</li><li><strong>Hyperlinks </strong>— The hyperlinks in this sheet will help you move to specific months on the calendar. Each member will be able to view which tasks are coming up for them individually, either their daily schedule, upcoming deadlines, or weekly schedule.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qktXfwOD1sFAR9aj" /></figure><h3>Evaluation</h3><p>Although the project tackled all of the intended issues and requirements, there are several improvements that we could make to increase user-friendliness and efficiency.</p><ol><li>It would be beneficial if the textboxes in user forms were highlighted in a specific colour if they still had to be filled out, so the user would not have to wait for an error message to pop up on the document.</li><li>Another potential development is combining various aspects of the project into fewer sheets to minimize the amount of time the user spends navigating.</li><li>Having a more coherent view of the entire project as a whole to view the current health of the project as well as the status of each milestone in progress.</li></ol><p>Since the product we created was the minimal viable product, we felt that the features we included satisfied the basic requirements of the client, however a after conducting further user testing there are improvements which we can make.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fd4b656aea6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/vba-team-decision-making-tool-7fd4b656aea6">VBA Team Decision Making Tool</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brampton Civic Hospital]]></title>
            <link>https://medium.com/vyomesh-iyengar/brampton-civic-hospital-83bda9a9f6f0?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/83bda9a9f6f0</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Sat, 02 Jan 2021 20:41:20 GMT</pubDate>
            <atom:updated>2021-01-17T22:26:14.854Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*EJ-BmQhHASQhX2Om5bKYNw.jpeg" /></figure><p>Brampton Civic Hospital is one of three hospitals under the William Osler Health System acute care community hospital group, working with hundreds of volunteers at each site. I began as a volunteer at the hospital in June 2017, and continued until September 2020.</p><p>During my time as a Student Team Lead one of the main tasks I undertook was creating a mini-map system for visitors to use. I found that due to the number of elderly people visiting the very large hospital, it was often difficult to remember navigational directions. In an effort to curb this problem, I worked with other volunteers to conduct research and create solutions using an iterative design process, where we gathered feedback and implemented it to meet the visitor needs.</p><h3>Pandemic Volunteer, 2020</h3><p>In the middle of the COVID-19 pandemic, the hospital invited volunteers to return as part of the Pandemic Response Team. During this time, we were expected to put on multiple hats and take on the role of any volunteer in any department that needed help.</p><h4>New Situations</h4><p>Given the nature of the situation regarding COVID-19, we were presented with new guidelines regarding patient-visitor-volunteer interactions almost every third day. It was imperative that we learnt the new guidelines as we received them in order to ensure that all members of the community were kept safe. There were often situations which were not prescribed, and being one of the more senior volunteers on the team, I dealt with how to handle these unfamiliar circumstances. Doing this resulted in toeing the line between taking the visitor’s wishes into consideration, and hospital policies, but ultimately taking action which was for the safety of all involved.</p><h4>Delivery (of patients and packages!)</h4><p>Due to new restrictions on who/what was allowed into the hospital after screening, the volunteers handled both delivering packages to patients, and helping patients get to their appointments. When delivering packages the sender often did not have all the information regarding where the patient was, and so I often had to research either through hospital records or by talking to the nurses in various departments. Most of the patients who needed help getting to their appointment were most often either elderly, pregnant, or did not speak English. Each of these situations came with their own obstacles, which we as volunteers overcame to make sure that all visitors to the hospital had a pleasant experience. We acted as the line of communication between hospital staff and the patient’s families to ensure that the best care was given to those who came.</p><h3>Student Team Lead, 2019–2020</h3><p>As the Student Team Lead, I led a team of over 20 volunteers across various departments (Pediatrics, Diagnostic Imaging, Neurology, Dialysis, etc.) and acted as a point of contact to the Volunteer Department. I was tasked with helping out volunteers whenever they required additional resources, as well as onboarding new volunteers to orient them with the hospital.</p><h4>Training Volunteers</h4><p>A large part of my role was welcoming new volunteers to the hospital, showing them around each department in the hospital, introducing them to their role in the specific department, and how they work with the rest of the hospital operations. In order to successfully do this, I had to understand the basics of each role any volunteer in the hospital could possibly do, as well as be able to confidently run through how a typical day in their department would be like. Giving new volunteers tours of the hospitals also entailed a significant amount of knowledge regarding hospital operations, and the locations of each department.</p><h4>Overseeing Departments</h4><p>Supervising volunteers in over 20 departments per shift meant that I had to be extremely organized in scheduling, knowing when they would be absent, and handling any concerns they had regarding their volunteer experience. I found that the best way of doing this was to connect with each of them personally. Doing this ensured that they were comfortable enough to talk to me if they had any problems. I also worked with current volunteers at their department to setup shadowing if they found that they wanted some practice before they started, which was often very helpful in learning some of the more finer tips of each department.</p><h4>Streamlining Technologies</h4><p>In late 2019, the hospital introduced a new system of signing in for Dialysis patients and I took charge in working with the patients on the frontlines to handle any problems they faced, and gauge a general understanding of how both patients and staff felt about the new addition. I worked with the Volunteer Community Resources Department to come up with improvements to the system based on feedback we received to make it more useable for patients.</p><h3>Lobby and Emergency Volunteer, 2017–2019</h3><p>In the beginning of my journey as a hospital volunteer, I began as a Main Lobby Volunteer and handled visitor inquiries, helped with wayfinding, and assisted patients in getting to various locations around the hospital. After a couple months, I was also added to the Emergency Department shift where I helped patients move to different triages, and assisted nurses in bringing patients into the check-in area.</p><h4>Handling Unfamiliar Scenarios</h4><p>Some of my most memorable moments volunteering at the hospital came during my time volunteering at the Lobby and the Emergency Department. Working a weekday, evening shift meant that no two weeks were the same; I handled situations ranging from bringing in an elderly gentleman who had collapsed in front of the hospital to finding ways to transport a child with pneumonia up to the Pediatrics department, while obeying hospital protocols. Most times, these situations required extreme compassion and being able to separate tone from meaning, especially when it came to tired patients/visitors who are simply seeking help. Being able to place myself in the patient’s shoes was extremely important, as it allowed me to understand what exactly they needed, and what was in my power to get it done for them.</p><h4>Improving Communications</h4><p>In my first couple months as a Lobby Volunteer, one of my main tasks was simple wayfinding where I helped out visitors/patients access different departments in the hospital. I found that due to the large elderly population in the community, many of them were often not able to remember complicated directions around the large hospital. In an effort to solve this problem I introduced smaller hand-drawn maps where I would mark landmarks in the area and draw out the route they needed to take, so that they didn’t have to remember the entire process. Many other volunteers also found this solution to be quite effective and took this up, allowing for an improvement in volunteer-visitor communications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83bda9a9f6f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/brampton-civic-hospital-83bda9a9f6f0">Brampton Civic Hospital</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOAR Conference]]></title>
            <link>https://medium.com/vyomesh-iyengar/soar-conference-5c80d64dd691?source=rss----4711c77d4950---4</link>
            <guid isPermaLink="false">https://medium.com/p/5c80d64dd691</guid>
            <dc:creator><![CDATA[Vyomesh Iyengar]]></dc:creator>
            <pubDate>Thu, 31 Dec 2020 22:48:20 GMT</pubDate>
            <atom:updated>2021-01-09T08:49:14.987Z</atom:updated>
            <content:encoded><![CDATA[<p>SOAR Conference is a leadership conference for students in grades seven and eight, helping them bridge the gap into high school by providing them with mentorship, and visibility regarding community opportunities. During Conference, students are matched with high school mentors and are offered an insight into what high school life is like, as well as go through various fun workshops and games where they learn some ways to improve their soft skills for better success. At the end of the day, students leave with a new community, knowing that they have people to rely on for advice and support throughout the next four years of their life.</p><h3>Conference Chair, 2019–2020</h3><blockquote>For SOAR Conference 2020, I was one of three Conference Chairs, and led the preparation for all the aspects of conference. Though Conference was cancelled due to COVID-19, I still learnt a lot throughout the months of planning and effort that we put in.</blockquote><h4>Leadership Developers</h4><p>A huge part of the success of conference comes from the leadership developers who volunteer their time and energy to become mentors for each of the young children entering conference. One of my roles was helping interview each of the applicants and work to ensure that they had the qualities we were looking for in the mentors. We interviewed over 150 applicants and chose 30 applicants. During the process, I was expected to exhibit impartially and ensure that all the candidates were looked at with an unbiased view.</p><h4>Executive Team</h4><p>One of the first tasks I did with my co-chairs was set up an executive team, unlike previous years we chose not to wait till September to pick our executive team but did so during the summer, so that we could start working prior to school starting. After conducting interviews, and choosing our team, we sat down with the entire team, as well as each portfolio to understand what they wanted the year to look like, as well as provide them with an outline regarding their main tasks and the associated timelines. We set up a task management system for all the members so that we could keep track of the progress of each portfolio, and step in as required.</p><h4>Funding and Sponsorship</h4><p>Although we were a student-led conference, we had many overheads to take care of, which would not be covered by student and volunteer fees. As a result, we sought out external sponsors to help us offset the costs that we had either through monetary sponsorships, or goods. In the months leading up to conference we were able to get over $8,000 in monetary corporate sponsorships, and were working with local branches of companies such as Starbucks and Quesada for non-monetary contributions.</p><h4>Mentorship Program</h4><p>As part of a collaboration with the Rotary Club of Mississauga, we offered half our seats to students from low-income families at a heavily subsidized cost, however we found that every year there were always more students who wanted to come, both from the Rotary Club and schools from all over the district. In an effort to meet with the increase in demand that we were seeing, we decided to launch the SOAR Conference Mentorship Program where we worked towards branching our the program to hold in other schools around the district. Working with teachers, and students around the district we conducted interviews and began the process of introducing our prospects to the conference and its operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*wsB5jEyLuaTRnpfKFGFvSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oNAGvHSFusU_rqXUo-MlaA.jpeg" /></figure><h3>Head of Conference Committee, 2018–2019</h3><blockquote>As a part of SOAR 2019, I was one of the Heads of Conference Committee, which put me in charge of arranging both the food services for the day of conference, as well as onboarding and training the majority of the volunteers who were helping with operations.</blockquote><h4>Onboarding and Training Volunteers</h4><p>Volunteers in the Conference Committee are in charge of serving food, running the games and workshops, setting up/taking down tables and chairs, and all the behind the scenes work that has to get done during the day of Conference. As the Head of Conference Committee, one of my roles was to come up with a comprehensive training session which would help them understand the purpose of conference, the importance of their job, and how to successfully handle any problems they face during the day of conference. I worked with teacher supervisors and other executives to ensure that all standards were being upheld, and dealt with any, and all problems my team had.</p><h4>Arranging Food Services</h4><p>Similar to any day-long event with teenagers, we needed to have food at Conference, all of which had to be arranged under a budget of $2,500. Working with local restaurants, we arranged for lunch and dinner to be catered, along with an ice cream truck, which we got a discount from. With the remaining $900, we worked to create a budget-friendly, healthy breakfast which we simply purchased in bulk from Costco, using our out of the box resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2mZsO2PgiR9Bchu3byZbVQ.jpeg" /></figure><h3>Head of Entertainment, 2017–2018</h3><blockquote>In my first year as an executive with SOAR Conference, I was one of the Heads of Entertainment, and was tasked with reaching out to organizations within the community who were willing to work with incoming high school students to invite them to our Opportunity Fair. I also helped come up with the storyline for the day of Conference and executed our mealtime entertainment.</blockquote><h4>Opportunity Fair</h4><p>One of the biggest workshops we have during the day of conference is our Opportunity Fair, where we bring in local organization and community clubs to bring awareness to the delegates regarding places they could get involved in. In the months leading up to conference, I worked with various organizations such as the Brampton Library, Peel GEMS, VEX Robotics and others to ensure that they had all the information they needed to successfully set up a booth and present their information to the delegates.</p><h4>Mealtime Activities</h4><p>Working with the Conference Chairs for the year, we came up with a storyline to tie together all the aspects of conference that year. As someone who greatly enjoys putting on a show, and trying on different hats, I helped put together an entertaining show for the delegates to enjoy, while helping explain some of the aspects of the day we had planned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1cFwXo8zAfNQNKTaROmGQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c80d64dd691" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vyomesh-iyengar/soar-conference-5c80d64dd691">SOAR Conference</a> was originally published in <a href="https://medium.com/vyomesh-iyengar">Vyomesh Iyengar</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>