The Polymath Strategy: Systems Thinking vs. Overspecialization

Imagine a poorly coordinated emergency room.

A critically ill patient is lying on the table. Different specialists are looking at different things. One is looking at the heart. Another is looking at the blood chemistry. Someone else is examining the neurological symptoms. They are all trained. They all know what they are looking for. And what they are seeing may all be correct.

But the patient is getting worse.

Nobody is putting the observations together.

That, I think, is an important distinction.

The problem is not specialization. The problem is what happens when specialization cannot see beyond itself.

Education has a similar problem.

There are good reasons why we divide knowledge into subjects. Mathematics requires a different kind of thinking from history. Biology has its own methods. Chemistry has its own language. We cannot simply throw all of these together and call it education.

Specialization is necessary.

But there is a point where the way we organize knowledge begins to look like the way reality itself is organized.

And it isn't.

A polluted river does not become a chemistry problem at one moment, then an environmental problem at another, then a public-health problem when another person looks at it.

It is all of these things at the same time.

It may also be an agricultural problem. An economic problem. A political problem. A legal problem.

The river does not care which department is responsible for it.

This is where institutional siloing becomes interesting.

The danger is not simply that people know too little. Sometimes the more serious problem is that people know a great deal about one thing and very little about how that thing connects to everything else.

The most successful silo is not necessarily the one that keeps people from crossing its walls.

It is the one that convinces them the walls are natural.

The Calamansi

Consider a calamansi sitting on a kitchen table.

It is a small thing. We normally don't think much about it.

It is food.

Or perhaps, in a classroom, it becomes an example in a lesson about plants or agriculture.

But what happens if we stop asking what subject the calamansi belongs to?

Its shape can lead us to morphology. Its acidity leads us to chemistry and pH. Its weight and volume can become a lesson in measurement. Where it grows raises questions about geography and ecology. How it gets from a farm to a market introduces economics and supply chains.

And then there is culture.

Why is calamansi so common in Filipino food? How did it become part of the way we eat? What does that tell us about Filipino life?

Suddenly, the small fruit has become something else.

Not because the fruit changed.

Only the questions changed.

This may be one of the simplest ways to understand interdisciplinary learning.

A subject-centered system tends to ask:

What subject does this belong to?

But perhaps there is another question:

What can this thing teach us?

Those questions do not lead us in exactly the same direction.

The first question starts with the categories we have already created.

The second starts with the thing itself.

That difference matters.

We often assume that because we have divided knowledge into subjects, the world must somehow be divided in the same way. But the divisions are ours.

The world did not create the timetable.

We did.

When the Map Becomes the Territory

Education needs maps.

Students need mathematics, science, history, language, economics, and other disciplines. These fields give us ways of describing the world. They give us methods. They allow us to build on what others have already learned.

We need those maps.

But a map is not the territory.

A river does not know that Chemistry is taught in one classroom and Economics in another.

A community does not experience poverty on Monday, public health on Tuesday, governance on Wednesday, and culture on Thursday.

A child does not live in subjects.

Reality is integrated. Our institutions have to be organized. The problem begins when organization turns into fragmentation.

A timetable is useful. Departments are useful. Academic disciplines are useful.

But an administrative boundary is not automatically an intellectual boundary.

The problem is that students may eventually stop noticing the difference.

They learn that certain questions belong to certain classrooms. They learn which teacher to ask. They learn which textbook contains the answer. They learn to keep things in their proper places.

And perhaps this is where education teaches something that was never written in the curriculum.

It teaches students how to divide the world.

At that point, the curriculum has taught more than its stated lessons.

It has taught a way of seeing.

And that may be more important than we realize.

The Polymath Strategy

This is where the idea of the Polymath Engineer becomes useful.

I don't mean an engineer who somehow knows every subject.

That person does not exist.

What I mean is someone who can move between different ways of thinking and, more importantly, recognize when those different ways of thinking need to meet.

Think again about the emergency room.

The heart specialist sees something important. The chemist sees something else. The neurologist sees another piece of the problem.

The difficulty is not that any of them are wrong.

The difficulty is that the patient is one patient.

The Polymath Engineer understands this.

An engineering decision can become a chemistry problem. A chemical solution can create a health problem. A technological intervention can create an environmental problem.

A solution can solve one problem and create another.

That means the question cannot simply be:

Does this work

We also have to ask:

What else happens because it works?

And perhaps another question:

What are we not seeing yet?

The Polymath Engineer therefore does not simply collect disciplines.

He connects them before he acts.

That does not mean he replaces the specialist.

Quite the opposite.

The specialist is necessary. There are questions that require years of concentrated study. There are things I will never know as well as someone who has spent a lifetime studying them.

The point is not to become that person.

The point is to know when that person's knowledge is needed.

That is a different kind of intelligence.

It requires intellectual humility as much as intellectual breadth.

You have to be able to say:

I know this part.

And then:

But I may be missing something.

The Institutional Problem

This is why I keep coming back to institutional siloing.

A system can be organized and still be fragmented.

It can have excellent teachers, excellent specialists, excellent departments, and still have difficulty producing people who understand relationships across those divisions.

In fact, there is an uncomfortable possibility here.

The better we become at separating knowledge, the more important it becomes to teach people how to reconnect it.

We should not tear down every disciplinary wall.

That would solve one problem by creating another.

Instead, we need doors.

Students should be able to study mathematics deeply without being taught, implicitly or explicitly, that mathematics ends where biology begins.

A scientist should be able to recognize that a scientific problem can also have legal, economic, historical, or ethical consequences.

A historian should not have to become a mathematician to understand that numbers can reveal something history alone cannot.

And a child holding a calamansi should be allowed to wonder about more than the name of the fruit.

That child can ask where it came from.

Who grew it.

Why it grows there.

What is in it.

Why it tastes the way it does.

How much it costs.

Why people use it.

What happens to it after it leaves the farm.

The questions keep going.

And that is precisely the point.

What Are We Teaching?

Perhaps the deeper question is not whether schools teach enough subjects.

Perhaps we should ask what students learn about the relationship between those subjects.

We are very good at asking students for answers.

But do we teach them to ask whether they are asking the right question?

Do we teach them to ask what has been left outside the frame?

If a problem has been placed inside one subject, does that mean the problem actually belongs there?

Or did we simply put it there because that is where our institutions have become accustomed to putting it?

These are uncomfortable questions because institutions depend on categories.

We need categories.

But categories can become habits.

And habits can become invisible.

The student eventually stops seeing the boundary because the boundary has become normal.

This is not necessarily anyone's intention.

That is what makes it difficult.

Nobody has to tell a student, "Do not connect these things."

The structure of the institution may teach the lesson without ever saying it.

The Mind That Sees the Whole

The purpose of interdisciplinary education, then, is not simply to combine subjects.

It is to develop the ability to recognize relationships.

But there is a danger on the other side too.

We should not romanticize the person who knows a little about everything while knowing very little about anything.

Breadth without depth is not necessarily wisdom.

The answer is not to choose between the specialist and the generalist.

We need both.

We need people who can go deeply into a field.

And we need people who can move between fields.

More importantly, we need people who can do both when circumstances require it.

That is what I mean by the Polymath Strategy.

It is not about accumulating subjects.

It is about learning how to connect them.

It is not about eliminating boundaries.

It is about knowing when the boundary no longer describes the problem.

The calamansi remains one.

The disciplines multiply.

Then the questions multiply.

And somewhere in that movement, from the object to the question, from the question to another discipline, and from one discipline to another, the learner begins to see something that the silo cannot show.

The unity behind the parts.