Coinbase held a time-boxed event where 100+ engineers used an AI tool to simultaneously submit PRs for trivial fixes. This created a transformational moment, breaking inertia, proving the tool's value, and generating massive, visible momentum for adoption across the entire organization.

Mandating AI usage can backfire by creating a threat. A better approach is to create "safe spaces" for exploration. Atlassian runs "AI builders weeks," blocking off synchronous time for cross-functional teams to tinker together. The celebrated outcome is learning, not a finished product, which removes pressure and encourages genuine experimentation.

To drive adoption, Axios's CEO gave all staff licensed AI access and a simple mandate: spend 10% of your day finding ways it can improve your specific job and share wins. This bottom-up, experimental approach fostered organic adoption and practical use cases more effectively than a top-down directive.

To truly integrate AI, go beyond simply telling your team to "learn more." The founder of Search Atlas advocates for organizing multi-day, in-person hackathons. This focused, collaborative environment, where teams tackle specific problems together, fosters a deeper and faster mastery of practical AI applications than solo, online efforts can achieve.

Webflow accelerates AI tool adoption using company-wide "Builder Days." This combines a top-down executive mandate (e.g., "no meetings without a prototype") with bottoms-up enablement, including tool access, support channels, and prizes. The goal is to move the entire organization up the adoption curve, not just early adopters.

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.

Amplitude's CEO transformed his organization not by issuing a product roadmap, but by first focusing on internal education. An "AI week" and hackathons got the engineering team using AI tools like Cursor, building belief and capability before they were tasked with creating new AI features.

For large, traditional companies, the most critical first step in AI adoption isn't building tools, but fostering deep understanding. Provide teams sandboxed access to AI models and company data, allowing them to build intuition about capabilities before crafting strategy.

A three-day AI sprint is effective for generating ideas and enthusiasm, but the real, harder work is the "marathon" that follows. Success requires a dedicated task force to prioritize projects and methodically integrate the new AI workflows into day-to-day operations—a crucial step where many corporate innovation efforts fail.