Brian, Brandon, and Aaron discuss enterprise AI adoption using the sales analogy of whether AI is a “vitamin” or a “painkiller,” arguing that successful transformation still requires a burning-platform event. Brandon suggests AI adoption resembles past digital transformations: without urgent pressure (e.g., a data center closing), organizations resist change and justify existing processes. Brian describes a compressed hype cycle from ChatGPT excitement to pilots and guardrails, followed by difficulties with data, cost-effective scaling, and making AI behave deterministically, while fear of competitors keeps efforts alive. They add a third category, “Whippets”, short-term, resume-driven initiatives led by leaders who leave others “holding the bag.” They debate examples like Sheetz’ multiple VMs and argue that AI’s promise is personal productivity, but note a lack of enterprise collaboration and shared-memory tools that limit organizational impact.
SHOW: 1060
SHOW TRANSCRIPT: The Enterprise AI Show #1060 Transcript
SHOW VIDEO: https://youtu.be/XZqomQosv1w
SHOW LINKS:
SHOW SPONSORS:
- Nasuni - Activate your data for AI and request a demo
- NordLayer - Use ENTERPRISE10 for 10% off.
The thesis: Successful digital transformation usually has a forcing function; you migrate the data center because the real estate got sold, not because someone promised abstract savings. Deadline + shared incentive = people actually change. AI adoption mostly lacks that: no one's forcing the migration, so it defaults to "give everyone Copilot licenses and hope."
Core question: If your business is healthy and there's no burning platform, how do you adopt AI in a way that's more than expensive theater, without a crisis to manufacture urgency?
Discussion topics:
- Forcing functions vs. vibes: What are the AI-era equivalents of "the real estate got sold"? A support team that's actually understaffed, a process with a real bottleneck, a cost center leadership is already scrutinizing vs. a mandate to "use more AI."
- The unknown-unknowns problem: Most orgs don't know which of their workflows AI would actually help vs. where it's a novelty. How do you go find that out cheaply, without a company-wide token-burning experiment as the discovery mechanism?
- Bottom-up signal vs. top-down mandate: Does real usage data (who's actually using tools, for what) surface better targets than an executive committee guessing at use cases?
- Contrast with the failed "abstract savings" migration: What does an AI initiative look like when it's tied to a concrete, already-painful problem instead of a general efficiency narrative?
- The FOMO trap: Distinguishing "we don't want to miss the platform shift" (legitimate) from "we need AI headlines for the board" (theater), and how leadership can tell which one they're actually doing.
- Measurement: If there's no forcing function, what replaces the natural deadline/incentive alignment as the way you know it's working, or that it's time to kill it?
Final Thought
Is the right move small, cheap, bounded bets against known pain points, treating AI adoption like a search problem, not a rollout, rather than a company-wide transformation initiative looking for a reason to exist?
FEEDBACK?
- Email: show @ the enterprise ai show dot com
- Bluesky: @TheEntAIShow.bsky.social
- Twitter/X: @TheEntAIShow
- Instagram: @TheEntAIShow
from The Cloudcast (.NET) https://ift.tt/Flu83Qc
via IFTTT
No comments:
Post a Comment