<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Enablement on carney.wiki</title><link>https://carney.wiki/tags/enablement/</link><description>Recent content in Enablement on carney.wiki</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carney.wiki/tags/enablement/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI-Era Enablement Leader Is Becoming the Trust Architect</title><link>https://carney.wiki/blog/ai-enanblement-trust/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://carney.wiki/blog/ai-enanblement-trust/</guid><description>For years, sales enablement was treated as a support function.
It managed the decks.
It organized the content library.
It helped onboard sellers.
It made sure the latest messaging, battlecards, case studies, competitive notes, and training materials were available somewhere — ideally in a place the field could actually find them.
That work still matters.
But in the AI era, it is no longer enough.
As AI moves into sales workflows, CRM systems, call intelligence platforms, proposal tools, coaching systems, buyer engagement portals, and content libraries, the question is no longer simply:</description></item></channel></rss>