When Expertise Isn’t the Answer

Introduction

Most professions reward expertise and this generally plays as exactly what you’d expect for the profession to be effective. Patients deserve physicians who recognize subtle diagnoses. Aircraft deserve engineers who understand failure modes. Organizations benefit when accountants know the subtleties of tax law, software developers understand minute architecture details and researchers know how to distinguish signal from noise.

Expertise matters because it allows us to recognize what is in front of us and respond appropriately.

In The Second Apprenticeship, I argued that promotion often marks the beginning of a different kind of work rather than a culmination event. Technical mastery often earns the opportunity to lead, but leadership asks us to apply that mastery in a fundamentally different environment.

That naturally raises the question:

 What happens when expertise encounters a problem that has no established answer?

---

Recognition Before Creation

Much of professional education is built around pattern recognition, and since I’m a practicing physician,  I’ll use medicine as my clear example of this process in action. 

We learn anatomy before pathology. Normal physiology before abnormal physiology. We spend years learning what disease looks like, how it behaves, and what evidence tells us about the most effective treatments. As our experience grows, we become increasingly adept at recognizing patterns that less experienced clinicians might miss, as well as subtle variations from the “usual” pattern that still fit. 

Recognition is not guesswork, but rather disciplined observation informed by years of deliberate practice.  Neuroscience bears this out in descriptions of chunking behavior.  Medical students, resident physicians and more junior attendings can arrive at the same conclusion as me, but by going thru several micro steps, that at my level of experience seem to be one step. Over 2 decades plus,  I’ve chunked lots of bits of knowledge into broader patterns. Think of a phone number. It’s not 10 separate digits. It’s an area code, and a phone number. 

Experienced clinicians often seem to arrive at diagnoses almost intuitively. They recognize subtle constellations of findings, mentally eliminate unlikely possibilities, and narrow the field to the most probable explanation. What appears effortless is actually the product of thousands of previous encounters carefully organized in memory.

This is not some mystic ability unique to medicine (seriously, I wish I were that cool).

Engineers recognize failure modes.

Chess masters recognize opening systems 12 moves deep as a single idea.

Software developers recognize design patterns.

Military officers recognize tactical situations.

Researchers recognize methodological flaws.

Expertise often looks like extraordinary intuition, but intuition is usually recognition operating at remarkable speed, and this is one of the great strengths of technical professions.

---

When Recognition Reaches Its Limits

This is going to seem intuitively obvious to a casual observer, but recognition depends on there being something to recognize.

Clinical medicine illustrates this beautifully. Most of the time, we are not inventing treatments. We are selecting among therapies whose risks and benefits have already been studied. We are applying established knowledge to the patient in front of us. Sure there are variations and options to fit a patient’s situation and unique circumstances, but after enough experience those cases become variations on a theme, not some strange unknown. 

Even when cases become extraordinarily complex, our thinking is still anchored by physiology, evidence, accumulated experience, and disciplined reasoning.

Leadership encounters fundamentally different kinds of problems.

Should two departments be reorganized into one?

What are the unintended consequences of developing a new technology?

How should limited resources be distributed between competing priorities?

How much short-term financial pain should an organization tolerate to invest in long-term capability?

What is the right balance between standardization and local autonomy?

There may be thoughtful answers.

There may even be several good ones.

But there is often no guideline to reference, randomized trial, established algorithm, nor colleague who has already solved this exact problem.

The difficulty is not simply that these decisions are more complicated.

It is that they belong to a different category altogether.

The challenge shifts from recognizing the correct answer to creating a defensible one.

---

Creation Is Still Disciplined Thinking

The word creation makes some people (particularly technical expert types) uncomfortable.

It sounds subjective, artsy, creative, improvisational. As though disciplined thinking suddenly gives way to brainstorming and inspiration. Despite the phrase “practicing the art of medicine”, this type of uncertainty and unknowability sparks anxiety. 

I do not intend for the baby to be dispensed when we make room for clean bathwater.

Good leaders do not abandon disciplined reasoning simply because there is no established solution.

If anything, creativity requires leaders being more disciplined.

They gather evidence, seek perspectives different from their own.

They identify assumptions, and test ideas against reality.

They make decisions with incomplete information, and carefully watch for intended (and unintended) consequences. If new information emerges, they adjust.

That process is remarkably similar to what clinicians do every day.

We gather data, verify it, interpret it,  give it meaning and context.

We develop a working diagnosis, initiate treatment and observe the patient’s response.

Rinse and repeat. 

The underlying discipline has not changed; the domain of inquiry has.

Earlier in this series, I wrote that when physicians move into leadership, the object of care changes from the individual patient to the systems through which patients receive care.

This is analogous for other technical experts ascending to leadership roles. The same idea applies. 

The intellectual habits that make excellent clinicians remain valuable.

They simply have to operate in an environment where the answer is no longer waiting to be recognized.  Sometimes it has to be built from scratch.

---

The Seduction of the Right Answer

This transition is more uncomfortable than many technical professionals realize.

Our training conditions us to believe that if we think carefully enough, gather enough information, and consult the right expert, the correct answer will eventually reveal itself.

That belief serves us remarkably well in technical work, but can be a counterproductive liability in leadership.

Because some organizational problems are waiting for commitment, not discovery.

Eventually, leaders reach a point where additional analysis no longer produces greater certainty.

It merely postpones action.

This is where technical professionals often drift toward one of two equally unhelpful extremes.

Some become paralyzed by the expectation of perfection. They continue gathering information long after the additional information meaningfully changes nothing, hoping certainty will eventually arrive if they simply think hard enough.

Others react against that paralysis by embracing what is often defended as “good enough.” Too often, that becomes little more than rationalized mediocrity—a convenient excuse for lowering standards rather than exercising judgment.

Neither response respects reality.

Reality usually presents us with constraints we did not choose. Time. Resources. Information. People. The question is rarely whether we can produce the perfect solution. More often it is whether we can identify the best responsible action available under the conditions that actually exist.

That is very different from settling.

It acknowledges that doing nothing has consequences every bit as real as doing the wrong thing. Failure by omission can be as damaging as failure by commission.

Professionals act because action is warranted, not because perfection has arrived. Then, as reality teaches them something new, they continue improving what they have built.

These goals are characterized by “perfect” being the enemy of “done”, while balancing that “good enough” can be the enemy of “good”

How do you create a sufficiently good solution, coordinate people around it, learn from the outcome, and improve it over time?

Not by abandoning rigor, but rather by recognizing the kind of problem you are actually solving.

Being “right” remains valuable, but leadership is ultimately judged by effectiveness.

Effectiveness measured not simply whether the reasoning was sound, but whether the organization becomes healthier, more capable, and better positioned because of the decisions made.

That distinction becomes increasingly important as responsibility grows.

---

The Beginning of Uncertainty

Looking back, I suspect this was one of the biggest shifts I failed to recognize early in my own leadership journey.

I assumed that being a great leader came by leveraging my expertise, and becoming a better leader meant becoming a better expert.

So I read more, learned more, accumulated more knowledge, all so I could come up with better ideas.

Knowledge mattered, but I was expert enough at the beginning…it’s how I got the job. The trouble was, expertise wasn’t going to solve the problems I actually had.

The problem was whether I could help a group of exceptionally capable people move forward when none of us possessed complete certainty.

That realization sparked changes not confined to  how I think about leadership, but, it also changed how I think about mentorship.

Good mentors do more than provide answers; they facilitate people becoming capable of navigating situations after the mentor is no longer present.

Leadership operates the same way.

It is not simply about making good decisions.

It is about helping organizations become better at making good decisions long after the leader is gone.

That responsibility extends beyond today’s mission.

It includes tomorrow’s capability.

---

When Expertise Isn’t the Answer

Expertise remains one of the most valuable things an organization can cultivate.

Nothing in this series argues otherwise.

Without expertise, there is little foundation on which leadership can build.

But expertise has limits.

It excels at recognizing patterns, applying established knowledge, and selecting among known alternatives.

Leadership increasingly asks a different question.

What do we do when none of those alternatives exists?

That is not a failure of expertise. That would be the equivalent of saying a wrench failed to drive a nail. The wrench is a fine tool, just not for pounding nails. 

When expertise reaches the edge of its domain, disciplined thinking still matters.

Evidence and experience still matter.

What changes is that leaders must increasingly create the conditions, the options, and the coordinated effort that allow a good solution to emerge where no obvious one existed before.

The second apprenticeship is not about abandoning expertise.

It is about discovering where expertise ends—and where leadership begins.

And once we recognize that, another question becomes difficult to ignore.

If many of our most accomplished experts have spent their careers learning to recognize the right answer, what happens when they suddenly find themselves in situations where no right answer exists at all?