The Skills AI Cannot Choose for You

I keep seeing the same reaction to AI: people rush to learn the newest tool before the previous one has even settled into their work.

I understand it. I do the same thing. A new model appears, a new agent becomes possible, and suddenly yesterday’s workflow looks old. Some skills that took years to build are becoming cheaper almost overnight. Drafting routine text, summarising documents, producing a first version of code, collecting basic information — none of this has disappeared, but the scarcity around it is disappearing.

That made me ask a different question.

Instead of trying to predict which profession will be safe, what can I train that will still help me when the tools change again?

I have a hypothesis. There are two skills that form something like the supporting walls under the same roof: systems thinking and mathematical reasoning.

I cannot prove that either of them will remain valuable forever. “Forever” is a dangerous word, especially now. But the faster AI develops, the more important these two abilities seem to become.

The wrong question is: Which job will survive?

Jobs are bundles of tasks, and AI does not affect every task equally. The International Labour Organization estimates that one in four jobs worldwide has some exposure to generative AI, while saying that transformation is more likely than outright replacement. The World Economic Forum expects 39% of workers’ current skill sets to change or become outdated between 2025 and 2030. In the same report, analytical thinking remains the most sought-after core skill among employers.

Those forecasts are not laws of nature. They are signals. And the signal I take from them is that protecting one fixed professional identity is probably a weak strategy.

If a person defines their value as “I produce this particular output in this particular way,” AI can put pressure on that value very quickly. If the person can understand the larger situation, define the real problem, see consequences and test whether a proposed answer makes sense, they can move when the tool changes.

The output may change. The ability to orient yourself remains useful.

First wall: systems thinking

Most problems arrive disguised as isolated tasks.

“We need more leads.”

“We need to publish more content.”

“We need to automate support.”

AI is extremely good at helping with a clearly framed local task. It can generate landing pages, campaigns, messages, scripts and automations at a speed that was impossible a few years ago. But increasing the output of one part can make the whole system worse.

More leads can overload delivery. More content can weaken trust. Faster support can hide a product problem that should have been fixed at the source. A local improvement can create a downstream cost, and that cost often arrives with a delay.

Systems thinking is the habit of looking beyond the visible event. What produces it? What reinforces it? Where is the bottleneck? Which part is reacting with a delay? What behaviour does the current incentive reward? What happens after the obvious first result?

This matters with AI because AI makes local optimisation cheap. We can now produce more changes, faster. That also means we can produce second-order damage faster.

The systems thinker does not merely ask, “Can this be automated?” The better questions are:

What system is this task part of?
What result are we actually trying to improve?
Where will the additional load appear?
Which feedback loop will this change strengthen?
What might improve immediately while becoming worse three months later?
Who pays the cost if the model is wrong?

These questions are not a defence against technology. They are what allow technology to be used without becoming trapped by its speed.

Second wall: mathematical reasoning

When I say mathematics, I do not mean that everyone needs to become a mathematician or return to pages of school exercises.

I mean the discipline of making vague claims more exact.

How much? Compared with what? How often? Over what period? What is the base rate? Which variable changes the result most? What would have to be true for this conclusion to hold?

AI can produce an answer that sounds precise even when the assumptions beneath it are weak. Mathematical reasoning gives us a way to resist that surface confidence. It trains the instinct to check scale, units, probability, proportions and uncertainty.

Suppose an AI system claims that an automation will save a team a large number of hours per year. The calculation may be correct inside the assumptions it was given. But how often is the process actually performed? How many people will use the automation? How much time will checking mistakes consume? What is the cost of one serious error? Does the saving remain meaningful if adoption is only half of what we expect?

This is mathematics in a practical sense. It turns an attractive statement into a model that can be questioned.

It also trains a certain kind of honesty. An equation forces us to reveal what we are assuming. A probability reminds us that confidence is not certainty. A rough estimate can expose a beautiful idea that simply cannot work at the required scale.

Why the two belong together

Systems thinking without mathematics can become a beautiful diagram in which everything connects to everything, but nothing can be tested.

Mathematics without systems thinking can produce a perfect answer to the wrong question.

Together they do something more useful. Systems thinking helps us choose the boundary of the problem. Mathematics helps us test what happens inside that boundary. One shows relationships; the other applies pressure to our assumptions.

This is the roof I have in mind. Under one side is the ability to see the whole. Under the other is the ability to reason precisely.

AI can help with both. It can suggest variables we missed, simulate scenarios, explain an equation, challenge a causal map and find counterexamples. But there is a difference between using AI to strengthen thought and using it to avoid thought.

A 2025 study from Microsoft Research surveyed 319 knowledge workers and collected 936 examples of AI-assisted tasks. Higher confidence in generative AI was associated with less critical thinking, while higher confidence in one’s own ability was associated with more. The study is based on self-reports and does not prove that AI causes people to think less. Still, the pattern is worth noticing: a tool that can extend reasoning can also make it easier to stop reasoning too early.

How I would train these skills now

Reading helps, but systems thinking and mathematics become useful through contact with real decisions.

I would take one situation from my actual life or work each week: a sales process, a content pipeline, a personal habit, a family schedule, a product, a community or a financial decision.

Then I would do five things:

Draw the system on one page. List the main actors, resources, incentives, bottlenecks, delays and feedback loops. The drawing does not need to be clever. Its purpose is to make hidden relationships visible.
Choose three quantities. Find the few numbers that could change the decision: frequency, conversion, time, cost, probability, capacity or error rate.
Make a prediction. Write down what you expect to happen and when. Without a prediction, it is too easy to explain any outcome after it appears.
Use AI as an opponent. Ask it to identify a missing variable, propose an alternative causal explanation, find a counterexample and show which assumption is carrying most of the conclusion.
Return to the model. Compare the result with the prediction and change the map. The goal is not to be right the first time. The goal is to make the way you think correctable.

That last part may be the real skill: building models of the world that can survive contact with reality and still be updated.

Four books I would start with

Thinking in Systems: A Primer by Donella Meadows. This is the clearest starting point I have found. It explains stocks, flows, feedback loops, delays, resilience, boundaries and leverage points without turning the subject into abstract theory. The current Russian edition is titled Системное мышление. Как создавать и улучшать системы в бизнесе и жизни; earlier editions appeared as Азбука системного мышления.

The Fifth Discipline: The Art and Practice of the Learning Organization by Peter M. Senge. Useful when the system is an organisation. It connects systems thinking with mental models, collective learning and the ability of a company to adapt.

How to Solve It: A New Aspect of Mathematical Method by George Pólya. A compact book about problem solving: understanding the problem, building a plan, carrying it out and looking back. It is about mathematics, but the method travels well beyond mathematics.

How Not to Be Wrong: The Power of Mathematical Thinking by Jordan Ellenberg. A good bridge between mathematics and ordinary decisions. It shows that mathematical thinking is less about memorising formulas and more about seeing structures hidden beneath everyday claims.

A more useful relationship with AI

I do not want to compete with AI at producing the first acceptable answer. That race already looks pointless.

I want to become better at deciding which answer is worth producing, what it will change, how it can fail and whether the evidence beneath it is strong enough. AI can then become a multiplier instead of a substitute for judgment.

I do not know which models, interfaces or professions will dominate five years from now. I am increasingly convinced that learning another tool is not enough preparation for that uncertainty.

The roof will keep changing.

Systems thinking and mathematics still look like two good walls to build under it.

Sources

← All notes