Marketing Technology / Enterprise AI
April 2, 2026 · Shashi Bellamkonda · shashi.co
A few years ago I published research at Info-Tech Research Group on exactly this problem: marketing and IT operating in silos, each blaming the other for slow delivery, missed campaigns, and a martech stack that nobody fully owns. The research was called "From Silos to Synergy." The core argument was that no amount of tooling fixes a relationship problem between the Chief Information Officer and the Chief Marketing Officer. You have to build the partnership first.
Adobe just published a case study on Workday that reads like a worked example of that thesis. Workday's CIO Rani Johnson and CMO Emma Chalwin built a joint AI governance structure before deploying generative AI across the marketing organization. They co-sponsor technology decisions. They co-govern AI usage policies. They built three shared programs together. The technology they chose, Adobe's suite, is substantial. But the governance structure they built around it is what makes the story credible.
The Governance-First Architecture
The foundation is Adobe Real-Time Customer Data Platform, which Workday relaunched last year to unify its marketing data foundation. Layered on top is the Adobe GenStudio suite: Adobe Experience Manager for content management, Adobe Workfront for intake and approvals, Adobe Express for distributed creative production, and Adobe Firefly for generative ideation within brand guardrails.
Workfront is doing the structural work that most deployments skip: formalizing intake, production sequencing, and approval chains so that marketing and IT have shared visibility into what is actually moving through the pipeline. Without that backbone, generative AI in creative production creates faster chaos, not faster output.
The co-sponsorship structure is notable. Johnson and Chalwin jointly govern technology implementation and co-sponsor AI usage policies. They created three shared programs: Everyday AI, which gives all employees access to AI productivity tools; AI Pods, which pair business experts with engineering teams to build AI workflows; and a shared governance framework for brand safety and responsible use. That structure is harder to build than the technology it governs.
What the Numbers Actually Say
More than 90% of Workday's marketers are licensed on Adobe Express. Teams are independently producing social assets, field marketing materials, and product content using brand-curated templates without routing every request through the central creative team. The creative team reports at least 50% cost reduction and has shifted bandwidth toward higher-concept brand work.
"They remove friction so people can focus on the work that really matters, the strategic, human-centered work only people can do."
Emma Chalwin, Chief Marketing Officer, Workday
Firefly is positioned as an ideation accelerator, not a production tool. Teams explore visual direction and generate variations inside brand guidelines. The distinction matters: Workday is not replacing finished creative with AI output. It is compressing the early-stage work where most of the time-to-brief delay lives.
Where the Agentic Layer Is Actually Sitting
The forward-looking section of the case study covers Adobe Agent Orchestrator, which Adobe introduced at Summit 2025. Workday is using it for intent identification and prioritization, detecting buying groups in its target accounts, and creating agentic journeys. The case study is careful about the language here: Workday is "exploring" these capabilities and moving them "from proof of concept into production." That is honest framing. This is not a claim about a fully deployed autonomous marketing operation.
Adobe Journey Optimizer B2B Edition will extend personalization through AI-driven segmentation, connected to audience activation across Adobe Marketo Engage and LinkedIn. Automated data governance controls in the Real-Time Customer Data Platform reduce manual hygiene work, which is the kind of operational savings that rarely gets headline space but compounds over time.
The Workday-Adobe Relationship Is Not a Standard Deployment
One thing the case study makes clear, and which is easy to read past: Workday is a co-innovation partner with Adobe's product and engineering teams, not a customer running a standard deployment. Workday brings real-world business-to-business requirements directly into Adobe's development process. That relationship shapes what Workday gets access to and when, and it affects how readily this story translates to other enterprise buyers.
The Adobe Summit analyst briefings in late April will be the right moment to ask how broadly Agent Orchestrator is deployed beyond co-innovation arrangements, and what the standard implementation timeline looks like for enterprises that do not have a direct engineering relationship with Adobe.
Analyst Take
There is something in this story that the productivity metrics do not fully capture. People want to create. Most enterprise tools do the opposite: they add approval steps, constrain formats, and make simple tasks complicated. When Workday put brand-curated templates and generative AI tools into the hands of over 90% of its marketers, it was not just solving a throughput problem. It was giving people creative agency inside a governed structure. That tends to produce something beyond cost savings: it produces engagement.
The harder question, for any enterprise looking at this model, is whether the CIO-CMO relationship at their organization can actually sustain joint governance. Workday's results are not primarily an Adobe story. They are a leadership alignment story. The technology followed the partnership, not the other way around. How many enterprises are willing to build that first?
Sources
Bhambhri, Anjul. "How Workday Is Building an AI-Ready Marketing Engine with Adobe." Adobe for Business Blog, 31 Mar. 2026. business.adobe.com
Bellamkonda, Shashi. "From Silos to Synergy: Create Marketing and IT Alignment." Info-Tech Research Group, 2024. infotech.com
shashi.co · Strategy & Technology Analysis
