Have you seen your design team get lost after adding AI tools?
Has anyone else watched their design team get lost after adding AI tools?
HCI Today summarized the key points
- •This is a post asking why work doesn’t improve much even after a team introduces AI tools.
- •The author points out that even after adding AI, the team sees little change—and instead, confusion in existing work increases along with more unrecorded decisions.
- •The comments argue that the core issue isn’t the tools themselves, but the way AI is simply attached without the team sharing its problems and the purpose of adoption.
- •They also worry that AI may replace judgment, documentation, and collaboration processes—weakening members’ initiative and their understanding of context.
- •Overall, the post suggests that for AI adoption, integration, training, and change management matter more than access permissions, and that confusion only grows when there are no clear usage guidelines.
This summary was generated by an AI editor based on HCI expert perspectives.
Why Read This from an HCI Perspective
This article makes you look at AI adoption not as a matter of ‘choosing tools,’ but as a question of ‘whether the team can actually absorb the change in practice.’ For HCI/UX practitioners and researchers, it surfaces core issues all at once—technology acceptance, work redesign, cognitive load, and the dispersion of tacit knowledge. In particular, it highlights that AI can increase unrecorded decisions rather than simply reducing decision-making.
CIT's Commentary
From a CIT perspective, we read this discussion not only as a story of AI adoption failure, but as a sign of how precisely the human–tool–organization relationship needs to be aligned. Many teams treat accessibility (access) and adoption as the same thing, but in reality, role reallocation, how decisions are recorded, and the redesign of review responsibilities must come together. In other words, AI is not a tool that automatically fills the gaps in work; it’s a mechanism that exposes friction points in existing workflows. CIT frames this as a problem of ‘transitioning the work system,’ not merely ‘introducing technology.’ So you should first track which decisions disappear and which new ones emerge.
Questions to Consider While Reading
- Q.What HCI metrics or observation items would be most effective for diagnosing a team’s AI absorption capacity in advance?
- Q.What collaboration rules and documentation practices should be designed to reduce unrecorded decisions after AI adoption?
- Q.How can you distinguish and evaluate cases where AI lowers cognitive load versus cases where it actually increases it?
This commentary was generated by an AI editor based on HCI expert perspectives.
Please refer to the original for accurate details.
Subscribe to Newsletter
Get the weekly HCI highlights delivered to your inbox every Friday.