The uncomfortable career lesson in Spain’s latest AI work story is not that software can generate more images, code, or copy. It is that an employer can turn that productivity claim into a staffing argument. For workers, the weak response is adding a vague AI skills line to a CV. The stronger response is documenting the parts of the job that are not just output volume.

El Confidencial reported what it called the “Primera sentencia en España” linking an Expediente de Regulación de Empleo, or ERE, with artificial intelligence. That makes the case useful beyond the legal headline. It gives learners and midcareer workers a practical question to answer before a restructuring does: if AI changes the productivity assumption around your role, what evidence shows your judgment, accountability, client context, and workflow ownership?

What El Confidencial says changed in the productivity argument

According to El Confidencial, judgment no. 864/2026 from the Social Chamber of the Madrid High Court resolved an appeal tied to a collective dismissal at a video game development company and sided with the company. The company argued that AI improved the visual quality of video games, user ratings, agility, and efficiency, according to the same report. That is not the same as saying every creative or technical role is replaceable. It is a more specific signal: employers may increasingly frame AI not as a tool perk, but as a reason to redraw the amount of labor needed for a workflow.

For careers, the title on the badge is less important than the value trail behind the work. A designer who only presents finished assets is easier to describe as output capacity. A designer who can show how they interpreted player feedback, managed brand constraints, rejected risky generations, coordinated with engineering, and owned approvals has a different file of evidence. The same applies to analysts, marketers, support leads, producers, and developers: do not just say you use AI, show where you make decisions the tool cannot be accountable for.

HuffPost’s figures show why context matters

HuffPost reported that the video game design company applied an ERE to 13 workers in December 2024, citing losses and AI tools that could accelerate work. It also reported that revenue fell from €7.99 million in 2023 to €4.59 million in 2024, while a €646,297 profit turned into a €3.54 million loss. That matters because the AI argument did not appear alone in the account. It sat beside a deteriorating business case, which is often how workforce changes are justified in practice.

HuffPost also reported that the company said AI generated images could improve visual quality, shorten work time, and support reorganization in creative and graphic production areas. But it cautioned that the judgment “no entra a valorar la legitimidad” of replacing workers with AI or setting doctrine on that issue. In plain career terms, do not overread one ruling as a universal rule. Do read it as a warning that measurable workflow change can become part of how employers discuss headcount.

The BOE page for Spain’s Workers’ Statute shows the consolidated text was last updated on Oct. 21, 2026. Workers facing an actual ERE need qualified labor advice, not a LinkedIn thread or a certificate vendor’s webinar. But people planning their next skill investment can still take a clear lesson from the employment mechanism: AI literacy is not enough if your contribution is described only as faster production.

The skill signal is moving from tool use to ownership

Stack Overflow’s 2024 Developer Survey found that 76% of respondents use or plan to use AI tools in their development process. When a skill becomes that common, it stops being a differentiator by itself. Saying you can prompt a model is like saying you can use spreadsheets in a finance role: sometimes necessary, rarely sufficient. The signal moves to the workflow around the tool.

The OECD says more than one third of individuals across the OECD used generative AI tools in 2025, and it flags risks to privacy, safety, security, and human autonomy. Those risks are not abstract career decorations. They are exactly where human accountability can become visible: deciding what data should not be pasted into a tool, checking whether an output is safe to ship, explaining tradeoffs to a client, or owning the consequences when automated work affects users.

This is where credential inflation gets exposed. A short course that teaches AI buzzwords may help you start, but it will not prove that you can run a workflow under constraints. A useful learning path should leave you with artifacts: before and after process maps, quality checks, prompt logs tied to decisions, review rubrics, stakeholder notes, and examples of where you overruled or corrected model output. Hiring managers and internal promotion panels may not phrase it that cleanly, but they screen for proof that you can be trusted with the work, not just the tool.

What workers should document next

El Confidencial’s report should push workers to build a value dossier, not panic buy credentials. For each recurring task, write down what the tool produces, what you decide, who depends on that decision, and what risk you carry if it goes wrong. If you are 25, that record helps you turn junior output into evidence of operating judgment. If you are 45, it helps translate institutional memory and client context into something visible before the next reorganization spreadsheet is built.

The practical move is to make your job harder to compress into a unit count. Save examples of ambiguous briefs you clarified, defects you caught, customers you understood, constraints you balanced, and handoffs you improved. AI may change productivity assumptions, and in some workplaces it already has. Your response is not to claim immunity from automation, but to make the human part of the workflow specific, evidenced, and difficult to ignore.

Sources