Governance and Operations

 Automation is an ongoing process that needs regular upkeep and constant improvement. This is crucial because automation works with multiple systems, and these systems can change over time. 

For example, an automated workflow in a business might need adjustments if the software it interacts with gets updated. 

Additionally, we need to improve automation based on the results of previous deployments. If a new version of an automation tool performs better, it’s wise to upgrade to that version.

It's helpful to treat automation projects like any other IT projects. For instance, run them using agile methods with business stakeholders providing input. This approach ensures that the project stays aligned with business needs. Define clear Key Performance Indicators (KPIs) to measure success and Return on Investment (ROI). 

For example, if an automation project aims to reduce manual work by 50%, track this KPI to see if the goal is met. Or is the cost saving expected in the business case really happening.

Governance becomes more important with low-code tools that let non-IT users create their own automations. To manage this, implement strict change and release management processes. 

For example, have an architecture board review all new automations to ensure they meet both functional and non-functional requirements. Lastly, keep the automation team size optimized, ensuring it doesn’t grow larger than the savings it generates.