Aug 27, 2026 · 37 min
AI adoption fails when organizations ignore how people work
Beyond the Dashboard: Solving AI Adoption Gaps
The episode shows why technical capability alone rarely produces AI returns when culture, workflows, and employee concerns remain unaddressed.
- 1Organizations should define real work problems before selecting or building AI tools.
- 2Different teams need tailored workflows, training, and support rather than one universal AI deployment.
- 3Leaders can reduce deskilling fears and shadow AI by involving employees in collective use-case design.
Don't miss
Tamara Moellenberg explains why organizations should identify shared workflow frustrations before employees independently seek alternative AI tools.
The brief
Tamara Moellenberg of Red Associates argues that AI adoption is a human and organizational challenge, not simply a matter of deploying capable technology.
The conversation examines how workplace language shapes behavior: framing generative AI as a GPS may encourage people to outsource judgment and fear losing skills.
Rather than building one tool for everyone, organizations should involve employees early and design workflows around distinct teams, subcultures, and real use cases.
Microsoft Copilot works for some Dell use cases but falls short for marketing and other teams, exposing the tension between standardization, customization, and training.
The standout warning is that unsupported workflows can push employees toward shadow AI, making collective frustrations a better starting point than isolated user fixes.
Moellenberg’s central takeaway is that leadership signals, culture, and the surrounding work environment determine whether AI improves practice and produces a return.
Weekly email
State of the Pod, every Monday
The week's most-discussed names and stories from podcasts, with the moments behind them. Free, five minutes, unsubscribe in one click.