Driving optimization in IT Transformation Programs

Transformation programs are designed to bring about significant changes to an organization's processes, systems, and culture. These programs often involve the implementation of new technologies, the redesign of workflows, and the adoption of new ways of working. While transformation programs can bring many benefits, they can also be complex and challenging to manage.

 One way to increase the chances of success in a transformation program is to apply Lean principles. Lean is a management philosophy that emphasizes the continuous improvement of processes and the elimination of waste. It is based on the idea that value is created for the customer through the continuous flow of value-adding activities, and that waste is any activity that does not add value. 

There are several reasons why Lean interventions can be beneficial in transformation programs:

1. Lean helps to focus on the customer: By understanding the needs and expectations of the customer, organizations can design processes that deliver value and eliminate waste.
2. Lean promotes continuous improvement: Lean encourages organizations to continuously seek out ways to improve processes and eliminate waste, which can help to drive progress in a transformation program.
3. Lean helps to reduce waste: By identifying and eliminating non-value-adding activities, Lean helps to streamline processes and reduce costs.
4. Lean promotes collaboration: Lean encourages collaboration and transparency, which can help to build trust and foster a culture of continuous improvement.

 The application of Lean principles can be a powerful tool to support the success of transformation programs. By focusing on the customer, continuously seeking out improvements, reducing waste, and promoting collaboration, organizations can increase the chances of achieving their transformation goals. There are a number of engineering metrics that can be tracked and optimized using lean levers. Some examples include:

1.  Lead time: This is the time it takes for an idea or feature to be developed and deployed to production.
2. Deployment frequency: This is the number of times that code is deployed to production in a given period of time.
3. Defect density: This is the number of defects per unit of code.
4. Code coverage: This is the percentage of code that is exercised by automated tests.
5. Code review turnaround time: This is the time it takes for code reviews to be completed.
6. Code review acceptance rate: This is the percentage of code reviews that are accepted without requiring changes.
7. Velocity: This is the rate at which work is completed over time.
8. Code reuse: This is the percentage of code that is reused across multiple projects or modules.
9. Mean time to recovery (MTTR): This is the average time it takes to recover from a production issue.

 It's important to choose the right metrics to track, as they can provide valuable insights into the efficiency and effectiveness of your engineering team. Similarly it critical to identify the right metric to optimize to help alleviate the right challenge being faced by the transformation program at the right time.  Feel free to add on any more metrics you track in your programs.