Interest in DevOps has grown steadily since the movement emerged from the practitioner community in the late 2000s. Yet for many senior and middle managers, the concept can still feel abstract. DevOps does not have a single authoritative definition, it did not originate from a standards body or a major vendor, and its benefits are not always expressed in the language that executives find most persuasive. This article explains what DevOps actually means, why it matters at an organisational level, and what management at every level needs to do to make it succeed.
What Does the Term DevOps Mean?
DevOps is a compound of software development and IT operations. It emerged as a grassroots movement of developers and operations professionals who wanted to change the way organisations build, deliver and run software. The core idea is straightforward: the two disciplines that have traditionally worked in separate silos — development and operations — need to collaborate continuously rather than hand off work over a metaphorical wall.
In practice, DevOps encompasses three interconnected dimensions:
- Culture: shared responsibility for software delivery and reliability across development and operations teams.
- Process: lean, iterative workflows with short feedback loops, continuous integration, and continuous delivery.
- Automation: tooling that reduces manual toil, enforces consistency, and accelerates deployment pipelines.
For management, the most important dimension is culture. Technology can be procured; cultural change must be led.
Why Adopting DevOps Practices Matters
Modern customers expect software-driven services to be reliable, fast and improving continuously. That expectation puts pressure on every organisation — regardless of industry — to deliver working software more frequently and at higher quality. At the same time, computing infrastructure is growing more complex, spanning on-premises systems, public cloud platforms, containers and microservices.
The conventional approach to software delivery was not designed for this environment. In a traditional model:
- Developers are incentivised to ship new features as quickly as possible. Their accountability ends when code is handed to the operations team.
- Operations teams are incentivised to keep infrastructure stable. They inherit software they did not build, under pressure to deploy it safely while also managing costs, user accounts, capacity and security.
These objectives are structurally opposed. Developers want to change things; operations teams want to keep things stable. The resulting friction causes slow deployments, poor reliability and organisational dysfunction that no amount of tooling alone can fix. The root cause is misaligned incentives and a lack of shared accountability — a cultural problem that requires a cultural solution.
Management Has a Powerful Role to Play
The annual State of DevOps Report, produced by Puppet and co-authored with industry researchers, has surveyed tens of thousands of technical professionals over multiple years and consistently finds that leadership behaviour is one of the strongest predictors of IT and organisational performance. The 2017 edition highlighted several findings relevant to management:
- Automation drives performance: High-performing organisations had automated a significantly greater proportion of their configuration management processes than low performers, allowing them to spend far less time on manual, error-prone tasks that slow down delivery.
- Transformational leadership correlates with high-performing teams: Teams led by managers who exhibit vision, inspirational communication, intellectual stimulation, supportive behaviour and personal recognition consistently fall into the highest performance tiers.
- Lean product management accelerates delivery: Organisations that adopt lean practices — small batches, frequent releases, customer feedback loops — deliver value to customers faster and improve more rapidly than those using traditional project-based delivery models.
The implication is clear: DevOps transformation does not happen from the bottom up alone. Leadership must actively sponsor, model and reinforce the cultural changes required.
Considerations for Middle Management When Adopting DevOps
Middle managers sit at the intersection of strategic direction and day-to-day execution. They are frequently the difference between a DevOps transformation that gains traction and one that stalls. Three principles are particularly relevant at this level:
1. Systems Thinking and Flow
Optimising a single team or department in isolation rarely improves the overall system. Middle managers need to understand the end-to-end flow of work — from a business idea through development, testing, deployment and operation — and identify the constraints that slow it down. This requires visibility across teams: shared dashboards, automated metrics and a culture of transparency about status and blockers.
2. Fast Feedback Cycles
Short, frequent feedback loops allow teams to detect and correct problems quickly, before they compound. Middle managers can enable this by removing bureaucratic gates that delay information flow, encouraging automated testing and monitoring, and ensuring that teams act on what they learn rather than filing results away.
3. Experimentation and Continuous Learning
Continuous improvement depends on the ability to run experiments, measure outcomes and change course. Middle managers play a decisive role here: if the culture punishes failure, people stop experimenting and the organisation stops learning. Managers must actively create psychological safety — making it clear that a well-designed experiment that disproves a hypothesis is a valuable outcome, not a career risk.
The Role of Upper Management in DevOps Transformation
Senior leaders set the conditions in which DevOps either thrives or withers. Their responsibilities in a DevOps context include:
- Modelling acceptance of failure: When senior leaders publicly acknowledge that experiments can fail without blame, middle managers and teams follow suit. This signal must come from the top; it cannot be mandated by middle management alone.
- Allocating budget for learning: Research, training, conference attendance and dedicated innovation time all require funding. Organisations that treat these as costs to be cut signal that learning is not truly valued.
- Aligning the rewards system: If performance reviews and bonuses still reward individual heroics and feature throughput rather than reliability, collaboration and system-level outcomes, the incentive structure will undermine every DevOps initiative. Senior leaders own the rewards system and must align it with DevOps values.
- Communicating a clear vision: DevOps transformation requires sustained effort across months or years. Senior leaders must articulate why the organisation is changing, what success looks like and how progress will be measured — and then repeat that message consistently.
DevOps Is an Organisational Strategy, Not Just a Technical Practice
The most common mistake organisations make when adopting DevOps is treating it primarily as a tooling question. Choosing a CI/CD platform, adopting infrastructure-as-code or deploying containers are all valuable steps — but they will not deliver lasting performance improvements if the underlying culture remains siloed and blame-driven.
DevOps asks development and operations teams to share accountability for the entire lifecycle of software: from writing code through deploying it, monitoring it in production and iterating on it based on real user feedback. That shared accountability only becomes real when management structures, incentives, budgets and leadership behaviours support it.
For executives who are serious about organisational performance in a software-driven world, DevOps is not optional and it is not a project with a defined end date. It is an ongoing commitment to building the culture, processes and capabilities that allow an organisation to learn and improve faster than its competitors.
Original source: businesscomputingworld.co.uk (2017). Reformatted and expanded for technical accuracy.