<?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 CFB Bots on Medium]]></title>
        <description><![CDATA[Stories by CFB Bots on Medium]]></description>
        <link>https://medium.com/@cfb-bots?source=rss-a68344d749f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9xyKpTiZ4rilZxDQfSICeg.png</url>
            <title>Stories by CFB Bots on Medium</title>
            <link>https://medium.com/@cfb-bots?source=rss-a68344d749f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:58:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cfb-bots/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[What Businesses Need To Know About UiPath Community Edition (Hint: It’s Not Free)]]></title>
            <link>https://cfb-bots.medium.com/what-businesses-need-to-know-about-uipath-community-edition-hint-its-not-free-0fff5a4e8123?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fff5a4e8123</guid>
            <category><![CDATA[uipath-community-edition]]></category>
            <category><![CDATA[uipath]]></category>
            <category><![CDATA[power-automate]]></category>
            <category><![CDATA[rap]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Sat, 22 Nov 2025 05:19:38 GMT</pubDate>
            <atom:updated>2025-11-22T05:19:38.444Z</atom:updated>
            <content:encoded><![CDATA[<p>Many organizations start their automation journey with the <a href="https://www.uipath.com/product/automation-cloud"><strong>UiPath Automation Cloud for Community</strong></a> (more commonly known as <strong>UiPath Community Edition)</strong> because it’s <em>free</em>, easy to get started, and great for learning. But as your business grows, continuing to rely on the UiPath Community Edition can put you at risk, especially if you are running these RPA bots for commercial purposes.</p><p>In this post, we break down <strong>who can legally use UiPath Community Edition</strong>, why many businesses unknowingly fall out of compliance, and how you can migrate safely to either UiPath’s commercial plans or a more cost-effective platform like <a href="https://www.microsoft.com/en-us/power-platform/products/power-automate"><strong>Microsoft Power Automate</strong></a>.</p><h3>What UiPath Community Edition Is Actually Intended For</h3><p>Traditionally, the UiPath Community Edition has been primarily intended for <strong>individual developers, small businesses, and learning purposes</strong>. For a business to qualify as a <strong>Small-to-Medium Business (SMB)</strong> and use the UiPath Community Edition for direct business purposes, it must, together with its Affiliates, collectively have:</p><ol><li>Less than 250 machines (physical or virtual) or users, AND</li><li>Less than USD 5 million in annual revenues.</li></ol><p>Organizations exceeding these limitations are considered <strong>Large Businesses</strong> and may only use the Community Edition for evaluation and non-profit purposes (such as education, hackathons, individual or institutional research, and internal trainings.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*aqf480gRqoLaL_Hn.jpg" /><figcaption>Reply from AI search agent on UiPath website</figcaption></figure><p>However, do note that there has been a subtle shift in this stance. The latest UiPath <a href="https://www.uipath.com/assets/downloads/community-agreement">Community Agreement</a> now states that Community Edition can be used <strong>“solely for non-commercial purposes, such as education and individual or institutional research.” </strong>Refer to clause 3.1 for more details.</p><p>This is also clearly stated on the <a href="https://account.uipath.com/login"><strong>sign-up page</strong></a> for the UiPath Automation Cloud for Community:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*rRVWb5B6FebsRjY6.jpg" /><figcaption>Sign-up page for UiPath Automation Cloud for Community</figcaption></figure><p>In summary, this means:</p><ul><li>You can’t rely on UiPath Community Edition to run automations in production environment that generate revenue or support your business operations, regardless of the size of your business.</li><li>Using UiPath Community Edition as a “free enterprise license” for your organization is not aligned with the agreement.</li><li>UiPath reserves the right to change terms, monitor usage and enforce compliance.</li></ul><p>Important: The above is a practical explanation for business and IT users and not legal advice. For a definitive interpretation, always consult your legal team and the official UiPath Community Agreement.</p><h3>The Risks of Non-Compliance With the UiPath Community Agreement</h3><p>Many companies, including their employees, are unaware of the limitations and restrictions on the usage of the UiPath Community Edition. However, ignorance is not an excuse and continuing to use the software for commercial purposes creates several risks:</p><h3>1. License Non-Compliance</h3><p>You may be operating outside the terms of the UiPath Community Agreement. This becomes a major issue during <strong>vendor audits and compliance reviews</strong>. In certain instances, there may be pressure to regularize licenses quickly, often under tight timelines and unfavorable terms.</p><h3>2. No Enterprise Support</h3><p>Community users receive <strong>no guaranteed support or Service Level Agreements (SLAs)</strong>. If your production robot fails, there’s no formal escalation path. In addition, the UiPath Community Edition comes with certain restrictions in software capabilities which may limit what you can accomplish with UiPath’s agentic automation platform.</p><h3>3. Operational Instability</h3><p>Free tiers can change without notice. For example, are you aware that clause 3.1 states that “<strong>UiPath reserves the right to delete all Customer Data in the Software if the Customer fails to use that Software for more than 90 (ninety) consecutive calendar days</strong>”? Relying on the UiPath Community Edition for mission-critical work therefore presents a long-term risk to your business continuity.</p><h3>4. Strategic Lock-In</h3><p>Bear in mind that most RPA software (including UiPath) are proprietary in nature, meaning it is difficult to convert to another RPA platform. If you have established a significant automation program, you might find that your options for migrating out of UiPath Community Edition are costly, complex, and/or highly disruptive.</p><p>In other words, if you are a business, you definitely need to consider transitioning away from UiPath Community Edition into something more compliant and sustainable.</p><h3>Your Migration Options</h3><p>Start by conducting an internal audit to understand your UiPath setup, existing UiPath subscriptions (if any), current workloads and future plans. Then, consider the following options:</p><h3>Option 1: Upgrade to UiPath commercial plans</h3><p>For organizations committed to UiPath:</p><ul><li>Select the right mix of licenses across the <strong>platform, users, robots and consumption SKUs</strong> based on your requirements and use cases.</li><li>Design a <strong>target architecture</strong> that meets your enterprise needs including deployment options (on-premise or cloud), high availability, disaster recovery, etc.</li><li>Plan a structured migration from Community tenants, users, and robots to enterprise environments</li><li>Implement best practices for folder and tenant design, governance and change management, monitoring, logging and support, etc</li></ul><h3>Option 2: Migrate to Microsoft Power Automate</h3><p>If you want a <strong>more cost-effective, yet trusted</strong> RPA platform, Microsoft Power Automate is often the best choice. For example, for one of our clients, migrating from UiPath to Microsoft Power Automate <a href="https://www.cfb-bots.com/case-study-uipath-to-power-automate-migration"><strong>reduced subscription fees by a staggering 8.9x</strong></a> alone.</p><p>In this case, you would need to analyze your existing UiPath workflows before coming up with a suitable migration strategy. For example, identify quick wins — processes that can be easily converted to Power Automate cloud or desktop flows. Or to introduce AI-powered automation with AI Builder and Azure OpenAI at a later stage when the core RPA processes have been migrated successfully.</p><h3>Option 3: Hybrid UiPath + Power Automate</h3><p>Many organizations benefit from a <strong>hybrid model</strong>:</p><ul><li>Keep UiPath where deep RPA or legacy integration is critical</li><li>Use Power Automate for high-volume SaaS, Microsoft 365 and workflow automation</li><li>Define clear <strong>ownership, guardrails and integration points</strong> between both platforms</li></ul><p>Generally though, if you are a SMB, our recommendation is to stick with one platform. Most SMBs simply do not have the time, resources, and capability to support multiple RPA platforms.</p><h3>Final Thoughts</h3><p>UiPath Community Edition is fantastic for learning, experimenting and building proofs of concept. But relying on it for production automation becomes both risky and non-compliant.</p><p>Migrating early — whether to UiPath’s commercial plans or Microsoft Power Automate — ensures stability, support, and scalability for years to come. If you’re unsure whether your current UiPath usage is compliant or want to explore your options, we’re here to help.</p><p><a href="https://www.cfb-bots.com/book-your-free-consultation">Contact CFB Bots for a free consultation and migration assessment.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fff5a4e8123" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to migrate from UiPath to Power Automate?]]></title>
            <link>https://cfb-bots.medium.com/how-to-migrate-from-uipath-to-power-automate-2cb5f9a32c8e?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cb5f9a32c8e</guid>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[uipath]]></category>
            <category><![CDATA[power-automate]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[rpa-tools]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 02:02:58 GMT</pubDate>
            <atom:updated>2025-09-18T02:02:58.803Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Key Considerations for a Successful Transition or Conversion</strong></p><p>Migrating your RPA workloads from UiPath to Microsoft Power Automate Desktop (PAD) can be a strategic move — whether you’re optimizing licensing costs, consolidating RPA platforms, preventing vendor lock-in, or leveraging Microsoft ecosystem benefits. Unfortunately, this transition is more complex than a simple lift-and-shift. Ultimately, each RPA software is proprietary and not designed with compatibility and interoperability in mind. To ensure a smooth and successful migration, it’s critical to perform a thorough pre-migration audit and develop a well-structured plan.</p><p>In this article, we’ll walk you through key considerations and potential pitfalls when preparing to migrate from UiPath to PAD. From identifying non-transferable components to mapping complex workflows and business logic, we’ll highlight what to look out for during the planning phase — so you can avoid disruptions and maximize ROI from your automation investments.</p><p>Before we dive in, here are a few quick points to highlight:</p><ul><li>This analysis is performed using UiPath Studio version 2024.10.14 LTS and Microsoft Power Automate Desktop version 2.55.158.25087. As the capabilities of the RPA platforms are continually evolving, it is important to check the official documents of both <a href="https://docs.uipath.com/">UiPath</a> and <a href="https://learn.microsoft.com/en-us/power-automate/">Microsoft</a> on the latest features and functionalities.</li><li>In addition, we are mainly focused on automation created with UiPath Studio, not UiPath StudioX or UiPath Studio Web. Similarly, for Microsoft, we are interested in desktop flows created using Microsoft Power Automate for desktop and not cloud flows via <a href="https://make.powerautomate.com/">https://make.powerautomate.com/</a></li><li>For PAD, we will exclude premium activities which require a paid subscription plan (Power Automate Premium).</li></ul><p>Our analysis will be broken down into the following key topics:</p><p><strong>Variables and Data Types</strong></p><ul><li>Variable Scope — Local vs. Global</li><li>Missing Data Types</li><li>String Typing vs. Implied Typing</li></ul><p><strong>Control Flow</strong></p><ul><li>Flowcharts and State Machines</li><li>Sequences</li><li>Parallel</li><li>Trigger Scope</li></ul><p><strong>Activity-to-Action Mapping</strong></p><ul><li>Premium-Only Actions</li><li>Imperfect Mapping</li><li>1-to-Many Mapping</li><li>Missing Functionalities</li></ul><p><strong>Selectors</strong></p><ul><li>Selectors vs. UI Elements</li></ul><p><strong>Exception Handling</strong></p><ul><li>Try Catch vs. On Block Error</li><li>Throw and Rethrow</li><li>Global Exception Handler</li><li>Error Message</li></ul><p>Specifically, we will highlight the key differences between both platforms that you need to be cognizant of. Where possible, we will provide concrete examples to illustrate the point as well as potential remedies. With that in mind, let’s get started.</p><h3>Variables and Data Types</h3><h4>Variable Scope — Local vs. Global</h4><p>UiPath allows you to define the scope of each variable, e.g. you can restrict the usage of a variable to a particular sequence or workflow, in effect creating local variables. For example, it is perfectly valid to create 2 different variables of the same name but with different scope (and possibly data type). In PAD, there is no such concept of scoped variables. Essentially, all variables are global and can be accessed from anywhere within the same desktop flow, even across different sub flows.</p><p><strong>AI Insights: Variable scope differences require deliberate handling as there is a high risk of naming conflicts, especially when migrating from workflows that reuse variable names locally. Failure to do so may inadvertently break the business logic and result in unintended data overwrites.</strong></p><h4>Missing Data Types</h4><p>UiPath supports a multitude of data types, including complex .NET types and custom classes. In PAD, the supported data types are much more limited, namely text, numeric, boolean, list, datatable, datarow, custom object, and connector object. Issues will arise, for example, when SecureString variables are created to handle passwords in UiPath because there are no such equivalents in PAD. Worse still, using the implicit data type in PAD (i.e. text) is not a good security practice.</p><p><strong>AI Insights: Prior to any migration, it is vital to identify all variables whose data types cannot be mapped exactly and to identify the most appropriate equivalents.</strong></p><h4>Strong Typing vs. Implicit Typing</h4><p>A common frustration among UiPath developers transitioning to PAD is the lack of explicit typing. In UiPath, developers can define variable types directly. In contrast, PAD infers variable types from the context or the output of an action — there is no way to arbitrarily declare a type. For instance, you cannot create a boolean variable unless you assign it a true or false value, and all user inputs are treated as text by default. This implicit typing can complicate certain operations — such as using booleans or integers in expressions — because you must ensure the variable was previously set with the correct type.</p><p><strong>AI Insights: Implicit typing in PAD requires careful sequencing of actions to ensure that all variables are initialized with the correct type before use.</strong></p><h3>Control Flow</h3><h4>Flowcharts and State Machines</h4><p>UiPath supports the creation of complex workflows using a mixture of sequences, workflows and state machines. Indeed, the popular and commonly adopted Robotic Enterprise Framework (REFramework) incorporates all 3 control flow elements in its design. On the other hand, PAD flows are primarily linear sequences with no direct equivalents for workflows and state machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/0*1Nd8GjNV1RCL8iDZ.png" /><figcaption>UiPath REFramework</figcaption></figure><p><strong>AI Insights: Since many UiPath projects today utilize the REFramework, it is helpful to have an equivalent framework in PAD such as the Power Automate Framework to standardize and streamline the conversion process.</strong></p><h4>Sequences</h4><p>In UiPath, sequences are a fundamental building block used to logically organize related activities within a workflow. Although PAD provides a similar concept through the “Region” and “End region” actions, their usage often results in visually cluttered and harder-to-maintain desktop flows. As such, each migration requires thoughtful consideration — not all sequences should be mapped one-to-one. Instead, it’s critical to evaluate the intent behind each sequence and determine the best possible action (pardon the pun). For instance, if a sequence merely wraps all the activities within the Then branch of an If condition, replicating it as a region may add unnecessary complexity.</p><p><strong>AI Insight: Not all UiPath sequences should be mapped directly — effective migration to PAD requires rethinking structure to avoid clutter and preserve workflow clarity.</strong></p><h4>Parallel</h4><p>The “Parallel” activity in UiPath enables true concurrent execution of multiple branches, either until all complete or a defined condition is met — making it ideal for handling asynchronous logic and event-driven workflows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*i1ARpeIYjPcPCzPh.png" /><figcaption>Source: UiPath Community Forum</figcaption></figure><p>In contrast, PAD offers only a limited form of parallelism: it allows a child desktop flow to run alongside its parent. However, this feature is constrained — only one parallel instance can run at a time, and child flows are not permitted to spawn additional parallel flows. These limitations make PAD unsuitable for replicating complex parallel logic as implemented in UiPath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/0*GQ0zb3BuDdHjIv-u.png" /><figcaption>Source: Microsoft Learn</figcaption></figure><p><strong>AI Insight: Workflows leveraging parallel activities in UiPath often require fundamental redesign in PAD, as its support for concurrency is highly limited and restrictive.</strong></p><h4>Trigger Scope</h4><p>The activity “Trigger Scope” in UiPath provides powerful event-driven automation by allowing the robot to listen for various system events such as file changes, hotkeys, mouse actions, and more. When any of these triggers occur, UiPath can immediately execute a predefined sequence in response. This enables the development of highly responsive and dynamic workflows. In contrast, Power Automate Desktop (PAD) lacks native support for real-time event monitoring. It cannot independently listen for system-level triggers or initiate flows based on asynchronous events.</p><p><strong>AI Insights: Should triggers be necessary, a cloud flow with the required triggers must first be created, followed by invoking the desktop flow to achieve similar event-driven behaviour. Note that this use case would require a paid Power Automate subscription plan.</strong></p><h3>Activity-to-Action Mapping</h3><p>Many standard UiPath activities lack a direct counterpart in PAD, forcing developers to either redesign the process logic or implement workarounds — such as combining multiple actions, embedding scripts, or building reusable subflows. These approaches can lead to significantly more complex and harder-to-maintain desktop flows.</p><h4>Premium-Only Actions</h4><p>For example, consider the UiPath activity “Log Message”. While PAD offers a similarly named “Log message” action, it is a premium-only feature, available only with a paid subscription.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/0*qqeocagLN-rPPwpU.png" /><figcaption>UiPath “Log Message” activity</figcaption></figure><p>For users on the free plan, an alternative is to implement a reusable subflow that can replicate this activity. However, the downside is that the overall script becomes much more complex and verbose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*GbCkpGYlAbUs2s3l.png" /><figcaption>Reusable subflow “Write_To_Log”</figcaption></figure><h4>Imperfect Mapping</h4><p>Even when this feature is accessible, the mapping is imperfect. Specifically, in UiPath’s “Log Message” activity, there are a total of 5 log levels–Trace, Info, Warn, Error, and Fatal. Whereas in PAD, the “Log message” action only has 3 log levels–Info, Warning, and Error. Consequently, this discrepancy forces developers to manually remap or consolidate log levels, often reducing the granularity and effectiveness of logging, and making debugging more difficult post-migration.</p><p>Let’s consider another common automation scenario–reading data from an Excel file. In UiPath, this would involve just 2 activities–”Use Excel File” and “Read Range”. The former allows us to specify the Excel file that we want to read while the latter reads all the data in a named worksheet into a data table variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/0*uU2K47T6GIsQtLbD.png" /><figcaption>Using UiPath to read data from Excel</figcaption></figure><h4>1-to-Many Mapping</h4><p>In PAD, you would need 3 actions–”Launch Excel”, “Read from Excel Worksheet” and “Close Excel”. The first 2 actions are similar to the aforementioned UiPath activities, but you need an additional 3rd action to explicitly close the Excel file. Needless to say, closing any file or application after use is a best practice that all RPA developers should observe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*n6qTuKmNX2Fy6cUL.png" /><figcaption>Using PAD to read data from Excel</figcaption></figure><p>To take this discussion further, one common activity that needs to be performed after reading the Excel data is to filter the data table to remove the empty rows. UiPath offers multiple ways to do this: from a straightforward “Filter Data Table” activity to more advanced options using LINQ expressions embedded in other activities like “Assign”. In PAD, the typical approach involves using the “Delete empty rows from data table” action. While this seems more streamlined, it also means that business logic in UiPath may be hidden within expressions, making such logic harder to detect and translate accurately during migration.</p><h4>Missing Functionalities</h4><p>Finally, there are entire categories of functionality in UiPath that are simply absent in PAD. For instance, UiPath provides dedicated activities for Excel pivot table operations such as “Create Pivot Table” and “Refresh Pivot Table”. PAD offers no equivalent. To replicate this, developers must fall back on custom VBScript or brittle UI automation, both of which introduce maintenance and compatibility risks. Ironically, given that PAD is part of the Microsoft ecosystem, one might expect stronger Excel integration — but in practice, UiPath still provides the more robust feature set.</p><p><strong>AI Insights: Functional gaps between UiPath and PAD are significant and non-trivial. Effective migration requires rethinking process logic, addressing platform limitations, and often redesigning workflows to achieve equivalent automation outcomes.</strong></p><h3>Selectors</h3><h4>Selectors vs. UI Elements</h4><p>Selectors in UiPath are represented as XML-like fragments. Each selector is essentially a hierarchy of UI elements (from root window to target element) described by tags and attributes in an XML structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/0*fpnD-qM9wz4OPR8B.png" /><figcaption>Selector of Notepad’s Open menu item in UiPath</figcaption></figure><p>In PAD, selectors, which are actually known as UI elements, use an attribute-value notation with a hierarchical “&gt;” syntax instead of XML. They appear similar to CSS or jQuery selectors. Each level of the UI hierarchy is represented as “element[Attribute=”Value”]” chained by “&gt;” symbols. This notation lists the desktop or app window and then the child element with identifying attributes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/0*smI5G5-VaRtJhzr_.png" /><figcaption>UI element of Notepad’s Open menu item in PAD</figcaption></figure><p>Both platforms ultimately rely on UI accessibility frameworks (Microsoft UI Automation or Active Accessibility) to obtain these element attributes.</p><p>Key differences between UiPath’s selectors and PAD’s UI elements:</p><ul><li><strong>Fuzzy Search</strong>: UiPath selector’s fuzzy search capabilities enable you to locate strings based on a pattern, rather than on an exact match. There is no such feature in PAD.</li><li><strong>Anchor-based Search</strong>: In UiPath, you can search for a UI element by using other UI elements as anchors. This is often used when a reliable selector is not available. Likewise, there is no such functionality in PAD.</li><li><strong>Full vs. Partial Selectors</strong>: Selectors in UiPath can be full or partial. Full selectors contain all the elements needed to identify an UI element, including the top-level window. Partial selectors, on the other hand, do not contain information about the top-level window. There is no such differentiation for UI elements in PAD.</li><li><strong>Application/Browser Automation Scope</strong>: In UiPath, you need to use the “Use Application/Browser” activity first before you can implement any UI automation activities. There are no such requirements in PAD; however, for browser automation, you would implicitly need to have a web browser instance opened (e.g. via the “Launch new Chrome” action).</li></ul><p>The above is just a simplified discussion of the differences between UiPath’s selectors and PAD’s UI elements. Drop us a comment below if you would like us to delve further into this topic in a subsequent post.</p><h3>Exception Handling</h3><p>Robust error handling is vital in RPA. The approach in UiPath and PAD is somewhat different.</p><h4>Try Catch vs. On Block Error</h4><p>UiPath provides a “Try Catch” activity where you can try specific exception types under “Catches” and define the “Finally” block. The equivalent in PAD is the “On block error” action, but there are a very notable differences:</p><ul><li>PAD’s “On error block” does not differentiate exception types — it catches any error in that scope. You cannot have multiple catch branches for different exception types like in UiPath. All errors trigger the same error handler block. If this functionality is critical to your workflow, one workaround is to call a subflow in the error handler and let the subflow handle the various exception types.</li><li>As PAD lacks a “Finally” construct, workarounds are needed, e.g. putting cleanup steps both after a normal sequence and inside the error handler to ensure execution in all cases.</li><li>Interestingly, PAD includes built-in error handling for certain actions through the “On error” property, allowing developers to define exception handling at the individual action level. This level of granular control is not available in UiPath.</li></ul><p><strong>AI Insights: Exception handling is more limited in PAD as compared to UiPath — though it compensates somewhat with per-action error handling not found in UiPath.</strong></p><h4>Throw and Rethrow</h4><p>Additionally, UiPath provides “Throw” and “Rethrow” activities to raise exceptions and propagate caught errors, respectively. Since PAD lacks an equivalent throw action, developers must deliberately trigger a failed action to simulate an error — an awkward and inelegant workaround. Ditto for rethrow. The same applies to rethrowing errors, which involves a more convoluted approach, such as setting a variable and checking it after the error-handling scope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/0*MlD8epxi_GI5TJH3.png" /><figcaption>“Throwing” an error in PAD</figcaption></figure><p><strong>AI Insights: PAD lacks the capability to raise and propagate exceptions like in UiPath. If this functionality is critical to the business process, workarounds will be required.</strong></p><h4>Global Exception Handler</h4><p>UiPath offers a Global Exception Handler mechanism — a workflow that automatically intercepts any uncaught exception at the project level. PAD has no global exception handler for desktop flows, so such logic will need to be replicated using a combination of “On error block” and subflows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/0*FYBwn8u882-sMZ0v.png" /><figcaption>Global Exception Handler in UiPath</figcaption></figure><p><strong>AI Insights: PAD lacks the Global Exception Handler that is available in UiPath. If this functionality is critical to the business process, workarounds will be required.</strong></p><h4>Error Message</h4><p>In UiPath, errors are typically thrown as .NET Exception objects, which can be caught and inspected for details such as .Message, .Source and .StackTrace. In contrast, PAD does not provide a rich exception object. You will need to use the “Get last error” action to return an error type variable that provides six different properties: the name, the location and the index of the action that failed, the subflow that contains this action, and the details and the message of the action.</p><p><strong>AI Insights: Unlike UiPath, which uses detailed .NET exceptions, PAD handles errors using an error object retrieved via the “Get last error” action which provides only six key properties.</strong></p><h3>Conclusion</h3><p>Migrating from UiPath to Power Automate Desktop is a technically demanding process that requires more than a simple activity-to-action translation. Differences in how the platforms handle variables, control flow, UI interaction, and exception management mean that a successful migration often involves rethinking and redesigning workflows.</p><p>While PAD offers a compelling option — especially for organizations interested in a cost-effective software — it lacks several advanced features found in UiPath. As such, identifying non-transferable components, anticipating functional gaps, and preparing viable workarounds are essential to ensure a seamless transition without compromising automation integrity or business logic.</p><p>Note: To learn more, please visit <a href="https://www.cfb-bots.com/uipath-migration-services">UiPath Migration</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cb5f9a32c8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to think about AI]]></title>
            <link>https://cfb-bots.medium.com/how-to-think-about-ai-f0e421fe0d32?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0e421fe0d32</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Mon, 12 May 2025 04:02:27 GMT</pubDate>
            <atom:updated>2026-02-19T13:21:21.378Z</atom:updated>
            <content:encoded><![CDATA[<p>How employees and companies can survive <em>and </em>thrive in the age of AI [Updated Feb 2026]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QxbLhkutpkkyoIlC" /><figcaption>Photo by <a href="https://unsplash.com/@neonbrand?utm_source=medium&amp;utm_medium=referral">Kenny Eliason</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><ul><li>AI is a generational shift — similar to computers, the internet and mobile — that is revolutionizing how work gets done. It is no longer a question of <em>if</em> or <em>when</em>.</li><li>No one knows exactly how this shift will play out. But waiting for clarity has a cost: you give up the first-mover advantage.</li><li>Tasks once simple for humans — like data entry — are now fully automated. Tasks once complex — such as coding — have been made easier with AI. And tasks once deemed impossible — for example, the one-person unicorn — have become the new reality, thanks to the trifecta of automation, AI, and human ingenuity.</li><li>Put differently, going from zero to one requires human ingenuity. But scaling from one to hundred requires both automation and AI. With AI, you no longer have to choose only two out of the following three: cheaper, faster, <em>and</em> better. It is possible to have your cake and eat it — but only if you try.</li><li>To be AI-first requires a fundamental rethink of how work gets done. For example, what would your company (or job) look like if it was started in 2025? Applying AI gloss or a band-aid over existing processes and workflows will not suffice.</li><li>In practice, this means delegating the heavy lifting to AI agents while you act as the conductor or orchestrator of work.</li><li>AI is not a perfect technology (yet) and can make mistakes. Notwithstanding this, to wait for the technology to mature will be a colossal mistake on our part. Despite the hype around AI, we are still likely to underestimate what AI can achieve in the (very) long run.</li><li>If you tried AI tools (especially older or free versions) and weren’t impressed, don’t assume that was the ceiling. The gap between perception and reality can become a competitive gap.</li><li>To paraphrase Bill Gates, we often overestimate what AI can achieve in one year and underestimate what it can accomplish in ten. While today’s AI is impressive, it still has its limitations — for instance, you can’t yet design and manufacture an entire car using AI alone. The key is to view AI as a journey of small, incremental wins that build on each other. Start small: skateboard, then scooter, bicycle, motorcycle, and eventually a car. Each step builds momentum, and over time, the compounding effects of AI will truly amaze you.</li><li>There is a right and wrong way to use AI today. The wrong way to use AI is to simply control-C/control-V the outputs of AI without applying critical thinking or adding any differentiated value (for example, our uniquely human experience) to it. After all, AI is highly democratized with almost universal access. Mindless copy-and-paste will only get you so far.</li><li>As with any new trends, there will be winners and losers. It is virtually guaranteed that AI will result in at least some job losses. Heck, AI is an existential threat not just to employees, but to companies — and even entire industries. This is no time to bury our heads in the sand and pray that all will be good.</li><li>There is no AI-first company without AI-enabled employees. This means that AI proficiency needs to be part of the evaluation for both new <em>and</em> existing hires.</li><li>For employees, deep expertise still matters — but it won’t be enough on its own. Demand is rising for people who can combine domains, work cross-functionally, and operate in new AI-enabled modalities. In other words, be curious.</li><li>An AI mindset is a lean mindset. Always ask yourself if today’s work can be accomplished by AI or automation instead of traditional manpower — such as employees, contractors and freelancers. In the AI age, Jeff Bezos’ two-pizza rule should be adjusted to one-pizza with a healthy sprinkling of GPUs instead.</li><li>While AI is eating the world, it’s important to remember that the value of AI is defined by the outcomes, not merely the outputs. Understand the distinction between the two: an AI-generated content is an output, but a viral post that brings visitors to your website is an outcome.</li><li>In other words: your judgment becomes your edge: choosing the right goals, defining what “good” looks like, and knowing when an answer is plausible but wrong.</li><li>Doing more — preferably 10x or more — with the same or less is the only way to really future-proof yourself. Note that <em>more</em> refers to both quantity <em>and</em> quality.</li><li>Now is a wonderful time to be a SMB. AI is a powerful force multiplier that can help David compete with Goliath. The only limits are the scale of your ambition and the clarity of your vision. Larger competitors, in contrast, will have their work cut out dealing with legacy issues.</li><li>But be patient and hold on to your conviction that AI is the right play, even if the people around you disagree.</li></ul><p>Some practical advice (regardless of where you are):</p><ul><li>Use AI every day, now.</li><li>Do not be penny-wise, pound-foolish. Invest in paid AI tools as long as you can justify the cost from the value you derive out of these tools. Heck, pay out of your own pocket if you have to. Your future self will thank you for it.</li><li>Trust, but verify. AI models are inherently probabilistic, not deterministic. Consequently, the higher the stakes, the more critical it is to review the results with a healthy dose of cynicism.</li><li>Learn to be a good manager of AI agents — start with effective prompting, then progress to multi-agent workflows, tool use, and evaluation loops.</li><li>Learning needs to be both self-directed and continuous. What was state-of-the-art six months ago is now merely table stakes. Similarly, the boundaries of the art of the possible are being redrawn weekly — if not daily.</li><li>Be prepared to get your hands dirty and apply what you learn. Learning about AI, while important, is merely a means to an end.</li><li>Learning from successful use cases is one of the simplest and least risky ways to get started.</li><li>Retain responsibility for any work outputs, even if they are entirely AI-generated. Taking ownership is the surest route to gain AI mastery.</li></ul><p>Note: Access the original blog post <a href="https://www.agenticworkforce.io/blog/ai-agents-1/how-to-think-about-ai-18">here</a>. It will be updated periodically to reflect our latest thinking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0e421fe0d32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wheels of Change]]></title>
            <link>https://cfb-bots.medium.com/wheels-of-change-eb39d15cf5e8?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb39d15cf5e8</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Thu, 11 May 2023 00:54:16 GMT</pubDate>
            <atom:updated>2023-05-11T00:54:16.608Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbjtKBzgr2pSEJxllH6kvQ.jpeg" /><figcaption>Wheels of Change</figcaption></figure><p>Change is always hard, until it becomes inevitable.</p><p>Then something magical happens. Everyone starts embracing it, often wondering why it took so long for change to happen in the first.</p><p>Take automobiles as an example.</p><p>Cars were invented and made widely available in the late 19th and early 20th century. With more than 100 years of hindsight, the utility and benefits of the motor car is indisputable.</p><p>But this was not always the case.</p><p>Do you know that in 1896, Washington DC banned these “horseless carriages” (as cars were commonly known then) on the grounds that they threatened the livelihoods of horses. The following was reported in the Washington Post:</p><blockquote><em>The commissioners of the District of Columbia are determined that the horse whose occupation has so largely been taken away by reason of the use of bicycles shall not further be displaced by horseless carriage.</em></blockquote><p>Talk about putting the horse before the carriage!</p><p>There is a palpable sense of automation anxiety arising out of a combination of fear of being displaced by technology, innate resistance to change, lingering suspicions over management agenda as well as lack of support for upskilling or reskilling.</p><p>And such anxieties are only exacerbated in the current economic malaise. According to an NBER report, recent recessions tended to be followed by jobless recoveries as the level of automation in enterprises rises.</p><p>And as Upton Sinclair so eloquently put it, “it is difficult to get a man to understand something, when his salary depends upon his not understanding it.”</p><p>Could we be seeing history repeat itself with the advent of automation and artificial intelligence? Only time will tell.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb39d15cf5e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Man Versus Machine]]></title>
            <link>https://cfb-bots.medium.com/man-versus-machine-52f4aac3783a?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/52f4aac3783a</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 08:16:06 GMT</pubDate>
            <atom:updated>2023-04-24T08:16:06.395Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GyNVAiHlYYoV0A6zU67E0A.jpeg" /></figure><p>John Henry is an American folk hero and a “steel-driving man”.</p><p>Back in the good old days, constructing a railroad tunnel is extremely laborious. To blast the rocks, men are required to first manually hammer a steel drill into the rock to make holes for the explosives.</p><p>According to urban legend, John Henry competed and won against a steam-powered rock drilling machine in a race for the ages. Besides being a model of physical strength and endurance, John Henry also came to symbolize the backlash against the mechanization of (erstwhile) human work.</p><p>Alas, it was but a pyrrhic victory. For John Henry was said to have succumbed to exhaustion of work shortly after.</p><p>Fast forward to today.</p><p>According to one survey, the average office worker spent more than 3 hours a day on manual, repetitive computer tasks that aren’t even part of their primary job. And 67% of employees struggle to leave office on time due to time spent on manual, repetitive digital administration tasks.</p><p>Case in point: the infamous “996” work culture in China’s tech industry where employees are expected to work from 9am to 9pm, 6 days a week.</p><p>The world needs less John Henrys, not more.</p><p>And if automation can help, why not?</p><blockquote><em>One machine can do the work of fifty ordinary men. No machine can do the work of one extraordinary man. — Elbert Hubbard</em></blockquote><p>The operative word here is “work”, or more precisely, the nature of work.</p><p>Work that is mundane and menial can and should be outsourced to machines and robots.</p><p>Not doing so will be nothing but a fool’s errand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f4aac3783a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 ways to boost the ROI of your RPA program]]></title>
            <link>https://cfb-bots.medium.com/8-ways-to-boost-the-roi-of-your-rpa-program-9260919d7ca5?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9260919d7ca5</guid>
            <category><![CDATA[total-cost-of-ownership]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[return-on-investment]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Thu, 23 Mar 2023 23:09:29 GMT</pubDate>
            <atom:updated>2023-03-23T23:09:29.005Z</atom:updated>
            <content:encoded><![CDATA[<p>Part 1 — How to slash your RPA subscription fees</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h2zl7Of0xFo41cKXn7cC4g.jpeg" /><figcaption>8 ways to boost the ROI of your RPA program</figcaption></figure><p>Are you frustrated that your RPA program is not providing the Return on Investment (ROI) promised by your vendor at the start of the program?</p><p>Or perhaps concerned about your skyrocketing Total Cost of Ownership (TCO), driven in part by your RPA software vendor intend on raising subscription pricing at will and prioritizing their profitability over your needs?</p><p>If the above describes your current predicament, read on to learn the 8 ways you can reduce the TCO and improve the ROI of your RPA program.</p><p>While RPA can help businesses generate value — both tangible and intangible — in the form of improved customer and employee experience, higher productivity, and more, this article focuses primarily on how you can slash the cost of your RPA program in today’s environment which is both inflationary and recessionary.</p><p>To begin with, let’s examine the 3 biggest cost components of any RPA program — <strong>Software, Services and Support</strong>:</p><ol><li>Software refers to the RPA software licensing costs. Generally speaking, most pricing models are based around annual subscriptions on a named user basis. Also, many RPA vendors now provide different products across the broader automation platform — including Process Mining, Machine Learning/Artificial Intelligence, Intelligent Document Processing, Low Code Application Platforms, Business Analytics and more — and these are typically licensed separately.</li><li>Services refers to the costs incurred in engaging the professional services of third party service providers to implement the RPA solutions. Generally speaking, such costs depends on the number of processes as well as the complexities of these processes. These services typically span the entire project lifecycle including discovery, design, development, testing and deployment.</li><li>Support refers to the costs of maintaining the deployed RPA solutions in production. RPA maintenance is not well understood and often ignored by companies at their own peril. Broken bots may occur due to a variety of reasons including changes to the UI/API of the underlying applications, changes to the data formats (both inputs and outputs) and changes to the business process itself.</li></ol><p>Without further ado, let’s dive into how you can reduce your RPA operating expenses across these 3 components.</p><h3>RPA SOFTWARE</h3><h3>1. Actively negotiate your subscription costs during new license purchases and renewals.</h3><p>The RPA software market is highly competitive with many vendors providing a largely undifferentiated, commoditized product. Often, by pushing the right buttons, these vendors would be amenable to providing discounts off published list prices. In addition, as you scale your RPA program and buy more licenses, request for additional volume discounts knowing that the majority of RPA implementations still do not go beyond 10 bots.</p><h3>2. Adopt a multi-vendor strategy.</h3><p>Avoid being at the mercy of your sole RPA software vendor and being subjected to frequent (should we say unwarranted) price uplifts by diversifying your RPA software. This will help keep your RPA software vendors on the straight and provide additional leverage during your price negotiations (see point 1).</p><h3>3. Manage your license utilization proactively.</h3><p>Especially when you have a citizen developer program or are scaling RPA within your company. Many a times, developer licenses allocated to employees remain un-utilized as they are either too busy or simply not interested. In addition, bot utilization can be low due to the small number of processes being automated or infrequent processing (e.g. monthly, quarterly or annual processes). In such instances, you may want to consider consolidating and rationalizing some of the licenses in order to save money.</p><h3>4. Consider consumption-based pricing models for processes that run less frequently, i.e. monthly, quarterly and annually.</h3><p>Traditional RPA pricing model that is based on named user is often commercially non-viable for such long tail processes due to low bot utilization (see point 3). Unfortunately, the reality is that such processes are the norm, not the exception, in most organizations, particularly SMBs. Adopting a pay-as-you-go pricing enables you to truly democratize automation and realize an automation-first strategy.</p><h3>5. Keep a lid on costs while making RPA accessible.</h3><p>If you have common processes that need to be run by a group of employees, getting one named user for each employee can be cost prohibitive. Instead, consider either using service accounts for such automations (if within a department) or purchasing a per-process plan that allows unlimited number of employees within the organization to run that (high value) automation.</p><h3>6. Explore alternative RPA software.</h3><p>Sometimes it may be worth your while to venture off the beaten tracks. Even though RPA is a relatively young market, there is a surprisingly large number of RPA software available. Besides popular choices like <a href="https://www.automationanywhere.com/">Automation Anywhere</a>, <a href="https://powerautomate.microsoft.com/en-us/">Microsoft Power Automate</a>, <a href="https://www.blueprism.com/">SS&amp;C Blue Prism</a> and <a href="https://www.uipath.com/">UiPath</a>, there are also open source alternatives such as <a href="https://openrpa.dk/">Open RPA</a>, <a href="https://robocorp.com/">Robocorp</a> and <a href="https://aisingapore.org/aiproducts/tagui/">TagUI</a>. Choose one that needs your technical requirements <em>and</em> operating budget.</p><h3>7. Be wary of hidden costs.</h3><p>As many of the incumbent RPA software vendors make the pivot to become business automation platforms, it pays to do your research and identify the platform components that you need to fulfil your desired use cases. Clarify upfront if there are any paid add-ons or pay-per-use features that you will incur to avoid getting a nasty shock when you receive your monthly invoice later on.</p><blockquote>Per-user pricing model can be complex, especially for enterprise customers with a large user base. There are various different add-ons, plus limitations on storage, file capacity and daily requests. — Gartner</blockquote><h3>8. Not all bots are created equal.</h3><p>In the world of RPA, there are basically 2 types of bots — attended and unattended. As long as user interaction is not required during the automation, most users prefer unattended bots due to the ability to trigger and schedule processes without manual intervention. However, while the underlying software is similar, there is a huge price differential between attended and unattended bots licenses with the latter costing as much as 6X times the former. Hence, all else the same, attended bots should be your first port of call. Or consider a robot scheduling software that allows you to trigger and schedule an attended bot.</p><p><strong>Stay tuned for part 2 and 3 of this blog post where we will highlight ways you can slash the services and support costs of your RPA program.</strong></p><p>Good automating!</p><p><em>Do you know of any other ways to reduce the RPA subscription fees? Do drop us a comment below.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9260919d7ca5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Of emerging technologies and adoption cycles]]></title>
            <link>https://cfb-bots.medium.com/of-emerging-technologies-and-adoption-cycles-e5c98f0e0800?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5c98f0e0800</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[golf]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Fri, 22 Oct 2021 04:34:11 GMT</pubDate>
            <atom:updated>2021-10-22T04:34:11.754Z</atom:updated>
            <content:encoded><![CDATA[<p>The unfair advantages known to and ignored by (almost) everyone</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ArqyeZqPM2lziEElbNPPSg.jpeg" /><figcaption>TrackMan</figcaption></figure><p>The <a href="https://www.trackman.com/">TrackMan</a> is a Doppler radar device that is able to track many critical data, including ball speed, spin rate, club speed and path, face and attack angles, and more. It was first introduced to the world of golf around 2007, and some of its early adopters include the who’s who of golf, such as Tiger Woods and Michelle Wie.</p><p>The TrackMan revolutionized the business of performance improvement by focusing on a data-driven approach, then a novelty. On hindsight, one might consider this a no-brainer, considering the wave of digital transformation that has swept across many sports from baseball (remember Moneyball?) to basketball.</p><p>Yet, despite its obvious advantages, initial adoption was surprisingly slow. As late as in 2013, 5 years after launch, <strong>only approximately 30% of the players</strong> on the professional tour were using a TrackMan to finetune their game. And <strong>not for a lack of awareness</strong> — the Trackman’s benefits were well known and widely publicized.</p><p>Turns out such adoption patterns are nothing new. The sobering fact is that we Homo Sapiens are creatures of habits with an innate resistance to change, even in the face of overwhelming evidence.</p><p>This also brings to mind Rogers’ Diffusion of Innovation theory where the process of adoption over time follows the classical normal distribution with 5 distinct adopter categories — innovators, early adopters, early majority, late majority and laggards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vFKHdzCf3isiaiQiE5pxTg.png" /><figcaption>Technology Adoption Lifecycle</figcaption></figure><p>As observed by author Ryan Holiday, “today’s conservative ideas were once controversial, cutting-edge, and innovative.” In other words, it does require a leap of faith for the innovators and early adopters to embrace change, even if they make a lot of sense.</p><p>Case in point: In 1943, Thomas Watson, chairman of IBM, remarked, “I think there is a world market for maybe <strong>five computers</strong>.” Today, it is estimated that there are over <strong>2 billion computers in the world</strong>.</p><p>Might the trick be to “identify the future that has already happened,” to quote the late management guru Peter Drucker?</p><p>Surveying today’s technology landscape, what do we see? According to <a href="https://www.gartner.com/en/documents/4001926/market-share-analysis-robotic-process-automation-worldwi">Gartner</a>, “the RPA software market grew 38.9% in 2020 to $1.9 billion and held its position as the fastest-growing segment in the enterprise software market.” This for the <strong>3rd year in a row</strong>!</p><p>This makes perfect sense, one would think. After all, there are plenty of motivations for shifting to a digital workforce, including:</p><ol><li>the strategic imperatives of digital transformation (one reinforced by the Covid-19 pandemic);</li><li>an acute shortage of manpower in many markets, especially developed ones;</li><li>unfulfilled customer expectations, e.g. real-time and tailored services, as a result of operational constrains (read manual and tedious processes); and</li><li>loss of productivity due to a mostly disengaged, overworked and over-stressed workforce.</li></ol><p>Yet, it appears that <strong>most organizations have not embraced an automation-first mindset</strong> on a scalable and sustainable basis. For example, <a href="https://www.forrester.com/report/the-rpa-services-market-will-grow-to-reach-12-billion-by-2023/RES156255?objectid=RES156255">Forrester</a> research indicates that “more than half of all RPA programs worldwide employ fewer than 10 bots. Furthermore, <strong>less than 19%</strong> of RPA installations are at an <strong>advanced stage</strong> of maturity.”</p><p>Could this be yet another example of slow adoption of soon-to-be mainstream technological innovation? More importantly, are you up for it? 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5c98f0e0800" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation as a force for good]]></title>
            <link>https://cfb-bots.medium.com/automation-as-a-force-for-good-8ea6ce5cd8f7?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ea6ce5cd8f7</guid>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[industry-4-0]]></category>
            <category><![CDATA[robotics]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Fri, 15 Oct 2021 09:14:59 GMT</pubDate>
            <atom:updated>2021-10-15T09:14:59.536Z</atom:updated>
            <content:encoded><![CDATA[<p>Mention automation and invariably, it arouses a tinge of automation anxiety in some people. Robots are going to replace and displace us from our jobs, or so they claim.</p><p>The truth, though, is much more nuanced. Let’s consider the humble telephone switchboard for example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Ml5UALYQVRolRokHlR1GQ.png" /><figcaption>Telephone switchboard operators doing their work</figcaption></figure><p>In the late 19th and early 20th century, manual switchboards were used to connect telephone circuits so as to establish telephone calls between users or other switchboards. Fun fact: The early switchboard operators were young men, but they were quickly replaced by women who had a much better work attitude, in addition to a sweet voice. This generated some of the most “high-tech” jobs of that era, certainly within the telecommunications industry which exclusively hired men for technical roles.</p><p>Nonetheless, with the proliferation and increasing ubiquity of the telephone, the manual switchboard operations became increasingly unsustainable. For example, by 1909, Bell Telephone System projected that every American women between ages 17 and 60 would have to work as a switchboard operator by the year 1925 if the manual system of handling calls were to be continued.</p><p>To paraphrase a popular saying, necessity is the mother of innovation. In this case, a clear process needs and demographic challenges meant that the first automatic switchboard was designed and put into service just a few years later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-AMsNkeLkUDPHb9FkdXzuw.jpeg" /><figcaption>Automated solution to the manual switchboard</figcaption></figure><p>Oh, and what happened to those switchboard operators? Well, they simply reskill and upskill (to borrow our modern terminology) to become telephone operators and receptionists.</p><p>The moral of the story is that as society advances and technology evolves, so do the jobs of the day. And automation can be a force for good if they are applied judiciously to address real pain points.</p><p>Back to the present, one such pressing challenge is the acute loss of employee productivity.</p><p>Do you know that employees are feeling increasingly disengaged at the workplace (and this is based on research pre-COVID) with a staggering <a href="https://www.automationanywhere.com/company/press-room/global-research-reveals-world-s-most-hated-office-tasks">40% of employees</a> surveyed reporting that they do not look forward to going to work in the morning?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*CEKUdaiu0iU0uhqqCv-aNA.png" /><figcaption>The most HATED tasks</figcaption></figure><p>Dig deeper, and it is not hard to see why. These employees spent on average <a href="https://www.automationanywhere.com/company/press-room/global-research-reveals-world-s-most-hated-office-tasks">more than 3 hours a day</a> on manual, repetitive computer tasks. As a result, more than two-thirds struggled to finish work on time. And as you can imagine, some of the most hated tasks include data entry work, filing digital documents and generating reports from IT systems.</p><blockquote><strong>“Clearly the most unfortunate people are those who must do the same thing over and over again, every minute, or perhaps twenty to the minute. They deserve the shortest hours and the highest pay.”</strong></blockquote><blockquote><em>John Kenneth Galbraith</em></blockquote><p>This is a tragedy of unfulfilled economic and human potential. In this digital age, employees are still burdened with what we call swivel-chair activities, extracting data from one system of records and manually keying into another.</p><p>Hence, it is my firm belief that automation, in this case Intelligent Automation or Robotic Process Automation, can help to deliver the triple-win, where shareholders, customers, and employees all benefit from automation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xYKqABj36ed_Xxr-SkvCag.png" /><figcaption>Intelligent Automation can deliver the triple win</figcaption></figure><p>After all, eliminating mundane, menial work results in far happier employees, who in turn provide better customer service and help the company generate more profits. For example, research has shown that companies with the most engaged employees were <a href="https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx">22% more profitable</a> than those with the least engaged employees.</p><p>If you share our vision of making work enjoyable and are interested in collaborating on the digital workforce of the future, <a href="https://www.cfb-bots.com/contact-us">get in touch</a> with us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ea6ce5cd8f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RPA Software Microsoft Power Automate Desktop Now FREE for All Windows 10 Users]]></title>
            <link>https://cfb-bots.medium.com/rpa-software-microsoft-power-automate-desktop-now-free-for-all-windows-10-users-72edd060f17e?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/72edd060f17e</guid>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[rpa-tools]]></category>
            <category><![CDATA[power-automate]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Mon, 29 Mar 2021 04:46:33 GMT</pubDate>
            <atom:updated>2021-03-29T04:46:33.811Z</atom:updated>
            <content:encoded><![CDATA[<p>Microsoft <a href="https://flow.microsoft.com/en-us/blog/automate-tasks-with-power-automate-desktop-for-windows-10-no-additional-cost/">announced on Mar 2, 2021</a> that it’s making its Robotic Process Automation (RPA) software, <a href="https://flow.microsoft.com/en-us/desktop/">Microsoft Power Automate Desktop</a>, available to all Windows 10 users at <strong>no additional cost.</strong></p><p>That’s saying RPA is accessible for free on <a href="https://www.computerworld.com/article/3199373/windows-by-the-numbers-windows-10-rolls-on-past-70.html">72% of all desktops and laptops running on Windows</a>! This is groundbreaking — especially for businesses who have been dragging their feet on RPA adoption mainly due to cost.</p><p>So, what does this mean for you?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*tghrNGC13Y2cA6ZZ8P_u1A.png" /><figcaption>Microsoft Power Automate Desktop now FREE for all Windows 10 users</figcaption></figure><p>In this article, we discuss:</p><ol><li>Is it <em>really </em>free?</li><li>How this removes barriers to automation for businesses</li><li>How this empowers business users</li><li>Learning Microsoft Power Automate Desktop</li><li>A word of caution</li></ol><h3>Is it really free? What’s the catch with the Microsoft Power Automate Desktop?</h3><p>Yup, it really is free, as in beer. You can just <a href="https://flow.microsoft.com/en-us/desktop/">download it</a> and have a go.</p><p>It seems Microsoft is making Power Automate Desktop free to push paid plans, such as the Power Automate per user with Attended RPA plan, targeted at larger enterprises with more sophisticated automation needs.</p><p>The paid plans allow advanced capabilities like sharing and collaborating across flows, identifying bottlenecks in your business processes, extracting data, and controlling flows for governance purposes.</p><p>Here’s a summary of the things you’ll need a paid plan for:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cUVhSZ9WV9hznD6bVeLJ_w.jpeg" /><figcaption>Power Automate Desktop paid enhancements</figcaption></figure><p>You’ll need a paid license to do these more sophisticated things on Microsoft Power Automate Desktop</p><p>Do note that Power Automate (both desktop and cloud flows) is part of the broader Power Platform which also includes Power BI for analyzing data for insights, Power Apps for building custom apps easily and rapidly, and Power Virtual Agents for building chatbots using a no-code interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rhZrPVmpOkV51I7Rwz4BJw.png" /><figcaption>The Microsoft Power Platform family</figcaption></figure><h3>Free Microsoft Power Automate Desktop Removes Barriers to Automation for Businesses</h3><p>The top 3 hurdles to advancing automation strategies, according to <a href="https://www.ssonetwork.com/intelligent-automation/reports/ssons-global-state-of-intelligent-aautomation-market-report-2020">SSON’s research</a>, are:</p><ul><li>Skills availability</li><li>Funding</li><li>Green light/business case</li></ul><p>By making Microsoft Power Automate Desktop free for all Windows 10 users, Microsoft is helping to overcome all these hurdles at once.</p><p>Instantly, one barrier that has been holding companies back from stepping into RPA has been removed: <strong>License cost</strong>. That’s a significant chunk of the funding required to get an automation program off the ground. This also makes it easier to build a business case to convince management to go into RPA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*JtothT9MyKAjHkDsx0HwoA.png" /><figcaption>Top 3 Hurdles to Advancing Companies’ Automation Strategy</figcaption></figure><p>Microsoft Power Automate Desktop’s no-code interface means it’s easier to train more employees to be proficient in automation, so it’s cheaper and quicker to build up a pool of automation experts within the organization.</p><p>As we will discuss next, the availability of Microsoft Power Automate Desktop also empowers individual business users to become citizen developers. This is something businesses should support and embrace, because citizen developers possess an intimate understanding of their own business processes and have a <strong>multiplier effect</strong> on accelerating the progress of automation in the company.</p><h3>Free Microsoft Power Automate Desktop Empowers Business Users</h3><p>Business users who have been frustrated by the staggering amount of repetitive tasks they have to do every day can now take matters into their own hands — they no longer have to get their bosses to approve the expense, or wait for IT to have the bandwidth to support them.</p><p>With Microsoft Power Automate Desktop’s no-code interface, these business users can become <strong>citizen developers</strong> — developing automation solutions for their own use or their teams’ use — almost overnight. Adopting such a people-first approach thus allows us to truly democratize automation and achieve the holy grail of automation — the <strong>triple-win</strong>: Employers, customers, and employees <em>all</em> benefit.</p><p>In fact, you can <a href="https://flow.microsoft.com/en-us/desktop/">download Microsoft Power Automate Desktop</a> <em>right now</em> and sign in with your existing Microsoft account credentials to get started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9aEfJ-Wpa6Fgs51ZpqSu7g.png" /><figcaption>Power Automate Desktop — download</figcaption></figure><p>Although no coding is required to use Microsoft Power Automate Desktop, there <em>is</em> a learning curve. Nevertheless, there are plenty of resources made available by both Microsoft and third parties on the Internet to help users get started.</p><h3>Learning Microsoft Power Automate Desktop</h3><h3>Microsoft Learn</h3><p>Microsoft Learn has several modules teaching you how to work with Microsoft Power Automate Desktop. A search for “Power Automate Desktop” in <a href="https://docs.microsoft.com/en-us/learn/">Microsoft Learn</a> turns up 849 results!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kbwOAf02lRc5z36cpTJ4rw.png" /><figcaption>Search Results on Microsoft Learn</figcaption></figure><p><a href="https://docs.microsoft.com/en-us/learn/paths/pad-get-started/">Get started with Microsoft Power Automate Desktop</a>, for example, is a quick and simple learn-at-your-own-pace Learning Path, which Microsoft estimates you can complete in under 1.5 hours. It guides you through your first steps with the software, and helps you create your very first simple automation: Creating a flow that copies a selected folder and then adds information about the created backup in a Microsoft Excel file.</p><p>Other examples include <a href="https://docs.microsoft.com/en-us/learn/modules/pad-ocr/">OCR technologies in Power Automate Desktop</a> and <a href="https://docs.microsoft.com/en-us/learn/modules/pad-email/">Automating email handling in Power Automate Desktop</a>.</p><h3>Microsoft’s Documentation</h3><p>For the more technically inclined users, Microsoft’s <a href="https://docs.microsoft.com/en-us/power-automate/desktop-flows/introduction">documentation on Microsoft Power Automate Desktop</a> provides detailed explanations on its various features. For others though, the staggering amount of information could get overwhelming fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iFFT7kmaZpAvnSUP50ZoSw.png" /><figcaption>Screenshot of Introduction to Power Automate Desktop in Microsoft Docs</figcaption></figure><h3>YouTube</h3><p>Besides these resources from Microsoft, another way to learn Microsoft Power Automate Desktop is by watching tutorial videos on <a href="http://youtube.com/">YouTube</a>. A quick search brings up dozens, if not hundreds, of tutorial videos you can learn from.</p><p>The downside to these free methods, however, is that you’ll have to spend a lot of time and energy sifting through this wealth of information to find what you need. Information overload is real. Many times, the very reason you want to automate your business tasks is precisely because you don’t have time. Where does that leave you?</p><h3>Specialized Small-Group Training</h3><p>This is where it may make sense to engage specialized, experienced trainers to teach you the ropes — fast — through an intensive course. Not only will good trainers distill the right information for your particular needs, they will also teach you best practices based on their experience carrying out automation projects in the industry.</p><p>Small-group training with a hands-on component and access 1-on-1 guidance is the best way to learn</p><p>The best training programs include hands-on exercises where you can automate a real-world scenario — even better if it’s your own real day-to-day business tasks — under the direct supervision of your trainer. This way, you can get 1-to-1 help for your particular situation, and also finish the course with a real task already automated.</p><p>CFB Bots’ Automation Academy, for example, has a <a href="https://www.cfb-bots.com/power-automate-desktop-training">3-day Introduction to Microsoft Power Automate Desktop course</a> that teaches participants the ins and outs of the software, complete with a capstone project at the end of the course.</p><p>After completing such a course, you continue to enjoy the convenience and accuracy of the business task you automated. This, coupled with the implementation knowledge still fresh in your mind, is great to keep your momentum going.</p><h3>A Word of Caution</h3><p>The sudden revelation that a coveted RPA software is now free can certainly spur us to get started right away on anything that looks automatable. But before you jump into automating everything with Microsoft Power Automate Desktop, remember, “<em>To a man with a hammer, everything looks like a nail</em>”.</p><p>Evaluate RPA as one tool among many — not as the only tool. Select suitable processes for RPA.</p><p><a href="https://www.cfb-bots.com/rpa-process-selection">Selecting and evaluating processes suitable for RPA</a> is still important. This is so that you invest your time, energy, and money on processes that are most likely to succeed. Other critical aspects of automation that must not be overlooked include governance, security, building an automation pipeline, and change management.</p><h3>A Robot for Every Employee</h3><p>From a macro perspective, the Mar 2 announcement might just be the watershed moment that heralds the era of a robot for every employee. If so, then Microsoft would have come full circle considering that Bill Gates was the pioneer that put a computer on every desk and in every home. The bottom-line: the digital workforce is ready — are you?</p><p>If you need help in applying Microsoft Power Automate Desktop in your organization, get in touch for a <a href="https://www.cfb-bots.com/book-your-free-consultation">free consultation</a>.</p><p>Good automating!</p><p><a href="https://www.cfb-bots.com/single-post/microsoft-power-automate-desktop-free">This article originally appeared on our Robotic Process Automation blog series.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72edd060f17e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Attended Automation the Antidote to Automation Anxiety?]]></title>
            <link>https://cfb-bots.medium.com/is-attended-automation-the-antidote-to-automation-anxiety-b3aff3f05df2?source=rss-a68344d749f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3aff3f05df2</guid>
            <category><![CDATA[robotics]]></category>
            <category><![CDATA[process-automation]]></category>
            <category><![CDATA[uipath]]></category>
            <category><![CDATA[roboticprocessautomation]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[CFB Bots]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 02:22:49 GMT</pubDate>
            <atom:updated>2020-12-09T02:22:49.295Z</atom:updated>
            <content:encoded><![CDATA[<p>The best time to start on the journey of digital transformation is twenty years ago. The second-best time is now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YNO7razKISUBsoycMbDq7g.jpeg" /><figcaption>Is Attended Automation the Antidote to Automation Anxiety?</figcaption></figure><p>In today’s increasingly digital-first economy that is concurrently being disrupted by the ongoing Covid-19 pandemic, automation is no longer a strategy. It is <em>the</em> way of work. In fact, with our work-life being punctuated by lockdowns and movement restrictions, an automation-first approach might be the <em>only</em> way to work.</p><p>To be sure, automation in and of itself is insufficient. True digital transformation only occurs when the technology trifecta of Automation, Analytics and Artificial Intelligence (AI) is judiciously and relentlessly applied across an enterprise’s people, processes and data to effect significant and sustainable changes.</p><p>And it is important to start with the end goal in mind.</p><p>But this is where many executives tend to get it wrong. Unlike industrial automation, the <em>raison d’etre </em>for embedding an automation-first mindset into the organization’s DNA is not necessarily digital labour arbitrage or cost take-outs. Rather, it is about enhancing both Customer Experience (CX) and Employee Experience (EX) — key battlegrounds that determine whether your company has a defensible moat in the next decade and beyond, but which have absolutely no bearing on your next set of quarterly results.</p><h3>An Automation-First Mindset Is Badly Needed</h3><p>The reality is that worker productivity and employee engagement remain persistently low worldwide. And these 2 factors reinforce each other, triggering a downward vicious cycle. The <a href="https://www.automationanywhere.com/company/press-room/global-research-reveals-world-s-most-hated-office-tasks">stark facts</a> make for difficult reading:</p><ul><li>The average office worker spent more than 3 hours a day on manual, repetitive computer tasks that aren’t even part of their primary job;</li><li>Almost half find such digital administration boring and a poor use of skills;</li><li>The top 5 hated tasks are: general data entry, managing email traffic, filing digital documents, compiling reports from IT systems and invoice management;</li><li>40% of employees say they don’t look forward to going to work in the morning;</li><li>67% of employees struggle to leave office on time due to time spent on manual, repetitive digital administration tasks; and</li><li>More than 80% indicated that they wish their employers would automate more tasks, and that they would be attracted to work at a company that embraces automation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x4YThCxcPfbVe6yhaFqUPg.jpeg" /><figcaption>An Automation-First Mindset Is Badly Needed</figcaption></figure><h3>The Elephant in the Room: Automation Anxiety</h3><p>The fear of being displaced by technology, innate resistance to change, lingering suspicions over management agenda as well as lack of support for upskilling or reskilling is generating a palpable sense of automation anxiety. And such anxieties are only exacerbated in the current economic malaise. According to an <a href="https://www.nber.org/system/files/working_papers/w18334/w18334.pdf">NBER report</a>, recent recessions tended to be followed by jobless recoveries as the level of automation in enterprises rises.</p><p>And as Upton Sinclair so eloquently put it, “it is difficult to get a man to understand something, when his salary depends upon his not understanding it.”</p><h3>Attended vs Unattended Automation</h3><p>This is where attended automation enters the fray. For the uninitiated, in the hypergrowth world of Robotic Process Automation (RPA), there are two main flavours — attended automation and unattended automation. The following diagram provides a quick overview of the difference between these two types of automation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68tcKbyEcvz0BvIwxeshnQ.jpeg" /><figcaption>Attended vs Unattended Automation</figcaption></figure><p>Historically, RPA has its roots in unattended automation — digital workers residing in servers and automating high-volume, transactional tasks and processes that occur mainly in the back-office. And by some analysts’ estimates, this remains the predominant mode of automation, making up approximately 75% of RPA software licensing revenues.</p><h3>Unattended Automation Does Not Benefit the Average Employee</h3><p>Unattended automation is not without its challenges though. Because unattended automation delivers the most value (read: cost savings) when there are large volumes of repetitive, transactional tasks that can be automated, it is not surprising that deployments tend to be driven “top-down” and focused narrowly on certain lines of businesses like shared services or global business services where there are economies of scale.</p><p>While there is nothing inherently wrong, this approach is rather tactical and not truly transformative for the entire organization. In addition, scaling unattended automation becomes unwieldy beyond a certain point; hence the observation that most organizations have less than ten bots in production.</p><p>Nor does the average employee benefit from the automation initiative — no triple win here! Indeed, what do you do with the tens and hundreds of back-office employees whose work you have now completely automated and eliminated?</p><h3>A Robot for Every Person: Attended Automation at Scale</h3><p>There has to be a better and more equitable approach towards managing automation within an enterprise. The solution? A people-first approach where automation is democratized throughout the entire enterprise.</p><p>Where every employee becomes a citizen developer (i.e. attended automation) and is equipped with their own digital assistant and collaboration tools. Where everyone is empowered and engaged to leverage these digital tools to accelerate innovation and value-creation “bottom-up”, without any fear of making themselves redundant in the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MrQkFwj4W0J4YMHtA7Yn2A.jpeg" /><figcaption>A Robot for Every Person: Attended Automation at Scale</figcaption></figure><p>This vision of “<a href="https://www.forbes.com/sites/alexkonrad/2019/09/11/from-communism-to-coding-how--daniel-dines-of-7-billion-uipath-became-the-first-bot-billionaire/">a robot for every person</a>” is nothing but digital dexterity at scale. By putting the power of automation firmly in the hands of individuals who best understand the work they do and allowing human ingenuity to take over (within certain governance guardrails), attitudes towards automation shift from defensive and sceptical to liberating and empowering.</p><h3>Cumulative Gains From Attended Automation at Scale</h3><p>With citizen development and attended automation at scale, the <a href="https://www.cfb-bots.com/single-post/2018/12/03/The-Long-Tail-of-Robotic-Process-Automation">long tail of automation</a> becomes a viable strategy. The corollary is an innovative and dynamic enterprise where employees are continuously seeking that 1% performance improvement (e.g. time savings) and sharing those gains enterprise-wide to achieve the <a href="https://www.uipath.com/blog/introducing-automation-flywheel">automation flywheel</a> effects.</p><p>To provide some perspective, saving <strong>20 minutes per workday</strong> for one employee might not sound like much. But for a large enterprise of <strong>10,000 employees</strong>, this translates to savings north of <strong>100,000 man-days per annum</strong> by compounding and cumulating these gains.</p><p>“Perhaps the most powerful benefit is that it creates a contagious enthusiasm. Everyone starts looking for ways to improve. There’s something inherently rewarding about identifying marginal gains — the bonhomie is similar to a scavenger hunt. People want to identify opportunities and share them with the group.” — Sir David Brailsford</p><h3>The Rise of the Digital Assistant</h3><p>According to <a href="https://www.gartner.com/en/newsroom/press-releases/2019-01-09-gartner-predicts-25-percent-of-digital-workers-will-u">Gartner</a>, by 2021, 25% of the workforce will be augmented and assisted by a digital assistant, up from less than 2% in 2019. Far from competing with their human counterparts, these attended bots will become the vehicle for realizing real digital transformation for every employee.</p><p>Good automating!</p><p><a href="https://www.cfb-bots.com/single-post/attended-automation-antidote-to-automation-anxiety">This article originally appeared on our Robotic Process Automation blog series.</a></p><p><em>What are your thoughts around attended automation and a robot for every person? Do drop us a comment below.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3aff3f05df2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>