We scan new podcasts and send you the top 5 insights daily.
When cloud computing emerged, individual employees expensed AWS instances on corporate credit cards, resulting in unmanageable decentralization that companies later had to rein in. Stillwell explains that Pega preempted this dynamic in AI by centralizing all AI vendor requests through a cross-functional steering committee involving engineering and IT leadership, ensuring unified governance, architecture, and cost controls right from the start.
Effective AI governance starts with an "AI Council" composed of passionate users, IT, legal, and operations staff. Unlike a top-down "Center of Excellence" that dictates rules, this council's primary role is to create enabling policies and guidelines that empower grassroots adoption and safe experimentation across the organization.
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.
To ensure governance and avoid redundancy, Experian centralizes AI development. This approach treats AI as a core platform capability, allowing for the reuse of models and consistent application of standards across its global operations.
For regulated industries like banking, Boston Consulting Group and OpenAI advocate for a centralized middleware layer, or 'control plane.' This architectural component acts as a single gateway through which all AI systems must operate, enabling consistent oversight, standardized controls, and auditable governance across the entire organization.
Instead of reacting to unsanctioned tool usage, forward-thinking organizations create formal AI councils. These cross-functional groups (risk, privacy, IT, business lines) establish a proactive process for dialogue and evaluation, addressing governance issues before tools become deeply embedded.
To manage the complexity and risk of AI agents, companies should adopt a centralized model. Rather than allowing individuals to build agents freely, a dedicated internal team should build, govern, and distribute a suite of approved agents to departments, ensuring consistency and control.
To implement a cohesive AI strategy in a large organization, avoid siloed decision-making. Instead, empower a dedicated leadership pod (Product, Engineering, AI) to own the end-to-end vision. This prevents features from being diluted into a 'lowest common denominator' by committee.
Many companies successfully govern AI with small, cross-functional review boards. However, this trusted manual process becomes a bottleneck when moving from a few internal AI projects to hundreds, especially when dealing with third-party tools and generative AI.
To avoid chaotic spending, enterprises must replicate their "Cloud 2.0" governance models for AI. This means establishing a central platform engineering team to broker access to models, set budgets, and control the tools agents can use. This prevents runaway costs and security risks from decentralized AI development.
Esper's executive team preemptively created a cross-functional AI policy, appointing a coordinator while mandating that each functional leader develop their own strategy. This prevented rogue AI use and ensured a cohesive, company-wide approach instead of isolated efforts.