Artificial Intelligence

Who is afraid of AI? Who should be?

If you follow current debates, you might think that everyone should be afraid of AI.
Or no one. Or only “the others.”

A recent policy brief by the Kiel Institute for the World Economy takes a more differentiated – and refreshingly evidence-based – view.

Here some insights from a knowledge management perspective:

  1. Exposure is not the same as replacement:
    One of the most important clarifications in the study is also one that is often missing in discussions: “Exposure to AI … indicates the potential applicability of AI to an occupation’s tasks — it is not inherently a measure of substitution or complementarity.”
    In other words:
    Just because AI can do parts of your work does not mean it will replace you.
    For knowledge work, this is a crucial distinction. Even in organisations where AI is already deeply embedded it does not necessarily reduce headcount. Instead, we see shifts in how work is done and what kind of knowledge becomes critical.
  2. Surprise(?): High-skilled knowledge workers are most exposed
    The study shows a pattern that is different from previous economic transformations: Highly cognitive, non-physical, low-social-interaction jobs (e.g. analysts, developers, translators) are most exposed to AI. Whereas, jobs requiring manual skills or intensive interpersonal interaction are least exposed.
    It is not the “low-skilled” jobs that are immediately most affected – it is classic knowledge work.
    From a KM perspective, these are precisely the domains where structured knowledge, explicit processes, and codified expertise already exist – making them easier for AI to engage with. Or following Willkes definition of knowledge work it is the knowledge-intense work (not the actual knowledge work).
  3. No (immediate) job loss – but skill shifts
    The empirical results across Denmark, Portugal, and Sweden are remarkably consistent:
    – No significant negative effect on total employment
    – Clear shift towards higher-skilled work (“skill upgrading”)
    Firms exposed to AI “raise their high-to-low skill employment ratios” and reallocate toward high-skill white-collar jobs.
    This fits closely with what many of us observe in practice:
    Routine documentation is automated, analytical work is accelerated. But interpretation, integration, and contextualisation become more important.
    Or, in KM terms: We are moving from information processing to meaning-making (from explicit to tacit).
  4. The overlooked dimension: social and tacit knowledge
    A particularly interesting methodological choice in the study is the inclusion of social skills as a counterweight to AI exposure:
    Social tasks are assumed to be more difficult to automate. This aligns strongly with long-standing KM insights:
    Tacit knowledge is hard to codify.
    Social interaction is key to knowledge creation (think SECI…).
    Context and trust cannot easily be replicated by systems.
    If you connect this to earlier discussions on this blog (e.g. on knowledge transfer during offboarding or peer-based formats like Peer Assist), a clear conclusion emerges:
    What protects jobs is not the absence of AI—but the presence of social, contextual, and experiential knowledge work.
  5. Not all AI is the same – and that matters
    Another important nuance in the study: Different AI subdomains have different effects. In particular: Language modelling, speech recognition, reading comprehension show positive associations with employment across all skill groups.
    This is highly relevant for organisations currently introducing generative AI: These systems are not only automation tools – they are collaboration technologies. They amplify communication, documentation, and coordination – core KM processes, if used correctyl and not as a Google 2.0.

What does this mean for knowledge management?

If we step back, the findings point to a shift in the KM agenda.

From:

  • Capturing knowledge
  • Structuring information
  • Reducing redundancy

To:

  • Enabling skill development
  • Supporting AI-augmented workflows
  • Strengthening social knowledge processes

Or more provocatively:
The real risk is not that AI replaces knowledge workers.
The real risk is that organisations fail to redefine knowledge work.

So, who should be afraid?

The answer from the study is clear: It depends on the tasks you perform.

Be concerned if your work is:

  • Highly standardised
  • Easily codified
  • Low in social interaction

Be optimistic if your work involves:

  • Interpretation and judgment
  • Cross-context integration
  • Collaboration and sensemaking

However, AI does not primarily eliminate work. It reshapes the skill profile of work. Which is not a surprise, is it?
But what are the implications for knowledge management?

  • We need better ways to develop and transfer higher-order skills.
  • We need to redesign knowledge processes for human–AI collaboration.
  • And we need to take tacit and social knowledge more seriously than ever.

Because in the end, the question is: Who is prepared to work differently with knowledge?

And another question that arises from this is: What does this mean for young people entering the workforce?
To be continued.

What We Can Learn from Medical Technology Industry About Reliable AI

It is quite rare for my two main areas of consultancy – knowledge management and computerised system validation in the pharmaceutical sector – to overlap, but when it comes to AI…

Whilst many companies are still experimenting with prototypes, the medical sector has already established a strict framework for the safe use of these technologies: Good Machine Learning Practice (GMLP).
These ten principles, developed by leading regulatory bodies such as the FDA (US Food and Drug Administration) and the IMDRF (International Medical Device Regulators Forum), provide a blueprint for robust and trustworthy AI systems, not only in the regulated field of medical technology.

Here are the key GMLP principles:

  1. Interdisciplinary teams rather than siloed solutions
    An AI model is only as good as the understanding of its intended purpose. GMLP requires experts from various disciplines to collaborate throughout the entire lifecycle. Engineers, data specialists and the actual end-users must work together to define the clinical or business benefits the AI is intended to deliver, as well as the risks involved.
  2. Sound software engineering and security
    AI is software – and should be treated as such. This means consistently applying best practices in software engineering, cybersecurity and risk management. A methodical design process ensures that decisions are traceable and that the integrity and authenticity of the data are maintained.
  3. Data quality and representativeness
    A common mistake in AI projects is a ‘bias’ in the data. GMLP stipulates that datasets must reflect the actual target population. If, for example, only data from a specific user group is used, the model will fail in the real world. Careful data governance is key here.
  4. Strict separation of training and test data
    To objectively evaluate a model’s performance, the training and test datasets must be strictly independent of one another. This prevents ‘label leakage’ – a phenomenon whereby the model ‘guesses’ the outcome based on hidden clues in the training data, rather than learning genuine patterns. Only through independent testing can it be demonstrated that the AI also works with new, unknown data.
  5. Suitability of reference standards
    Use of the best available (clinical) methods for generating reference data
  6. Tailored model design
    The model design must be suited to the available data and the intended use in order to minimise risks such as overfitting
  7. Focus on human-AI interaction
    In practice, AI rarely operates entirely independently. GMLP therefore focuses on the interaction between humans and machines. It is essential to ensure that users can interpret the AI’s outputs correctly and that no dangerous over-reliance on the system develops. Transparency and clear information about the system’s limitations are essential for this.
  8. (Clinically) Relevant test conditions
    Testing is carried out under conditions that simulate real-world clinical use
  9. Clear user information
    Users are provided with transparent information about the system’s capabilities, limitations and updates/re-training.
  10. Control does not stop after roll-out
    An ML model is not a static product. GMLP requires continuous monitoring of performance in real-world use (‘post-market monitoring’). This allows performance declines caused by changing data patterns (dataset drift) to be detected at an early stage and risks associated with retraining the model to be managed.

At first glance, applying these principles may seem like a lot of work. However, it is just necessary if we should build trust in AI, isn’t it? And for me the main message is: „It is the controlled data quality, stupid“.

Forecast to knowledge – recording of WMOOC live session available online

Another recording of a live session of our Knowledge Management MOOC (WMOOC) 2025 is now online. The only one in English at this year’s course. With this live session, we left behind the boundaries of the organization we usually operate within and looked at our topic of KM from a (global) political perspective. It was extremely interesting and stimulating. Thank you very much, Yannick! (Duration 43’40 Min.)