According to the ITIL 4 Specialist: High Velocity IT course, what are the five key objectives that organizations should aim to achieve when adopting a high-velocity IT approach, and how do they interrelate?

In the context of ITIL® 4 Specialist: High Velocity IT (HVIT), adopting a high-velocity approach is not merely about increasing speed. It is about enabling digital organizations to achieve their business goals rapidly and effectively. To guide this transformation, ITIL 4 outlines five key objectives that an organization must focus on. These objectives are interconnected and work together to create a holistic system that balances speed with stability, value, and compliance.

The Five Key Objectives of High Velocity IT

These objectives provide a framework for organizations to ensure their digital transformation efforts are comprehensive and sustainable, moving beyond siloed improvements to create systemic business agility.

1. Valuable Investments

This objective focuses on ensuring that all IT initiatives and investments are strategically aligned with business outcomes and deliver maximum value. In a high-velocity environment, where resources can be consumed quickly, it is critical to make smart, data-driven decisions. This involves more than just a traditional business case; it requires a continuous and dynamic approach to investment.

• Prioritization: Using techniques like weighted shortest job first (WSJF) or cost of delay to prioritize features and projects that will deliver the most value in the shortest time.
• Minimum Viable Products (MVPs): Focusing on delivering MVPs to the market quickly to test hypotheses, gather user feedback, and validate that the investment is on the right track before committing more resources.
• Portfolio Management: Actively managing the portfolio of digital products and services to ensure they continue to align with changing business strategies and market demands.

2. Fast Development

This is the most intuitive objective of HVIT. It centers on accelerating the entire lifecycle of digital products and services, from the initial idea through to deployment and operation. The goal is to dramatically reduce the lead time for changes and new features, enabling the organization to respond quickly to opportunities and threats.

• Agile and DevOps Practices: Adopting methodologies like Scrum and Kanban, along with a DevOps culture of collaboration and shared responsibility between development and operations teams.
• Automation: Implementing a fully automated Continuous Integration/Continuous Delivery (CI/CD) pipeline to automate the building, testing, and deployment of code.
• Small, Frequent Releases: Breaking down large projects into small, manageable batches of work that can be developed, tested, and released independently and frequently.

3. Resilient Operations

Speed without stability is a recipe for disaster. This objective emphasizes the need to build and maintain highly reliable and resilient services, even in an environment of constant change. The focus shifts from preventing all failures (which is impossible) to ensuring services can recover from failure quickly and automatically with minimal impact on users.

• Designing for Failure: Utilizing architectures like microservices and cloud-native patterns that are inherently resilient.
• AIOps and Observability: Leveraging AI for IT Operations (AIOps) and comprehensive monitoring (observability) to predict, detect, and automatically resolve issues before they impact customers.
• Chaos Engineering: Proactively injecting failures into systems in a controlled way to identify weaknesses and improve resilience before an actual outage occurs.

4. Co-created Value

This objective fundamentally changes the relationship between the IT organization and its consumers (both internal and external). Instead of a simple service provider-consumer dynamic, HVIT promotes a partnership where value is created together. This requires a deep understanding of the customer's journey and needs.

• User-Centric Design: Employing techniques like Design Thinking to empathize with users and design solutions that genuinely solve their problems.
• Continuous Feedback Loops: Integrating user feedback mechanisms at every stage of the service lifecycle, from initial idea to live operation, to continuously refine and improve the product.
• Shared Goals: Ensuring that IT teams and business stakeholders have shared objectives and are jointly accountable for the value delivered.

5. Assured Conformance

High-velocity environments must still operate within governance, risk, and compliance (GRC) constraints. This objective is about ensuring that these requirements are met without becoming a bottleneck that slows down delivery. The key is to integrate GRC activities directly into the automated value stream.

• DevSecOps: Shifting security and compliance "left" by integrating automated security scanning, policy checks, and compliance validation into the CI/CD pipeline.
• Compliance as Code: Defining compliance rules and policies as executable code that can be automatically checked and enforced.
• Shared Responsibility: Fostering a culture where everyone on the team, not just a separate GRC department, is responsible for meeting conformance requirements.