We scan new podcasts and send you the top 5 insights daily.
Teams embrace AI more quickly when it enables them to perform entirely new tasks they couldn't do before, like coding or advanced data analysis. This is more motivating than using AI for incremental improvements on existing workflows, which can feel less exciting and impactful.
Instead of relying solely on top-down, consultant-led workflow automation, enterprises should empower individual employees with AI tools. This builds user fluency and intuition, allowing them to pull AI into their own workflows, resulting in greater overall impact and less disempowerment.
To get skeptical engineers to adopt AI, don't focus on complex coding tasks. Instead, provide tools that automate the tedious, soul-crushing "paper cut" tasks like writing unit tests, linting, and fixing design debt. This frames AI as a tool that frees them up for more enjoyable, high-impact work.
Providing AI licenses isn't enough. Companies must actively manage the transition of employees from basic users (asking simple questions) to advanced users who treat AI as a collaborator for complex, high-value tasks, which is where real ROI is found.
To overcome employee fear of AI, don't provide a general-purpose tool. Instead, identify the tasks your team dislikes most—like writing performance reviews—and demonstrate a specific AI workflow to solve that pain point. This approach frames AI as a helpful assistant rather than a replacement.
The biggest resistance to adopting AI coding tools in large companies isn't security or technical limitations, but the challenge of teaching teams new workflows. Success requires not just providing the tool, but actively training people to change their daily habits to leverage it effectively.
When employees are 'too busy' to learn AI, don't just schedule more training. Instead, identify their most time-consuming task and build a specific AI tool (like a custom GPT) to solve it. This proves AI's value by giving them back time, creating the bandwidth and motivation needed for deeper learning.
C-suites are more motivated to adopt AI for revenue-generating "front office" activities (like investment analysis) than for cost-saving "back office" automation. The direct, tangible impact on making more money overcomes the organizational inertia that often stalls efficiency-focused technology deployments.
Bill Glenn suggests a phased AI rollout for teams. Phase 1 focuses on efficiency and automating repeatable tasks to gain productivity. Phase 2 moves to strategic work, using AI for insights and decision-making assistance. This provides a clear, manageable roadmap for adoption.
To get mainstream users to adopt AI, you can't ask them to learn a new workflow. The key is to integrate AI capabilities directly into the tools and processes they already use. AI should augment their current job, not feel like a separate, new task they have to perform.
Instead of focusing on AI features, understand the two mental shifts it creates for customers. It either offers a superior method for an existing, tedious task ("a better way") or it makes a previously unattainable goal achievable ("now possible"). Your product must align with one of these two thoughts.