Get your free personalized podcast brief

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

For optimal team performance, there should only be one 'non-technical builder' (L2) per team. Adding more does not increase output and often creates a 'too many chefs in the kitchen' dynamic. This L2 should be supported by a technical expert (L3) for scalability and governance.

Related Insights

The best people to build internal AI tools aren't the most technically skilled but those with deep 'company DNA.' They understand the work in an 'uncanny way' and can align AI to replicate nuanced, high-quality outcomes, often outperforming distractible 'AI excited' enthusiasts.

AI tools collapse traditional roles. Andre suggests modern teams will consist of four archetypes: a commercial person (sales/marketing), a product builder (vibe-coding solutions), a technical scaler (ensuring reliability), and an infra/security person (protecting the system).

The most effective team structure for new AI products involves a "co-founder" pairing. One person is a designer who can also build and rapidly prototype ideas. The other is a traditional software engineer who follows behind, ensuring the underlying architecture is robust and scalable, effectively "paving the trail."

To avoid chaos in AI exploration, assign roles. Designate one person as the "pilot" to actively drive new tools for a set period. Others act as "passengers"—they are engaged and informed but follow the pilot's lead. This focuses team energy and prevents conflicting efforts.

Avoid building one AI agent to do everything. Instead, create a hierarchy with a 'manager' agent that delegates tasks to specialized sub-agents (e.g., for coding, research). This prevents context overload and performance degradation, mirroring an effective human team structure for scalable automation.

A single AI agent tasked with a broad range of responsibilities will lack the necessary depth and fail, similar to a human generalist. The solution is to create a 'team' of specialized digital workers, each an expert in one area, that collaborate to complete complex tasks.

Separating AI agents into distinct roles (e.g., a technical expert and a customer-facing communicator) mirrors real-world team specializations. This allows for tailored configurations, like different 'temperature' settings for creativity versus accuracy, improving overall performance and preventing role confusion.

A single AI agent attempting multiple complex tasks produces mediocre results. The more effective paradigm is creating a team of specialized agents, each dedicated to a single task, mimicking a human team structure and avoiding context overload.

To manage innovation when non-technical staff build AI tools, form a "triad": 1) an AI super-user from the business unit, 2) a dedicated tech partner for support and governance, and 3) the practice head to decide on scalability. This structure balances speed with stability.

Contrary to traditional scaling, adding people to an early-stage AI project often slows it down. When the product concept is small enough for one or two people to hold in their heads, the cost of coordination and alignment with a larger team outweighs the benefits of more builders.

Limit AI-Enabled Teams to a Single 'Non-Technical Builder' to Avoid 'Too Many Chefs' | RiffOn