I’ve been the shallow expert at times. It’s easy to mistake a convincing explanation for understanding, especially when it agrees with what you already think.

Coding agents make that mistake easier. They can research a subject, compare approaches, and help build a solution. The help is real. But the finished work can give us confidence we haven’t earned.

The cost of producing authoritative-sounding analysis has fallen faster than the cost of evaluating it.

That gap is where shallow expertise takes hold. We know enough to repeat the conclusion, but not enough to explain the assumptions behind it. We may not even recognize what’s missing. The report reads well. Our confidence grows.

Then the conditions change. A dependency behaves differently. A small change has a large effect elsewhere. Or a rare surprise breaks the model entirely. That risk never goes away. Understanding cannot predict every surprise, but it can recognize where the model ends and ask what happens beyond it.

This takes non-linear thinking. It means following dependencies and feedback loops, then seeing when the original problem needs to be reframed. Finding that question is the higher-order skill. The question always matters more than the answer. Forty-two tells us nothing until we know what was asked.

A team needs that reasoning to make a decision. Handing it a 150-page document does not establish that we’ve done the work. If we cannot explain the system ourselves, we’re asking everyone else to shoulder the burden of understanding it. The person questioning an assumption is doing necessary work. Defending the document against them only leaves the gap intact.

“Brevity is the soul of wit.” Bring the team a clear account of what matters: the assumptions, the tradeoffs, the consequences, and what would change the recommendation. Leave room for questions. Anyone asking a team to act on an answer should be able to reason beyond it.