When Nobody Owns the Outcome

A leading private bank asked us to build an AI platform that could sharpen investment decisions for its wealth management clients. We implemented a RAG architecture with vector embeddings and LLM integration, the kind of system that retrieves relevant market intelligence, reasons across portfolio context, and generates recommendations a relationship manager can act on quickly. The results during the pilot phase were strong. Recommendations were more precise. Risk flags arrived earlier. Client portfolio performance metrics moved in the right direction.

Six months after deployment, a question nobody had asked at the start became unavoidable.

When the model flags a risk and the portfolio manager does not act on it, who owns that outcome? The technology team built the model and maintained the architecture. The investment team received the recommendations and made the final calls. The risk function had signed off on the controls. Compliance had approved the process. A major wealth management firm we worked with in parallel had the same structure and the same unanswered question sitting at the center of it.

Each team owned something clearly. Nobody owned what happened to the client at the end of the chain.

We encountered the same accountability gap in a completely different sector. A large US health insurer managing tens of thousands of workers compensation claims annually asked us to centralize critical claims information across a single integrated platform. Claims owned the intake process. Risk owned the controls. Care coordination owned the claimant journey. The new platform connected all three functions in ways that had never been possible before. Yet when a claimant outcome went wrong after deployment, every function could explain their role clearly while nobody could answer a simpler question with any confidence.

Who owns the result?

This pattern appears consistently across engagements, across sectors, across geographies, and increasingly across organizations that have invested seriously in AI. It is not a technology problem. It is an organizational design problem that technology makes visible, and makes urgent, because AI does not stay in one team's lane. It moves across functions, surfaces in workflows owned by different people, and generates outputs that carry consequences for teams who never saw the model being built.

A model may be owned by one team. The data may be owned by another. The workflow may sit with operations. The controls may belong to risk. The approvals may come from compliance. The customer impact may be experienced somewhere else entirely. Everyone owns a component. Nobody owns the outcome.

This is one of the patterns Enterprise Intelligence Architecture keeps surfacing across engagements. Accountability does not fragment at the technology layer. It fragments at the boundary between functions that were never designed to share an outcome, and then AI arrives and makes that boundary problem load bearing rather than merely inconvenient.

Organizations tend to define ownership around functions because functions are easier to manage, easier to staff, easier to measure, and easier to defend in a governance review. Outcomes rarely follow those boundaries. Customers do not experience functions. Regulators do not investigate functions. Boards do not measure functions. They experience and evaluate outcomes, and when outcomes go wrong they look for someone who owns the whole thing, not the person who owned the third step in a six step process.

This connects directly to work we published with Prof. Arpan Kumar Kar at IIT Delhi at BIGS 2025. The paper examines how systems built on retrieval and reasoning introduce new actors into decision chains that traditional governance models were never designed to account for. When a system can retrieve, reason, and act with some degree of independence, responsibility does not stay fixed where it was assigned at the start of a project. It has to be actively redistributed, the same way outcome ownership has to be actively assigned when an initiative spans more functions than any single owner can see across. The investment AI platform and the claims automation platform both illustrated this redistribution problem in live production rather than in theory.

Ownership and accountability are not the same thing. Ownership can be distributed across functions, and often has to be. Accountability rarely can be. Someone has to be the person who answers for the result, not just the person who managed their piece of it.

The organizations that scale AI most effectively are often not the ones with the most sophisticated technology. They are the ones that can answer a simple question faster than everyone else.

Who owns the outcome?

As AI capabilities become distributed across technology, operations, risk, compliance, and business teams, how should organizations define accountability for outcomes that no single team fully controls?

Source: Enterprise transformation consulting engagements across BFSI and healthcare. Vikas Sharma, Senior AI and Digital Transformation Advisor | linkedin.com/in/sharma1vikas. Research referenced: "From Agentic AI to RAG: A Framework for Responsible AI," co-authored with Prof. Arpan Kumar Kar, IIT Delhi, BIGS 2025, AIS eLibrary.