AI Makes Cross Disciplinary Polymath Thinking Valuable
The judgment gap that AI cannot close
Something quietly consequential happens when a language model drafts a compliance memo, summarizes a dataset, or proposes an architecture in seconds. The output arrives polished, plausible, and complete — and the person receiving it has to decide whether to trust it. That decision is not technical. It is judgment, and judgment is precisely what the tool does not supply. Research from the Open University of Catalonia (UOC) has found that this gap is reshaping what the AI-era job market values, with polymath profiles — people who hold relevant knowledge across several disciplines and can connect it — gaining ground as the skills employers expect evolve (CIO). [1] The lift here is concrete rather than aspirational. AI has made technical knowledge cheap; the best explanation of almost anything is seconds away for anyone with a browser. What the technology cannot manufacture is the ability to make an informed judgment about what it produces. As UOC education researcher Laia Lluch Molins puts it, what’s scarce is no longer knowledge itself, but the ability to make informed judgments (CIO). [1]. [1] That scarcity is the opening for people who think across boundaries.
What a polymath actually is — and is not
The word invites misunderstanding. A polymath is not a person who knows a little about a great many things, a trivia generalist with a wide but shallow shelf. Óscar García Gozálvez, senior director of permanent staffing services at Hays Spain, draws the line precisely: a polymath is someone who possesses relevant knowledge and skills in multiple disciplines, with a broad and cross-disciplinary vision who’s able to make connections in order to problem solve, innovate, and make better decisions (CIO). [1]. [1] The emphasis falls on relevance and on connection, not on volume.
Molins sharpens the distinction further. The difference between a polymath and a specialist is not how much a person knows but what they do with what they know (CIO). [1]. These workers formulate new questions and solve problems that no single discipline could crack on its own. That capacity for synthesis is what makes them attractive to companies now, and it is a different asset from depth.
The economics of connection
Why would a company pay for breadth when it has spent decades rewarding depth? Because the value lands at the level of the whole organization rather than inside one function. Polymath profiles generate economic and strategic value for the entire company instead of remaining contained within isolated specialties (CIO). [1]. The gain is not that these people do more tasks — they do not simply tick off longer lists — but that they connect dots others cannot see.
The mechanism is worth spelling out. AI is not only replacing discrete tasks; it is breaking down the barriers between disciplines. When the tooling itself blurs the line between a data question and a legal question, or between a security problem and a compliance problem, the person who can move across those lines becomes the one who can actually use the tooling. Molins frames the division of labor cleanly: polymaths don’t compete with AI in what AI does well, but rather help solve what AI struggles with (CIO). [1]. The machine handles retrieval and generation. The human handles the judgment about which retrieved thing matters and why.
Where the friction sits: the recognition problem
The obstacle to this lift is not the absence of capable people. It is the absence of categories to recognize them. Molins offers a diagnostic that cuts through a lot of corporate rhetoric: Tell me how you evaluate your team, and I’ll tell you what kind of profile you’re developing (CIO). [1]. Companies may talk endlessly about cross-functionality, but if that cross-functionality is neither respected nor listened to, multi-talented individuals stop contributing and stop sharing new perspectives. The talent does not disappear. It goes quiet.
This lands hardest on CIOs, because IT environments have historically rewarded technical depth above almost everything else. A recognition system built to measure depth does not always know where to place someone whose worth lies precisely in connecting, translating, and asking the questions others do not ask. Molins names the risk with unusual clarity: the risk isn’t the polymath profile not fitting, but the culture lacking the categories to appreciate it (CIO). [1]. The missing piece is not the person. It is the slot.
The bottlenecks are already visible
Inside IT organizations, the need is not hypothetical. Molins observes that bottlenecks are mostly due to miscommunication or a lack of alignment with the business, not technical hinderances (CIO). [1]. That distinction matters enormously. If the delays were technical, more engineers would fix them. Because they are translational — between teams, between IT and the business, between what a system does and what the organization needs it to do — the hybrid profile is not a foreign body but the missing piece.
This is the quiet argument for breadth that specialists sometimes miss. The person who can speak the language of the database team and the language of the finance team does not replace either. They remove the friction between them, and friction is where schedules die. A technically brilliant team that cannot explain its constraints to the business may keep missing deadlines it could have met, and no amount of additional technical skill will fix a problem that lives in the gap between functions.
The three intersections that will matter
Molins identifies three intersections where polymath value will concentrate (CIO). [1]. The first is business acumen, treated as something transversal and valuable rather than a soft add-on. The second is communication and collaboration skill, the connective tissue that keeps work flowing and prevents silos from hardening. The third is knowledge of the humanities and social sciences, which brings in ethics — an area that will gain considerable weight in the coming years.
That third intersection deserves attention because it is the one most often dismissed as decoration. As AI moves from pilot to real-world adoption, the hard questions that surface are not about throughput. They concern bias, data ethics, and responsibility. García Gozálvez notes growing interest in profiles that combine technology, risk, compliance, and AI governance — a combination that is neither pure engineering nor pure policy (CIO). [1]. The people who can hold both sides of that combination are the ones who will define how organizations deploy these systems without creating liabilities they cannot see.
Reading the hiring market honestly
The trend is real but not yet a boom, and honesty about that matters. Looking at the Spanish market, García Gozálvez reports no massive demand for generalist profiles (CIO). [1]. What has increased is the search for professionals with a strong primary specialty plus a second or third skill that amplifies their impact on the company. The market is not hiring for breadth instead of depth. It is hiring for depth plus reach.
His expectation is that this accelerates over the next three to five years, as companies move from learning to incorporate AI to learning how to work in environments where AI has changed everything (CIO). [1]. The first phase is adoption. The second phase — the harder one — is the redesign of how work flows once the tool is everywhere. That redesign is where cross-disciplinary judgment stops being a nice-to-have and becomes the operating requirement.
What the hybrid profile actually delivers
The strength of the hybrid IT profile, in Molins’s framing, is having a solid technical foundation from which to build bridges with sound judgment (CIO). [1]. The foundation is not optional. A person who cannot evaluate a technical claim cannot translate it, and a translator who does not understand the source language is just guessing. The bridges are built from something solid, which is why the market wants a strong primary specialty first and amplification second.
The collaborations being sought follow that logic: software engineering paired with AI, data paired with cloud, cloud paired with security, cybersecurity paired with risk and compliance (CIO). [1]. Each pairing is not a doubling of skills but a compression of the distance between two domains that increasingly have to talk to each other. Add critical thinking and business acumen, and the profile becomes something an organization can build strategy on rather than simply staff a function with.
The time horizon problem
There is a reason the shift feels slower than the argument for it. In the author’s view, the value a polymath creates — a decision avoided, a misalignment caught, a question asked at the right moment — is diffuse and often invisible in the quarter it occurs. The cost of not having one is equally diffuse, showing up later as a project that drifted, a compliance gap that surfaced, a team that kept building the wrong thing efficiently. Progress and consequence rarely share the same time horizon, and organizations measure what lands on the calendar.
That mismatch is the real obstacle. What AI has not lifted is the ceiling on judgment, and judgment is where the remaining advantage lives. The organizations that will benefit most are the ones willing to build the categories to see that advantage — to evaluate their teams for connection and translation, not only for depth. The lift is real. The question is whether the scoreboard is ready to register it.