Episode 386 AI Transformation Fails Without Context: What Enterprise Leaders Need to Know
Explore more in the episode archive.
Summary
AI transformation fails when teams skip the most important ingredient: context. Host Dr. Darren welcomes Artem Koren, Chief Product Technology Officer at Sembly AI, to unpack why enterprise AI success depends on clear intent, quality standards, and better requirements—not just buying a platform. The
Why Context Is the Real AI Advantage
AI is moving fast, but enterprise success still comes down to something very human: context. Artem Koren, chief product technology officer at Sembly, argues that AI transformation fails when leaders treat it like a simple software purchase instead of an operating model shift.
That matters because most organizations are asking the wrong question. It is not “Do we have AI?” It is “Can AI produce something trustworthy, useful, and repeatable for our business?”
The Old Rules of Transformation Still Apply
Change management has not disappeared just because AI is new. Leaders still need to help teams understand what is changing, what they need to do differently, and how to move from legacy workflows to future ones.
That human side of transformation—education, support, adoption, and alignment—remains the same. What has changed is the speed, scale, and ambiguity of the technology itself.
From Functional Software to Intent Technology
Traditional software was built around clear inputs and predictable outputs. You defined a requirement, built the feature, and expected the same result every time. AI works differently.
Koren describes this as a shift from information technology to intent technology. Instead of telling software exactly what to do, leaders now describe the outcome they want and rely on AI to interpret the request.
Why “Good Enough” Needs a New Definition
That new model creates opportunity, but it also creates risk. AI can generate slides, documents, and summaries quickly, yet the output may not meet the quality bar a business actually needs.
In practice, that means enterprise teams need better requirements, clearer success criteria, and stronger governance. If a slide deck still needs two days of cleanup after generation, the tool is not saving time—it is creating expensive noise.
Key takeaways
Define the business problem before choosing the AI tool.
Set a clear quality bar for the output.
Measure repeatability, not just novelty.
Test for brand, compliance, and workflow fit.
Why Large Enterprises Struggle More
Large organizations have more tribal knowledge, more stakeholders, and more consistency requirements. That makes AI harder to deploy well, not easier. A tool that works for a small team may fail in a company where presentation style, legal language, and approval processes are tightly controlled.
Koren’s point is simple: AI needs context from the organization, not just prompts from the user. The more complex the company, the more important it becomes to bake in business context, audience expectations, and operational constraints.
The Real ROI Question
Buying Copilot, Gemini, or ChatGPT access is not the same as creating ROI. Leaders need to tie AI to a specific workflow or business outcome, then measure whether it improves speed, quality, and consistency.
That could mean faster slide creation, better customer communication, or new presentation formats altogether. The biggest opportunity may not be automating old work—it may be redesigning the work entirely.
Listen, Share, and Join the AI Augmented Movement
If your team is exploring enterprise AI, this conversation is worth your time. Listen to the full episode, share it with a colleague who owns digital transformation, and leave a comment with your biggest AI adoption challenge. You can also connect with Sembly at sembly.ai and follow the AI Augmented movement to keep the discussion going.