An example of companies asking for things that require consultants to understand how they fit into the client’s business vision is how Kubernetes became a buzzword in recent years.
Everybody was all of a sudden saying, "Oh, containerize, containerize, containerize."
One of the challenges to understand, though, is what's in the container.
The container will standardize things. If something goes down, it automatically rolls back up, but there wasn't much focus, until recently, on what's in the container.
Consultants should be asking the client, "What is the value you're trying to get by containerizing?"
If they say, "I want consistency in deployment," great.
If they say, "When something goes down, I want to make sure it automatically comes back up, I don't want to have to worry about manual intervention," awesome. That does it.
But sometimes they might say, "I want a better customer experience," or, "I want my app to be more responsive." A lot of clients think that if I containerize it and move it to the public cloud, I'm going to get that, and now, they're realizing, "I don't. I haven't looked inside my little container." If an app takes 5 minutes to start up, every time the app comes up, it will take 5 minutes. This may not be the customer experience they want.
What's in the container is really critical.
Consulting firms should incorporate client goals into a solution with an Outcome-Based Approach from the start to define what they are trying to achieve. This is so their consultants can provide the right advice, framing their recommendations in a way that leverages their strengths and expertise to solve client problems in creative ways.