<?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 Nishant Manchanda on Medium]]></title>
        <description><![CDATA[Stories by Nishant Manchanda on Medium]]></description>
        <link>https://medium.com/@nm_nishant?source=rss-1cdca46b3026------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*D1PiAmVLHezoZOpd.png</url>
            <title>Stories by Nishant Manchanda on Medium</title>
            <link>https://medium.com/@nm_nishant?source=rss-1cdca46b3026------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:23:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nm_nishant/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[Explaining Product roadmap — Instamojo Way]]></title>
            <link>https://medium.com/@nm_nishant/explaining-product-roadmap-instamojo-way-cce56c6fbd6d?source=rss-1cdca46b3026------2</link>
            <guid isPermaLink="false">https://medium.com/p/cce56c6fbd6d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-roadmap]]></category>
            <dc:creator><![CDATA[Nishant Manchanda]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 09:14:16 GMT</pubDate>
            <atom:updated>2019-03-04T09:14:16.260Z</atom:updated>
            <content:encoded><![CDATA[<h3>Explaining Product roadmap — Instamojo Way</h3><p>Product roadmap has been a very sought after and most often confusing term in the industry. Let’s first get on to what exactly product roadmap is all about and how to drive it.</p><p>In simple words, Product Roadmap tells the management, product owners, and other stakeholders, how the product is going to take shape in future, what all features are planned to be introduced in the product over a period of time. Hence, it tells the direction of the product, how it is planned to be matured.</p><p>Now in order to make a product roadmap and bring it in the best use of the product development, Product owners update it regularly keeping in mind the market scenario, technological advancement, customer feedback, and yes, of course, organizational goals.</p><p>Also remember, it’s not a document, which once developed becomes a constitution of the product. It’s an ever-evolving document, which is regularly reviewed and updated by the product owners. Basis the change in situation or customer feedback, management takes a decision in what feature to launch and what not.</p><p>To summaries what product roadmap does</p><blockquote>· Describe the vision and strategy of the product</blockquote><blockquote>· Provide a guiding document for executing the product strategy</blockquote><blockquote>· Helps in aligning all the stakeholders</blockquote><blockquote>· Facilitate discussion of options and scenario planning</blockquote><p>And what product roadmap is not</p><blockquote>· A Product detailed feature list</blockquote><blockquote>· A product solution document</blockquote><blockquote>· A resource planning document</blockquote><blockquote>· A technical document etc.</blockquote><p>Now, Let’s consider the example of Instamojo Product Roadmap. How it evolved over a period of time since it’s inception in 2012 and how the product owners are seeing this product to be in the coming quarters of 2019.</p><p>About Instamojo</p><p>First, let me give you a background of Instamojo</p><p><a href="https://instamojo.com/?utm_campaign=what_is_instamojo&amp;utm_content=sampad&amp;utm_source=quora"><strong>Instamojo.com</strong></a><strong> is a digital payments platform bundled with tons of e-commerce features to enable any business or individual to sell, manage &amp; grow effortlessly, securely and cost-effectively</strong>. The platform is built upon the existing financial infrastructure of bank accounts, credit cards or other digital payment instruments to create a pervasive &amp; persistent real-time payment solution.</p><p>Today, Instamojo has forayed into several business verticals. Thousands of users are using Instamojo to collect payments for ebooks, reports, tickets, tutorials, merchandise, invoices, services, and much more. Some of the current features of Instamojo platform are: Collect Payment, Manage Accounting, Resolve Disputes, Understand Data</p><p>Product Roadmap of Instamojo</p><p>Now let’s understand how Instamojo drove it’s product roadmap to achieve the organizational goals and vision.</p><p>When it first started in 2012, the main goal was to enable individuals, freelancers, home-prenuers, SOHO businesses to sell &amp; collect payments for digital goods, directly from customers by sharing a payment link.</p><p>Co-Founder Samad Swain shared his initial product strategy where he defined the organizational focus on three things — Reach, Revenue and Retention. In the early stages, they focused on Reach and Retention, which eventually shall lead to revenue.</p><p>Keeping this In mind the roadmap for the initial phase was accordingly</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*zfIWbQNrI0EOBI4RQ-UYHg.png" /><figcaption>Image Source — <a href="https://thoughtfarming.wordpress.com/2017/05/19/the-road-so-far%e2%80%8a-%e2%80%8ainstamojos-roadmap-to-success/">https://thoughtfarming.wordpress.com/2017/05/19/the-road-so-far%e2%80%8a-%e2%80%8ainstamojos-roadmap-to-success/</a></figcaption></figure><p>After the first launch, Instamojo continuously worked towards the improvement of their product to provide more services to their customers and stay competitive in the market segment they are present.</p><p>Here is how they moved along in their product roadmap strategy.</p><p>Roadmap — 2014</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*H05v3SpsIW8NW8xTnWzpng.png" /><figcaption>— <a href="https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810">https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810</a></figcaption></figure><p>Roadmap 2015</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*wd8axIRcVoR-0XtaTqwjkw.png" /><figcaption>Source — <a href="https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810">https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810</a></figcaption></figure><p>Roadmap 2016</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*FmUD2S5iUq34CT10snOSUw.png" /><figcaption>Source — <a href="https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810">https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810</a></figcaption></figure><p>Roadmap 2017</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*8Ji1nJCEIlA_4qfHXnB9Nw.png" /><figcaption>Source — <a href="https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810">https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810</a></figcaption></figure><p>Roadmap 2018</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*uFHQ5w9YvetbQOsJ3esikA.png" /><figcaption>Source — <a href="https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810">https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810</a></figcaption></figure><p>Roadmap for 2019</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*JsyjRL2mJNTqN4DsqNg1pQ.png" /><figcaption>Source — <a href="https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810">https://medium.com/@vivekkirubakaran/a-study-of-product-roadmap-for-instamojo-ea69acef6810</a></figcaption></figure><p>Tough this is a yearly roadmap, it has to be reviewed every 6–12 weeks depending upon the dynamic environment of the segment Instamojo is competing in.</p><p>Hope this has made it clear to you now, how product map helps in defining the direction of the product and gives a clear picture to all the stakeholders how and where the product is moving towards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cce56c6fbd6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Development At Zomato]]></title>
            <link>https://medium.com/@nm_nishant/agile-development-at-zomato-cea7a956e69d?source=rss-1cdca46b3026------2</link>
            <guid isPermaLink="false">https://medium.com/p/cea7a956e69d</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Nishant Manchanda]]></dc:creator>
            <pubDate>Tue, 19 Feb 2019 14:12:20 GMT</pubDate>
            <atom:updated>2019-02-19T14:12:20.949Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been building tech products for almost a decade now and have tried many development methodologies. Mainly the Waterfall and Agile. But with my experience, Agile has been the best in today’s fast-paced and dynamic scenario, where consumers’ need is changing at a drop of the hat. And adding to this, many players are competing in the market to solve the customers’ need. To ensure the demands of the user are met, product managers are constantly working to improve their product and reducing the ideation to launch cycle.</p><p>Talking about the agile methodology, I believe, all organizations make minor changes in the structure and methodology they follow, but the main structure remains the same, which is iterative and incremental. Let’s first talk about the agile methodology of software product development.</p><p>Agile means — an ability to adapt to the changes as and when needed.</p><p>As mentioned earlier, it is one of the most widely used methodologies for software development. It provides much-needed flexibility on a constant basis to accommodate the changing needs of the consumer so as the need to change the product.</p><p>Agile methodology has mainly two Frameworks.</p><p>1. Scrum Framework</p><p>2. Kanban Framework</p><p>If you are working on an agile methodology, you must be following one of the frameworks to develop your tech product.</p><p>Let’s talk more about the Scrum framework here</p><p>Scrum is a way of defining the team structure in such a way that it motivates collaborative work and ownership without having much of hierarchy. It works as a small challenge which is called sprint, where a group of developers, testers, scrum master, and a product owner come together to form a sprint team and find a solution to customers’ need by developing a specific feature.</p><p>Scrum is managed through Sprints, and each sprint has multiple epics and user stories to cover.</p><p><em>Following are the phases of a Scrum Framework :</em></p><p>· <strong>Product Backlog Grooming:</strong> Consisting all features, bugs etc in the list.</p><p>· <strong>Sprint Planning</strong>: To make the Sprint Backlog ready for the sprint.</p><p>· <strong>Daily Scrum Meeting</strong>: This meeting to take an update from each developer on what they did yesterday, what are they going to do today and if they have any blocker and to keep the entire team on the same page.</p><p>· <strong>Sprint Review</strong>: At the end of the Sprint there will be a review meeting to check the latest and confirm the requirements done.</p><p>· <strong>Sprint Retrospective: </strong>This happens after the sprint is over and to find out where we went wrong, can be improved or any shoutout.</p><p>Now let’s consider a case study of Zomato and we shall talk about introducing a few features through agile methodology</p><p>Most of you must know about Zomato or might have used it as well to order food online. Those of you who don’t know about Zomato, let me tell you about it.</p><p><a href="https://www.zomato.com/">Zomato</a> is a restaurant search and listing application. Currently, operates in 24 countries, including India, Australia, and the United States. The vision of the product is to provide information and rate/reviews of the restaurants. A user can order food online and get it delivered at their desired location.</p><p>Now let’s do a case study to understand the agile process to understand it better</p><p>Zomato, as you know, it’s primarily a mobile app, which user can use to find a restaurant and place an order.</p><p>We shall be taking this case study to build the following three features</p><p>1. Rate &amp; Review Restaurant</p><p>2. Filters for search</p><p>3. Online Ordering</p><p>Let’s consider the above three points taken from the Long term product roadmap or product vision, which is generally created at the top level after various feedback processes and strategic decision.</p><p>Now let’s discuss how we can transform the above three features into a functional feature and prepare a plan for the same.</p><p>Let’s first break the features into epics/stories and prepare a product feature plan or product backlog sheet</p><p><strong>Product backlog — Product Backlog is a high-level document which contains the epics or user stories added as a part of user feedback, business strategy, or product vision.</strong></p><p><strong>1. Rate &amp; Review Restaurant</strong></p><p>A. As a user, I want to rate the restaurant from 1 to 5, 1 being poor and 5 being best.</p><p>b. As a user, I want to write my review about the place</p><p>c. As a user, I want to add photographs of the restaurant as a part of a review</p><p>d. As a user, I want to share the feedback on social media platforms</p><p><strong>2. Filter &amp; Search</strong></p><p>a. As a user, I should have an option to choose a restaurant within 15 mins of drive</p><p>b. As a user, I should be able to filter restaurant basis cuisine</p><p>c. As a user, I should be able to filter restaurants expenses basis — Meal for two — 200–500, under 1000, above 1000</p><p><strong>3. Online order</strong></p><p>a. As a user, I should be able to place an order from multiple restaurants at the same time</p><p>b. Ad a user, I should be able to reorder the same things in easy steps</p><p>So let’s create a Product backlog from the above points</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*iva8WwZuZ299UvJd_XxwGQ.png" /></figure><p><strong>Sprint Backlog</strong> — From the Product backlog, Product owner picks up the more high priority items (epics/User stories) and put it into sprint backlog to discuss with the sprint team and do the feasibility study.</p><p>As said, Sprint backlog contains high priority epics/user stories from the product owner perspective, but that has to be discussed</p><p>So here is the set of user stories or epics, depending upon the deeper level of any use case can be identified during the feasibility analysis</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*jXB-MQ-FfBXzzkTffUkA1g.png" /></figure><p>As a part of sprint backlog, I choose the spics/ user stories basis the priority set in the product backlog and after selecting the items, I prefer to again set a priority among the selected items. So in the above example, I have priority 1 and 2 both.</p><p><strong>Sprint Planning</strong> — This is the next step, where product owner discusses the epics/ user stories with the scrum team, which consists of a product owner, Scrum master, tester, solution architect, and developers. They all sit and discuss the feasibility of the selected stories and provide feedback t the product owner whether the functionalities can be built in the defined time period or not. Items selected for sprint stays in the sprint planning document, and rest goes back to the sprint backlog.</p><p>At this stage, the team decides on the tasks against each user story and all developers decide who is going to do what and takes the complete ownership of delivering the same.</p><p>Continuing with the example, Let’s consider two of the high priority items are selected to be delivered in this sprint, one item is going back to the sprint backlog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*YuxfusZBdMfyDRTOYBuZSg.png" /></figure><p>Once the sprint is finalized and timelines are decided, the next phase is Sprint daily standup.</p><p>Sprint Daily Standup — In this activity, all the participants of the sprint shares their work status in terms of</p><p>1. What they did yesterday</p><p>2. What they will do today</p><p>3. Do they need any help to finish their pending tasks or want to share some learning</p><p>This gives the scrum master a daily heads up whether the sprint is going as per the plan or not. Scrum master prepares a burndown chart also to track the efforts planned, vs finished, vs remaining. This helps scrum master in making necessary changes well in time and ensures the planned sprint is delivered.</p><p><strong>Sprint Review — </strong>This happens at the end of the sprint when the dev team presents the developed functionality to the Product owner who decides on the go or no go of the feature in the product.</p><p>Sometimes, the developed functionality is not as per the desired standards or product owner has some idea to improve the same, the decision of not launching the feature can be taken.</p><p>Generally, this brings the end of the sprint, but few teams go a step ahead and perform one last activity in the scrum methodology</p><p><strong>Sprint Retrospective</strong> — At this stage, all team members discusses what all they did good or bad and how they can improve on the same in the next sprint to increase the overall performance of the team.</p><p>So this is how scrum methodology has been used in the industry to develop some of the most innovative and consumer-focused products.</p><p>Happy Agile development to you.</p><p>Signing off for the day</p><p><strong>Nishant Manchanda</strong></p><p><a href="http://www.customer121.com/">www.Customer121.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cea7a956e69d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product adoption life-cycle for Mobile wallets in India]]></title>
            <link>https://medium.com/virtual-round-table/product-adoption-life-cycle-for-mobile-wallets-in-india-e17a2ba86e45?source=rss-1cdca46b3026------2</link>
            <guid isPermaLink="false">https://medium.com/p/e17a2ba86e45</guid>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Nishant Manchanda]]></dc:creator>
            <pubDate>Wed, 10 Oct 2018 14:22:24 GMT</pubDate>
            <atom:updated>2018-10-10T14:22:24.924Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Product Adoption Lifecycle of Mobile wallets in India</strong></p><p>Mobile wallets, a concept which is still not clear to every Indian consumer who transacts online. There are many reasons behind the less adoption of cashless economy. Though when Google launched Google Wallet back in 2011, it was a clear chicken and egg situation, which all the Fintech companies had to break in order to set the road for user adopting the wallets for their day to day transactions over cash. The challenge was not only on one side but on the payment receiver side also. Unless someone is ready to accept the payment via wallet, no one can pay.</p><p>Over a period of time, companies like PayTM, MobiQuick, PhonePay etc. Have invested a lot in clearing the hiccups or especially chicken and egg situation in the market and increase the adoption rate of the Mobile Wallet in the Indian Market. Though the market is still not mature rather at a growing stage, we shall talk about how it started and what stage it is at now.</p><p><strong>Where Mobile wallet Adoption In India</strong></p><p>Let’s first understand where we stand in terms of the Mobile wallet adoption stage in India. In my view, the industry is at the “Early Majority”. The CHASM has been taken care well enough by the industry players and have created a mature product to be adopted by the major consumer base. It’s a very good stage for any established player to build a great user base and get higher returns on the investment they have made. Though this growth shall attract many new players in the game and might give a tough competition to the existing players.</p><p>Now let’s understand more about the different stages of the product Adoption lifecycle and how at different stages Indian mobile wallet companies attracted the consumer and make them adopt the product</p><p><strong>Innovators</strong> — In any industry, they are the sought after people not just by the companies but by the followers (future customers of the brand) also. They are high-risk takers in terms of trying out new products. Many times these kind of users are great influencers and help any product / Brand reach the masses. These users are also a great source of feedback to the companies. Though the number of users fall under this category is very less i.e. 2.5%, but the impact they have on the future success of the product is very high. Their usage, adoption, and opinion matters.</p><p><strong>Early Adopters</strong> — These types of users follow the Innovators and adapt the product as soon as it’s out in the market. Along with Innovators, they make an important set of the user for any product to focus in the initial stage of the Product adoption life cycle.</p><p><strong>Early majority</strong> — They are the one who are the next major set of users in the product adoption lifecycle and helps any product to reach its peak. They are approx. 34% of an overall user base of users. These sets of users adopt the product once they believe in it. Unless they see right examples of usage by other users and are convinced with their pre usage dissonance, they don’t adopt any product. More often they need a high amount of offers to be attracted towards the product usage.</p><p><strong>Late Majority</strong> — Though this set of the user also comprise of almost the same amount of users as Early adopters i.e. 34%, but they are little different from the early adopters. This set of users need more examples of product delivering the worth of its price and value proposition. Once they are fully satisfied that the product has no issues and is being very well tested in the market, only then they start adopting it.</p><p><strong>Laggards</strong> — This set of users falls under the last type of users in any product adoption life cycle. The set is as good as 16% of the total user base and needs a high validation of product before they accept it. This set of users are generally not risk takers and do not change their habits easily. Sometime they need a high amount of influencing power, especially from their peers to adopt the product.</p><p><strong>Challenges and what made the revolution in Mobile Wallet</strong></p><p>When Google Wallet was launched back in 2011, it was a classic challenge of economics — Demand Vs Supply. There were no demand and supply. The adoption for innovators was not easy as there were no merchants who would accept the payment via a mobile wallet. Other challenges were the slow internet connection, less security, less adoption and confidence in the online transaction etc. Soon many other players entered the ring and started competing to gain the maximum adoption in the market. The introduction of 4G and higher smartphones penetration was a supporting factor.</p><p>It was Nov 8th 2016, when the announcement of the discontinuation of INR 500 and INR currency by Indian Prime Minister, Narender Modi, whole country faced a situation of cash drying out of the economy. This was the golden moment for mobile wallet players to solve the problem and showcase a strong use case to the wider audience. PayTM responded very strongly to the move and gained maximum market share.</p><p><strong>Mobile Wallets Vs Other payment methods in India</strong></p><p>Well, Mobile wallets have many players to compete with. They compete not just with cash but with Cards and Newly launched UPI method of payment by Indian Govt.</p><p>In the urban market, the cashless economy has started to pick up. The strategy followed by PayTM post demonetization of bringing all possible small vendors into the ecosystem helped this industry grow many fold and increased the use of Mobile wallets by consumers. The petty cash transaction at the street vendors level has been replaced by the Mobile wallets. It’s a positive sign as more number of non-tech savvy users are adopting the Mobile wallet way. Parking lots, Toll plaza, Movie halls, Metro tickets and many more such places where cash transactions were more and cards were very less, Mobile wallet has taken a major share.</p><p>And the trend has not been limited to small transactions. Mobile wallets have made their remarkable presence in large ticket items also. This is primarily through major tie-ups done by the Mobile wallet players with many brands. More cash backs and discounts/offers is the way Mobile wallet companies have been giving tough competition to the card payment method. Though the credit cards are still having the last laugh because Mobile wallets are to be recharged first and then used for payments. The way mobile wallet companies are aggressively working towards acquiring a major market share, Soon we shall see some solutions around the same as well.</p><p><strong>Growth Hacks used by the Mobile wallet companies in India</strong></p><p>Growth hacks have become a common part of any Growth strategy and marketing strategy. Mobile wallet product companies are not lagging behind. In fact, these companies used an enormous amount of growth hacks in order to change the habit of consumers. Some of the growth hacks are widely used by such companies are — Cashback and Discounts/offers. Partnership with major players/brands such as Metro rail, Utility bills, Payments for basic needs/daily needs such as petrol pumps, vegetable vendors etc. Also played a major role in quick adoption and higher retention of the mobile wallet companies.</p><p><strong>Summary</strong></p><p>Overall, the mobile wallet product adoption is on growth in India and companies can see a major growth in the coming years. Though such success has already started attracting more players in the game and technological advancement is also paying a major growth of the industry. Govt. is also keen on making a cashless economy and policies introduced recently are helping the mobile wallet adoption rate in India. Not to my surprise, soon people would start gifting money through Mobile wallets — LOL.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e17a2ba86e45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/virtual-round-table/product-adoption-life-cycle-for-mobile-wallets-in-india-e17a2ba86e45">Product adoption life-cycle for Mobile wallets in India</a> was originally published in <a href="https://medium.com/virtual-round-table">Virtual Round Table</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who I Am, What I Do, Why I am Here……………]]></title>
            <link>https://medium.com/virtual-round-table/who-i-am-what-i-do-why-i-am-here-7c43c0bb75f9?source=rss-1cdca46b3026------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c43c0bb75f9</guid>
            <dc:creator><![CDATA[Nishant Manchanda]]></dc:creator>
            <pubDate>Wed, 27 Mar 2013 07:37:49 GMT</pubDate>
            <atom:updated>2013-03-27T07:37:49.552Z</atom:updated>
            <content:encoded><![CDATA[<p>Who I Am – I am a consumer of the world. I am an existing consumer of daily need items without which I can not survive. I am a consumer of those items whose marketers are trying to influence me to buy their product. I am a consumer of those products which I want to make aspiration of my life. I am the power, I am the Judge, I am the observer, I am smart, I am a fool, I am no one, I am Everyone.</p><p>What I Do – I said in my introduction, “I am a consumer”. Being a consumer, it’s my duty to see what marketers have with them to communicate with me. I decide what to do with that message. I am bestowed with the freedom to perceive any message from the communication despite being bothered by what marketer is trying to communicate with me. I have a complete freedom to add that product / service, which marketer is trying to sell me, in my daily need items or add them in my aspiration to buy some day in my life. So in nutshell, I decide what to do with what is communicated with me.</p><p>Why I am Here – Well, that’s some thing funny. Everyone knows why some one writes a blog. By the time you must have got an idea.</p><p>Check out the main blog http://virtualroundtable.wordpress.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c43c0bb75f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/virtual-round-table/who-i-am-what-i-do-why-i-am-here-7c43c0bb75f9">Who I Am, What I Do, Why I am Here……………</a> was originally published in <a href="https://medium.com/virtual-round-table">Virtual Round Table</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>