@prefix : . @prefix schema: . @prefix owl: . @prefix prov: . @prefix dcterms: . @prefix skos: . a schema:CreativeWork, schema:Article ; schema:name "Agentic AI Enablement and Budget Ownership Meshup"@en ; schema:headline "Agentic AI needs enablement capacity and explicit budget ownership"@en ; schema:description """A thesis and guidance oriented meshup connecting Darlene Newman's three AI enablement groups with Derek du Preez's enterprise budget ownership problem for agentic AI."""@en ; schema:abstract """The meshup argues that agentic AI does not scale through tool rollout or isolated flagship projects. Darlene Newman's stuck-middle enablement problem and Derek du Preez's budget-ownership problem converge on the same operating reality: enterprises need funded semantic foundations, federated capability, governance, production-grade cross-system architecture, and explicit answers to who pays, who owns risk, and where value accrues."""@en ; schema:inLanguage "en"@en ; schema:dateCreated "2026-05-28"@en ; schema:author , ; schema:publisher ; schema:isBasedOn , ; schema:about , , , , , , , , , , , ; schema:hasPart , , , , ; prov:wasGeneratedBy , . a schema:SocialMediaPosting ; schema:name "There are three kinds of AI Enablement programs happening right now"@en ; schema:url ; schema:author ; schema:description """The post separates enterprise AI enablement into a hype path based on broad tool rollout and usage metrics, funded strategic projects with real platforms and sponsorship, and a stuck middle that wants to transform work but lacks support, semantic foundations, measurable ROI, and investment."""@en ; schema:about , , , ; schema:isPartOf . a schema:NewsArticle ; schema:name "Who pays for agentic AI? The enterprise budget problem no vendor will address"@en ; schema:url ; schema:datePublished "2026-01-16T03:59:43-08:00"@en ; schema:dateModified "2026-01-16T04:20:04-08:00"@en ; schema:author ; schema:publisher ; schema:image ; schema:description """The article frames agentic AI adoption as an enterprise budget, ownership, architecture, and governance problem: data teams, application owners, and IT all want value, but funding and accountability do not map neatly to vendor architecture slides. It also highlights unresolved questions about transactional systems, data platforms, vendor control, systems of record, cross-system workflow execution, auditability, approvals, and where value ultimately accrues."""@en ; schema:about , , , , , ; schema:isPartOf . a schema:ArticleSection ; schema:name "Thesis"@en ; schema:description """Agentic AI programs fail to scale when leadership treats adoption telemetry as transformation evidence, treats a funded exception as the operating model, or accepts vendor architecture slides as an enterprise funding model. The enterprise middle needs budgeted capability, semantic work, workflow redesign, governance close to real work, and a cross-system ownership model that decides who funds agents, who controls transactional execution, who carries risk, and where value accrues."""@en ; schema:isPartOf ; schema:about , , , , , . a schema:ArticleSection ; schema:name "Notable comments"@en ; schema:description """Public comments from the LinkedIn and diginomica discussion threads reinforce the thesis by adding operating-model, workflow-governance, intake-path, data-quality, and budget-ownership constraints."""@en ; schema:isPartOf ; schema:hasPart , , , , , , , , . a schema:HowTo ; schema:name "Guidance for scaling agentic AI beyond hype and exceptions"@en ; schema:description """A practical sequence for moving from scattered agentic AI experiments toward scalable enterprise enablement."""@en ; schema:step :step1, :step2, :step3, :step4, :step5 ; schema:isPartOf . :step1 a schema:HowToStep ; schema:name "Segment the portfolio by enablement condition"@en ; schema:text "Separate broad tool adoption, funded strategic projects, and stuck-middle work domains before using one KPI model for all AI activity."@en ; schema:position "1"@en ; schema:isPartOf . :step2 a schema:HowToStep ; schema:name "Fund semantic foundations as shared product infrastructure"@en ; schema:text "Budget semantic layers, process models, data contracts, and governance as reusable enterprise infrastructure rather than as optional project overhead."@en ; schema:position "2"@en ; schema:isPartOf . :step3 a schema:HowToStep ; schema:name "Assign ownership for cross-system agent workflows"@en ; schema:text "Decide who pays, who owns risk, where approvals live, and how value accrues when agents cross data platforms and transactional applications."@en ; schema:position "3"@en ; schema:isPartOf . :step4 a schema:HowToStep ; schema:name "Build federated capability near the work"@en ; schema:text "Equip business teams to model their work, operate semantic context, redesign workflows, and build with governed platforms rather than only consume tools."@en ; schema:position "4"@en ; schema:isPartOf . :step5 a schema:HowToStep ; schema:name "Measure transformation by redesigned work"@en ; schema:text "Track cycle time, decision quality, exception handling, reuse of semantic assets, and governed workflow throughput instead of only logins, prompts, or training completion."@en ; schema:position "5"@en ; schema:isPartOf . a schema:FAQPage ; schema:name "Enterprise agentic AI enablement FAQ"@en ; schema:mainEntity , , ; schema:isPartOf . a schema:Question ; schema:name "Why is tool adoption not enough for AI transformation?"@en ; schema:acceptedAnswer . a schema:Answer ; schema:text "Tool adoption proves access and activity. Transformation requires semantic context, redesigned workflows, governance, operating ownership, and local capability to change how work gets done."@en . a schema:Question ; schema:name "What is the budget problem in agentic AI?"@en ; schema:acceptedAnswer . a schema:Answer ; schema:text "Agentic workflows cut across data platforms, systems of record, business teams, IT, security, and governance. Value may accrue in one place while cost and risk sit in another, so budget ownership must be explicit."@en . a schema:Question ; schema:name "How should enterprises unblock the stuck middle?"@en ; schema:acceptedAnswer . a schema:Answer ; schema:text "Treat the stuck middle as a portfolio of work redesign opportunities. Fund semantic foundations, create enablement pods, provide governed platforms, and measure outcomes around work changed rather than tools used."@en . a schema:DefinedTermSet ; schema:name "Glossary"@en ; schema:hasDefinedTerm , , , , ; schema:isPartOf . a schema:DefinedTerm, skos:Concept ; schema:name "Agentic AI"@en ; schema:description "AI systems designed to plan and act across tasks, tools, data, and workflows with varying degrees of autonomy."@en ; owl:sameAs . a schema:DefinedTerm, skos:Concept ; schema:name "Semantic layer"@en ; schema:description "A shared meaning layer that gives AI systems governed business context, relationships, and interpretable concepts for reasoning over work."@en ; owl:sameAs . a schema:DefinedTerm, skos:Concept ; schema:name "Stuck middle"@en ; schema:description "Business teams motivated to use AI for valuable work redesign but lacking the investment, platform support, semantic foundations, and capability needed to build."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Budget ownership"@en ; schema:description "The explicit assignment of funding, accountability, risk ownership, and value attribution for cross-functional agentic AI capability."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Vendor architecture"@en ; schema:description "The competing platform claims, roadmap assumptions, system boundaries, and control points vendors use to position agentic AI capabilities across data platforms and transactional applications."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Value accrual"@en ; schema:description "The question of which business unit, platform owner, application vendor, or enterprise function receives measurable value from agentic AI relative to who funds and governs it."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Systems of record"@en ; schema:description "Authoritative enterprise systems whose data, transactions, approvals, and audit trails become central when agentic AI crosses application and data-platform boundaries."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Governance"@en ; schema:description "Decision rights, controls, policies, auditability, and approval structures for AI-enabled workflows."@en ; owl:sameAs . a schema:DefinedTerm, skos:Concept ; schema:name "Federated capability"@en ; schema:description "AI building and operating capability distributed close to business work while remaining connected to central platforms and governance."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Operating model"@en ; schema:description "The roles, intake paths, design practices, governance routines, and platform responsibilities that let AI capability become repeatable enterprise work."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Intake path"@en ; schema:description "A governed route by which business-team automation opportunities reach a funded enablement center and return as supported AI capability."@en . a schema:DefinedTerm, skos:Concept ; schema:name "Data quality"@en ; schema:description "The fitness, reliability, interoperability, and governance of enterprise data used by AI agents and semantic layers."@en ; owl:sameAs . a schema:Comment ; schema:name "Comment by Kristine Krueger, PhD"@en ; schema:author "Kristine Krueger, PhD"@en ; schema:url ; schema:datePublished "2026-05-27T15:46:23.589Z"@en ; schema:text """AI programs stall because organizations treat enablement as training and adoption while the harder gap is workflow, decision, governance, and operating-model redesign."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "3"@en ] . a schema:Comment ; schema:name "Comment by Paul M."@en ; schema:author "Paul M."@en ; schema:url ; schema:datePublished "2026-05-27T13:33:09.172Z"@en ; schema:text """The stuck middle needs a design-table role where work becomes AI-ready workflows, decision criteria, data context, semantic definitions, and governance requirements."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "1"@en ] . a schema:Comment ; schema:name "Comment by Bernardo Guinea"@en ; schema:author "Bernardo Guinea"@en ; schema:url ; schema:datePublished "2026-05-27T17:08:51.055Z"@en ; schema:text """Broad Copilot rollout plus parallel experimentation with ChatGPT, Claude, internal platforms, agents, and governance created fragmentation rather than transformation."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "1"@en ] . a schema:Comment ; schema:name "Comment by Matt Cobby"@en ; schema:author "Matt Cobby"@en ; schema:url ; schema:datePublished "2026-05-27T22:46:48.532Z"@en ; schema:text """Some teams are already working through the hard post-rollout yards by experimenting in context, even though there is no general solution for the stuck middle yet."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "2"@en ] . a schema:Comment ; schema:name "Comment by Paul M."@en ; schema:author "Paul M."@en ; schema:url ; schema:datePublished "2026-05-27T13:33:14.419Z"@en ; schema:text """Workflow governance should define which governed resource buckets a workflow may use, which perspectives are valid, and which sources are authoritative for a decision."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "1"@en ] . a schema:Comment ; schema:name "Comment by Javier Angel Martinez Rodriguez"@en ; schema:author "Javier Angel Martinez Rodriguez"@en ; schema:url ; schema:datePublished "2026-05-28T05:24:41.666Z"@en ; schema:text """The missing middle mechanism is an intake path that moves a team's low-value work opportunity to the funded center and returns as usable capability."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "1"@en ] . a schema:Comment ; schema:name "Comment by Jon Reed"@en ; schema:author "Jon Reed"@en ; schema:url ; schema:datePublished "2026-01-16"@en ; schema:text """Agentic AI buyers who expect results without breaking down silos, upgrading older systems, and improving data platforms and quality are headed for disappointment."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "0"@en ] . a schema:Comment ; schema:name "Comment by cliveb"@en ; schema:author "cliveb"@en ; schema:url ; schema:datePublished "2026-01-16"@en ; schema:text """A concise budget-side challenge: ERP buyers may be using layoff expectations as a way to justify or fund agentic AI investment."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "0"@en ] . a schema:Comment ; schema:name "Comment by Jon Reed"@en ; schema:author "Jon Reed"@en ; schema:url ; schema:datePublished "2026-01-16"@en ; schema:text """The comment sharpens the article's ownership debate by challenging whether CRM vendors should be treated as systems of record for agentic enterprise workflows."""@en ; schema:about ; schema:isPartOf ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount "0"@en ] . a schema:Person ; schema:name "Darlene Newman"@en ; schema:url ; schema:identifier "https://www.linkedin.com/in/darlenenewman/"@en . a schema:Person ; schema:name "Derek du Preez"@en ; schema:url ; schema:identifier "https://diginomica.com/author/ddpreez"@en . a schema:Organization ; schema:name "diginomica"@en ; schema:url . a schema:SoftwareApplication ; schema:name "Microsoft Copilot"@en ; schema:url ; schema:description "Microsoft's AI assistant product family, referenced as an example of broad enterprise tool rollout."@en . a schema:SoftwareApplication ; schema:name "kg-generator skill"@en ; schema:url ; schema:description "Codex skill used to generate RDF-Turtle knowledge graphs from source material."@en . a schema:SoftwareApplication ; schema:name "rdf-infographic-skill"@en ; schema:url ; schema:description "Codex skill used to generate RDF-backed HTML and Markdown companion artifacts."@en . a schema:SoftwareApplication ; schema:name "OpenLink Virtuoso"@en ; schema:url ; schema:description "Linked Data runtime referenced for RDF publication, SPARQL querying, and resolver-backed exploration."@en .