<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ashwini Kamath on Medium]]></title>
        <description><![CDATA[Stories by Ashwini Kamath on Medium]]></description>
        <link>https://medium.com/@ash_kamath?source=rss-a2194d38efa1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RR8eA_O2ryHacQ-TdF7Mqw.jpeg</url>
            <title>Stories by Ashwini Kamath on Medium</title>
            <link>https://medium.com/@ash_kamath?source=rss-a2194d38efa1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:11:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ash_kamath/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cloze Test — Assessing if your words make sense]]></title>
            <link>https://medium.com/design-ibm/cloze-test-assessing-if-your-words-make-sense-68ecd52a8a72?source=rss-a2194d38efa1------2</link>
            <guid isPermaLink="false">https://medium.com/p/68ecd52a8a72</guid>
            <category><![CDATA[user-research-design]]></category>
            <category><![CDATA[content-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[content-creation]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Ashwini Kamath]]></dc:creator>
            <pubDate>Mon, 18 Nov 2019 16:47:52 GMT</pubDate>
            <atom:updated>2019-11-18T16:51:07.835Z</atom:updated>
            <content:encoded><![CDATA[<h3>Filling in the blank with a Cloze Test</h3><h4>Assessing if your words make sense</h4><p>I am a user researcher on a product team that was tasked with establishing a content style guide in order to:</p><ul><li>Establish a consistent language when presenting information to customers</li><li>Create a content model that resonates with customers</li></ul><p>In a true user-centered fashion, the team started thinking about ways to engage customers and potential customers in a co-creation process.</p><p>User research is often synonymous with interviews and field research and is usually known (notoriously) for taking a few weeks to deliver an outcome. I love learning about methods I can use to bust that myth by getting feedback more quickly — and the Cloze test was one such opportunity.</p><p><a href="https://medium.com/u/d1afc4050106">Tom Roach</a>, a designer on the product team I work with, was looking to test the terminology used for some of the key concepts in the product. There was a lot of debate within the team about what the “right” terms were, and we decided to leverage our users to help us decide.</p><blockquote>In short, we wanted to know if our users understood the terms we had come up with, or if we needed to keep exploring.</blockquote><p>First, we evaluated some of the widely used statistical comprehension and readability testing methods like the <a href="https://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readability_tests">Flesch-Kincaid Index</a> and the <a href="https://en.wikipedia.org/wiki/SMOG">SMOG Index</a> and realized that:</p><ul><li>These methods are meant for testing paragraphs of text, not just labels or terms by themselves.</li><li>These methods evaluate if the text is readable and don’t necessarily indicate if it is understandable/comprehensible.</li><li>They also do not help evaluate alternative options.</li></ul><p>Sticking to the spirit of the IBM <a href="https://www.ibm.com/design/thinking/page/framework/loop">Loop</a>, we wanted to establish a process which would allow us to quickly and effectively test and iterate until the terminology was clear to our users. Also, phase 1 was testing only a few key concepts, so we needed something that could be easily repeated for future phases. Tom suggested the Cloze Test. I had read about this before but had never applied it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*w4lLPEMT2b0Ofv1gFk8AVw.jpeg" /><figcaption>Image by Lorenzo Cafaro from <a href="https://pixabay.com/photos/correcting-proof-paper-correction-1870721/">Pixabay</a></figcaption></figure><h3>So, what exactly is a Cloze Test?</h3><blockquote>A test in which one is asked to supply words that have been removed from a passage in order to measure one’s ability to comprehend text.</blockquote><blockquote>(Source: Oxford Dictionary)</blockquote><p>A Cloze Test is like Mad Libs or fill-in-the-blanks. Participants add in words that have been removed from a passage, thereby demonstrating their understanding and expectations of the content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*rkj8U7NfAyWvih0lEf_MBQ.png" /><figcaption>Example of a Cloze Test passage with words removed</figcaption></figure><h3>How we adapted the Cloze Test</h3><p>Usually, a Cloze Test is open, wherein participants can fill in any word they think fits in the space. To add some structure, we decide to try out a <strong>closed Cloze Test</strong>, where we would provide a list of options to choose from. This also aligned with our goal of evaluating different options for each term. So we drafted a paragraph that including 10 key concepts, with 4–5 alternative options for each concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*X_GWWJbxoYqI-5UVj0gOXA.png" /><figcaption>Our Cloze Test passage</figcaption></figure><p><strong>Example Options List</strong></p><p>For each word, we provided a list of options that participants could choose from. Participants could also add their own words if none of the words in the list resonated with them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*eIJU5iHU7uQPeShpR6PzXQ.png" /><figcaption>Options for Word 1</figcaption></figure><h3>Method</h3><p>We published the test to an online testing tool in a survey-like format so that participants were able to see the entire paragraph at all times. For each missing word participants were asked to select the best fit from the list of options provided to them. They were able to navigate between words if they changed their mind along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NlmVEyQP25kxbP6p2H5Cgw.png" /><figcaption>Screenshot from a session showing the participants screen with the paragraph and the list of options for word</figcaption></figure><p>These sessions were unmoderated and we recruited thirty participants that represented the targeted demographic of the product.</p><h3>Metric for success</h3><p>We adapted the Neilsen benchmark for comprehension, where each word must get at least a 60% agreement score:</p><p>Neilsen says, “<em>If </em><strong><em>users get 60% or more right on average</em></strong><em>, you can assume the text is reasonably comprehensible for the specified user profile employed to recruit test participants”.</em></p><p>We adapted it to 60% agreement, which is considered statistically significant:</p><p><em>If </em><strong><em>the agreement score between participants is 60% or more</em></strong><em>, you can assume the text is reasonably comprehensible for the specified user profile employed to recruit test participants.</em></p><h3>Method to the madness</h3><p><em>Also known as synthesizing the results and playing back to stakeholders</em></p><p>For each option of each word, we calculated an <strong>agreement score,</strong> which is the % of participants that chose that option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hTeCymWBjROvkMn21W-t0g.png" /><figcaption>Agreement Scores for Words 1, 2 and 3</figcaption></figure><p>For presenting the results to stakeholders, the word that got the top votes was filled into the blank, but we used color to identify if the word had met our “60% or greater agreement score” metric. This was a simple but important detail, which served as a reminder that a top vote didn’t always mean high agreement. We may need to go through multiple words until we get significant agreement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-0quB3Y_fGHhbR2rwgMXRQ.png" /></figure><ul><li>Green: high agreement i.e 61–100% of participants chose this option</li><li>Orange: medium agreement i.e 31–60% of participants chose this option</li><li>Red: low agreement i.e 1–30% of participants chose this option</li></ul><h3>Afterthoughts</h3><p>This simple method helped us gather feedback on the effectiveness of the terminology relatively quickly.</p><ul><li>After listening to the sessions, I realize how important it is for product related Cloze tests to recruit participants that represent your demographic, even if your paragraph is simple. The context and subject matter expertise they come in with eliminates the chances of guesswork.</li><li>Listening to the recordings of a few sessions and the participants’ rationale as they made their choices were very insightful.</li><li>Last but not least, it’s important to align as a team on the important terms that you want to test.</li></ul><blockquote><em>Who knew, a quick Mad Libs-like exercise could be leveraged to inform enterprise product design.</em></blockquote><p><strong>Resources we used to learn about Cloze Testing</strong>:</p><ul><li><a href="https://uxstudioteam.com/ux-blog/ux-copywriting/">UX Copywriting: 3 Copy Testing Methods That Beat A/B Testing + QUIZ</a></li><li><a href="https://medium.muz.li/cloze-testing-the-leading-ux-test-for-content-comprehension-87e03923362b">Cloze Testing — The Leading UX Test for Content Comprehension</a></li><li><a href="https://www.nngroup.com/articles/cloze-test-reading-comprehension/">Cloze Test for Reading Comprehension</a></li><li><a href="https://alistapart.com/article/testing-content/">A List Apart: Content Testing</a></li></ul><p><em>Ashwini Kamath is a Sr. Design Research, who works on IBM Data and AI products in Austin, TX. The above article is personal and does not necessarily represent IBM’s positions, strategies, or opinions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68ecd52a8a72" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/cloze-test-assessing-if-your-words-make-sense-68ecd52a8a72">Cloze Test — Assessing if your words make sense</a> was originally published in <a href="https://medium.com/design-ibm">IBM Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 things I’ve learnt in the last 10ish years as a designer]]></title>
            <link>https://medium.com/letters-to-a-young-designer/10-things-ive-learnt-in-the-last-10ish-years-as-a-designer-5b8543dce6?source=rss-a2194d38efa1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b8543dce6</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ashwini Kamath]]></dc:creator>
            <pubDate>Mon, 16 Jul 2018 14:38:29 GMT</pubDate>
            <atom:updated>2018-07-16T14:38:29.638Z</atom:updated>
            <content:encoded><![CDATA[<p>The good and sometimes challenging thing about any design problem is that there is no one right answer. It’s about iteration, its about failing early and its about learning as you go. The minute you think you know all there is to know, something new or different comes your way to show you that you are on a journey where you will be continuously learning. And that is how you improve your craft.</p><p>There are various types of design — interaction design, architecture, landscape design, service design, process improvement are a few that come to mind — and in all cases the journey of continuous learning, the circle of iteration, the process of “post-iting” holds true. (I refer to post-iting as the process of quickly capturing low fidelity ideas and along the way discarding the ideas that you don’t want to take forward). In my last 10ish years as a designer — starting as an architect and then moving to UX design — I’ve learnt that being able to adapt to the fluid and iterative nature of this field has been the key, and something I have been the very conscious of.</p><p><strong><em>If I had a deck of flash cards to keep reminding me of the rules of this game, here is what they would say:</em></strong></p><h4><strong>1. There is no one right answer</strong></h4><p>If you think you have a good idea or something constructive to say, say it. Don’t hold back because someone already suggested something and all the heads around the table nodded. This is not math, where 2+2 is 4 and that’s the end of the conversation. Even if people are agreeing, your option could still be relevant. Or you might find a way to bring two ideas together. Or you speaking up may give others in the room the confidence to do so too, and now you have many different ideas on the table, instead of “settling”.</p><h4><strong>2. Don’t be afraid of being uncomfortable</strong></h4><p>You have to be okay with being uncomfortable. The relative nature of design coupled with the idea of it being a collaborative activity (which means co-creating, convincing, selling, evolving, iterating) pushes us out of our comfort zone everyday. I love this <a href="https://www.ted.com/talks/luvvie_ajayi_get_comfortable_with_being_uncomfortable">TED talk by Luuvie Ajayi</a>, take a moment to listen to it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fluvvie_ajayi_get_comfortable_with_being_uncomfortable&amp;display_name=TED&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fluvvie_ajayi_get_comfortable_with_being_uncomfortable&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Ftalkstar-photos.s3.amazonaws.com%2Fuploads%2F1787a6e6-86df-48e0-9711-4b3a034bd686%2FLuvvieAjayi_2017W-embed.jpg%3Fh%3D316%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="316" frameborder="0" scrolling="no"><a href="https://medium.com/media/abcb0d1b39163dac1d01d65c9d84a0c0/href">https://medium.com/media/abcb0d1b39163dac1d01d65c9d84a0c0/href</a></iframe><h4><strong>3. Don’t be afraid of asking questions</strong></h4><p>I’ll be the first one to admit, this is not easy and may take some practice (aka gets better with experience). The thing to remember is that at the heart of it, we are problem solvers. We need to ask questions — even if it is just asking why — to get to the heart of the problem. For some people asking questions and having all the heads turn towards them is not easy, to that I say “get comfortable with being uncomfortable” (now where have you heard that before?).</p><p>There is so much knowledge and information coming at you everyday, the only way you will be able to make sense of it is by asking questions. It’s better to ask the “silly” (or so you think) question about what an acronym stands for than to move ahead without knowing it at all. I can guarantee you, over half the room will secretly be thankful that you asked because they didn’t know either.</p><blockquote>Don’t be afraid to ask questions. Don’t be afraid to ask for help when you need it. I do that every day. Asking for help isn’t a sign of weakness, it’s a sign of strength. It shows you have the courage to admit when you don’t know something, and to learn something new. — Barack Obama</blockquote><p>But, there is a way of asking questions to make sure you are constructive, not attacking and you are targeting the problem you want to solve. Here is an <a href="https://hbr.org/2015/03/relearning-the-art-of-asking-questions">article from Harvard Business Review</a> that I have read several times as a way of reminding myself that my questions need to inform and hopefully progress the discussion. Since we are so passionate about our work and a lot of times speaking to or defending the ideas we may have, its always good to remind ourselves of the outcome we are hoping to achieve.</p><p>Also, remember that you don’t always have to ask a question…think of the problem at hand and the end goal or outcome that you are hoping for.</p><h4>4. Have a point of view about where you would like your career to go</h4><p>When you talk to mentors, or ask people for career advice, you have to know what you want to be when you grow up. A design executive once told me that from the people she had mentored, those who had their own opinion about their career and and got help and advice on how to get there were the most successful. And those who were hoping that their manager, mentor or organization would tell them what to become struggled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/0*xUm2pR8xiOxFMnhO.jpg" /><figcaption>Know your goals, get help on how to get there. Don’t ask someone else for your goals.</figcaption></figure><p>So even though things may change, you have to plan towards something. I encourage people to have an end goal (long term plan), but then work towards milestones or shorter term goals. This way you don’t feel the pressure of knowing exactly where you will be 7,10,20,30 years from now but you are still goal oriented and planning towards something (could be end of the year).</p><h4>5. Seek (constructive) feedback</h4><p>The only way you can make your work better is to get feedback on it. Don’t be afraid to show your work — at all stages and fidelities — to get critique. And since it is important to get good, constructive feedback think about these things when you ask for feedback:</p><ul><li>Frame the problem so people know what they are giving feedback on</li><li>Tell them exactly what you want feedback on. For example, if you want feedback on a particular interaction let them know so they don’t give you feedback on the quality of copy (which you know still has to be worked on)</li><li>Select the correct audience based on the feedback you are seeking.</li></ul><p>In my experience, regular feedback along the design cycle results in a stronger solution.</p><h4>6. There is something to learn from every person in the room</h4><p>Get rid of the thought that the highest paid person in the room has the most knowledge. Especially in big corporations its easy to get bogged down by the titles of the people in the room. Remember, everyone has their own expertise and a unique set of skills. So don’t only follow what seniors have to say, listen to everyone. Depending on the topic and the outcome, seniority may not matter. Also, for design feedback, your peers/co-designers may have more impactful feedback than an executive.</p><h4>7. Take some time to pause ever so often</h4><p>I say at two levels: 1) a complete break from work, 2) pausing and stepping back to see the bigger picture.</p><p>Completely taking a break is 100% necessary to make sure you don’t get burnt out and feel energized working as a problem solver. The reason I have this explicitly as a “point to remember” is because I have seen many people who get so involved in their project or begin to believe that without them the project won’t move forward, that they don’t take a break and then realize they have stretched themselves.</p><p>Pausing and stepping back while working on something is critical because as designers we get so caught up in the (sometimes unnecessary) details of the solution that we lose sight of the bigger picture. The architect in me lovingly calls this the “AutoCAD syndrome” aka zooming in so far into a drawing to intricately detail it out, that you lose sight of the scale you are working at and when you print it looks like a big blotch. There are many ways to pause and step back — seek critique, revisit the problem statement or project brief, revisit the design goals, look back at the personas or who you are designing for and see if their problems are being solved, etc.</p><h4>8. Seek mentorship</h4><p>I have had several mentors and each of them has taught me something about myself that I didn’t realize. While mentors provide information and knowledge, they also may be able help you identify ideas for improvement. You don’t have to have one mentor at a time, you can have several mentors and the goals for each those relationship may be different. For example, I had a mentor who was close to my everyday and was able to monitor leadership skills and how I could improve there. Another mentor (not privy to how I function everyday) was a senior person with a lot of experience at the company I worked for, who helped me navigate the corporation. And yet another mentor worked with me early on in my UX career to review the quality of my research artifacts. If you need more convincing on the benefits of having mentors, here are <a href="https://www.inc.com/john-rampton/10-reasons-why-a-mentor-is-a-must.html">10 Reasons Why a Mentor is a Must</a>.</p><h4>9. The grass always seems greener on the other side</h4><p>When the going get tough the easiest thing that comes to mind is to jump ship and move jobs. If you are considering that kind of a change seriously, it’s important to remember that all organizations come with their own set of problems. So think about what is most important for you, what will push your career forward and what will make you more satisfied personally — take a decision based on that. For example, what is more important to you at this stage of your life (and for the next 2–5 years): work-life balance or take home pay. These are all personal decisions and there is no right or wrong. But thinking that the next job (who’s office looks amazing on social media thanks to all the freebies) will have no pains, is foolishness.</p><h4><strong>10. The best advocate for you, is you</strong></h4><p>You know your strengths and achievements better than anyone else. The passion with which you can advocate for yourself is probably unmatched. So do it. If you feel you deserve a raise or a promotion or a special project…ask for it. <em>But don’t be pompous or presumptuous, make sure this ask is backed by evidence</em>. When you go to your manager/HR/authority with this ask, make a case for yourself using your portfolio for work. Show what you have achieved and why they should agree with you.</p><figure><img alt="Image result for asking for a promotion meme" src="https://cdn-images-1.medium.com/proxy/0*w9hfrpxJ0hCg4G2-." /></figure><p>Disclaimer: These were not it order of importance. All of these aren’t special or specific to designers, but have always been a good reminder of the world I work in, and have been very instrumental in giving me the confidence to grow as a designer in a big corporation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b8543dce6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/letters-to-a-young-designer/10-things-ive-learnt-in-the-last-10ish-years-as-a-designer-5b8543dce6">10 things I’ve learnt in the last 10ish years as a designer</a> was originally published in <a href="https://medium.com/letters-to-a-young-designer">Letters to a young designer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bombay I grew up in taught me tolerance]]></title>
            <link>https://medium.com/@ash_kamath/the-bombay-i-grew-up-in-taught-me-tolerance-39855cd4b9e9?source=rss-a2194d38efa1------2</link>
            <guid isPermaLink="false">https://medium.com/p/39855cd4b9e9</guid>
            <category><![CDATA[tolerance]]></category>
            <category><![CDATA[religion]]></category>
            <category><![CDATA[bombay]]></category>
            <dc:creator><![CDATA[Ashwini Kamath]]></dc:creator>
            <pubDate>Tue, 01 Dec 2015 02:03:27 GMT</pubDate>
            <atom:updated>2015-12-14T15:49:01.787Z</atom:updated>
            <content:encoded><![CDATA[<p>I grew up in South Mumbai, it was called Bombay then. Apparently Mumbai offers a far more “modern”, people say “westernized” or “Americanized” lifestyle when compared to many other parts in India. But when compared to the rest of the world, yes it has leaps and bounds to grow and go. But today, where the headlines are predominantly about religious wars, intolerance, racism, sexism, it makes me wonder if the Bombay <em>I grew up in </em>could actually stand as an example of tolerance to the rest of the world.</p><p>This post is definitely all about my experience and perspective, and maybe not very generalizable. But that’s exactly the point. I wish it was. If everyone grew up in the Bombay that I did, the world might be a more tolerant place.</p><p><strong>Know no religion</strong></p><p>As a child when people asked me what religion I was, I would say Maharashtrian. Why? Because the other language I knew, beside English, was Marathi. Maharashtrian is not a religion, it is what people who live in the state of Maharashtra may be called. But I didn’t know any other way. My parents never forced any religion or religious views on my brother and me. My grandmother (who I called Mummy, because my dad did) was more liberal that my parents. As far as I remember, the things that were constantly iterated in our home were 1) always help others, especially the less fortunate 2) never disrespect any profession, 3) never lie, 4) money and luxuries — here today, gone tomorrow. I think these things are inherent to most religions or faiths.</p><p><strong>We practiced everything</strong></p><p>Like I said I didn’t know what religion I belonged to until much later in life. That too, I learnt it from a relative, and not my parents. My mom stopped at a small chapel, or a church on the way back from work several times a week, sometimes we went to the temple, sometimes visited the mosque near our house, and I accompanied my friends to their places of worship when I was with them. I learned alot about the rituals associated with many religions. And thus that was my mindset — I was Christian, Muslim, Hindu, Buddhist, Jain, and more — all in one — because my family and I practiced everything</p><p><strong>Religious practices = food and celebration</strong></p><p>My family loves food and festivities. At home we cook all kinds of cuisines — dishes from various parts of India, Thai, Chinese (with an Indian twist), Mediterranean, Italian, you name it. We celebrate Diwali with as much pomp as we do Christmas. In fact my grandma loved decorating the Christmas tree, and I was her helper. A tradition that we have carried forward after her passing. My family eagerly awaits Ramzan each year, so that they can go out and devour the delicious food that runs through the night for that occasion. By no means am I trying to dismiss the values and practices behind these occasions, but saying that when they are presented to a child with so much positivity, they become a good memory — something you look forward to. So no matter what religion that festival is associated with, you love being a part of it.</p><p><strong>Caught me young</strong></p><p>I was fortunate to attend an International school, which meant I had classmates from all religions. This was amazing, because I grew up experiencing many cultures and practices right from kindergarten. I’m also thankful for the exposure I got to so many languages. I may not be fluent, but I can certainly have a basic conversation in 5 languages. Having said that, I bring up the“classmates from all religions” only now. In school all I knew was we were all Bombayites (residents of the city of Bombay).</p><p><strong>My family has them all</strong></p><p>Lots of “inter-caste” (I hate that word) marriages in my family, has led to us being a mixed bunch. And when you have aunts, uncles, or cousins who you love, and know may practice or believe in something else, you learn to respect it.</p><p>Today as I sit back and read the news, I am very thankful for a childhood that taught me to be tolerant. Tolerant and accepting — of people, religion, beliefs, practices, ideas. Thank you:</p><ul><li>Mom and dad: for never teaching us that there is only 1 particular way, and allowing us to form our own thoughts and opinions</li><li>Mummy: for being way ahead of most people in your generation, and teaching us that religion is about creating a positive atmosphere for everyone around you</li><li>My extended family: for being so diverse, and accepting</li><li>My school: for the multicultural exposure</li><li>Last but no the least, the city of Bombay for allowing me to grow up in such an environment</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39855cd4b9e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>