Ulrik la Cour Christiansen / Cases

Why AI stays narrow

Master's thesis: 13 interviews at Statens Serum Institut on why a company-wide AI tool was only used for a few things.

Graded 12, presented at an SDU staff seminar, September 2026

Role
Sole researcher, master's thesis
Question
Why did a company-wide AI tool end up used for only a few things?
Method
13 interviews across research and support roles, plus a working prototype
Result
4 findings, graded 12, invited to present at a staff seminar, Department of Business and Management, SDU, September 2026
A task insomeone's routineIs the AI's outputcheap to check?yesnoAI gets used forfinding things, polishingtext and writing codeAI stays unusedeven by the same person,in another taskThe task decides the fit, more than the person does.
The core finding in one picture.

The question

Statens Serum Institut gave all staff a company GPT tool. Use stayed narrow: some people used it for a few tasks, many not at all. The usual explanations blame people: resistance, missing training, weak management. I asked whether the work itself explains it better.

What I did

A qualitative single case study: 13 semi-structured interviews with researchers and support staff across very different roles, analysed with template analysis into 35 codes, 9 themes and 3 dimensions. Four interviewees did two structurally different kinds of work, which gave a within-person comparison: the same person, different tasks, different adoption.

I then built the tool the interviewees described, a scope-specified reference assistant in n8n, and compared its behaviour with the generic tool.

The theory behind it

The thesis combines organisational routine theory with the dynamic capabilities literature. Routine theory says work is carried by recurring patterns of action, and a new tool has to fit into them to stick. Dynamic capabilities explains why an organisation's ability to change those patterns is built and learned over time, and cannot simply be bought.

Put together, they predict what the interviews showed: a generic AI tool is absorbed where it fits the routine and where its output can be verified cheaply, and nowhere else. The method was an abductive single case study with template analysis, and a design science prototype to test the remedy the users described.

What I found

  1. Adoption depends on the task more than on the person. Four interviewees used AI in one part of their job and not in another, so the same person gives both outcomes.
  2. AI lands where its output is cheap to check. Across roles, use converged on finding things, polishing text and writing code.
  3. Not using it is four different problems, each with its own fix, and nobody in the organisation was turning individual learning into shared practice.
  4. The users already describe the fix: AI scoped to one job, anchored in their own material, built into the tools they use, with clear rules on what it is for.

What it means for a company

More training and encouragement will not move the number. Pick routines where results are easy to verify, build a scoped tool for each, and give a small cross-functional team the mandate to find the next one. Implement it routine by routine.

He developed an original analytical perspective on this very topical and highly relevant question, the process innovation being driven by AI, by combining two different, established theories in a way that has not yet been applied to the question in the scientific literature, as far as I am aware.

Markus C. Becker, Professor at the Strategic Organization Design unit, University of Southern Denmark, editor of the Handbook of Organizational Routines, and my thesis supervisor (from his letter of recommendation)

Stack: Qualitative single case study, template analysis, design science prototype in n8n.

Code: The thesis is available on request.

All cases