Let’s start with the punchline—DevOps is not about tools. It’s not about Jenkins, not about Docker. And it’s not about Kubernetes. I know you’re probably shocked. But you might look elsewhere if you picked up this article, hoping for a deep dive into the latest CI/CD pipeline tricks. Instead, let’s talk about what DevOps is.
DevOps, at its core, is about people. Not tools. Not code. Not tech. Just people. Sure, tech plays a role, but without a team that’s aligned, engaged, and ready for change, all the fancy software in the world won’t help you.
You could install the latest Jenkins release or set up the coolest Docker container system, but the tool becomes irrelevant if your team doesn’t care about the process. DevOps is about people first, then process, then (and only then) tools.
Start With People, Not Tools
So, how do you start with people? You get them on board. That’s the first and most critical step. No tool will ever succeed if your team isn’t ready for change. People need to feel involved and connected to the process.
Imagine forcing a tool on your team before they’ve even agreed on what the process should be. Disaster, right? That happens when companies jump straight to tools, hoping the tech will fix everything. Spoiler alert: it won’t.
When you impose a tool without creating the right culture, it feels like the tool is happening to them, not through them. And let’s face it, that’s not how people work. You can’t just drop a tool and expect magic to happen. Humans need buy-in — they need to feel part of the journey.
The Trap of Tool Obsession
There’s another danger lurking when it comes to tools. You get excited. Maybe too excited. The second you get your hands on the latest tech piece, everything suddenly starts looking like a nail to your shiny new hammer. You know the feeling.
You bought a new table saw, and your entire house needs remodelling. The same is true for software tools.
You bring in Jenkins or Kubernetes, and suddenly, you’re applying it to every problem you have, whether it makes sense. But tools should never define your problems. Your problems should define the tools. Otherwise, you’re just adding complexity, and that’s the last thing anyone needs.
The Human-First Philosophy of DevOps
This all comes down to a very simple philosophy: people first. The tools? We’ll get to those eventually, but only once the team and process are in place.
That’s why, in DevOps, the real magic happens in the collaboration between your people. Tools will come and go, but culture is what drives sustainable success.
Now, I’m not saying tech doesn’t matter at all. Tech is part of the equation, but how you use it makes the difference. And that’s where the CAMS model of DevOps comes in prioritising culture, automation, measurement, and sharing.
DevOps Doesn’t Mean the End of System Administrators
There’s a fear I hear a lot when I talk to traditional sysadmins. “Is DevOps going to make me obsolete?” It’s a fair question, especially with the rise of automation, infrastructure as code, and virtualized environments. But the truth is, ops isn’t going anywhere. Sure, the role of the systems administrator is changing, but it’s changed since the dawn of computers.
Expertise in infrastructure, security, capacity planning, and monitoring expertise will always be needed. DevOps doesn’t erase those needs — it just shifts how we approach them. The sysadmins of tomorrow will need to pick up skills like Python. But if we survive the transition from token-ring networks to TCP/IP, we’ll also survive learning a few new tricks in automation.
Embrace Change, But Keep the Core
So, is DevOps killing the sysadmin? Hardly. It’s allowing us to evolve, grow, and adapt to a world where development and operations overlap more than ever. But at its core, ops will always be there. Someone needs to plan, scale, secure, and maintain the infrastructure. Those needs don’t disappear because we’ve added automation to the mix.
The key to thriving in DevOps is to keep focusing on what has always mattered: people. Get them on board with change, give them the right process, and only then choose the tools that make sense.
Final Thoughts
DevOps isn’t a revolution of technology — it’s a revolution of mindset. It’s about collaboration, adaptability, and culture. If you’re focusing on the tools, you’re missing the point. Focus on your team, your process, and your goals. The tools will follow naturally. This is the human side of DevOps, and it’s the part that matters most.
If you would like to connect with me to discuss DevOps, connect here.
Interesting thought!