High-velocity IT: Speed, Culture and Resilience
High-velocity IT is about succeeding in a volatile, uncertain, complex and ambiguous (VUCA) environment: digital transformation, agile, lean and DevOps ways of working, and operating models that are both fast and resilient.
Objectives
High-velocity IT pursues five objectives: valuable investments, fast development, resilient operations, co-created value and assured conformance.
Ways of working
- Lean: optimize flow, eliminate waste, limit WIP, respect people.
- Agile: iterative delivery, fast feedback, cross-functional teams.
- DevOps: culture, automation, lean, measurement and sharing; CI/CD; everything as code.
- Techniques: loosely coupled architecture, feature toggles to decouple deployment from release, canary and blue-green releases, chaos engineering, observability, service level objectives with error budgets, blameless post-incident reviews, technical debt management.
Culture and resilience
A generative culture lets information flow freely and analyses failure rather than punishing it. Psychological safety and antifragility - improving after a shock, not merely surviving it - are operating assets, not soft extras.
Worked example
A bank wants weekly releases instead of quarterly. Deployment is decoupled from release with feature flags; blue-green deployment and automated tests cut deployment risk; an SLO with an error budget pauses feature work when reliability degrades. Reasoning: velocity rises while conformance is assured by automated, embedded controls rather than by a slower approval queue.
Traps
Reducing DevOps to a toolchain. Applying high-velocity techniques without risk proportionality in regulated change. Equating resilience with redundancy. Ignoring technical debt until it caps delivery speed.