Unlocking Value in DevOps: My Role as a Consultant in Driving Change and Overcoming Bottlenecks

Published on
3 minute read

In my journey as a DevOps consultant, I often find myself reflecting on the core of my role. The question, “What is my primary role in a DevOps consulting gig?” is not as straightforward as it may seem. The answer is deeply intertwined with the context of each unique engagement. It hinges on where the customer currently stands, what they aim to achieve, and the specific challenges they face.

Provoking Thought and Change

At the heart of my work is a singular goal: to provoke my clients into re-evaluating how they manage and deliver their work. This involves scrutinising the systems they have in place and identifying opportunities for disruption that can lead to significant benefits.

DevOps is fundamentally about optimising the flow of value—from the initial idea all the way to the end customer. This process doesn’t end there; it’s equally crucial to close the feedback loop, ensuring that insights from customers are fed back into the system.

Identifying Bottlenecks

A key part of my role is to identify what’s getting in the way of this flow. Here are some common areas I focus on:

  • Technical Issues: Sometimes, the bottleneck is technical. For instance, if builds are taking an excessive 24 hours to complete testing, that’s a clear indicator that something needs to change. My job is to delve into these technical challenges and find solutions that can streamline the process.

  • People Problems: Other times, the issue lies with people and processes. For example, if an approval is required but the responsible individual only reviews requests bi-weekly, it creates unnecessary delays. This waiting period is wasteful and can severely hinder the feedback loop.

Finding Solutions

So, how do I uncover these bottlenecks? It’s about asking the right questions and engaging in meaningful conversations with the team. I encourage clients to look critically at their workflows and identify the longest delays. Once we pinpoint these areas, we can start to “poke at them”—to explore, experiment, and ultimately improve.

The Bigger Picture

Ultimately, my role transcends mere problem-solving. It’s about fostering a culture of continuous improvement and agility within organisations. By optimising processes and enhancing collaboration, we can create a more efficient and responsive environment that delivers value to customers more effectively.

If you’re interested in discussing these concepts further—whether it’s about Agile, Scrum, or DevOps—please don’t hesitate to reach out. I’m always open to a chat over coffee, and I welcome your thoughts and comments.

Thank you for taking the time to read my insights. If you found this post helpful, please like, follow, and subscribe for more content. Your engagement is invaluable to me!

So the question is, what is my primary role in a DevOps consulting gig? I think that’s a difficult question to answer without the context because I find it depends very heavily on where the customer is, what they’re trying to do, what they hired you for, and what their problem is.

But if maybe quantifying that primary goal is to provoke the customer into thinking about how they manage and deliver the work that they do and how the system that they have in place delivers that work and can be disrupted for their benefit, right?

So DevOps is about optimising that flow of value from idea all the way through to the customers of that product and then closing that feedback loop, right? Getting that feedback back into the system.

So what is it that’s getting in the way of that? Find the thing that’s taking the longest in that process and go poke at it and pick at it. And that could be a technical focus, right? A tool issue. The builds are taking 24 hours to do all the testing. Well, that’s too long, right? How do we go fix that?

Or that could be a people problem. This approval needs to happen, but the person who does the approval only does it once every two weeks. So if you get the timing wrong, right, you’re just waiting for that approval in order to be able to close that feedback loop. That’s just waste. That’s wasted time.

So how do you find those things? So I think that would be my focus.

Thanks for watching the video. If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else, Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.

Pragmatic Thinking People and Process Value Delivery Product Delivery Software Development Market Adaptability Operational Practices Value Stream Management Discovery and Learning Flow Efficiency

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Hubtel Ghana Logo
Emerson Process Management Logo
DFDS Logo
Slaughter and May Logo
Milliman Logo

NIT A/S

Teleplan Logo
MacDonald Humfrey (Automation) Ltd. Logo
Microsoft Logo
Capita Secure Information Solutions Ltd Logo
Boxit Document Solutions Logo
Illumina Logo
ALS Life Sciences Logo
Flowmaster (a Mentor Graphics Company) Logo
Epic Games Logo
YearUp.org Logo
Big Data for Humans Logo
Akaditi Logo
Washington Department of Enterprise Services Logo
Washington Department of Transport Logo
Ghana Police Service Logo
Nottingham County Council Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Trayport Logo
Cognizant Microsoft Business Group (MBG) Logo
New Signature Logo

CR2

Graham & Brown Logo
Kongsberg Maritime Logo