<?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 Vviral Shah on Medium]]></title>
        <description><![CDATA[Stories by Vviral Shah on Medium]]></description>
        <link>https://medium.com/@viralshah?source=rss-266fa39d98c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*C8JU62wftZbylmd6.jpg</url>
            <title>Stories by Vviral Shah on Medium</title>
            <link>https://medium.com/@viralshah?source=rss-266fa39d98c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:56:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@viralshah/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[Workflow Automation Silos Vs Structured]]></title>
            <link>https://medium.com/@viralshah/workflow-automation-silos-vs-structured-5d360d9cf17b?source=rss-266fa39d98c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d360d9cf17b</guid>
            <category><![CDATA[process-automation]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[agentic-workflow]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <dc:creator><![CDATA[Vviral Shah]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 05:20:08 GMT</pubDate>
            <atom:updated>2026-09-29T05:20:08.976Z</atom:updated>
            <content:encoded><![CDATA[<h3>Often workflow automation taken as a silos can lead to more process misalignment then process improvement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*AZVbQjfTKDMPj-u21EpWjQ.jpeg" /><figcaption>Workflow Confusion</figcaption></figure><p>Performing automation in isolation inside a business process often does more harm than good. Often, it has been noticed that such automation can help the overall bottom line of activity, but creates major process misalignment at the top or across the overall process of the business function. Over my fifteen years of leading enterprise SaaS and automation initiatives, I have repeatedly seen companies mistake localized speed for systemic efficiency. This often makes them wonder why their technology investments are not moving the needle.</p><p>This challenge is particularly relevant today as we enter what Gartner defines as the “BOAT” (Business Orchestration and Automation Transformation) era. This moment intends to deliberately combine different tech into a single platform. This can help companies to focus on a single tool rather than using multiple tools or disconnected processes.</p><p>As the AI sector is gaining huge push in the industry. Many companies try to automate small tasks to save time. As per LinkedIn’s recent survey, close to 80% of these projects fail to grow beyond the trial phase. Think about an HR function in a large-scale organisation. Using HR as an idea to set the context. What would happen if the team only automates the hiring or resume review process? This typically means getting all the sourced candidates; the automation will review candidates’ profiles, match with the JD and industry relevance terms, and shortlist them.</p><p>Now this can be faster for the recruiter, but what about the larger HR functions? Wouldn’t it be helpful if we automated the entire process? Meaning posting leads on job portals, sourcing the right candidates, setting up the right tasks for the shortlisted candidates, having humans in the loop for the review process, getting their paperwork or background check done, along with their pay rate (Of course, HITL is needed here), setting up their banking, employee identification, etc by the same workflow. That can be a massive savings and better use of resources.</p><p>When the organisation automates these processes in silos, they are merely shifting the bottlenecks further down the pipeline. This is a huge automation structural hurdle. A study done by researchers and published on ResearchGate back in 2022 found that organizational silos exist in 83% of surveyed companies. As many as 97% of respondents stated that these silos have a negative effect on their organization’s performance.</p><p>As a thought idea, it’s always better to check the end-to-end cycle and plan and plant the automation as and where it’s necessary, in places where it can help to speed up the complete end-to-end processes rather than a smaller pie of work. To win an operational WAR, one needs to fight with an army of BOTS rather than a single soldier BOT.</p><p>In a past delivery<br>role I led, we stopped looking at individual task pain points and instead<br>mapped out entire cross-functional workflows from start to finish. For real<br>benefit of the AI automation workflows, a true operational transformation should<br>have the following main steps. This can not only map the entire process out, but<br>also help to solve the process and get automation benefit to maximum.</p><p>Step 1: Discover &amp; Map the Current Process (As-Is): Should include Process mining, detailed stakeholder interviews, listing all the silos, and their desired benefits to the team as well as to the company</p><p>Step 2: Standardize and Optimize the Workflows: Ensure that redundancy gets addressed and quantify benefits of each silos. There should be real value to have automation of any process. The second important thing is to have a standard set of automation rules.</p><p>Step 3: Architect the integrated Ecosystem (To-Be scenario): Have core orchestration (BPM/IPaaS), API first strategy; for any legacy application, use RPA (Robotic Process Automation). Clearly identify areas where we need HITL (Human in the loop), and plan the validation as non-negotiable for HITL.</p><p>Step 4: Develop and Deploy Iteratively: Define the right value system, agile sprint, and have robust error handling</p><p>Step 5: Change Management and Governance: Have a structured process of user training, and have COE (Centre of Excellence)</p><p>Step 6: Continuous monitoring and optimization: Keep the learning curve wide, learn from the flow, understand and document the problems, and ensure to see those problems as a larger ecosystem or a larger process, rather than a small chunk of the process.</p><p>By connecting these disparate steps into a unified workflow, we align different departments, eliminate unnecessary manual handoffs, and ensure data flows seamlessly without human friction. We must move away from “task automation” and transition toward full “process integration” where humans are strategically positioned to make critical decisions rather than copy-pasting data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFzbLT_z-AZWelongt7RPg.jpeg" /><figcaption>Comparison Silos Vs Structured</figcaption></figure><p>As enterprise automation platform Flowable points out, relying solely on task-level automation merely creates “automation islands” where individual jobs are automated but the handoffs between systems are not; true business orchestration is what joins these islands into a single governed process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVZ3ttzPqUJJWotujVWZ2g.jpeg" /><figcaption>Long Term Benefits</figcaption></figure><p>Using this approach to enterprise automation projects, I had built clarity on how to solve a full-scale 360* problem with clarity on business values and growth post this automation. My team had delivered undeniable business value, including $5 million in positive revenue impact and $3.4 million in direct cost savings. Furthermore, by eliminating the manual handoffs and disconnected tools between siloed systems, we achieved an 86% error reduction across core operational processes. These numbers demonstrate that true value comes from connecting the dots, not just polishing a single dot.</p><p>True operational<br>efficiency is never about making a single task go faster, but to build a tasks<br>systems that can deliver and perform without interruption.</p><p>When you plan your next automation initiative, look at the entire journey rather than just the easiest task that lies directly in front of you.</p><p>How has your organization managed the balance between quick wins in task-level automation?</p><p>I would love to hear your thoughts.</p><p>Connect with me: <a href="https://www.linkedin.com/in/vviral/">LinkedIn</a>, <a href="https://substack.com/@vvs24">Substake</a>, <a href="https://medium.com/@viralshah">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d360d9cf17b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Most enterprise automation projects fail long before a single line of code is written, and it is…]]></title>
            <link>https://medium.com/@viralshah/most-enterprise-automation-projects-fail-long-before-a-single-line-of-code-is-written-and-it-is-07e465de8111?source=rss-266fa39d98c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/07e465de8111</guid>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[it-service-management]]></category>
            <category><![CDATA[ai-flow]]></category>
            <category><![CDATA[operations-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Vviral Shah]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 14:56:01 GMT</pubDate>
            <atom:updated>2026-09-25T14:56:01.675Z</atom:updated>
            <content:encoded><![CDATA[<pre>AI Chatbot: The 9-form chaos that was slowing down 10,000 people</pre><p>Most enterprise automation projects fail long before a single line of code is written, and it is rarely because of weak technology. Instead, these initiatives collapse because organizations attempt to automate processes that nobody actually understands. As a trending discussion on LinkedIn emphasizes, the golden rule of modern workflow design is simple: before you automate a process, you must first fix the process, because automating a messy workflow only makes the mess happen faster. While industry experts frequently debate the exact failure rate of these initiatives, with Reimage noting that the ubiquitous “70% failure” statistic is actually a misquoted change-management figure rather than a measured digital transformation rate, the struggle to achieve lasting change is real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2y_0LCKyBWuOB51QMN32lg.png" /></figure><p>In fact, McKinsey’s actual digital transformation research found that only 16% of respondents successfully improved and sustained their performance. Still, we treat software as a magical band-aid for operational confusion, assuming that layering artificial intelligence over a broken process will somehow make it whole.</p><p>In most corporate environments, when a workflow becomes slow or confusing, the standard response is to build another form, open another support queue, or launch a new ticketing portal. Over time, departments build their own isolated solutions to manage incoming requests. Often, employees are loaded with so many tools, which creates the maximum amount of confusion about where to submit their questions and hoping they land in the right inbox. This creates a massive digital tax on employee productivity and drives up operational costs. This rush to automate without structure is a widespread issue; according to USAN’s 2026 research reported by Meme Burn, while 98% of enterprise contact centres now use AI, only 12% have a fully optimized strategy, exposing a massive gap between technology adoption and real execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*3-DQwxOZmvSshU2sqWq8BA.jpeg" /></figure><p>In a past enterprise project I led, this exact approach had created a paralyzing nine-form chaos that was slowing down 10,000 global users. Whenever an employee needed help, they had to choose from nine separate, complex request forms. This could eventually lead to frustration as well as customer dissatisfaction due to incorrect submissions, misrouted tickets, and constant manual redirection. The engineering team was eager to jump straight to building a highly complex, multi-layered machine learning routing engine. However, as we analysed the workflow, we uncovered a deeper, non-technical roadblock: the real friction was not the forms themselves, but the fact that no two business units agreed on what those nine forms were actually supposed to do.<br> <br> Before writing any code or configuring an AI model, we had to step back and tackle what I call ‘step zero’: forcing our key stakeholders into a room to agree on a single, unified business taxonomy. Mostly, the team spends days mapping out user intents, defining terms, and aligning departmental definitions. This foundational work is critical; as Gartner insights reveal, a lack of data readiness is a top barrier to AI, driving over 75% of organizations to prioritize AI-ready data investments such as establishing business context through metadata management and semantic layers before trying to scale. Once we had got hold of this shared foundation, we designed and delivered a unified AI chatbot that served as a single, intuitive front door for all 10,000 users globally. The chatbot identified the user’s role, understood their natural-language intent, automatically routed the request to the correct backend system, and kept track of the progress in one central location.</p><p>Just by focusing on taxonomy first and then diving into technology, we achieved a 76% reduction in request turnaround time and unlocked rapid user adoption. Over my 15 years in enterprise SaaS, prioritizing this structural alignment before implementing automation has consistently delivered significant business impact, including more than $3.4 million in cost savings and an 86% reduction in operational errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*YIumC0KMFl6n4D2BYvQQlg.jpeg" /></figure><p>True efficiency is not about buying the most advanced AI tools; it is about doing the hard work of organizing your business rules before you automate them. If you do not clean up your internal taxonomy first, AI will help your organization make mistakes much faster.<br> <br> How does your team handle the ‘step zero’ of mapping out messy processes before introducing automation? <br> <br> Love to hear your thoughts!</p><p>#DigitalTransformation #OperationsManagement #ProcessImprovement #ITServiceManagement</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07e465de8111" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Development Agile Methodology — Case Studies: Zomato]]></title>
            <link>https://medium.com/@viralshah/product-development-agile-methodology-case-studies-zomato-a25166b35dc3?source=rss-266fa39d98c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a25166b35dc3</guid>
            <category><![CDATA[foodtech]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[assignment]]></category>
            <category><![CDATA[zomato]]></category>
            <dc:creator><![CDATA[Vviral Shah]]></dc:creator>
            <pubDate>Tue, 17 Apr 2018 13:54:18 GMT</pubDate>
            <atom:updated>2018-04-17T13:54:18.613Z</atom:updated>
            <content:encoded><![CDATA[<p>“Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning.” — Albert Einstein</p><p>The Base:</p><p>To build a product from scratch is quite a task. There are many factors that needs to be considered for developing a successful product. For a product manager, this is a huge challenge.</p><p>To lay down the foundation, there are basic steps the product manager should be following to start development of the product.</p><p>Conception of the Idea &gt; Market and user research &gt; Product planning &gt; Design &gt; Development &gt; Testing &gt; Deployment &gt; Maintenance</p><p>The product life cycle chart:</p><p>The product planning / development and releasing product to the market are the crucial steps, these has to be taken care with utmost care.</p><p>Let’s me talk about one of the most widely use concept. Agile / Scrum methods.</p><p>Let’s take example of Agile. What do we mean by that?</p><p>Agile methodology is a software development process framework that embraces the iterative and incremental approach — open collaboration, and process adaptability throughout the life-cycle of the project.</p><p>Incremental and Iterative characteristics</p><p>Incremental software development entails delivering finished components of the whole in parts. It allows the team to stagger the release of features which are of utmost value to customers.<br> <br> The iterative approach produces earlier release and better stakeholder’s feedback. The feedback is used to review the project priorities and make changes to the requirements, functionalities, estimations, plans, resources, etc. as required.</p><p>What are the benefits of Agile Method?</p><p>This iterative agile approach is more flexible and its short time-span iterations seek improvement for the project in small release, with minimal planning, rather than plan at length. This helps to minimize the overall risk, and allows the project to adapt to changes more quickly.</p><p>Let’s talk about this approach for our case study. Zomato App.</p><p>Consider below features from zomato app</p><p>· Rate/Review a restaurant</p><p>· Filters for search</p><p>· Online Ordering</p><p>The process for agile development will have started with above features being part of the product backlog and in the priority order to make it to the sprint backlog</p><p>Execution of Agile for Zomato Food App</p><p><strong>Step1 </strong>— Development team will share their views with the product owner on the time needed and will share the plan on the tasks that can be completed in the defined two weeks period.</p><p><strong>Step 2 </strong>— Delivering a working software in two to three weeks <strong>(version1)</strong></p><p>Working software (version1) will be more useful and welcome than just presenting documents to clients in meetings</p><p><strong>Step 3 </strong>— Collaborating ideas from the team members and possible feedback from the clients, features are refined (added/deleted)<br> Requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important<br> <strong>Step 4 -(version 2) </strong>Responding to change over following a plan — — agile development is focused on quick responses to change and continuous development</p><p><strong>Rate/Review a restaurant feature:-</strong></p><p><strong>Version 1 (simple)</strong></p><p>Rate on 5 Point scale</p><p>Average rating for a restaurant</p><p>List of recent 5 reviews with dropdown for other reviews</p><p><strong>Version 2</strong></p><p>Included colour codes for rating — Maroon, red, orange, Yellow, light green and green</p><p>Avg rating along with display out of total no. of reviews</p><p>Add button sort reviews basis</p><p>Recent reviews/High to low /Low to high/Most recent reviews first/ Reviews by people you follow</p><p><strong>Filters for search feature:-</strong></p><p><strong>Version 1 (simple)</strong></p><p>Search by restaurant name</p><p>Select location</p><p>Select cuisine</p><p><strong>Version 2</strong></p><p>Common search bar — name, cuisine, dishes</p><p>Choose/detect location or nearby filter</p><p>Occasion types –</p><p>Drinks &amp; night life /Dining out/ Desserts /Cafes &amp;more</p><p><strong>Version 3</strong></p><p><em>Keeping version 2 as it is</em></p><p>Added more tabs like —</p><p>Trending this month, Best Collection, Adding Mood tab — Sports and drinks, live music, drinking under the stars etc.</p><p><strong>Online Ordering feature:-</strong></p><p><strong>Version 1 (simple)</strong></p><p>Show list of restaurants that allow online order</p><p>Online menu with price</p><p>Add / Remove dishes to /from cart</p><p>Order summary and Place order</p><p>Add/select address</p><p>Payment by cash or card</p><p>Delivery boys name and number</p><p><strong>Version 2</strong></p><p>For each restaurant also display appx. Delivery time</p><p>Colour coding of veg (green) and nonveg (red)</p><p>Highlighting offers on dishes</p><p>Also adding map (GPS location)</p><p>Including wallets</p><p>Delivery boy contacts details and tracking order status</p><p>Rate delivery</p><p><strong>Summary –</strong></p><p>Agile development methodology attempts to provide many opportunities to assess the direction of Zomato app throughout the development lifecycle.</p><p>In an agile paradigm, every aspect of development requirements, design, etc. is continually revisited throughout the lifecycle to preserve a product’s critical market relevance and ensure team’s work doesn’t wind upon a shelf, never released, is an attractive option for stakeholders and developers alike.</p><p>The results of this “inspect-and-adapt” approach to development greatly reduce both development costs and time</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a25166b35dc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Adoption Cycle : Mobile Wallet In India]]></title>
            <link>https://medium.com/@viralshah/the-product-adoption-cycle-mobile-wallet-in-india-671a04267bf7?source=rss-266fa39d98c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/671a04267bf7</guid>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Vviral Shah]]></dc:creator>
            <pubDate>Sun, 13 Aug 2017 19:27:40 GMT</pubDate>
            <atom:updated>2017-08-13T19:27:40.585Z</atom:updated>
            <content:encoded><![CDATA[<p>Mobile Wallet — a new way to “Digital India mobile payment”</p><p>Introduction: Imagine a scenario where a common man goes to buy onion half kg in the market.</p><p>Vegetable vendor: 37.50 Rupees Sir!</p><p>CM: I have 40, do you have change?</p><p>Vegetable vendor: sorry sir, can I put two chilies extra sir?</p><p>CM: Well I don’t need those, but it’s ok, never mind.</p><p>Have you ever faced a situation like this? May be arguing with auto guy, for change or to a local kirana store for one rupee change? How do you avoid this situation, welcome to the world of digital wallet. What it is? : In simple terms, it is a digital technology to pay your bills online instantly without having to pay by cash or use your credit or debit card all the time. It acts like a virtual wallet, which can be preloaded with your preferred amount of money from your bank account or credit or debit cards and used to spend it online. You can simply use your smartphone or a tablet to make the payment. With e-Wallet apps installed on your mobile, you need not carry cash in your hands every time.</p><p>Mobile Wallets or Digital Wallets or e-Wallet apps will allow you to pay electricity bills, mobile recharge, get movie tickets and what not right from your mobile device you hold in your hands. You can quickly and feasibly load your mobile wallets by either using your credit or debit or via internet banking.</p><p>There are mainly three types of Mobile wallets:</p><p><strong>Open PPI: </strong>Allows a user to buy goods and services, withdraw cash at ATMs or banks and transfer funds</p><p><strong>Semi-closed PPI: </strong>can be used to buy goods and services from merchants that has a contract with the issuer to accept mobile wallet as a payment instrument. It doesn’t permit cash withdrawal or redemptions.</p><p><strong>Closed PPI:</strong> Issued by a company to buy goods and services only from that company. It doesn’t permit cash withdrawals or redemptions.</p><p>*PPI: Pre paid instruments</p><p>There is a strong rise in the mobile wallet companies over the year. PayTm, Freecharge, Mobikwik are some of the top wallet companies in India. Post 8th Nov, 2016, due to demonetization it has close to 207%. The attached graph talks about the growth of mobile wallet users and transactions in India.</p><p><strong>M-wallet users adoption life cycle:</strong></p><p>There is a sudden growth in mobile wallet user in last year. The amount has increased close to 207% and it’s still growing. After the announcement is demonetization there is strong growth in the m-wallet payment. Let’s check M-wallet user adoption through a bell curve diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*xSbtRTwKN1C6qWSqKIbMJg.png" /><figcaption>Source: realcomm.com</figcaption></figure><p>The entire user cycle is divided into 5 main parts. Namely Innovators, Early Adopters, Early Majority, Late Majority, Laggards.</p><p><strong>I</strong>nnovators are those M-Wallet users who can be safely assumed to be using the digital payment platform since its inception. They are the tech savvy younger generation and mostly fall under the 18–30 Age group. They form only <strong>2.5%</strong> of the market but influence a larger section of buyer segment to use the product. Ideally, they spend almost all their money through digital payments, for example : <strong>Uber Money</strong> for Cabs, <strong>Paytm </strong>for Grocery, <strong>Net Banking</strong> for fund transfer, <strong>Debit card</strong> for Amazon orders, <strong>Credit card</strong> for iPhone EMI and the list goes on. The ideal innovator can live their life without cash, such is his desire for technology and digitization. They are ready to grab on to any future M-Wallet product too.</p><p><strong>E</strong>arly Adopters are probably the most important users for M-Wallet in India because they can become the product <strong>evangelists</strong>. These are people who are highly influenced with the innovators and seek motivation to use the product. In the Indian M-Wallet scenario, most early adopters lie in the 18–35 Age group and live in metro and some tier-1 cities. They are working professionals, students, businessmen and technology friendly folks who are aware of the benefits of digitization. They adopted to use the M-wallets once companies like <strong>Paytm</strong>, <strong>Freecharge </strong>and <strong>Mobikwik </strong>began to be popular in media, news, advertisements and peer users. The early adopters generally comprise <strong>13.5%</strong> of the total users.</p><p><strong>E</strong>arly Majority is a set of users who usually take some motivation from the early adopters and are somewhat late (but still in time before the product becomes outdated) to adopt a product. Now here comes a good and a bad news for M-Wallets in India. The good news is, early majority is about <strong>34%</strong> of the total users. The bad one is, M-Wallets have not really been able to get much hold of this segment. These users check various technical forums, talk to the earlier two categories, seek a lot of feedback and do a lot of research before adopting a product. When a product sales hit a wall between early adopters and early majority, this situation is called chasm as you can see in on the curve. For a product to become successful, it’s crucial to jump out of the chasm and get a hold of the early majority. M-Wallets though have users from this category but the numbers are not enough to make the jump yet. Although the Demonetization push by the Government of India might give the necessary push needed for M-Wallets to jump out of the chasm.</p><p><strong>L</strong>ate Majority is a set of users who are skeptical about the usefulness, quality, value and ROI of the product. It won’t be completely wrong to say that they are skeptical of everything about the product. But they eventually adopt the product at a later stage, once they have proven feedback of product success. Usually by this time the innovators and early adopters have moved to the newer versions. From the graphical data presented in the article, it is obvious that the majority still wants to hold the cash. With a mere<strong> 22%</strong> of transactions being cashless (which include plastic cards and other digital modes also) Late majority is definitely not the place where M-Wallets exist today and they comprise <strong>34%</strong> of the users.</p><p><strong>L</strong>aggards have a habit of building a wall between them and technology. They are extremely averse to change. They are typically older than the other users too and take a lot of time to analyze if they even need the product. They are the kind of users who might visit a mobile recharge shop and buy a paper voucher (if it was still available). They are also extremely cautious about spending a penny extra, especially on technology products. They wait for deals like “50% + 75 % OFF” or “Clearance Sale”. They are definitely not the user base for M-Wallets in India today and comprise <strong>16%</strong>of the users (Fortunately).</p><p><strong>Where does Mobile wallet lie in product adoption curve?</strong></p><p>· As of 2017 the mobile wallet sector can be placed into an Early Adapters Stage in product life cycle.</p><p>· If we consider the market size for mobile wallets to be all the users in India who have a mobile and a bank account it recently crossed 978 million users, adoption for mobile wallet by taking popular mobile wallet apps into reference is about 200 million users which would be about 19% of the market size.</p><p>· Although it’s a huge rise but we also need to study the factors that have caused a surge in wallet user, most significantly the demonetization that happened in India in Nov 2016. It is a major factor for mobile wallet adoption and we need to analyze how it impacts in the long run.</p><p>· Factors and challenges which affected rate of mobile wallet adoption.</p><p><strong>Awareness: Not many people in India are comfortable using Internet.</strong></p><ul><li>Less usage in rural area (Technology) — Users in Tier 3 and rural areas are still not familiar with smartphones and for many functioning a feature phone is quite a task. Add to that the promotion/discount coupons to be used for availing cash backs and suddenly this seems way out of the comfort zone for many users. The over-all penetration of smartphone is about twenty million users in India. Though a big number the actual number of smartphones in Tier 3 and villages is far less and can be pegged currently at 5 crore.</li><li>No alternative of cash — It seems that the real challenge in Tier 2/3 cities may be the older habit of using cash for account receivables and payable. An estimated 12–13% of GDP of India deals in cash based transactions. A user simply cannot make a cashless transaction if she keeps getting paid in cash. The extra run to the bank to deposit money is currently not an option for many and they continue to pay in cash.</li><li>Internet service are not great (Technology) — This is a prominent concern for a rapid adoption of wallets in Tier 3 cities and rural areas. Some of the wallets, like Mobikwik, are moving towards SMS as an option but this may defeat the purpose by making it even more cumbersome than paying through cash.</li><li>Maturity of the market (Economic) — Most of the wallets today have expanded their base by offering heavy discounts to the user. Paytm, for example, is yet to turn black and show real profits to its investors. This constant drain on the wallets can lead to some of these going out of business and adds to the general anxiety of the consumers when it comes to committing for a long-term relationship. The market is not matured enough to start giving returns to the mobile wallet companies. <br>Too many options (Buyer power) — This is still an area where the users tend to use the wallet on a hot deal and then disappear from the radar. The wallet ecosystem as a whole is growing but loyalty to individual wallets is still low.<br>According to a study, only 30% of users were actively using a wallet post the first deal after a period of 3 months. The most popular mobile payment apps in terms of time spent are those that provide services over and above pure payment like mobile recharging, ability to book movie tickets, shopping etc.</li><li>Fraud cases: Urban cities are seeing many fraud cases and due to that the confidence is low for the customers. There are many users though they have heavy usage of mobile phones and internet, they are still not too comfortable using online / mobile payment method.</li></ul><p><strong>Comparison with other payment methods:</strong><br>At present available cashless payment systems include credit/debit cards, e-wallets such as Paytm, Unified Payment Interface (UPI), IMPS, USSD, RTGS, and NEFT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*pBJeBn9jlWseXQgLQ2_yIQ.png" /></figure><p>The detail comparison of different payment options are listed below.</p><ol><li>Time taken to complete a transfer/payment; <br>2. The maximum amount you can transfer; <br>3. The financial details/information (e.g. account number etc) that you need to complete the transfer; <br>4. How is the transaction validated/authenticated; <br>5. Whether you will earn interest on the money kept in reserve in the payment system? <br>6. Whether you need to specify who the money is being transferred to in advance i.e. register the beneficiary (recipient) of the<br>7. What infrastructure/technical support is a must for the transfer to happen <br>8. And lastly, what are the costs involved There is no single ‘best’ payment option for everyone and all transactions. However, you could try to pick a payment option suitable for your purpose.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*soZje7hiqaCFjFbBsaOrWw.png" /></figure><p><strong>Cheap Smart Phones and the Internet</strong></p><p>With the availability of low-cost internet and inexpensive handsets, mobile internet is easily accessible to the middle class segment that contributes to major part of the Indian population. Thus, the usage of mobile wallets has started to become more popular among Indian people.</p><p><strong>Security </strong><br> Most of the people do not like to carry the huge sum of money with cash due to fear of theft. For such masses, the mobile wallets are a real advantage. Mobile wallets provide a hassle-free and secure method to carry and transfer the huge amount of money from one person to another. It also reduces the fear of taking credit cards for all transactions and hides the sensitive bank data from being exposed the merchant’s site or establishment; further leading to the reduced probability of unwanted financial happenings.</p><p><strong>Government Policies</strong><br> The Indian government has also introduced multiple schemes to encourage the use of cashless payment in India. The introduction of cashless transactions from railways to Highway tolls and launching apps such as BHIM and UPI, the government is working aggressively towards the goal of cashless economy. The RBI has approved ‘payments bank’ license for many Mobile Wallets including Paytm and has also raised the usage limit to Rs 20,000 for accounts without KYC and Rs 1,00,000 for accounts with KYC</p><p><strong>Attractive offers </strong><br> Many attractive offers have also been introduced by both governments as well as mobile wallets company to lure more and more customers. From discounts at petrol pumps by the government to attractive cash back offers by mobile wallets companies, mobile wallets users are getting decent offers on most of the mobile payments.</p><p><strong>Demonetization<br></strong>The sudden demonetization of 1000 and 500 currency notes by Indian Government has made a huge shortage of paper currency in the country for a while. Thus many people and merchants switched to mobile wallets and other cashless transaction methods for everyday transactions. As per the live mint report on the after effects of demonetization on PayTM, India’s largest mobile wallet company: <br> Paytm has touched a record five million transactions a day (on Friday and Saturday, each) and is on the way to process over Rs24,000 crore (by March 2017), more than any other payment network in the country,” <br> “Since 9 November, the company claims to have registered a 700% increase in overall traffic on the platform and 1000% growth in the value of money added to Paytm accounts. In addition, the average transaction value has increased by 200% and the number of mobile app downloads by 300%.”</p><p><strong>Summary:</strong><br>Due to demonetization, government promotion for the digital India, it’s certain that the digital payment will be a big boom in India However, the government needs stronger policies to promote digital India, to secure digital payment and also a strong plan for it’s growth is very much necessary.</p><p>Ref Site: <a href="http://economictimes.indiatimes.com/wealth/invest/post-demonetisation-which-digital-payment-method-to-use-heres-how-to-choose/articleshow/56173994.cms">http://economictimes.indiatimes.com/wealth/invest/post-demonetisation-which-digital-payment-method-to-use-heres-how-to-choose/articleshow/56173994.cms</a></p><p><a href="https://www.quora.com/What-are-the-total-no-of-mobile-wallet-users-in-India">https://www.quora.com/What-are-the-total-no-of-mobile-wallet-users-in-India</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=671a04267bf7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>