Concept card

BARC — Lessons from the Leading Edge: Successful Delivery of AI/GenAI

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is BARC — Lessons from the Leading Edge: Successful Delivery of AI/GenAI?

Use-case selection is the single highest-leverage decision in AI delivery — five specific criteria separate a high-probability-of-success use case from the predictable failure modes that keep sinking enterprise AI projects.

BARC's "Lessons from the Leading Edge" distills a pattern that every SAP analytics consultant now has to internalise: enterprise AI and generative AI initiatives fail far more often than they succeed, and the failure modes are neither random nor mysterious — they recur across industries, vendors, and use cases in ways that are avoidable if a delivery team knows what to check for before committing budget.

Why AI delivery fails differently from conventional software

Conventional enterprise software projects fail from familiar causes — scope creep, weak sponsorship, poor requirements. AI systems add a distinct failure surface on top of those: they degrade silently as the data distribution they were built on drifts away from the data they encounter in production, they produce confidently wrong answers (hallucination) under conditions that are difficult to anticipate at design time, and their realised value depends on a human-adoption behaviour — will the domain expert actually trust and act on the output — that project plans routinely overestimate. The gap between an impressive prototype demo and a production system that keeps delivering value six months later is wider in AI than in almost any other software category, which is exactly why understanding what separates the two is among the most commercially valuable judgment calls a consultant can offer a client.

Use-case selection as the highest-leverage decision

Why it matters

The five success criteria are concrete, not generic: bounded task with clear success criteria, sufficient historical data volume, an available domain expert evaluator, detectable/recoverable errors, and augmenting rather than replacing human judgment.
The named failure modes are equally specific: fully autonomous high-stakes decisions with no human review, sparse/unstructured/unknown-quality data, use cases chosen for technical interest rather than business impact, and success defined as "the model is accurate" instead of "the business outcome improved."
For SAP analytics specifically, strong starting use cases are named: automated narrative generation from structured financial/operational reports, intelligent search over knowledge bases, anomaly detection, and natural-language queries over governed semantic layers like Joule-on-Datasphere.

Key points

BARC research focused on actual production AI/GenAI delivery (vs. pilots).
Leading-edge sample = self-selected high-maturity organisations.
Covers both classical AI and GenAI delivery patterns.
Maps onto the Joule + Knowledge Graph delivery wave SAP customers are entering.
Specific lessons paywalled — use card to anchor the conversation, not to quote percentages.
BARC — Lessons from the Leading Edge: Successful Delivery of AI/GenAI is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.

Terms used on this page

Leading-edge sample: BARC's self-selected subsample of organisations that have shipped AI/GenAI in production — distinct from pilots. Used to extract delivery lessons that the broader market hasn't yet encountered.
Delivery model: The operating model wrapping an AI/GenAI product in production: change management, trust-building, data-quality controls, governance process, and model-lifecycle management. Separate from the ML/LLM technology itself.
GenAI: Generative AI — AI systems that produce text, code, or structured output from prompts. In the SAP context: Joule, Joule for Consultants, and BDC's embedded AI copilots.
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →