Making the Invisible Visible: Understanding the Mismatch Between Organizational Goals and Worker Experiences in AI Adoption
Drawing on interviews across healthcare, finance, and management, this paper argues that AI adoption often fails because workers are excluded from design and decision-making, creating a critical mismatch between organizational goals and real-world experiences that requires multi-level adaptation strategies to resolve.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine a company decides to install a brand-new, super-smart robot assistant in the office. The bosses think, "Great! This robot will make everything faster, cheaper, and easier." They imagine the human workers will just sit back, relax, and let the robot do the heavy lifting while they focus on "important" stuff.
But in reality, the workers are frustrated. They feel like the robot is getting in the way, making mistakes, or taking over jobs they actually enjoy. The result? The workers ignore the robot, work around it, or just hate it.
This paper is like a detective story that asks: Why does this mismatch happen? The authors went into real offices (hospitals, banks, and management companies) and talked to 16 workers to find out what's really going on. They discovered that while the bosses see the robot as a "magic tool," the workers see it as a clumsy, invisible partner that doesn't understand how they actually work.
Here is the breakdown of their findings using simple analogies:
1. The "Silent Partner" Problem (Structural Issues)
The Analogy: Imagine a basketball team where the coach (the boss) tells the players to pass the ball to a new robot player. But the robot never talks to the other players, doesn't know the team's secret hand signals, and refuses to pass the ball back.
What the paper found:
- Isolation: The AI systems often work alone. They don't help the team talk to each other. In a hospital, for example, the AI might give a doctor a diagnosis, but it doesn't help that doctor explain it to the nurses or other specialists. It breaks the "team huddle."
- The "Big Boss" vs. "The Worker" Gap: The bosses love the AI because it tracks productivity and makes schedules. But the workers feel like the AI is a spy watching them. The bosses want the workers to follow the robot's orders, but the workers feel the robot doesn't understand their daily reality, so they secretly ignore it.
2. The "Wrong Tool for the Job" Problem (Task Issues)
The Analogy: Imagine you are a professional chef. You love chopping vegetables and plating the food (the creative, skilled part). But the new robot is assigned to chop the vegetables and plate the food, leaving you with the job of scrubbing the pots and peeling the onions (the boring, repetitive part). You feel useless and annoyed.
What the paper found:
- Taking the Fun Stuff: In finance and management, workers felt the AI was taking over the "fun" parts of their jobs (like making the final loan decision or planning an ad campaign) and leaving them with the boring, tedious data entry.
- Getting in the Way: In healthcare, the AI sometimes gave bad advice or alerts that weren't helpful. Instead of helping the doctor, the doctor had to stop, check the robot's work, and fix its mistakes. This slowed everyone down.
- The "Black Box" Feeling: Workers felt they had no control. If the AI said "No" to a loan or a treatment, the worker couldn't explain why to the customer or patient. They felt like they were just messengers for a robot they didn't understand.
3. The "One-Size-Fits-All" Problem (Worker Issues)
The Analogy: Imagine a teacher giving the exact same textbook to a kindergarten student and a PhD professor. The professor is bored because the book is too simple; the student is lost because it's too hard.
What the paper found:
- Confusion for Newbies: New workers (trainees) needed the AI to explain how it made a decision so they could learn. But the AI just gave a simple "Yes" or "No," leaving them in the dark.
- Annoyance for Experts: Experienced workers (experts) just wanted a quick check. They didn't need the AI to explain the basics; they needed it to spot rare, tricky errors. Instead, the AI gave them too much basic info, slowing them down.
- Fear of Mistakes: Workers were scared to trust the AI because they didn't know when the AI was unsure. If the AI was wrong, the worker was the one who got blamed.
The Solution: Making the Invisible Visible
The authors argue that to fix this, companies need to stop treating workers like "passengers" and start treating them like "co-pilots." They suggest three changes:
- Talk to the Workers (Worker Level): Don't just dump the AI on them. Ask them what they need. If a new doctor needs a different explanation than a veteran doctor, the AI should change its voice to match. It should speak the language of the worker, not the language of the computer.
- Fix the Job Description (Task Level): Don't let the AI take the "fun" parts of the job. Let the AI do the boring, repetitive stuff (like scheduling or data entry) so the humans can do the thinking, the explaining, and the creative work. The AI should be a helper, not a replacement.
- Connect the Team (Structure Level): The AI shouldn't just talk to one person; it should help the whole team talk to each other. It should act like a translator that helps the doctor, the nurse, and the admin understand each other better, rather than creating a wall between them.
The Bottom Line
The paper concludes that AI fails not because the technology is bad, but because the people using it are invisible in the design process. If companies want AI to work, they need to listen to the workers, respect their expertise, and design systems that fit into the real, messy, human way people actually do their jobs.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.