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 question 'What can AI do?' is broad and overwhelming. A more practical approach is to identify existing, time-consuming tasks and ask, 'Can AI do this for me?' This reframes AI as a personal efficiency tool for specific problems, rather than a complex technology to master.

Block's CTO observes a U-shaped curve in AI adoption among engineers. The most junior engineers embrace it naturally, like digital natives. The most senior engineers are also highly eager, as they recognize the potential to automate tedious tasks they've performed countless times, freeing them up for high-level architectural work.

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.

AI tools are most readily adopted for tedious tasks engineers dislike, such as performing code reviews, fixing lint errors, and managing CI processes. This automation makes the core job of an engineer more focused on creative, high-impact work, thereby increasing job satisfaction.

To win over skeptical team members, high-level mandates are ineffective. Instead, demonstrate AI's value by building a tool that solves a personal, tedious part of their job, such as automating a weekly report they despise. This tangible, personal benefit is the fastest path to adoption.

Instead of fearing AI, design engineers should leverage it to automate boilerplate and foundational code. This frees up mental energy and time to focus on what truly matters: crafting the nuanced, high-quality interactions and animations that differentiate a product and require human creativity.

Rather than pushing for broad AI adoption, encourage hesitant individuals to identify one task they truly dislike (e.g., expenses). Applying AI to solve this specific, mundane problem demonstrates value without requiring a major shift in workflow, making adoption more palatable.

To gain organizational buy-in for AI, start by asking teams to document their most draining, repetitive daily tasks. Building agents to eliminate these specific pain points creates immediate value, generates enthusiasm, and builds internal champions for broader strategic initiatives, making it an approachable path to adoption.