insights

AI, behaviour and work.

Articles on how people work with AI, followed by what the research says so far. Always sourced, with a new article every week.

latest 21 October 2026 · the psychology of AI · 3 min read

Why your team trusts AI too much, or too little

Some people copy every AI answer without checking; others give up after one mistake. What research says about trust in AI, and how to get your team to the right level of trust for each task.

  1. After one AI mistake, people give up faster than after the same mistake by a colleague. That's algorithm aversion.
  2. At the same time, we readily copy polished AI answers without checking. That's automation bias.
  3. The goal isn't more or less trust, but the right trust for each task. Three questions help.
Read article →
research

What we know about AI at work.

What the research says about what AI delivers, why people do or don’t trust it, and what makes them keep using it. Every claim comes with its source.

last updated: October 2026

01

What AI delivers, and where it goes wrong

  • In an experiment with realistic writing tasks, people using ChatGPT finished roughly 40 percent faster, and their work was rated about 18 percent higher.[1]
  • Among customer support agents, issues resolved per hour rose by 15 percent on average. Less experienced agents gained the most.[2]
  • Consultants who used AI on tasks it handles well completed more tasks, faster and to a higher standard. On a task outside that range, they were more likely to get it wrong than colleagues without AI.[3]

for your team AI pays off most when people know which tasks it helps with and which it doesn’t. That isn’t technical knowledge, it’s judgement, and judgement can be trained.

02

Trust: too much or too little

  • People abandon an algorithm faster after seeing it make a mistake, even when it outperforms humans on average. This is known as algorithm aversion.[4]
  • In other situations the opposite happens: people are more likely to follow advice when they believe it comes from an algorithm.[5]
  • People working with automated systems check less carefully the more reliable the system seems. This is known as automation bias.[6]

for your team The goal isn’t more trust or less trust, it’s the right amount for each task. And that starts with understanding how a language model arrives at an answer.

03

When people actually start using a tool

  • Whether people adopt a new technology depends heavily on two things: do they find it useful, and do they find it easy.[7]
  • Later research adds social influence and organisational support: what colleagues and managers do and expect matters.[8]

for your team One enthusiastic colleague isn’t enough. Adoption happens when the value shows up in people’s own work, and when the team agrees on it together.

04

Technostress

  • New technology can be a source of stress: pressure to work faster, always being reachable, or the sense of never keeping up. This technostress is linked to more role stress and lower productivity.[9]

for your team Pushback on AI is often uncertainty rather than unwillingness. More tool explanations won’t fix that. A proper conversation and clear agreements will.

05

Learning as a group

  • Teams learn better when people feel safe to ask questions, make mistakes and voice doubts. This is known as psychological safety.[10]

for your team That’s why the training runs on group discussion and your own examples, not just explanation.

06

Our own numbers

From the first AI sessions onwards, I measure before the training and four weeks after how often participants use AI and how confident they feel doing it. The results will appear here once there’s enough data.

Sources

  1. [1] Noy, S., & Zhang, W. (2023). Experimental evidence on the productivity effects of generative artificial intelligence. Science, 381(6654), 187–192. doi.org/10.1126/science.adh2586
  2. [2] Brynjolfsson, E., Li, D., & Raymond, L. R. (2025). Generative AI at work. The Quarterly Journal of Economics, 140(2), 889–942. doi.org/10.1093/qje/qjae044
  3. [3] Dell'Acqua, F., McFowland, E., Mollick, E. R., Lifshitz-Assaf, H., Kellogg, K., Rajendran, S., Krayer, L., Candelon, F., & Lakhani, K. R. (2023). Navigating the jagged technological frontier: Field experimental evidence of the effects of AI on knowledge worker productivity and quality. Harvard Business School Working Paper 24-013. doi.org/10.2139/ssrn.4573321
  4. [4] Dietvorst, B. J., Simmons, J. P., & Massey, C. (2015). Algorithm aversion: People erroneously avoid algorithms after seeing them err. Journal of Experimental Psychology: General, 144(1), 114–126. doi.org/10.1037/xge0000033
  5. [5] Logg, J. M., Minson, J. A., & Moore, D. A. (2019). Algorithm appreciation: People prefer algorithmic to human judgment. Organizational Behavior and Human Decision Processes, 151, 90–103. doi.org/10.1016/j.obhdp.2018.12.005
  6. [6] Parasuraman, R., & Manzey, D. H. (2010). Complacency and bias in human use of automation: An attentional integration. Human Factors, 52(3), 381–410. doi.org/10.1177/0018720810376055
  7. [7] Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319–340. doi.org/10.2307/249008
  8. [8] Venkatesh, V., Morris, M. G., Davis, G. B., & Davis, F. D. (2003). User acceptance of information technology: Toward a unified view. MIS Quarterly, 27(3), 425–478. doi.org/10.2307/30036540
  9. [9] Tarafdar, M., Tu, Q., Ragu-Nathan, B. S., & Ragu-Nathan, T. S. (2007). The impact of technostress on role stress and productivity. Journal of Management Information Systems, 24(1), 301–328. doi.org/10.2753/MIS0742-1222240109
  10. [10] Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. doi.org/10.2307/2666999

haven’t done it yet? the team scan takes a minute.

Start the team scan