← All writing
Series · Essay 3 of 8

Expertise Is Structure

Expertise isn't accumulated knowledge; it's the ability to structure a problem so it becomes intelligible.

Evan Prout
October 20, 2026
5 min read

Two founders are deciding whether to raise money now or wait. Both ask the same AI system for help.

The first asks, "Should we raise now?" She gets back a balanced, forgettable paragraph: it depends on market conditions, runway and growth trajectory.

The second asks the system to argue for raising now as aggressively as a board member who wants growth at any cost. Then she asks it to argue the opposite as a conservative CFO worried about dilution. Then she asks what a founder would need to see to know which one is right for this specific company.

Same tool. One got a paragraph. The other got a decision she could defend to her board.

The difference wasn't the machine. It was the structure of the question. And that difference says something important about what expertise actually is.

What Expertise Actually Is

I think expertise is often misunderstood, even by people who have plenty of it.

We usually treat it as accumulated knowledge. The expert knows more facts, has more experience, holds more specialized information. That's part of it. But it misses the core.

Expertise is the ability to structure a problem so it becomes intelligible.

A good strategist doesn't start with answers. She starts by framing the situation: what forces are at work, what assumptions are built into the proposal, what's known and what isn't. A scientist builds hypotheses and designs experiments that let others check the reasoning. A lawyer doesn't just state an opinion. He builds a chain that connects facts, precedent and interpretation.

In each case, the expert builds an environment in which the problem can be examined. Questions are framed carefully. Assumptions are made explicit. The relationships between ideas are spelled out. The result isn't instant certainty. It's clarity.

Experts also see differently. A financial analyst sees cost structure and risk exposure. An engineer sees constraints and feasibility. A strategist sees competitive dynamics and long-term position. Each is a structured way of reading the same situation. That's why organizations have always spread expertise across people: a hard decision needs several of these lenses at once, and no one person carries all of them.

Why AI Exposes This

AI is usually described as something that knows things. It was trained on enormous amounts of text, so it should be able to answer almost anything. You ask, it responds.

Experience says otherwise. AI doesn't retrieve answers. It generates language that reflects the reasoning built into the prompt. A vague prompt produces a vague response. A poorly framed problem produces shallow analysis. A carefully structured inquiry produces something coherent.

Novices tend to ask broad, undirected questions. What should I do? What's the best strategy? The system answers with general language that sounds useful and lacks depth. Experts define the problem, add constraints, ask for specific perspectives, and refine as they go.

The machine doesn't supply the structure. The user does. That's why the second founder got a better answer. She brought an expert's structure to the question: competing perspectives, explicit stakes, and a test for deciding between them.

Amplification Cuts Both Ways

This is where scale finally catches up to expertise. In the past, looking at a problem from several angles meant assembling the people who held them, and that took time and coordination. Now one person can generate several structured perspectives in a single session. Economic, technical, behavioral and operational readings can sit side by side. The reasoning environment gets bigger than any individual mind.

But amplification has no opinion about quality. AI multiplies reasoning structures. It doesn't supply their discipline. A well-structured inquiry produces a richer field of analysis. A poorly structured one produces more poorly structured analysis, faster. The machine doesn't correct the shape of the thinking. It extends it.

And it amplifies the form of reasoning without supplying judgment. Without judgment, the amplification of expertise turns into something else: the amplification of plausibility. The system can produce several coherent explanations of a situation, each reasonable on its face. Coherence isn't correctness. Someone without the expertise to tell them apart can't distinguish real analysis from persuasive language.

Synthetic Expertise

That's the risk that worries me most. I call it synthetic expertise.

Picture a junior analyst asked whether the company should acquire a smaller competitor. She puts the question to an AI system and has an answer in seconds: strategic fit, revenue synergies, integration risk, cultural considerations, all under clean headings. She has never been through an acquisition. She doesn't know which of the listed risks are the ones that actually sink deals, or which synergies are boilerplate optimism dressed up as insight. But the memo reads like the work of someone who does.

Nothing in the document flags itself as plausible rather than expert. That distinction lived in the analyst's judgment, and she was too impressed by how finished the language looked to apply it.

I've sat in rooms where this exact thing happened, and no one noticed.

So AI has two effects at once. For people with expertise, it widens the space they work in. For people without it, it raises the odds of mistaking structure for substance. That's why expertise becomes more important in the presence of AI, not less. Someone has to recognize when the reasoning is incomplete: the missing variable, the weak assumption, the analysis that's all surface.

How to Bring Structure

If expertise is structure, you can practice it deliberately, with or without AI.

  • Frame before you ask. Write down the actual decision and what would change your mind.
  • Assign perspectives. Ask for the case from specific roles with specific stakes, not a balanced overview.
  • Make assumptions explicit, then test the ones the conclusion depends on most.
  • Ask what's missing, not just what's there.
  • Know where your expertise ends. When you can't tell a strong risk from a boilerplate one, that's the moment to find someone who can.

Expertise Made Visible

There's a real upside here. When reasoning is externalized in language, you can watch how experts work. The questions they ask, the assumptions they challenge and the perspectives they bring in all become explicit. That makes expertise easier to examine, and in some cases easier to teach. It stops being a private, tacit gift and starts looking like a structured process anyone can learn.

The expert's advantage was never having the answers. It's asking better questions.

Sources
Evan Prout

A strategist in Grand Rapids who writes about how organizations think.

About →
Next
More writing →
Subscribe

New essays as they're written.

Get the next one →