CIO 360 Archives - 91¶¶Òő /category/capability/cio-360/ IT Consulting, Strategy & Outsourcing Services Company Wed, 05 Mar 2025 06:45:59 +0000 en-US hourly 1 https://wordpress.org/?v=6.8.5 /wp-content/uploads/2020/03/itc-logo.png CIO 360 Archives - 91¶¶Òő /category/capability/cio-360/ 32 32 Enterprise Architecture Reimagined: Exploring Its Facets in the Ai Epoch /blog/enterprise-architecture-reimagined-exploring-its-facets-in-the-ai-epoch/ Thu, 16 May 2024 12:26:55 +0000 /?p=41263 The post Enterprise Architecture Reimagined: Exploring Its Facets in the Ai Epoch appeared first on 91¶¶Òő.

]]>

Enterprise Architecture (EA) as a practice, as a role, as a thought process has come a long way in the last three and half decades since its inception. Various standards, frameworks, industries, and governments joined hands and climbed the ship of EA from time to time and reached destination (goal) of their stipulated time.

EA role has both evolved and involved over the period and at this time of the AI era (other terms in the AI Epoch), multiple people have coined or termed different new terminology of EA as per their own perspective. The origin of these terminologies over the period has the basic thought that “EA is in crisis.” These all-coined terminologies are nothing but different viewpoints of EA.

EA was never and will never be in crisis. Organizations and industries crisis from the past was failure of not implementing EA. Such as the banking crisis (post which BIAN was set up) or the real estate crisis of the 2000s or the recent COVID-19 crisis. Each time one or multiple industries gets affected and there was a change in gear within organization(s) to understand EA as per their own understanding by following EA standards and frameworks specific to their industry. Over time, the standards, and frameworks pertinent to these specific industries and Enterprise Architecture have undergone a process of evolution and enhancement.

For a span of ten years, I have maintained a catalogue of EA Reference Architecture. It is important to note that the alterations to the site links are minimal and the list is not comprehensive, extending beyond the specified industry verticals or domains. While there are multiple such catalogues accessible in the market, this one is my preferred choice as it facilitates effective tracking.


In 2024 itself, one of the ” with context to obviously EA in crisis. People contested it across the news and social media with few in agreement and few in disagreement. My viewpoint is from disagreement with the strong contest is EA was and will never be specific to any stack be it business or technology stack. Then why do you need a full stack? EA was always full stack; it is not about any of the cards from the stack.

Below is the snapshot from one of EA frameworks TOGAF 10, which describes that EA is more than 70% about business and the remaining 30% would be part of data, application, and technology.

 

Issue or Crisis has always been in understanding EA. “There is always an ambiguity in understanding EA because EA is an area of the field with everything ambiguous.” Explained nicely by Dr. Pallab Saha, The Open Group CEO at one of the events. EA was never in crisis; it was always people or organizations who never realized the value of an EA until there was a crisis knock at the door. A few examples of such a mindset are in late 2020 and now ; both have not emphasized EA much. EA in such large banks has always been more of a department to complete the compliance checklist.

Now the reason this happened in Apr’2024 itself, is this AI Epoch. AI was always there in the background, in our studies during graduation but now it is reality in front of us. As mentioned earlier in this article, all EA frameworks and standards across industries are evolving to cater to AI (not just Gen AI). Last year 2023, even Gartner reflected to all CXOs, and leaders with similar guidance on the dilemma of EA during AI times.

The success of any EA depends on multiple factors, but the mantra is simply “Scale Fast, so that can’t be undone,” again from Dr. Pallab Saha. This EA mantra allowed multiple EA designs to become frameworks and standards. Consider the example of DoDAF which is EA Framework for the US Department of Defense, MoDAF which is EA Framework for the UK Ministry of Defense, or IndEA which is for the Indian Government.

Another reason in the AI era, everyone is worried about the “EA in crisis” kind of stuff is because AI is influential, and EA is noisy for 90% of organizations across the world from all diverse types of industries. The best example to explain EA being noisy would be COVID-19 crisis. Various industries disrupted by COVID-19, especially healthcare, hospitality, tourism, manufacturing, supply chain, and travel, among others. Again, the reason was not proper EA utilization whether internal or outsourced. Even research firms like Gartner, IDC, and Forrester started emphasizing EA with titles such as “EA – the dawn of new era,” and “EA – must for transformation.” As it again has gone backseat for few organizations, but all the organizations started realizing that EA is must to achieve their business vision with a timeline of 3-5 years as the target.

The authentic use of AI in EA is when AI operates as an auxiliary or support system, rather than serving as a substitute. AI tools have facilitated the acceleration of tasks within EA. However, the comprehension and expertise of Enterprise Architects remain essential for validating data points and perspectives in alignment with the business vision. Facilitating a collaborative environment between AI and EA governance could provide organizations with a competitive advantage, enhancing their alignment with their business vision and expediting the execution of EA tasks.

Multiple EAMs (Enterprise Architecture Management) or EA Tools are already incorporating AI in their core. One such tool is LeanIX which enables AI utilization within its EAM (Enterprise Architecture Management) tool. Even The Open Group has started work towards “”

Now coming to EA facets (multiple names), multiple terminologies coined over the period. I learned during one of the EA webinars, which is a fact, that there are more than eight (8) million architects’ titles in the market. If we narrow this down to EA, the count will be more than two (2) million. Organizations as per their understanding of EA and their convenience as per their businesses, have defined, coined, or termed these architectural roles. In this cycle, even EA frameworks like TOGAF have jumped and coined another term such as Digital Architect.

Another reason to have so many terminologies for an EA is because of the mindset “Architecture is about taking control of an organization.” Architecture is not about taking control of an organization. It is about giving control to organizations. You still need the organization. The clue is in the name, organization.

From my viewpoint, there are only four facets to any EA framework as mentioned in Figure 3 earlier and they are business, data, application, and technology. To contest my thought process, there is already a trend in the market that allows Architecture-as-a-service (AaaS) such as (again open source). These AaaS tool(s) are specific to an application component of EA.

There are multiple Enterprise Architects who share similar thought processes and agreements, and they play a significant role in supporting the EA practice worldwide. One such individual is Sam Holcman, whose focus is streamlining the Business Architecture component of Enterprise Architecture. Similarly, courtesy to George Hohpe, Martin Fowler, Neal Ford, and Mark Richards who keep inspiring new architects to move towards EA. The very definition of EA is now enabled as syllabus at universities, especially in India apart from other countries which would enable EA facets taught to our educational mindset even before we start working as an individual.

The mantra that I have learned over the period, especially as an EA, is to be useful and trusted to be an influencer as an EA. To achieve or execute this mantra, the focus should be on people.


References:

  • The Software Architect Elevator – George Hohpe
  • Fundamentals of Software Architecture – Neal Ford
  • Whole EA – Tom Graves
  • TOGAF
  • DoDAF
  • BACOE
  • Gartner

Author:

Neeraj Gautam,
Enterprise Architect at 91¶¶Òő

The post Enterprise Architecture Reimagined: Exploring Its Facets in the Ai Epoch appeared first on 91¶¶Òő.

]]>
Why Organizations Using Devops Tools Are Getting Ahead of the Rest /blog/why-organizations-using-devops-tools-are-getting-ahead-of-the-rest/ Mon, 13 May 2024 12:37:04 +0000 /?p=41244 The post Why Organizations Using Devops Tools Are Getting Ahead of the Rest appeared first on 91¶¶Òő.

]]>

The benefits of DevOps are widely known and simple to understand. The practice brings together people, processes, engineering, operations, and technology to deliver products faster, better, and more confidently to meet business goals. However, some organizations do this better than others. Separating the leaders from the laggards is the use of tools. The teams that use DevOps tools achieve outstanding results. Our experience shows that using DevOps tools can reduce lead times to deployment by 45 percent, reduce failure rates by 50 percent, and bring down support cases by 70 percent.

With such a promising upside, the DevOps market is naturally set to balloon. suggest that it will grow from an estimated $8.66 billion in 2022 to $47.81 billion by 2030, growing at a CAGR of 23.80 percent over the forecasted period.

Life before DevOps: Chaotic

DevOps, through the adoption of agile and lean practices, has introduced a sea change in the science and art of product development. Life before DevOps was chaotic for project managers. Miscommunication between developers and the operations team would result in haphazard development, delayed deployment, the need to constantly monitor application maintenance and performance, a lack of continuous integration, and spiraling operational costs. A simple code issue would set the project manager off to see if the data team had changed values or if the developer had a reason to change a column name and to see what the tester had to say. It was a never-ending chain of debugging—with the primary outcome being employee burnout.

Life after DevOps: Under control

This has changed. The chaos can now be brought under control. Using DevOps tools and processes, program managers can now quickly identify which code broke functionality, who wrote the code, and the time it will take to fix.

In Azure DevOps, user stories are task descriptions that are treated as work items. A developer is assigned a task and must transform the user story into a functionality. To do this successfully, the developer needs, say, a database table and an API. This information is captured in the work item, along with the relevant test cases that get updated in a tool. When the developer commits the code, it is linked to this work item.

Improving the value of DevOps

Every organization that embraces DevOps believes it has evolved as a business. In reality, these organizations, without realizing it, are living with sub-optimal results from their DevOps initiatives. The situation is comparable to that of generative AI. Every organization claims to be using generative AI. However, the value of generative AI is directly linked to the data it is trained on. If the data is inadequate, the model cannot be effective. It is the same with user stories. If the project manager does not record detailed user stories, outcomes will be sub-optimal. DevOps tools are critical to avoid this prospect.

DevOps tools allow user stories to be captured in detail. Typically, the tool will capture the features a user story needs to deliver (see Figure 1), the acceptance criteria and standards (usability, design, performance, security, etc.) that will be considered to judge if the user.

Story has been successfully executed as a feature, the difficulty level in completing the task, the developer or the team to which the task has been farmed out, dependencies/impediments, associated feature requests, time spent to deliver a task, task status, etc. These tools provide a platform to record discussions and conversations before the work item is committed as code. The complete end-to-story helps the program manager stay on top of what is happening without human dependencies. Organizations that are not using these tools cannot claim to have embraced DevOps. These organizations have only implemented an Agile process with standup meetings and scrum calls. The project manager’s role should be to ensure the tools and systems capture the details.

Once the details are in the system, a dashboard can provide a deep dive (see Figure 1): How many stories and work items do we have? How many commits have been done for a particular code snippet? What is the build health? What is the quality of the code before it is put into its environment? How many builds have been successful? Is the developer doing unit testing before pushing the code?

The barriers to benefits

Several DevOps tools are available to capture development tasks (see Figure 2). These include Azure DevOps, Bitbucket, Gitlab, GitHub, Selenium, etc., which help inject transparency into development. The challenge for the project owners and managers is to ensure the team is ready to move away from traditional development models and embrace transparency. Without a mindset change and a cultural change, the tools cannot be ineffective.

Part of the reluctance to change the mindset is rooted in a misconception. Many believe the tools will eliminate the need for humans in the process. This is not true. The tools merely show the efficiency of the process that the team is following. The tools tell us how clean the product is when it goes to market, what kind of observability we have, the time a task is likely to take, etc. Tracking this information is a huge and complicated job. The tools simplify it; they automate nothing.

Organizations need to realize—and eventually, they will—that they have been using DevOps for 15 years but have not simplified it. This is because they are resistant to change. The organizations that close the culture gap and change will move ahead. The rest will play catch-up.

How to trigger cultural change with Agile Methodology

The challenge for organizations is to address the gap quickly. Here is one way to do it: Most project managers have two or three projects to manage simultaneously. The Project Management Office (PMO) should make sure there are daily calls for each project, and the manager is forced to provide a status update. Usually, the manager is a layman, not a developer. To them, the PMO should ask, “The developer did something. Did you understand what was done?” The obvious answer is, “No!” But this is where the change can be triggered. The PMO must ask the manager to read the details from the DevOps tool and get on top of the delivery. The point is to challenge managers with simple questions, “How much time will the developer take for the next build?” or “Who do you think is the right resource for the task?” or “What are the dependencies for a task?” The answers to these questions can be generated by the tool. Many of these tools have pre-defined queries, making them simple to use.

It is easy to see that organizations that claim to have embraced DevOps may not be extracting as much from the practice as possible. Their ROI is low. For example, they may not be able to unlock the ability to experiment and innovate, deliver superior product quality, release code quickly, dramatically improve time to resolution, address unplanned work with agility, reduce the cost of production, and reduce developer burnout. To all this, there is one simple answer: Create Agile culture that uses DevOps tools like a pro.


Author:

Swetha Yalamanchili,
Head of DevOps

The post Why Organizations Using Devops Tools Are Getting Ahead of the Rest appeared first on 91¶¶Òő.

]]>
Brands that Embrace Digital will Stay Ahead in the D2C Model /blogs/brands-that-embrace-digital-will-stay-ahead-in-the-d2c-model/ Wed, 21 Sep 2022 08:07:10 +0000 /?p=38693 Sanaya woke up late on a Monday morning to discover that she had run out of her favourite skimmed milk. It was 8:30am and raining incessantly outside. She had to […]

The post Brands that Embrace Digital will Stay Ahead in the D2C Model appeared first on 91¶¶Òő.

]]>
Sanaya woke up late on a Monday morning to discover that she had run out of her favourite skimmed milk. It was 8:30am and raining incessantly outside. She had to join an important meeting from 9:00 am. The presentation document was loading in the laptop. She quickly picked up the mobile and started typing the brand name on a retail ecommerce website. She found the product out of stock but came across other brands in that category. She went on to check the company’s D2C website but could not navigate through the multiple options toward the product ordering page. In a hurry, she returned to the retail website and found that it was already displaying all the options of alternative brands in the same category. She observed that the other brands don’t have the convenient packaging that she had been enjoying in her preferred brand. But that day she didn’t have time to decide. She quickly chose and paid for an alternative brand and reached for the laptop to look through the presentation, which she would discuss in the meeting.

It is a common situation that most shoppers face while buying packaged goods online. Due to high demand many daily used products go out of stock in retail sites. But it is more annoying to experience longer time in any shopping website due to lack of clarity about how to select and pay for a product. Direct-to-customer (D2C) is the new trend shaping the consumer-packaged goods (CPG) industry across the globe. Primary reason being low entry barrier, which is enabling private label brands to appear in the market with frequency higher than ever. However, not all brands could sustain the race of attracting consumers to their brands. It is more due to the marketing strategy they follow than the quality or features in the products. Drawing consumers to the products is the primary major challenge in this business model. Second major challenge is ensuring continuous availability of products, which means ensuring an uninterrupted supply chain process. If we introspect more into the primary challenge, we find three reasons underlying. First one is all about understanding the need of each & every customer and designing product as per their requirements. Second is keeping a tab of competitors’ offerings in the marketplace. Third is using information related to earlier two cases to develop personalised buying experience for every customer. The only solution that could help us resolve all these problems is data. Data is the ammunition in this expanding war of customer acquisition and retention. Collection of data about customers’ preferences and competitors’ new offers, storing those data and using those effectively are of primary importance in building a successful D2C business model.

If we go deeper into this, we find that next level of challenge is identification of data. It is customary for every marketer to understand and find the type of data one needs to understand customers’ requirements. Parallelly, one needs to find the data required on competitors’ offerings to strengthen the grip on the marketplace. Once understood, firms should think about the resources through which all these data can be collected and stored. And finally, how these data can be used to generate insights about customer’s behaviour.

To help firms in this journey, digital technology services are on the rise. The advent of intelligent automation has equipped the software service providers develop digital tools to understand the ongoing trend and find which areas need more focus to make the business run profitably. Robotic process automation (RPA), cloud technology, Artificial Intelligence (AI) based algorithms and machine learning (ML) programs are examples of digital tools which have paved the way for technology focused CPG firms to monitor their businesses closely and engage consumers more effectively. Every consumer has a different and unique way of shopping. Therefore, engaging with each consumer through the right channel, right promotion and right offer is undoubtedly a critical task. In top of that increasing penetration of mobile technology has brought all category of consumers at the same place and at the same time resulting in an extra level of complexity in data collection. Therefore, developing a robust data storage facility is no more a choice but a necessity for managing such increasing diversified consumer base. 91¶¶Òő through its rich experience of working with multiple CPG consumers can provide both on-premises and cloud-based database solutions to manage terabytes of data on a continuous basis.

Once the data storage facility is set up, suitable data collection resources should be developed to ensure uninterrupted data feeding to the repository. Whenever a consumer engages in any purchasing activity through online channel, millions of data are transferred to the marketing firm. Multiplying this with number of available channels, nearly trillions of data are needed to be handled every day. Hence, the solution is to have resources having the capability to find relevant data in any format from any channel and incessant feeding of these data to the storage facility. 91¶¶Òő’s intelligent automation team can develop any customised intelligent bots using robotic process automation (RPA) for collecting data from any channel at any time with 100% efficiency. Not only from websites, but these bots can also even identify the necessary data from any document in any format. This can help the firms analyse multiple purchasing invoices to figure out average purchase value for any customer.

After collection the data, next important steps are identification of relevant KPIs and development of analytical models for the purpose of understanding the status of ongoing business and generation of insights about customer’s buying pattern. 91¶¶Òő has a dedicated analytics team who has developed analytical models as per business need and has helped firms understand consumer journey at every touchpoint starting from exploration to procurement of any product.

After data management the next critical area where D2C firms should put highest focus is managing the supply chain of entire processes. If designing products as per consumer’s need is the primary challenge that D2C firms face now-a-days, then the next big challenge is taking these products to the consumer’s doorstep. The solution that addresses this concern is smart supply chain. Although most of the firms engage third parties for delivery of products, making the products available to delivery partner’s warehouses or distribution centres need a thorough monitoring of supply chain. 91¶¶Òő’s Industry 4.0 and Digital team together provide efficient and effective supply chain solutions with the help of Internet of Things (IoT), RPA and AIML. Not only our solutions ensure automated monitoring of entire supply chain process but also can eliminate the redundant processes, reduce the energy consumption at intermediate stages wherever possible and build models for optimising selection of packaging materials.

The problem that Sanaya faced at the beginning of this article could have easily been avoided had the brand manufacturer focussed on these issues and collected data about Sanaya’s buying pattern. Also, they should have ensured availability of the product at retailer’s site by adopting smart supply chain practices. Emerging digital technologies like robotics, artificial intelligence, cloud technology and IoT are a blessing for firms. However, leveraging these technologies to maximise the profit and capture the market share needs a blend of expertise & experience over the years. 91¶¶Òő’s rich experience of working with global CPG manufacturers in multiple channels and multiple regions for diversified products have helped develop suitable digital technology-based offers for D2C firms. In an industry like CPG where competition has been a paramount concern from new product perspective, emergence of D2C practice has made the situation more complex. To compete successfully and lead in the marketplace, firms must embrace the digital tools for navigating through the wave of unlimited new products.


Author:

Debal Chakraborty,
Principal Consultant

The post Brands that Embrace Digital will Stay Ahead in the D2C Model appeared first on 91¶¶Òő.

]]>
Evolution of IT Service Desk Operations (SDOps) /evolution-of-it-service-desk-operations-sdops/ Tue, 18 Jan 2022 12:59:39 +0000 /?p=37477 During the late 80s and 90s, IT Helpdesk was a different beast as compared to what we have today. It acted as a single point of contact for users’ IT […]

The post Evolution of IT Service Desk Operations (SDOps) appeared first on 91¶¶Òő.

]]>
During the late 80s and 90s, IT Helpdesk was a different beast as compared to what we have today. It acted as a single point of contact for users’ IT issues/ requests. Terms such as “catch and dispatch” and “log and flog” became prevalent and are being used to date.

With rapid adoption ITIL framework, the focus shifted to services and management (business outcomes). This resulted in a gradual change from IT Helpdesk to IT Service Desk, which is now equipped with multiple channels that end-users could use for requesting support services. It has also enabled and empowered the end-users to solve a certain level of issues themselves.

Technology has made quantum leaps over the past decade, but the majority of the organizations continue to operate with the dated model when fewer things went wrong with IT. The onset of the pandemic in early 2020, drove the CIOs to think digital and move towards an operation that encouraged “Shift-left” and “Remote”.

The modern Service Desk Operations or “SDOps” (as we like to call it), offers an intelligent “first line” of entry point into IT Organisation comprising of Artificial Intelligence (AI) enabled automated solutions that users can access with Zero-human touch. To reduce the involvement of human agents, it is anchored around self-service and self-healing initiatives. Some of these enabling tools/ trends are listed below:

  • AI and NLP powered Chatbot – Empowering the end-user to converse with a chatbot to get their issue resolved via self-service
  • Digital Experience Management (DEM) – allows organizations to develop a deep, continuous understanding of each employee’s needs across the entire digital enterprise. The DEM platform is capable of Service Desk diagnosis & remediation, Root cause analysis, Proactive Endpoint Services, and Asset Optimization
  • Automation and orchestration capabilities – From the use of simple scripts to the use of RPA for simulating human-like activities for resolution of issues
  • Integrated IVR based telephony – AI-based telephony option to intelligently redirect the calls to appropriate resolver groups
  • Remote support and Augmented Reality – enables users to leverage both smart technologies and a remote expert at a world-class service desk to resolve their issues

Adopting a “shift-left” approach enables issue resolution close to the end-user, thereby, bringing in an enhanced end-user experience and reducing the wait time. This directly impacts the cost of dealing with the incidents and enhances the services levels. The productivity of the business end-user improves significantly, and they are motivated to resolve the issues themselves, rather than reaching out to the service desk.

What the future holds?

Post pandemic, organizations have begun to realize the power of “shift-left”, which results in minimum human interaction and resolution closer to the users, at the IT service desk. This has propelled a rise in the adoption of AI-enabled capabilities, automation, and knowledge management capabilities. AI interfaces will eventually become an integral part of SDOps in the next few years, providing the end-users with a self-learning robotic bot as an alternative to a human agent. This will lead the way in Value Demonstration, enhancing and enriching End-User Experience.

As we move ahead, the operational cost for running an IT Service desk is expected to drop as AI interactions will mature and provide round-the-clock support to end-users without the need to have human agents covering a 24×7. Moreover, AI-based interactions at Level 0 going to cost less, thus, incentivizing the organizations to drive adoption of new technologies at the end-user level. The rate of technological development in the current day and age would result in IT Service Desk becoming more of a facilitator ensuring that all the end-user services ‘just work’.

91¶¶Òő’s E3 framework provides a strong foundation for the ‘Digital Workplace’ to be leveraged, a differentiated framework for transforming the end-user workplace. This framework comprises of

  • Experience: Identify User experience journeys through Value Stream Mapping
  • Efficiency: Drive Extreme Automation for an efficient self-service experience
  • Effectiveness: Accelerate adoption for benefit realization

Author:

Abhimanyu Pandey
Lead Consultant – INFRA,
91¶¶Òő

The post Evolution of IT Service Desk Operations (SDOps) appeared first on 91¶¶Òő.

]]>
Digital workplace aligned to industry-specific personas /digital-workplace-aligned-to-industry-specific-personas/ Wed, 12 Jan 2022 12:15:03 +0000 /?p=37459 The traditional workplace is undergoing major transformations as enterprises around the globe adapt to more agile work strategies. In doing so, organizations are getting stuck between a complex web of […]

The post Digital workplace aligned to industry-specific personas appeared first on 91¶¶Òő.

]]>
The traditional workplace is undergoing major transformations as enterprises around the globe adapt to more agile work strategies. In doing so, organizations are getting stuck between a complex web of systems, implemented in silos addressing only specific needs of the business, without the benefit of a holistic digital workplace strategy.

With enterprises adopting Work From Anywhere reality, and with the advent of the digital age, Digital Workplace has truly evolved to be digital and is here to stay. Digital Workplace solution needs to be envisioned with end-users forming the core of the solution. It is crucial for an organization to ensure that each end-user has a seamless workplace experience regardless of time and space.

To build an effective Digital Workplace solution with the end-user being at the center, it is imperative for an organization to focus on persona-based services. To achieve this, a well-planned discovery exercise needs to be initiated. Discovery has to be an iterative process that gets refined progressively and incrementally with continuous user feedback.

Accurate Persona mapping is the base for creating truly customized and efficient digital workplace solutions for different verticals.

  • Personas are end-user prototypes that represent the requirements of groups of users, with users aligned with the enterprise’s business goals and therefore exhibiting a specific set of user characteristics. They act as ‘substitutes’ for real users and help guide decisions on strategy, functionality, design, and development
  • Personas help in designing the solution by identifying the user motivations, expectations, and goals responsible for user behavior. They are based on knowledge of real users and imitate the end-user in the digital world
  • Personas also provide a reliable and realistic understanding of how a business could expect a group of employees to embrace the new solution

The problem

The primary reason for discontentment within enterprises that deploy digital workplace solution is their one size fits all approach irrespective of the users’ requirements, their industry segment, technological maturity, and its user’s willingness to adapt to change. The ever-changing technological landscape combined with work from anywhere has made it challenging and complicated for workplace solutions to provide a consistent end-user experience.

Some of the top industry-specific persona examples include and not limited to:

Banking

Supporting on-demand customer requests and managing high customer expectations in remote work scenarios arising due to pandemic-induced lockdowns. A digital workplace solution curated for Banking Professionals enables them to connect with the banking systems remotely and securely for transactional activities in a seamless manner. The solution enables unified collaboration within the staffing ecosystem easing the processes such as inter-departmental approvals, financial transactions, and reporting.

Manufacturing

Managing and maintaining production capacity and other activities with a lower workforce and quick turnaround in case of breakdowns or IT issues. To facilitate remote resolution, the production engineer should have access to event logs, live execution system status, and augmented reality-based smart remote support. Digital Workplace solutions can enable the engineer to seamlessly resolve the breakdown through persona-driven access.

A well-researched and regularly updated set of end-user personas allows in preparing a solution that can manage the scale and complexity of the modern workplace while ensuring end-user delight and cost-saving. 91¶¶Òő’s E3 framework builds a strong foundation for the ‘Digital Workplace’ to be leveraged, a differentiated framework for transforming the end-user workplace. This framework comprises of

  • Experience: Identify User experience journeys through Value Stream Mapping
  • Efficiency: Drive Extreme Automation for an efficient self-service experience
  • Effectiveness: Accelerate adoption for benefit realization

Author:

Shreet Das,
Pre-sales Lead, Digital workplace,
91¶¶Òő

The post Digital workplace aligned to industry-specific personas appeared first on 91¶¶Òő.

]]>
Keeping your data protected from ransomware attack in the new era /keeping-your-data-protected-from-ransomware-attack-in-the-new-era/ Mon, 03 Jan 2022 07:11:34 +0000 /?p=37412 As per IBM X-Force Threat Intelligence report, Ransomware was the top threat type, comprising 23% of attacks. In 2019, the U.S. was hit by an unprecedented and unrelenting barrage of ransomware […]

The post Keeping your data protected from ransomware attack in the new era appeared first on 91¶¶Òő.

]]>
As per , Ransomware was the top threat type, comprising 23% of attacks. In 2019, the U.S. was hit by an unprecedented and unrelenting barrage of ransomware attacks that impacted at least 966 government agencies, educational establishments and healthcare providers at a potential cost in excess of $7.5 billion (). Average Data breach costs increased significantly from $3.86 million in 2020 to $4.24 million in 2021 (). Ransomware attacks cost an average of $4.62 million, more expensive than the average data breach ($4.24 million). Malicious attacks that destroyed data in destructive wiper-style attacks cost an average of $4.69 million.

The number of organizations deciding to pay a ransom has risen to 32% in 2021 compared to 26% in 2020 (). Even after paying for Ransomware, only 8% of them got all their data back, nearly a third, 29%, couldn’t recover more than half the encrypted data. However, on average, only 65% of the encrypted data was restored after the ransom was paid. Approximately 37% of global organizations (more than one third) said they were the victim of some form of Ransomware attack in 2021 (IDC’s “). 92% who pay don’t get their data Back (.

We all know that Confidentiality, Integrity and Availability are the 3 pillars of security. Integrity of Data is an important dimension, which means that data has not been altered in an unauthorized manner when data is “at rest, getting processed, or in transit”. Here we will be focusing only on “at rest” Data related to Ransomware. It’s evident that, while there is a high level of efforts required to prevent “Attackers from getting in” or “escalating their privileges within system” the best bet for an organization remains to “Protect their critical data from unauthorized access and destruction”.

Ransomware attacks focus on encrypting any data to which they could get write access, including the backup system. This may also happen due to poorly implemented permissions that exposed backup data stored anywhere. This makes Ransomware attack more effective because organizations can’t recover data from backup systems.

The big step towards getting data protected is to have isolated, immutable backup of data which is not accessed in general and have very strict administrative access authentication, authorization adjustments for a set of admins. There was a time when data backup on physical tapes were kept off-site to be protected from any Data center physical damage as part of BCP/DR approach. That was one of the best ways to ensure data integrity. We should leverage Cloud offerings which are equally effective to protect data from any Ransomware attack.

Now let’s discuss about immutable backup methods which will be the key ask here. Azure has introduced Blob storage options to operate like an Immutable storage and enables users to store business-critical data in a WORM (Write Once, Read Many) state for a defined time interval. While in a WORM state, data objects can be created and read, but cannot be modified or deleted for a user-specified interval. By configuring immutability policies for blob data, customers can protect their data from overwriting and deletion. Another benefit of Azure Blob storage is having a legal hold, which stores immutable data until the legal hold is explicitly cleared. When a legal hold is set, objects can be created and read, but not modified or deleted. It’s important to understand how immutability is implemented and whether it is truly WORM, even if OS administration accounts are compromised.

Those who are on AWS platform, can use AWS Backup Vault Lock to prevent (accidental or malicious action) any user from deleting their backups or making changes to their backup lifecycle settings. AWS Backup Vault Lock (S3 Glacier) improves customer’s security postures and ensures a mechanism for restore, even in a worst-case scenario like total account compromise. Another service that’s useful for data protection is the AWS object storage S3, where you can use features such as object versioning to help prevent objects from being overwritten with Ransomware-encrypted files, or Object Lock (S3), which provides a write once, read many (WORM) solutions to help prevent objects from ever being modified or overwritten. 

You can use Compliance retention mode if you never want any user, including the root user in your AWS account, to be able to delete the objects during a pre-defined retention period. You can use Legal Hold as an infinite retention period. Once applied it is not possible to delete any object until the hold is released manually (only by users with special permissions). Every backup within the retention period is an immutable backup with point-in-time restore capabilities. Also, we have S3 MFA delete-enabled bucket option which safeguard from permanent delete of an object version or change the versioning state of the bucket.

Similarly, GCP storage containers with Bucket Lock offers write-once (WORM), immutable storage to meet your compliance standards and ensure your data’s integrity while offering instantaneous access for quick restores. As part of protection, once you lock a bucket, you cannot unlock it until all objects are out of the retention period. Retention policies prevent the deletion or modification of the bucket’s objects. Applying Bucket Lock to a storage bucket in the Archive class can help you achieve WORM compliance for long-term data archival as well.

Apart from introducing immutable backup options which provide a secure storage for your data, we all know initial steps such as to keep multiple copies of data backup (keeping data off-site), use a standard practice of Multi-Factor Authentication (MFA) for administrative accounts, separation of administrative roles. We also need to enable encryption of the data and segment the workflow so that authorized systems and users have limited access to use the key material to decrypt the data. We know that network sharing protocols work well for general-purpose file sharing. However, minor mistakes in permissions can lead to data being exposed. In place of using them, we recommend using object storage APIs, for example Amazon S3 compatible APIs, virtual tape libraries, or keep storage as “local” to the backup server (do not access over a network sharing protocols).

Interesting part to understand here is, the technology which was initially introduced for a security compliance requirement to keep the golden copy of any data for later auditing or reconciliation, has taken a shift to be also used to safeguard from ransomware attacks to maintain integrity of data. Cloud storage is an economical solution because resources are readily available, is scalable, and multi-tiered.


Author:

Deepak Kumar,
Cloud Practice Head,
91¶¶Òő

The post Keeping your data protected from ransomware attack in the new era appeared first on 91¶¶Òő.

]]>
Pathway to successful RPA Implementation /pathway-to-successful-rpa-implementation/ Tue, 12 Oct 2021 04:20:20 +0000 /?p=37166 The interest in automation has reached new peaks. Organizations that had invested in automation are successfully riding the COVID-19 crisis. Others are hastily examining how their businesses could leverage automation. […]

The post Pathway to successful RPA Implementation appeared first on 91¶¶Òő.

]]>
The interest in automation has reached new peaks. Organizations that had invested in automation are successfully riding the COVID-19 crisis. Others are hastily examining how their businesses could leverage automation. More specifically, they are examining Robotic Process Automation (RPA) to lower costs and overcome the depletion in workforce that has been a consequence of lockdowns and social distancing requirements. Organizations from Healthcare to Financial Services, Travel, Consumer Packaged Goods (CPG) and Manufacturing will have a higher quantum of automated processes by the time we emerge from the COVID-19 crisis. 

While intent to implement RPA is growing, there are budget cuts to contend with. Organizations have therefore turned cautious, chiefly because they cannot identify the processes, they should automate to unlock the ROI, efficiencies and the bottom-line growth promised by RPA. 

The path to successful RPA implementation is not always evident—and there is justified anxiety that the wrong decisions could produce sub-optimal returns. Processes in the functions like Finance, IT, HR and Procurement usually contribute to maximum number of use cases. Precedents could be one way to resolve the indecision.

Keep efficiency, effectiveness, and experience the focus

Organizations have a variety of stimuli that propels them towards RPA adoption: to drive efficiency, enforce compliance, create a fungible workforce, stay ahead of technology, increase the life of legacy investments, and improve employee morale. However, in the most immediate future, organizations considering RPA would do well to apply the technology to solve their most immediate business problems (see figure 1).

Figure 1

91¶¶Òő has worked with several customers across industries that illustrate the business problems that make ideal use cases for RPA:

  • An airline customer wanted last minute emails received for cargo bookings to be turned into orders in their cargo system. They used RPA to solve the problem
  • A US-based fashion house wanted to convert spread sheets coming in from designers into a Bill of Material and thereafter into purchase orders. RPA was the solution
  • A banking customer wanted real time testing to be done for 300+ mainframe scenarios for new products. RPA-based testing enabled faster time to market

For organizations considering RPA, another way to resolve the problem would be to adopt RPA if it is a customer facing process. These processes always deliver value higher than others.

Get around the uncertainty 

It is natural to be anxious about making investments in RPA. The technology is transformative but unfamiliar. Our experience shows that organizations are most concerned about selecting the right platform, they are unclear if their processes are ready for automation, if their business cases can withstand the test of time, and how quickly they will see ROI. 

  • Rule of Five: Our advice to organizations dipping their toes in RPA for the first time is relatively simple. Identify five processes that run across five application used by jobs that follow business rules and have little movement. We call it the Rule of Five. It provides a safe and quick test ground to understand what works for your organization and what doesn’t
  • Process characteristics: The other approach to identifying the right use cases is to look at RPA to address tasks with a high volume, that are sensitive to speed, that are generally error prone and have irregular labor demands
  • Part of digital transformation: Many organizations are gravitating towards the thought that RPA is not just a way to mitigate costs or improve operational efficiency but as a key component of their digital transformation agenda (added to the list of strategies that include data, analytics, social, and mobile)

Going wrong is not failure – it is learning

A CPG customer got 91¶¶Òő to help identify process that could be automated. After process mining and value modelling, we identified 10 processes ripe for RPA. The customer wanted six automated. However, we soon realized that not one of the six could be automated because the process templates were not standardized. The program had to be put on hold, the processes standardized, and the program re-started. But failure is not always a reason to bring an RPA program to a halt. It is often an indicator of a need for course correction. 

Another CPG customer opted for a “fail fast approach” and started RPA implementation using a low scale product that did not touch their ERP. As adoption increased, SAP users in the organization also wanted to implement RPA. The customer realized the need for a product with larger capability and chose Automation Anywhere.

Anxiety around RPA vaporizes as adoption increases. Typically, organizations with less than 10 bots have challenges around process selection and business case creation. Organizations with 10 to 50 bots have challenges around governance, establishing operating models and modifying processes for automation. Organizations with over 50 bots cement an automation first cultural and nurture an RPA talent pool that ultimately sees the emergence of citizen developers.

Learning from experience

Our experience of working together provides insights that are worth sharing. When we decided to provide every one of our 9,000 employees with a bot – called Digital Buddy – we got Automation Anywhere as the expert services partner to assist in developing the bots and in managing change. We knew that our young and agile workforce wanted IT to help them move at speed. Our employees were eager to get their hands-on new technology and learn how to subsequently apply it to solve customer problems. Internally, we also realized there was more work than available skills. All the pieces necessary for RPA to find acceptance and deliver value fell in place. 

Today, we have the expertise to deliver RPA projects to customers using an extensive bot library, through our automation-as-a-service offering and a catalogue of automatable processes based on experience. 

Tomorrow’s economy will be led by digital workers that leverage RPA, with humans required for more cognitive work. Learning to tread the pathway to successful RPA implementation is therefore an urgent need today.


Author:

Sumeet Pathak,
Senior Director, Digital Innovation and Solutions,
Automation Anywhere

Mayank Jain
VP, Business Consulting Group,
91¶¶Òő


 

The post Pathway to successful RPA Implementation appeared first on 91¶¶Òő.

]]>
End-user experience and remote working during COVID-19 & beyond /end-user-experience-and-remote-working-during-covid-19-and-beyond/ Thu, 26 Aug 2021 14:13:21 +0000 /?p=36763 Remote working has been a steadily growing trend over the last decade. In the US, Census Bureau figures show it has grown 4X over the last 10 years, from 9.5% […]

The post End-user experience and remote working during COVID-19 & beyond appeared first on 91¶¶Òő.

]]>
Remote working has been a steadily growing trend over the last decade. In the US, Census Bureau figures show it has grown 4X over the last 10 years, from 9.5% working remotely at least once a week to 36% doing so now. Those numbers are likely to get a massive boost because of COVID-19. Microsoft Teams provides a clear indicator of the shape of things to come. It has reported a rise in usage from 900 million meeting minutes a day in mid-March 2020 to 2.7 billion minutes a day in early April. Every indication shows that remote working is set to be the default mode and become the “new normal”. The outcome of this is reflected in a study of over 500 venture-backed companies that showed 66% of founders were reconsidering their investments in their offices while 65% said they would not return their companies to the office.

The trend will force organizations to bring heightened attention to delivering exceptional end-user experiences on one side and building new support services and processes on the other to enable smooth remote working (see Table 1 for ‘What has COVID-19 changed?’). This is because users can no longer visit ‘tech bars’ (areas dedicated to IT support teams) or expect support teams to come to their desks to resolve issues. The problem is compounded by organizations’ having relaxed their norms around personal devices while, simultaneously, they have become cautious about their IT spends.

What has COVID-19 changed?
For end-users For IT support teams
Remote working/ distributed work Overwhelming tickets and call volumes
Remote meetings Infrastructure unable to handle support volumes
Virtual teams Security and connectivity issues with employee-owned devices
Scramble for stable internet bandwidth Digital transformation gaining speed

From SLAs to eXLAs

Organizations must work around their traditional notions of what comprises end-user experience to meet rising expectations. The old-fashioned concept of SLAs will need to be replaced by Experience Level Agreements (eXLAs) because users want everything faster. Organizations too are waking up to SLAs being misleading, resulting in undocumented productivity loss. For example, a user may log a ticket for a technical problem for which the SLA could be 20 minutes. A 100 such tickets every day for a mid-sized organization would work out to over ~500-man days lost every year. Meanwhile, the support dashboard would show “all green” because SLAs are being met. Invisible to management, users would have experienced the frustration of long waits and loss of productivity (see Figure 2 for what users do when faced with slow support).

The way to change this is to connect user experience and productivity. This can be done by leveraging automation and self-help and self-healing processes. Consumers—and we all are consumers—have become accustomed to managing tasks like “change password” and “install application” independently. Over the last decade, we have been doing this on our mobile phones with routine ease. But organizations are not geared to provide the same experience. The first thing you hear in an organization at the slightest hint of trouble is, “Have you logged a ticket?” The ticket is the center of service and experience. Not the user.

But when experience and productivity are connected using automation and self-help, there is a dramatic improvement in user experience (see Figure 3 for the change in user satisfaction between hands and feet support and self-help/automation).

The trick is to move the user to the core of the support process. This is where structuring the “new normal” begins (see Figure 4 for the structure).

In the new normal, interactions with users must move a notch up. They must become multi-lingual and intelligent. This can be achieved by using AI-enabled chatbots that don’t just refer to an FAQ but execute solutions for the user. This can also be supported by intelligent IVR that goes beyond the “Press-1-for-password-reset-and-2-for-agent-support.” IVRs can be made intelligent to identify the user by name with voice bots using natural language processing (NLP). These interactive bots should ensure that users need not refer to several apps, say from Workday and PeopleSoft or the intranet and a website but they should be contained to deliver app outcomes from within these bots. The user must not struggle to navigate to sources of information. Instead, the system should become a single window for all information, binding all information as a single source of truth. Finally, the system needs a strong wrapper of governance to take care of how data is managed and shared.

Levers to create the new normal

Most mid-sized organizations would have automated up to 10% of their support processes. The target should be to have self-service systems, automation and bots to manage in excess of 70% of these processes, freeing up time for agents at the service desk to attend to complex troubleshooting. The path to achieving this is by using six levers of transformation spanning self-service, intelligent automation, etc. (see details in Table 2).

Six levers for transformation

Lever Goal Focus
1 Self-service End user empowerment
  • Shift left
  • Multi-channel delivery
2 Robotic Automation Digital workplace
  • Chatbots and RPA
  • AI-enabled smart response
  • Orchestrated automation
  • Portals
3 Centralize and Optimize Service management
  • Integrated service model
  • Centralized and optimized service desk
  • Near-zero wait time
4 Defined Outcomes Service level
  • Quality of experience
  • Improved plans
5 Driving Change New ways of working
  • Get the work done using SMS, IVR, mobiles
  • Enabling BYOD
6 Simplification Strategy Simplified management
  • Ease of management with single pane of glass

How does the organization know that its efforts and investments in delivering user experience and support for remote employees and distributed workforce are effective? Currently, the processes to measure the impact of interventions are long-winded and complex. These processes need to be simplified, without which organizations will continue to get responses from two polar ends of the experience spectrum: those who are extremely unhappy and those who are extremely happy. This creates misleading perceptions. Instead, eXLA should be measured besides SLA covering channels such as chatbots, live agents, email, and instant messenger. To ensure that effectiveness can be measured the use of “Digital Experience” platforms becomes a must and compiling data from end user devices on performance and intelligence becomes important. In addition to this user sentiments should be captured in form of the response from users which can be collected using simple methods like gestures – thumbs up/down, likes / dislikes and smileys. Regular SLA metrics are always an important element to complete the 360 degree view. These can be translated into scores, providing more accurate insights into user experience. 

What does the new user experience look like?

An example of a typical session using an intelligent AI-driven bot helps understand how new support systems need to work. Assume that a user logs into the system to seek assistance with installing an application. Instead of dashing off an email to the service desk (or calling a service desk and waiting endlessly in a queue), the user interacts with a text-based chatbot that has identified the user by name. The bot presents a list of the top common queries to the user. In this instance, the user selects, “Install app” and the bot immediately lists the applications authorized for the role and which are not currently installed on the user’s system. The user selects the right application and the bot completes the installation. At the end of the processes, the user clicks on thumbs up/ down, like/dislike button to provide feedback.

A non-IT use case helps appreciate this further. Assume you are the user and you want a list of holidays. The chatbot lists holidays applicable to you using your role/ location/place of work. The bot understands that you may want to apply for leave and therefore presents you with a “My leave balance” prompt. You click on the prompt and the bot looks up your leave balance, displays it, and helps you complete a leave application. At the backend, the bot looks up a variety of systems from the intranet for the list of holidays to Workday to complete HR processes. You need not switch applications and hunt around for links. 

When the bot encounters a query it cannot respond to, the session is handed off to a live agent. The agent gets a copy of the entire interaction history with the bot and can understand the context of the query. The query can then be resolved using several channels from SMS to social media. 

At the back end, the interaction is captured on a dashboard as a new problem for which the knowledge base has to be created/improved so the bot can handle it independently the next time, without having to escalate it to a live agent. 

Organizations must up their game with remote/distributed work becoming a reality. End-user experience will play a major role in determining if your remote working initiatives succeed or not. If they put the user at the center of the process, success will be assured.


References:


Author:

Sujoy Chatterjee
VP, Infra Managed Services,
91¶¶Òő


 

The post End-user experience and remote working during COVID-19 & beyond appeared first on 91¶¶Òő.

]]>
Humanize Bots to maximize the benefits /humanize-bots-to-maximize-the-benefits/ Tue, 17 Aug 2021 07:32:34 +0000 /?p=36725 Video Blog (vlog) – Humanize Bots to maximize the benefits ï»ż Robotic Process Automation (RPA) has caught the attention of CXOs who are grappling with the  business impact induced by […]

The post Humanize Bots to maximize the benefits appeared first on 91¶¶Òő.

]]>
Video Blog (vlog) – Humanize Bots to maximize the benefits

Robotic Process Automation (RPA) has caught the attention of CXOs who are grappling with the  business impact induced by the COVID pandemic.   It is no longer a luxury but a business imperative to bring in automation in order to save time & costs, gain efficiency and provide more work-life balance to employees by allowing them to focus on higher value tasks while the bots take care of the mundane, repetitive tasks.

This frenzy has led many organizations to take the plunge into automation with most of them being at some stage of either piloting RPA or having deployed a few bots in production. It all seems very lucrative and thus very high expectations are set from the onset about the success the bots will bring for the company. But then, reality strikes, and most companies see that the outcomes aren’t really what they had expected. There are issues in scaling the bots beyond the initial few, issues with maintenance and frequent modifications required for handling different scenarios and paths for the same process, and updates required when the IT systems undergo a change. This results in a long and steep learning path for the companies that brings with it the frustration and a misdirected agony towards the usefulness of RPA.

But is it really the bots that are to be blamed for the problems being faced by such companies? Why is it that RPA is working like a charm for some companies while others are struggling to crack the code? 

It has to do with the way the successful companies look at (read as: treat) bots.

By humanizing bots and incorporating the following practices, companies can  derive maximum value from the investments made in RPA.

Treat them as  digital employees and name them

The premise of ‘Virtual Workforce’ is based on treating bots as digital employees. It is only natural to think so about bots. After all, the bots work 24×7, doing tasks that are   repetitive and mundane for humans. But treating them as employees and naming them gives them more mind space and top of the mind recall during change management. When employees name their digital assistants, they think of bots more like junior team members who report to them and help them with their daily tasks.

Give time and team to maintain the bots and look after them 

Just like humans, bots can also fall sick and have breakdowns. What’s important to note is that just like humans, there is a reason behind their falling sick. In most cases, the reason tends to be associated with change management aspects. When there is a process change in the traditional world (where people are managing the processes), documentation upgrades and training are part of the change management plan. This helps the operations teams to manage the changed processes effectively. But this is often not the case with automated processes. By thinking of bots like people, the team thinks about them during change management and caters to their needs just like the needs of people being impacted by the change. This makes sure that they are looked after, and the team keeps getting the benefits they originally got by keeping the bots working.

Build resilience into the bots

Processes can break for several reasons, whether being done by humans or bots. It could be due to bad data, unavailable source/target application, network connectivity, or any number of other reasons. Just like humans take alternate routes or steps to resolve the issue and move forward, so should the bots be able to. But bots won’t do this until they are trained  on it. Many a times, bot designers and developers consider only the ‘happy path’ while building the bots. When creating or training the bots, the ‘unhappy paths’ or ‘exception scenarios’ should also be considered, and the bot should be trained on what to do if such a scenario occurs. This not only keeps the bots running more efficiently, but also reduces maintenance and support efforts when they hit the ‘unhappy path’ because there are proactive actions built into the bots to handle such situations.

Manage the performance of bots like it’s done for people

People performance management is one of the most important aspect that is taken up in every organization. We pay a lot of attention and effort to make sure our people have the right toolset and mindset to perform at their best possible levels. Seldom does it ever happen for the bots deployed in the organization. By making sure that there are people assigned to monitor and manage the performance of the bots, we can make sure that the bots are performing at their best possible levels. With the new age automation platform, this is quite easy as they come with built-in performance dashboards and bots that monitor the performance of process bots and run diagnostics to make sure the overall performance is at expected levels. In addition, staff in the different business units with live bots can also access real-time dashboards that display the performance of the bots deployed in their unit.

Measure the success by number of automated process

Another common practice in organizations implementing automation is to measure the success of the program by the number of bots deployed. We often come across news flash about how an organization successfully deployed 100 RPA bots in 6 months’ time. Ideally, this should not be the measure of success. The true measure of success should be the number of processes automated by the bots. Don’t think about how many bots are deployed. Think instead, about how many processes can be run with a bot. When humanizing it, think of how many tasks or jobs a person can do in a day, then expand that across the bots running 24×7 and think of how many tasks can the bot do.

Conclusion

Initially it might seem a bit far fetched to think of a bot as a human and to take into consideration of the bot when thinking of process optimization. The business units need to work in collaboration with IT to make sure the bots are set up in a way that maximizes return on their investment. 

While looking at optimizing a process, planning for it with the bot in mind is different from planning for it with a human in mind. When optimizing a process with a human in mind, we would look to reduce the number of steps. When optimizing a process with a bot in mind, the more important factor should be the efficiency the bot brings, even if it means having a greater number of steps. 

Remember, the bot doesn’t mind doing more steps in a process since it’s executing them at a much faster pace than human. If the overall efficiency of the process improves, then that is a  trade-off that we should be in favor of. 

In short, giving bots names gives them a profile that has top of the mind recall and makes sure they are considered during the change management process. Also, when designing the bots, building fail safe mechanism by considering exception scenarios goes a long way to keep them running. Performance management for bots, just like for humans makes sure the company is getting its targeted  ROI and like humans, focus on how many processes the bot can handle rather than how many bots the company has.

Making the above mentioned psychological / behavioral changes to our outlook towards RPA bots can go a long way in improving the efficiency the bots bring while making sure the company is getting back the  ROI on the RPA initiative.

At 91¶¶Òő, we take this psychological approach and have embedded it into the DNA of the company’s approach to RPA. That is the reason why we have embarked on a journey to provide every employee (~9500) with a personalized digital buddy  that will make their life easier. And we have been able to successfully deploy close to 20 digital personas for various functional roles to help people in their daily work. Talk to us if you’d like to know how 91¶¶Òő can help make digital workforce a reality for your company.


References:

  1. Everest Group – RPA Annual Report 2018 – 
  2. The Future Digital Work Force: Robotic Process Automation (RPA) –
  3. Gartner’s 2019 Predictions for RPA Offerings –
  4. Optus brings bot needs into IT change planning –

Author:

Tanmay Prakash
Senior Principal Consultant, 
Business Consulting Group, 91¶¶Òő


 

The post Humanize Bots to maximize the benefits appeared first on 91¶¶Òő.

]]>