{"id":6982,"date":"2026-04-02T23:57:53","date_gmt":"2026-04-02T21:57:53","guid":{"rendered":"https:\/\/foglioeuropeo.ilfoglio.it\/?p=6982"},"modified":"2026-04-02T23:57:53","modified_gmt":"2026-04-02T21:57:53","slug":"why-ai-is-making-your-skill-grids-obsolete","status":"publish","type":"post","link":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/why-ai-is-making-your-skill-grids-obsolete\/","title":{"rendered":"Why AI is making your skill grids obsolete"},"content":{"rendered":"

Now that artificial intelligence has become an inescapable fixture of strategic roadmaps, the human resources dimension has crossed a threshold: it is no longer a support function, it is a business imperative. Over the past months, one question has surfaced with stubborn consistency in every boardroom, every editorial meeting, every off-site: How do we transform our teams?<\/em> The answer, however uncomfortable, is already visible: current skill frameworks will not survive the next three years intact.<\/p>\n

During a recent workshop with a dozen European press groups, we projected their organizational charts for 2027. The finding was unanimous and unsettling: between 40% and 60% of current positions will undergo profound transformation. Not elimination \u2014 mutation. That distinction is precisely where the complexity lies, and where most organizations are making their gravest mistake, confusing restructuring with retraining.<\/p>\n

The Pyramid is exploding<\/strong><\/p>\n

The binary model \u2014 those who know AI, those who don’t \u2014 is not merely insufficient. It is actively dangerous as a planning lens. A more useful framework identifies four skill strata within any organization. First, AI literacy<\/em> for the entire workforce: understanding what a prompt is, what a model does, what hallucination means, what an autonomous agent can and cannot decide. Second, AI proficiency<\/em> for roughly 30% to 40% of staff: integrating AI into daily workflows, mastering prompt engineering, experimenting with what practitioners now call “vibe-coding” \u2014 the fluid, intuitive interaction with generative tools. Third, AI specialization<\/em> for 10% to 15%: retrieval-augmented generation, fine-tuning, agentic architectures. And finally, AI leadership<\/em> for senior executives: strategy, governance, and the ethics that no algorithm can arbitrate on its own.<\/p>\n

At a major Scandinavian media group, the gap-mapping exercise between current capabilities and the 2027 target was sobering. Out of a team of 200 people, only 12 currently possess level-three competencies. The three-year objective: 30. That means training 18 people to expert level while sustaining daily production and evolving internal processes simultaneously \u2014 a management challenge as much as a technical one.<\/p>\n

Roles that do not yet have names<\/strong><\/p>\n

The editor-in-chief of 2027 will no longer manage humans alone. They will orchestrate hybrid human-AI teams, define acceptable thresholds of automation, and arbitrate daily between efficiency and editorial integrity. The data journalist will move beyond database analysis: they will train specialized machine-learning models, build autonomous fact-checking agents, and design augmented investigative workflows spanning data collection, processing, and real-time monitoring. The photo editor will become a curator of AI-generated imagery, a deepfake detection expert, and a guardian of visual authenticity \u2014 the C2PA standard, already quietly reshaping content provenance, will be their new grammar.<\/p>\n

New titles are appearing on org charts that did not exist twelve months ago: AI Coordinator, Prompt Engineer, AI Ethics Officer, Chief Agents Orchestrator. The strategic question is not whether to create these roles, but when \u2014 and whether to recruit externally or develop talent from within. As with the IT revolution of the 1990s, the answer is rarely binary. At a prominent British daily, an AI Coordinator was hired from outside, while three “AI champions” were promoted from within the sports, economics, and international desks. A hybrid model that marries technical fluency with institutional knowledge \u2014 and one that travels well across media cultures.<\/p>\n

Transforming without dismantling<\/strong><\/p>\n

Three organizational architectures are emerging from the field. The centralized model<\/em> \u2014 an AI Lab or AI Hub with dedicated expertise \u2014 offers coherence but risks insularity. The distributed model<\/em>, seeding champions across every department, builds cultural ownership but can lack coordination. The hybrid<\/em>, combining a central team with sectoral relays, is proving the most resilient, though it demands the most careful governance. There is no universal formula. The right choice depends on size, organizational culture, and existing levels of centralization \u2014 factors that are rarely separable.<\/p>\n

What all successful models share is a single non-negotiable: a planning horizon of at minimum two to three years, structured in clear tiers. First, foundations and general AI literacy across the organization. Second, targeted upskilling of 30% of the workforce in applied tools and workflows. Third, full maturity through continuous learning programs that evolve with the technology itself.<\/p>\n

This is a strategic imperative of the same order as governance reform or product innovation. The pace of technological disruption \u2014 models that reshape the landscape every three to six months \u2014 should not induce paralysis. It should sharpen foresight and demand institutional agility. Organizations that approach this transformation realistically, with humility about what they do not yet know, will build a durable advantage. Those that delay will find themselves not merely behind the curve, but competing for a shrinking pool of talent that the more decisive have already recruited.<\/p>\n

Christophe Isra\u00ebl<\/span><\/span> is a journalist and an consultant in AI & digital strategy.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Now that artificial intelligence has become an inescapable fixture of strategic roadmaps, the human resources dimension has crossed a threshold: it is no longer a support function, it is a business imperative. Over the past months, one question has surfaced with stubborn consistency in every boardroom, every editorial meeting, every off-site: How do we transform […]<\/p>\n","protected":false},"author":4,"featured_media":7013,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"iawp_total_views":45,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-6982","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-senza-categoria"],"acf":[],"_links":{"self":[{"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/posts\/6982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/comments?post=6982"}],"version-history":[{"count":7,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/posts\/6982\/revisions"}],"predecessor-version":[{"id":7109,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/posts\/6982\/revisions\/7109"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/media\/7013"}],"wp:attachment":[{"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/media?parent=6982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/categories?post=6982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/foglioeuropeo.ilfoglio.it\/en\/wp-json\/wp\/v2\/tags?post=6982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}