What a DevOps Consultant Can Stop Doing to Grow Faster

Let’s be honest about how DevOps consulting careers usually grow. You say yes to a client, then yes to a second, then you start learning a new cloud service on a Sunday because someone mentioned it on a call. A year later you are good at a lot of things and exceptional at none, and your calendar looks like a game of Tetris played by someone in a hurry. If you nodded along, keep reading. We are going to talk about the skills, requests and habits a consultant can say no to, and why a short “not doing” list may be the best career move you make this year.

Think of it as a conversation over coffee rather than a lecture. Nobody needs another list of skills to acquire. What most people in DevOps consulting need is permission to put some of them down.

Start with the uncomfortable question

Ask yourself: if I could only be known for two things, what would they be? Clients hire consultants for sharp answers, not for a vague “I can help with anything infrastructure”. The consultants who earn trust and referrals tend to be known for a narrow, memorable strength: delivery pipelines for regulated teams, or migrating messy estates, or coaching engineers through their first on-call rota. Everything outside that sits on a shelf, and shelves exist to be ignored.

Once you have your two things, the rest of your career decisions get easier, because you have a filter. Does this course, project or talk make you better at one of them? If not, it goes on the “not now” list.

Skills you can happily leave on the shelf

You do not have to learn every product that appears on a job board. A realistic consultant skips:

• Tools no current client uses. Learn them when a signed project needs them, not before.
• Deep specialisms far from your two things. Know enough to hold a sensible conversation, then hand off to a friend who does it daily.
• Every vendor certification. Pick the one that a real client has asked for; ignore the rest of the badge economy.
• Trends that are still arguments. If experts are still debating a practice, you can wait for the debate to settle.

This is not laziness. Consultants who try to keep every skill warm end up with all of them lukewarm.

Requests you can politely decline

Here is where income and sanity collide. Some work is simply a bad fit, and taking it costs more than it pays. Many consultants quietly refuse:

• “Quick favours” that expand into unpaid weeks.
• Projects whose goal is a slide deck for executives rather than a change anyone will make.
• Requests to attend every meeting “just in case you’re needed”.
• Work with no named person at the client who can say yes or no.

A friendly script helps: “That sounds interesting, but it is outside what I do best. Here is who I would ask instead.” It keeps the relationship warm and your focus intact. If you want to see what a well-scoped engagement looks like, a map of an engagement that starts with an assessment and ends with the client’s own people running things gives a good sense of where a consultant’s effort should and should not go.

Learning inputs you can mute

Every consultant carries a mental inbox of articles, podcasts, talks and newsletters. Treat it like any other inbox and unsubscribe ruthlessly. A handful of sources you actually finish beat a long list you feel guilty about. Pick one or two that serve your two things, schedule a short reading window each week, and let the rest scroll past. When something truly important happens in your area, a client or a peer will tell you anyway.

You can keep curiosity alive without the guilt by keeping an “interesting, not urgent” note. Jot the idea down, close the tab, and revisit the note quarterly. Most items will look less exciting by then, which tells you your instinct to skip them was sound.

Topics worth the effort despite the skip list

A not-doing list is not a hiding place. Some subjects keep earning their place on any consultant’s learning plan because clients keep asking about them. Security woven into delivery is one, and a guide on bringing security practices into DevOps pipelines shows the kind of depth that justifies a place on your short list. Another is cloud moves; the discussion of where consultants add value when organisations shift to the cloud is a nice reference for deciding how deep to go.

The point is that your list should be deliberate. Things you keep are chosen; things you skip are chosen too.

A quick word on personal buying decisions

The same mindset helps with ordinary purchases. Before you buy a new laptop for client work, a browse through True Review Now, a friendly review blog for people sizing up gadgets, software and local services, goes quicker if you have already decided which spec-sheet chatter you will ignore.

Building your own “not doing” page

Grab a notebook, or a note on your phone, and write these headings:

1. Skills I will not chase this year. Three to five items.
2. Work I will not take. Describe the type, not a specific client.
3. Meetings and channels I will leave. Be specific.
4. Content I will stop following. Name sources.
5. What would change my mind. A client need or a market shift, for example.

That last heading matters. A skip list with no exceptions is brittle, and the exception clause keeps you flexible without letting every shiny object back in.

Review it with someone

Finally, share the page with a mentor or a trusted peer. Saying “I am not doing this” aloud makes it real, and a good friend will tell you when you are skipping something you should not. Revisit it every quarter. If a skip item keeps coming up in client conversations, promote it to your keep list without drama.

Your career will not stall because you ignored a few things. More often it speeds up, because the clients who meet a consultant with a clear point of view tend to remember exactly what to call you for.

Kabir Malhotra