<\/p>\n At this point, your organization should have a generic understanding<\/a> of automation or only a single provider or vendor that builds the automations. This builder should create the automations from a proof of concept or highly specific to a small team. All development and support for the automation program are handled in a very scrappy way.<\/strong> Let us look at how we can move to the next stage, focusing on four main areas: organization, operations, enablement and reporting.<\/p>\n In the previous stage, we focused on the next three to five years and envisioning the future of your organization enabled by automation. Now, we\u2019ll transition into a strategy that will guide your company through those years. This strategic approach is critical because it allows you to think about how automation will impact your organization and how that should shape your business strategy going forward.<\/strong><\/p>\n In building this strategy, you should focus on key business areas that need improvement or extra oversight and governance. You should also consider aligning technology and business stakeholders to ensure you\u2019ve well-defined the strategy. This process will make sure you can move forward confidently knowing your organization is on the right path.<\/p>\n Implementing an automation center of excellence is a suitable place to align stakeholders and drive the strategic intentions of your automation efforts. We highly recommend building out a COE. You can even build it in a federated model as part of a larger COE or governing body. Having a governing body \u2013such as a COE \u2013 run your program ensures this alignment, but it also provides a place for technical and subject matter experts to interact and keep the momentum moving forward.<\/p>\n Going back to our lawn care example from earlier in the blog series, the COE is like the family maintaining their lawn. There are many needs like picking up sticks and leaves, edging sidewalks or pruning weeds. After looking at all these maintenance needs, the family identifies how they align with projects or tools they may also need. They can handle sticks and leaves by picking up the large sticks and mowing the rest to mulch them. They can use a lawn sweeper attachment after mowing or simply allow the mulched leaves to stay in the yard. Even further, the family could invest in a leaf blower to consolidate their lawn refuse.<\/p>\n These lawn care needs may seem trivial, but they relate to how you identify business needs.<\/strong> For example, you could identify an automation tool, such as Microsoft\u2019s Power Automate, that does great at system-to-system integration to handle multiple scenarios for you (like the mulching lawn mower with lawn sweeper attachment). Or, you could identify marketing automation needs that require a more specific tool (using a leaf blower instead of allowing leaves to pile up).<\/p>\n With the COE as the governing body of your automation program journey, you should identify the appropriate roles and individuals who require training. You should define these roles as standards for areas where you will implement automation.<\/p>\n For example, implementing robotic process automation<\/a> (RPA) into a new area requires a team champion who understands how RPA bots work and the procedure the bot will complete.<\/strong><\/p>\n You should also define roles and responsibilities to oversee the automation process \u2013 software developers who are experts in their field and quality assurance team members who can identify when errors occur. These quality assurance team members are not specific to departments but are more generalized support for larger areas of the organization.<\/p>\n You can also design the automation program to help broaden automation awareness among the general population by creating assets and education materials with the potential to change the narrative around automation. It is important to note the ultimate goal of the automation program is not to replace people with automation but to help people understand how these changes and updates will affect them.<\/p>\n Operationalized automation COEs formalize their intake process and backlog by defining scoring rubrics and criteria. This step ensures they can take in more requests and prioritize them so they can use available resources for fulfillment.<\/strong><\/p>\n You can build a formal intake process using forms or spreadsheets. An analyst who can confirm viability and potential ROI should verify the submitted ideas from users. This analyst should also review other important prioritization metrics such as cost and development time, complexity, expected exception rate, readiness for automation of the team, the ability of the systems to be automated and reusability of components in the automation.<\/p>\n When scoring opportunities, finding the right mix of projects for your organization\u2019s overall goals is important. One of the COE\u2019s jobs is to make sure that even though a project may look like it should be the highest priority, they know when the team should or should not take it on.<\/p>\n For example, if an automation takes data filled in from a website and inputs it into a CRM, this may sound like a great idea. However, the COE knows the roadmap of the CRM tool and would know the company is replacing the CRM in two months with this included feature. This request now becomes a bad project to recommend as a high priority.<\/strong><\/p>\n Taking those first steps towards intake and prioritization gives the team something to react to, build on and develop into standards or documentation they can use moving forward.<\/p>\n An operationalized automation delivery<\/a> and support model has defined standards, processes, tools and documentation for automating a business process. Ensuring that all automations and developers follow the same practices and standards provides you with quicker time to development, cross-training and easier support.<\/p>\n When building these standards and frameworks, consider naming standards across the organization and other key components you use. For example, if there is a standard way for automation or service accounts to bypass multifactor authentication, then document and follow that method throughout the frameworks you build.<\/strong> Additionally, understanding your organization\u2019s software development lifecycle (SDLC) and building that into the planning process of projects sets your program up for success.<\/p>\n Many organizations forget about automation education for support teams. This is the time to provide training or resources to support staff. This could include a full- or part-time support team that aids in these areas as part of the COE. If a helpdesk or support staff already exists, make them aware of automations and how to troubleshoot to ensure the automation program is a success.<\/p>\n To best separate development from production, we suggest matching the number of automation environments<\/a> to the number of environments of your core software. For example, if you have three environments for your core software, then you should also have three automation environments. This practice will help reduce the risk of having a mismatch between the environments and ensure enough resources are available to support them.<\/p>\n Remember to follow best practices around patching, naming standards and other regular maintenance for these environments just as you would for a line of a business system. Automation environments are not only for developers, but they are also important to operations teams. An out-of-date automation environment or data that does not match the production environment can cause issues when running automations in that environment.<\/p>\n It is also best practice to use a naming convention for your automation environments that is different than one used for production systems.<\/strong> This will help avoid confusion among support staff and prevent errors during runtime.<\/p>\n Similar to delivery and support, we should also look carefully at code standards and frameworks. The lens we should specifically look through centers on reusability and library components. For example, if building an RPA bot using UiPath, modifying the REFramework will be easier than building your own. This is because developers built the REFramework with RPA in mind, and other developers have already built on top of it.<\/p>\n Taking time to build out a component library of reusable components can also be a worthwhile investment.<\/strong> This is because it will make writing future bots faster and more efficient. With a component library, you can reuse the same components across multiple projects, making your work more consistent.<\/p>\n The goal of reporting at the operationalized stage is to review and audit the performance of your automation program to ensure it is performing as expected. This includes measuring the inputs and outputs of your bot, as well as the time taken for each action. Share these stakeholders and leaders on your center of excellence and across your organization to help provide insight into the benefits of automation.<\/p>\n The operationalized stage is all about making sure the foundations of your automation program are strong enough to support future developments and provide a way to scale the initiative. This includes building a center of excellence<\/a>, establishing the metrics to measure your program\u2019s success, implementing ways to improve and optimize your bot, and verifying your team is ready for the next steps.<\/p>\n Next, we\u2019ll look at how communicating strategy across the organization can help drive more dedicated automation resources.<\/strong> We\u2019ll also discuss how to scale to use technologies that cover more use cases.<\/p>\n\n ![\"Automation](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2022\/11\/blog_BPM-RPA-Maturity-Stages_1-3_11292022-1024x840.jpg\")
<\/a><\/p>\nOrganization<\/h2>\n
Vision, Strategy and Alignment<\/h3>\n
Education and Training Talent Under Your Center of Excellence<\/h3>\n
Operations<\/h2>\n
Your Center of Excellence\u2019s Intake and Prioritization<\/h3>\n
Automation Program Delivery and Support<\/h3>\n
Enablement<\/h2>\n
Technology Best Practices<\/h3>\n
Governance and Standards<\/h3>\n
Reporting on Automation Performance<\/h3>\n
Conclusion<\/h2>\n