What we know about how AI and technology become work.
Essays, evidence reviews, market notes and framework notes on AI and technology adoption in organizations.
- Trusting the system. Use, misuse and disuse of automationTrusting a system too much or too little has costs. What research on trust in automation says and what it means for adopting AI.Read →
- Generative AI at work. What the first field studies showTwo field studies on generative AI show real but uneven gains. Adoption depends on the task, on experience and on the judgement to use it.Read →
- Why AI pilots do not scale. What the studies showAlmost every organization is trying AI and few are scaling it. What recent studies show about the distance between the pilot and everyday work.Read →
- AI makes the question sharperWhen a technology suggests, decides or learns, adoption asks for more than new clicks. The underlying question stays the same.Read →
- Why training does not always reach the jobTraining transfer depends on who learns, how it is taught and the work environment, the hardest of the three to control. What the evidence says.Read →
- Change management and technology adoption. Where they overlap and where they differChange management models help prepare people. Technology adoption also calls for adjusting the initiative and looking at the actual work.Read →
- The productivity paradox. Why technology takes time to show up in resultsFrom Solow to the J-curve: why technology investments take time to show results, and the role played by changes in work and management.Read →
- How to measure technology adoption beyond loginsUsage dashboards count logins, not changes in the work. What research on measuring system use says and which questions to add.Read →
- AI agents. What changes in adoption when the tool actsAn AI agent does not only suggest; it carries out steps of the work. What it demands of people, and what research says about delegating to automation.Read →
- Routines are where change livesA new system changes little if the routines around it do not change. What research on organizational routines says about technology adoption.Read →
- The adaptation window. Why the period after go-live shapes how the work settlesImplementation studies show that adapting a technology is concentrated in a short period after it arrives. What that means after go-live.Read →
- Same technology, different outcomesTwo teams get the same system on the same day. Months later one uses it as part of the work and the other doesn’t. The difference lies in the relation.Read →
- Acceptance is not adoption. What TAM and UTAUT explain and what they leave outAcceptance models explain individual intention to use a system and its use. Adoption in an organization also means looking at the work and its context.Read →
- Training matters, but it is not enoughTraining builds part of an organization’s capacity. The rest has to exist in the organization, where the work happens.Read →
- The 70% myth. What the evidence says about change failureThe claim that 70% of organizational changes fail is repeated widely and has rarely been shown. What we know, and what to measure instead.Read →
- AI training. What a course does not buildTeaching people to use an AI tool is necessary, but it does not change the work on its own. What the data says and what else adopting AI takes.Read →
- Workarounds are evidenceThe parallel spreadsheet is not only a discipline problem. It is also information about what the change has not yet solved, worth reading before banning it.Read →
- Why technology implementations stall after go-liveGo-live proves that a system works, not that the work has changed. What research says about the stage where implementations stall.Read →
- Both sides can changeWhy adoption is not only something an organization has to achieve — and what changes when the initiative is open to adjustment too.Read →
- Using AI is not adopting it. What the data from Argentina showsPeople already use AI at work; organizations have not adopted it yet. What recent surveys on Argentina show and what it means for companies.Read →
- Installed is not adoptedA go-live tells you that a system works. It does not tell you whether the work has changed. Why installed and adopted are not the same thing.Read →