Truace
Subscribe
70/100

Moderate evidence

ProblemPublished recordScienceProblem Space

Full story
More
Export record JSONEmailLinkedInX

Does generative AI make us think alike? A systematic review and meta-analysis of homogenisation effects in human–AI co-creation

Truvace record
TRV-2026-2734raw data (JSON)
Version
v1Published
First published
Evidence type
Systematic review or meta-analysis
Sources
1 sourcePeer-reviewed
sha256
3e17ce083901…check it

Does generative AI make us think alike? As human–AI co-creation becomes embedded in creative practice, concerns have emerged that creative outputs may exhibit homogenisation, as reduced diversity of meanings, across users, even when individual creativity improves. We address this concern through a systematic review and three-level meta-analysis of empirical studies on homogenisation in human–AI co-creation (19 studies, 61 effect sizes). Results reveal a small but statistically significant homogenisation effect a…

The problem

A meta-analysis of 19 studies (61 effect sizes) found a small but statistically significant homogenisation effect, meaning less diverse creative output across users who co-created with generative AI.

What this doesn’t fix

The authors say the evidence for persistence beyond co-creative episodes and extension to real-world contexts is suggestive only, rather than firmly established.

Sources

1 on file
  1. Behaviour & Information Technologydoi:10.1080/0144929x.2026.2726451
    Peer-reviewed2026-08-31

Cite this record

v1

Truvace Impact Record TRV-2026-2734, v1: “Does generative AI make us think alike? A systematic review and meta-analysis of homogenisation effects in human–AI co-creation.” Truvace, 2026-11-12. /record/TRV-2026-2734 (accessed on the day you copy it). sha256 3e17ce0839014d9b…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv13e17ce083901…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2734 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.