Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Sendoso found that creating a central AI team relieved employees of the pressure to self-learn AI development. This stopped "usage theater," where people felt compelled to constantly use AI to seem productive, and instead allowed them to collaborate as subject matter experts.

Related Insights

Sendoso's initial strategy of giving every employee AI tools resulted in chaos: duplicate agents, inconsistent quality, and permission issues. They reversed course, centralizing development into an "Agentic Pod" model to maintain control, quality, and strategic focus.

Instead of each employee using their own separate AI, the more effective model is a central, multiplayer AI that acts as a shared 'company brain' or teammate. This approach, which Motion is building with its 'Runneth' agent, prevents duplicated efforts and builds a shared company-wide context.

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.

Every initially gave each employee a personal AI agent but found this created a massive maintenance burden and knowledge silos. They shifted to shared agents focused on team functions (e.g., analytics). This centralizes maintenance, improves continuity when employees leave, and scales benefits across the entire team.

The process of building a custom AI agent forced Newell's teams to collaborate more closely than in traditional software rollouts. It sparked critical conversations about existing versus ideal workflows, bringing people together to solve problems and improving organizational connectivity as a positive side effect.

HubSpot's AI team progressed from individual experimentation to cross-functional pods, and finally to a centralized unit under one leader. This structural change eliminated competing priorities and coordination costs, allowing the team to commit to bigger, bolder goals and execute at a higher pace.

Initial success with AI workflows led to hundreds of unmanageable, invisible automations. Sendoso pivoted to creating role-based AI "digital colleagues" with org charts and managers, making AI implementation transparent and manageable for the human team.

Merge fosters a company-wide AI culture by not just encouraging tool usage, but making it a component of performance. They feature AI-forward employees from all departments (R&D, accounting, marketing) and provide training to ensure adoption is universal, not just siloed in engineering.

A key sign of successful AI adoption isn't a reduced workload, but an increase in the team's ambition and capacity for experimentation. By lowering the cost and time of innovation, AI empowers teams to generate and test more ideas, which is a more valuable outcome than simply doing the same work faster.

Decentralized "let a thousand flowers bloom" initiatives often result in low-impact tools and "AI performance theater." A dedicated, centralized team builds production-grade, cohesive tools that are 5-10x better, driving real organizational leverage and preventing sales reps from getting distracted from their core job.

Centralized AI Development Boosts Morale by Eliminating "Usage Theater" | RiffOn