Over the past year, I've had the opportunity to work with a number of teams across different clients, industries, and projects. While the work itself varies considerably, I've noticed a pattern emerging that I can't seem to ignore. Teams with similar levels of experience, similar technical capabilities, and access to the same tools are producing dramatically different outcomes. Some are moving faster, learning faster, and creating more value for their clients. Others are working just as hard but seem to be making less progress. The gap isn't subtle anymore. It's becoming increasingly visible.

At first, I assumed the difference was technical. Perhaps one team had stronger engineers. Maybe another had better requirements, a more engaged stakeholder group, or a cleaner codebase. Those factors certainly matter, but the more I observed, the more I realized they weren't the primary drivers. The most significant difference wasn't technology, process, or even experience. It was how people viewed their role in solving problems and how willing they were to embrace new ways of working.

In some conversations, I still hear discussions centered around manually reviewing every file, manually creating documentation, manually building backlog items, and manually assembling understanding one artifact at a time. In other conversations, I hear teams describing how they are using AI tools to accelerate code reviews, generate documentation, analyze large systems, validate assumptions, and explore solutions before a single ticket is created. What's interesting is that both groups are trying to accomplish the same thing. They're attempting to understand a problem well enough to help a client move forward. They're simply taking very different paths to get there.

Before going further, it's important to acknowledge something that often gets lost in conversations about AI. These tools are wrong. Sometimes confidently wrong. They misunderstand requirements, invent facts, miss critical context, and occasionally arrive at conclusions that seem plausible until an experienced person takes a closer look. That's precisely why I don't view AI as a replacement for expertise. If anything, I've found the opposite to be true. The more capable the tool becomes, the more valuable judgment becomes. Someone still has to determine whether the answer is correct, whether the recommendation makes sense, and whether the output aligns with the realities of the business. The organizations creating the most value with AI aren't the ones blindly trusting it. They're the ones pairing it with experienced people who know when to trust the answer, when to challenge it, and when to throw it away entirely.

For most of my career, the software industry has rewarded people for becoming exceptionally efficient at activities that were necessary but rarely differentiated anyone. We learned how to write requirements documents, build project plans, create backlog items, document systems, review code, write tests, and summarize meetings. Those skills mattered because they helped projects move forward. Over time, however, many organizations began treating the production of those artifacts as the work itself. The ticket became more important than the conversation that created it. The documentation became more important than the understanding it was supposed to capture. We became so focused on producing evidence of progress that we occasionally lost sight of what progress actually meant.

What makes AI so disruptive isn't that it can write code or generate documentation. The industry has become fixated on those capabilities because they're easy to observe. The more important change is that AI is rapidly reducing the amount of effort required to produce many of the artifacts we've traditionally associated with knowledge work. Documentation that once took days can be generated in minutes. Code reviews that required hours of reading can be accelerated dramatically. Requirements can be extracted from transcripts. Test cases can be generated from existing code. Entire systems can be analyzed in a fraction of the time they once required. The artifact still matters, but it no longer commands the same amount of human attention.

When that happens, something interesting occurs. The value shifts. If producing the artifact becomes easier, then the value naturally moves upstream to the thinking that determines whether the artifact is useful in the first place. Suddenly the differentiator isn't who can write the most documentation. It's who can identify the most important problem. It isn't who can create the most backlog items. It's who can determine which backlog items actually matter. It isn't who can review the most code. It's who can understand the business implications of what that code is doing. The mechanical work becomes less scarce, which means judgment becomes more valuable.

This is where I believe many organizations are misunderstanding what is happening around them. They continue to ask whether AI will replace developers, analysts, project managers, or consultants. It's a reasonable question, but I think it's the wrong one. The more interesting question is what happens when the activities that consume most of our time no longer consume most of our time. If an engineer can understand a codebase in hours instead of days, what should they do with the time they just gained? If a consultant can produce documentation in minutes instead of spending an afternoon formatting a document, where should that energy be redirected? The answer to those questions tells you a lot about whether an individual or organization is likely to thrive over the next several years.

The teams seeing the greatest results from AI are not using it to avoid work. They're using it to spend more time on the work that actually matters. They are asking more questions. They are engaging stakeholders more frequently. They are exploring more options before making decisions. They are uncovering risks earlier and identifying opportunities that would have otherwise remained hidden. Most importantly, they are learning faster. And throughout my career, I've observed that organizations capable of learning faster than their peers almost always outperform them over the long run.

That's why I don't believe AI is fundamentally a technology story. I think it's a consulting story. Clients have never hired us because they wanted more documents, more tickets, or more code reviews. They hired us because they were facing uncertainty and needed help navigating it. Sometimes that uncertainty exists inside a software platform. Sometimes it's embedded within a business process. Sometimes it's hidden in organizational dynamics, competing priorities, or technical debt accumulated over years of decision making. Whatever form it takes, our value has always come from helping clients understand their situation and move forward with confidence. The software, documents, and deliverables are simply vehicles for delivering that value.

What I find fascinating is that AI is making this reality increasingly difficult to ignore. For years, someone could build an entire career around performing consulting activities without necessarily becoming a consultant. The distinction was hard to spot because the activities themselves required significant effort. Today, however, the gap is becoming much more visible. When the effort required to generate artifacts drops dramatically, the people who create value through judgment, insight, and understanding begin to separate themselves from those who primarily create value through execution of process. One group accelerates. The other struggles to understand why they seem to be falling behind despite working just as hard.

The pattern I've observed has very little to do with intelligence, work ethic, or technical capability. Most of the people on both sides of this divide are smart, hardworking professionals who genuinely care about delivering quality outcomes. The difference is that some continue to organize their work around the mechanics of delivery while others are increasingly organizing their work around the creation of knowledge and understanding. One group is focused on completing activities. The other is focused on reducing uncertainty. One is optimizing for output. The other is optimizing for insight.

I suspect we're going to see this pattern play out repeatedly over the next several years. Two organizations will have access to the same technology, the same information, and the same opportunities. One will use AI to become more efficient at yesterday's work. The other will use AI to create capacity for tomorrow's work. At first the difference will seem small. A little more velocity. A little more insight. A little better communication. But over time those advantages compound. They become better decisions, stronger client relationships, more strategic influence, and ultimately better outcomes.

That's why I don't believe AI is replacing consultants. If anything, I think it's making great consultants even more valuable. What it is replacing is the illusion that the artifacts were the source of value all along. As the mechanics become easier, we're being forced to confront a simple truth that has always existed beneath the surface of our profession: the best consultants were never hired because of what they produced. They were hired because of what they understood.

The organizations and individuals that thrive in this next chapter won't be the ones that can generate the most artifacts or complete the most tasks. They'll be the ones that can learn the fastest, understand problems the deepest, and turn information into action. AI can help accelerate those activities, but it cannot replace the judgment required to perform them well. In fact, as AI becomes more capable, judgment becomes even more valuable because someone still has to decide what matters, what is true, and what should happen next.

AI isn't changing the nature of consulting. It isn't eliminating the need for expertise, judgment, or experience. If anything, it is increasing their importance. The faster information can be generated, the more valuable it becomes to have people who can determine what that information means and what should happen next. The organizations that understand this will continue to pull ahead. The ones that don't may find themselves working just as hard as they always have, but creating less value in the process. That's why I don't believe AI is replacing consultants. I believe it's revealing them. Revealing who can turn information into understanding, activity into insight, and technology into meaningful outcomes for the people they serve.